ORA-00322, ORA-00312: At Startup [ID 1016968.102]

最新推荐文章于 2023-04-17 23:04:18 发布

cuilian2013

最新推荐文章于 2023-04-17 23:04:18 发布

阅读量198

点赞数

文章标签：数据库

ORA-00322, ORA-00312: At Startup [ID 1016968.102]

Problem Description: ==================== You have a media failure, which causes the database to crash. Problem Explanation: ==================== At startup, the database will mount, but gives the following errors at open: ORA-00312: "online log %s thread %s: '%s'" Cause: This message reports the filename for details of another message. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. ORA-00322: "log %s of thread %s is not current copy" Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup. Action: Restore correct file or reset logs. Search Words: ============= Hardware, recover Solution Description: ===================== First check that ORACLE_HOME and ORACLE_SID are set correctly, and if not, do so and re-start. Else, continue as follows. Recover the loss of an inactive, online redo log group. ALTER DATABASE CLEAR LOGFILE 'filename'; If there is more than one LOGFILE in the redo log group then you must specify all the log files. For example, the following fails: SVRMGR> alter database clear logfile '/vobs/oracle/dbs/log3.log'; alter database clear logfile '/vobs/oracle/dbs/log3.log' * ORA-1514: error in log specification: no such log ORA-1517: log member: '/vobs/oracle/dbs/log3.log But, specifying all the log files in the group works: SVRMGR> ALTER DATABASE CLEAR LOGFILE ('/vobs/oracle/dbs/t4.log','/vobs/oracle/; Statement processed. For more information Ref: Bug:763186 Dropping and recreating group also could be other alternative, 1) alter database drop logfile group 4; 2) recreate the group, and give it a new name: Eg: alter database add logfile group 4 ('/opt/app/oracle/FRA/DB102/onlinelog/redo04a.rdo','/opt/app/oracle/FRA/DB102/onlinelog/redo04b.rdo') size 50m; Solution Explanation: ===================== The database, at open, does a check of log file headers and found an online log that appears to be an incorrected restored file. In this case it was not incorrect, but inactive. By issuing the clear logfile, you can avoid going through an uneccessary open resetlogs when applicable.