I find that there is a ora-16401 error in oracle of alert.log after switchover primary to physical standby.
alert.log:
Fri Jul 03 09:57:08 2009
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 121 (4)
Fri Jul 03 09:57:24 2009
ksvcreate: Process(m000) creation failed
Fri Jul 03 09:57:46 2009
RFS[1]: Archivelog thread 1 sequence 121 cannot be reused
Fri Jul 03 09:57:46 2009
Errors in file d:\oracle\product\10.2.0\admin\primary\udump\primary_rfs_1040.trc:
ORA-16401: RFS 拒绝了归档日志
Analyst:
I try to disable log_archive_dest_2 in the new standby (the old primary),but this error occurs again.
I select the table of v$archive_dest,the following highlights:
1 LOG_ARCHIVE_DEST_1 VALID OPTIONAL SYSTEM LOCAL ARCH ACTIVE +PRIMARY/primary/
2 LOG_ARCHIVE_DEST_2 VALID OPTIONAL SYSTEM REMOTE LGWR PENDING (DESCRIPTION=(ADDRESS_LI
11 STANDBY_ARCHIVE_DEST VALID OPTIONAL SYSTEM LOCAL ARCH ACTIVE D:\oracle\product\10.2.
Although now the results show standby_archive_dest is optional and the arhived path is different from log_archive_dest_1, the ora-16401 errors occurs again.
Solution:
SQL> alter system reset standby_archive_dest scope=spfile sid='primary';
系统已更改。
SQL> shutdown immediate
数据库已经关闭。
已经卸载数据库。
ORACLE 例程已经关闭。
SQL> startup mount
ORACLE 例程已经启动。
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 218106756 bytes
Database Buffers 385875968 bytes
Redo Buffers 7135232 bytes
数据库装载完毕。
SQL> show parameter standby
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
standby_archive_dest string LOCATION=D:\oracle\product\10.
standby_file_management string AUTO
SQL> select * from v$archive_dest;
DEST_ID DEST_NAME STATUS BINDING NAME_SP TARGET ARCHIVER SCHEDULE DESTINATION
---------- -------------------- --------- --------- ------- ------- ---------- -------- ------------
1 LOG_ARCHIVE_DEST_1 VALID OPTIONAL SYSTEM LOCAL ARCH ACTIVE +PRIMARY/primary/
2 LOG_ARCHIVE_DEST_2 VALID OPTIONAL SYSTEM REMOTE LGWR PENDING (DESCRIPTION=(ADDRESS_LI
3 LOG_ARCHIVE_DEST_3 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
4 LOG_ARCHIVE_DEST_4 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
5 LOG_ARCHIVE_DEST_5 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
6 LOG_ARCHIVE_DEST_6 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
7 LOG_ARCHIVE_DEST_7 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
8 LOG_ARCHIVE_DEST_8 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
9 LOG_ARCHIVE_DEST_9 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
10 LOG_ARCHIVE_DEST_10 INACTIVE OPTIONAL SYSTEM LOCAL ARCH INACTIVE
11 STANDBY_ARCHIVE_DEST VALID MANDATORY SYSTEM LOCAL ARCH ACTIVE USE_DB_RECOVERY_FILE_DE
已选择11行。
Finding that standby_archive_dest change to USE_DB_RECOVERY_FILE_DEST
checking alert.log:
MRP0 started with pid=14, OS id=5264
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 122
Fri Jul 03 15:04:19 2009
Completed: alter database recover managed standby database disconnect from session
Fri Jul 03 15:05:12 2009
idle dispatcher 'D000' terminated, pid = (14, 2)
That errors does not show in alert.log.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/175005/viewspace-608250/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/175005/viewspace-608250/