Oracle database failed to start, error terminating the instance due to error 16014

Objective:

Morning to work, development to inform the database connection is not, say is reported memory overflow, check memory free space is really insufficient, then will high memory process end, but after the end is not connected, restart the database, tragedy occurred, the database actually Kai not come, because the day before changed the next Dastart file, has been a file change problem, But after using Sqlpuls/as nolog login Conn/as sysdba Connection data again startup is Qibulai.

Previously did not contact the Oracle database, want to find the error log, see if there are errors, the results of a meal to find, also did not find the error log where, but later found a boot log/oracle/app/oracle/diag/rdbms/orcl/orcl/alert/ Log.xml, a terminal monitoring this log problem, another terminal startup, the log side of the rolling, rolling a lot, the key in the last few lines, error a bug, and Error Record file/oracle/app/oracle/diag/rdbms/orcl/ ORCL/TRACE/ORCL_ORA_6319.TRC, the contents are as follows

MODULE Name: ([email protected] (TNS v1-v3)) 2015-09-17 11:17:30.014*** ACTION Name: () 2015-09-17 11:17:30.014 Dde:pro Blem Key ' ORA 312 ' was flood controlled (0x1) (no incident) Ora-00312:online log 2 thread 1: '/oracle/app/oracle/oradata/o Rcl/redo02.log ' Ora-16014:log 2 sequence# 419 not archived, no available destinationsora-00312:online log 2 thread 1: '/O Racle/app/oracle/oradata/orcl/redo02.log ' * * * 2015-09-17 11:17:30.014user (ospid:6319): Terminating the instance due to Error 16014

The confirmation error is

Terminating the instance due to error 16014

According to this error Baidu out a few solutions, and I have a similar situation, see this title scare me, thought hopeless, but fortunately, this is a test machine

The path to the Oracle error log was also unexpectedly discovered here

Original address: http://www.itpub.net/thread-1604189-1-1.html

Sqlplus /nologsql*plus: release 11.2.0.3.0 production on fri apr 20  10:35:15 2012Copyright  (c)  1982, 2011, Oracle.  All rights  Reserved. Sql> conn /as sysdbaconnected to an idle instance. Sql> startuporacle instance started. total system global area  417546240 bytesfixed size                   2228944 bytesvariable  Size             339742000  bytesdatabase buffers           67108864  bytesredo buffers                 8466432 bytesdatabase mounted. Ora-03113: end-of-file on communication channelprocess id: 2558session id: 125 serial number: 5[[ Email protected] ~]$ tail -f /u01/app/oracle/diag/rdbms/dg1/dg/trace/alert_ dg.logerrors in file /u01/app/oracle/diag/rdbms/dg1/dg/trace/dg_ora_2743.trc:ora-16014:  log 1 sequence# 63 not archived, no available destinationsora-00312:  online log 1 thread 1:  '/u01/app/oracle/oradata/dg/redo01.log ' user  (ospid:  2743): terminating the instance due to error 16014fri apr  20 10:45:37 2012system state dump requested by  (instance=1, osid=2743) ,  summary=[abnormal instance termination]. System state dumped to trace file /u01/app/oracle/diag/rdbms/dg1/dg/trace/dg_ diag_2699.trcdumping diagnostic data in directory=[cdmp_20120420104537], requested by  (instance=1, osid=2743), summary=[abnormal instance  Termination]. instance terminated by user, pid = 2743

I was trying to do it the day before. The Oracle archive mode was turned on when the data backup was exported, but the data export has been error Tns:could not resolve the Connect identifier S, Baidu is said to be the environment variable problem, but my environment variables have , and for a day I don't know why

See the problem and reason description, think it should be the problem of archiving, followed by the operation to close the archive mode

Sqlplus /nologsql*plus: release 11.2.0.3.0 production on fri apr 20  10:49:26 2012Copyright  (c)  1982, 2011, Oracle.  All rights  Reserved. Sql> conn /as sysdbaconnected to an idle instance. Sql> startup mountoracle instance started. total system global area  417546240 bytesfixed size                   2228944 bytesvariable  Size             339742000  bytesdatabase buffers           67108864  bytesredo buffers                 8466432 bytesdatabase mounted. Sql> alter database&nBsp;noarchivelog;database altered. Sql> alter database open;database altered. sql> archive log list;database log mode               No Archive ModeAutomatic archival              DisabledArchive destination             /u01/app/oracle/standbylogoldest online log  sequence     64Current log sequence            66

Turn on Archive mode again (this step is not yet operational, this is a convenient post-operation lookup)

Shutdown immediatedatabase closed. Database dismounted. Oracle instance shut down. Sql> startup mountoracle instance started. total system global area  417546240 bytesfixed size                   2228944 bytesvariable  Size             339742000  bytesdatabase buffers           67108864  bytesredo buffers                 8466432 bytesdatabase mounted. Sql> alter database archivelog;database altered. Sql> alter database open;database altered. sql> archive log list;database log mode              archive modeautomatic archival              EnabledArchive destination             /u01/app/oracle/standbylogoldest online log  sequence     64Next log sequence to archive    66current log sequence           66 as OK , there is no problem that the previous 63 logs could not be archived, but this must mean losing data in the production library! Continue to query the repository, found that the log only to 62, after the log can not be passed again, depressed, data loss first regardless, because it is a test library, but at least DG is to rebuild, tragedy! sql> select open_mode,database_role,db_unique_name from v$database;open_mode             database_role    db_ Unique_name-------------------- ---------------- ------------------------------read only              physical standby dg2sql> select dest_id,applied,sequence#  from v$archived_log where sequence# > 58 and dest_id=2;    dest_id applied    sequence#---------- --------- ----------          2 YES                59         2  YES               60          2 NO                 61         2  NO                 62 This thing to my summary is, or do not use broker switch, even if used, do not cut so fast, slowly! It's a bad day!

Oracle database failed to start, error terminating the instance due to error 16014