Oracle 尝试启动数据库时ORA-16014 ORA-00312

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 ： 13764045638 QQ号:47079569 邮箱：service@parnassusdata.com

[oracle@ocm_rac01 ~]$ oerr ora 16014
16014, 00000, "log %s sequence# %s not archived, no available destinations"
// *Cause:  An attempt was made to archive the named log, but the archive was 
//          unsuccessful. The archival failed because there were no archive log
//          destinations specified, or all destinations are in an error state.
// *Action: Verify that archive log destinations are specified or
//          take the necessary step to correct any errors that may have
//          occurred.
[oracle@ocm_rac01 ~]$ oerr ora 00312
00312, 00000, "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.

适用于:

Oracle Database – Enterprise Edition – Version 11.1.0.6 及以上
本文信息适用于任何平台。

症状

++ DB 当前在mount阶段，同时OPEN 模式启动遇到ORA-03113:

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 20052
Session ID: 661 Serial number: 5

++ When going through alert log we see DB terminating due to archival issue

Errors in file /opt/oracle/app/oracle/diag/rdbms/stbydb3/stbydb3/trace/stbydb3_ora_47516.trc:
ORA-16014: log 1 sequence# 1 not archived, no available destinations
ORA-00312: online log 1 thread 1: ‘/u02/oradata/stbydb3/redo01.log’
Wed Mar 02 17:28:23 2016
ARC1 started with pid=21, OS id=47526
USER (ospid: 47516): terminating the instance due to error 16014
System state dump requested by (instance=1, osid=47516), summary=[abnormal instance termination].

++ 问题日志是遇到归档时数据库LSTBYDB3本身的一部分

LOG FILE #1:
name #3: /u02/oradata/stbydb3/redo01.log
Thread 1 redo log links: forward: 2 backward: 0
siz: 0x19000 seq: 0x00000001 hws: 0x4 bsz: 512 nab: 0x53 flg: 0x0 dup: 1
Archive links: fwrd: 2 back: 0 Prev scn: 0x0000.00000000
Low scn: 0x0002.4574ba13 03/01/2016 14:29:46
Next scn: 0x0002.4574bb46 03/01/2016 14:29:55
FILE HEADER:
Compatibility Vsn = 186646528=0xb200000
Db ID=3146476263=0xbb8b6ae7, Db Name=’LSTBYDB3′
Activation ID=3146466297=0xbb8b43f9
Control Seq=905350111=0x35f68bdf, File size=102400=0x19000
File Number=1, Blksiz=512, File Type=2 LOG
Format ID is 2
redo log key is 894a8dc04d6d24cf3581f60492a7aef
redo log key flag is 5
descrip:”Thread 0001, Seq# 0000000001, SCN 0x00024574ba13-0x00024574bb46″

原因

本地归档的配置(这里是log_archive_dest_1 )错误地指向不同的db_unique_name “lstbydb3” 而实际上它是stbydb3

log_archive_dest_1=’LOCATION=/u02/archs/stbydb3/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=lstbydb3′

..
db_name = “lstbydb3”
db_unique_name = “stbydb3”

解决方案

连接到SQL*Plus，更正在”log_archive_dest_1″上的”db_unique_name” 参数并尝试打开 DB

alter system set log_archive_dest_1=”LOCATION=/u02/archs/stbydb3/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stbydb3″;
alter database open;