i use https://hub.docker.com/r/jaspeen/oracle-11g/ image restore db dump file. after commit , run image wait 20 minutes when db open:
sql> select status v$instance; status ------------ mounted after 20 minutes
sql> select status v$instance; status ------------ open entrypoint.sh log:
sqlplus: database mounted. alertlog: successful mount of redo thread 1, mount id 1430168652 alertlog: database mounted in exclusive mode alertlog: lost write protection disabled alertlog: completed: alter database mount alertlog: fri jan 29 05:49:06 2016 alertlog: alter database open listener: 29-jan-2016 05:49:06 * service_update * orcl * 0 listener: fri jan 29 05:49:29 2016 listener: 29-jan-2016 05:49:29 * (connect_data=(sid=orcl)(cid=(program=sqlplus64)(host=ubuntu)(user=user))) * (address=(protocol=tcp)(host=10.196.5.92)(port=43917)) * establish * orcl * 0 database mounted in exclusive modelistener: fri jan 29 05:56:42 2016 listener: 29-jan-2016 05:56:42 * (connect_data=(sid=orcl)(cid=(program=sqlplus64)(host=ubuntu)(user=user))) * (address=(protocol=tcp)(host=10.196.5.92)(port=43925)) * establish * orcl * 0 alertlog: fri jan 29 06:04:18 2016 alertlog: errors in file /opt/oracle/app/diag/rdbms/orcl/orcl/trace/orcl_m000_86.trc: alertlog: ora-01155: database being opened, closed, mounted or dismounted listener: fri jan 29 06:06:33 2016 listener: 29-jan-2016 06:06:33 * (connect_data=(sid=orcl)(cid=(program=sqlplus64)(host=ubuntu)(user=user))) * (address=(protocol=tcp)(host=10.196.5.92)(port=43935)) * establish * orcl * 0 listener: fri jan 29 06:09:09 2016 listener: 29-jan-2016 06:09:08 * service_update * orcl * 0 alertlog: fri jan 29 06:11:14 2016 alertlog: thread 1 opened @ log sequence 41 alertlog: current log# 2 seq# 41 mem# 0: /opt/oracle/app/oradata/orcl/redo02.log alertlog: successful open of redo thread 1 alertlog: fri jan 29 06:11:14 2016 why long starded?
db_recovery_file_dest_size of 3882 mb 0.00% used. alertlog: user-specified limit on amount of space used alertlog: database recovery-related files, , not reflect amount of alertlog: space available in underlying filesystem or asm diskgroup. may every time start recovery db? how avoid it?
we decide use zfs on iscsi db snapshot prod server. startup db in 1 minutes.
Comments
Post a Comment