FAL ARCHIVE FAILED

2009.11.01 10:39 上午 »Author: bosonmaster »
在主库有如下报错
ARCH: FAL archive failed. Archiver continuing
Sat Oct 31 16:28:37 2009
ORACLE Instance pdczh1 - Archival Error. Archiver continuing.
备库有下报错
Errors in file /u01/app/oracle/admin/dczh/udump/dczh1_rfs_15998.trc:
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
Sat Oct 31 16:31:52 2009
Errors in file /u01/app/oracle/admin/dczh/udump/dczh1_rfs_15880.trc:
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
 
METALINK 386417.1
A firewall has been added to the network between the primary and standby sites or already existsThe firewall may be Cisco-based and have a feature called 'fixup' enabled which may or may not be configured fully.
 
Database auditing may have also been enabled or is currently in use per the initialization parameter AUDIT_TRAIL.
 
CauseWhen auditing is enabled, queries or DML to the SYS.AUD$ table may trigger larger then normal TCP packetsWhen these packets go through the firewall, the 'fixup' can possibly modify the packet incorrectly and cause it to be corrupted which then breaks Oracle Net.
 
SolutionSeveral workarounds are available which must be evaluated and tested individually based on the requirements of each environment.
 
Listed with the most commonly used at the top:
 
Turn off database auditing.
 
 
If auditing must be maintained and the 'fixup' feature cannot be disabled, work with the network administrators to evaluate the MTU for the firewall and size the Oracle TCP packets to be below the current setting. The SDU/TDU settings are configured via the Oracle Net files on both primary and standbySee the References section below for related content.
 
 
Disable the 'fixup' feature and/or consult with the firewall vendor regarding patches/fixes to the feature.
 
 
Disable the firewall.

ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368]

2009.11.01 10:33 上午 »Author: bosonmaster »
在操作过程中,有如下报错
Errors in file /u01/app/oracle/admin/dczh/udump/dczh1_rfs_15830.trc:
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
Sat Oct 31 16:26:00 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 15880
RFS[4]: Identified database type as 'physical standby'
RFS[4]: Archived Log: '/arc1/2_192_691352710.dbf'
RFS[4]: Archived Log: '/arc1/2_193_691352710.dbf'
RFS[4]: Archived Log: '/arc1/2_194_691352710.dbf'
这个问题出现备库就夯筑了,在
METALINK也有下文字描述,最后只能SHUTDOWN AOBRT,产生的原因应该和12545错误有关,后来解决了12545问题,这个报错就没有出现过
The RSF process on a managed standby may raise an ORA-600 [KCRRRFSWDA.1]
or may hold onto global enqueues permanently preventing re-copying of
a log from the primary. This can happen if a problem occurs on the NET
connection between the primary and standby

Error 12545 connecting to pdczh for fetching gap sequence

2009.11.01 10:22 上午 »Author: bosonmaster »
在其恢复过程中,有如下错误,在主备设置好LOCAL_LISTENER解决,详细的看之前的文章
alter system set local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=10.18.6.184)(PORT=1521))'sid='czh1';
alter system set local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=10.18.6.185)(PORT=1521))'sid='czh2';
 
Error 12545 received logging on to the standby
FAL[client, MRP0]: Error 12545 connecting to pdczh for fetching gap sequence
Sat Oct 31 00:21:25 2009
Errors in file /u01/app/oracle/admin/dczh/bdump/dczh1_mrp0_1092.trc:
ORA-12545: Connect failed because target host or object does not exist
Sat Oct 31 00:22:05 2009
FAL[client]: Failed to request gap sequence
 
GAP - thread 2 sequence 172-172
 
DBID 742969478 branch 691352710
FAL[client]: All defined FAL servers have been attempted.

Warning: OS async I/O limit 128 is lower than recovery batch 1024

2009.11.01 10:18 上午 »Author: bosonmaster »
在启动恢复的时候,alert.log如下报错,看错误是和异步IO,有关了,检查了相关参数,发现有人忘了设置privgroup
创建 /
etc/privgroup 添加如下内容
dba MLOCK RTSCHED RTPRIO
执行如下语句使其生效
 
setprivgrp -f /etc/privgroup
设置完后,问题解决。
Warning: OS async I/O limit 128 is lower than recovery batch 1024
Sat Oct 31 00:16:25 2009
Errors in file /u01/app/oracle/admin/dczh/bdump/dczh1_ora_1134.trc:
Sat Oct 31 00:16:25 2009
Warning: OS async I/O limit 128 is lower than recovery batch 1024
Sat Oct 31 00:16:25 2009
Warning: OS async I/O limit 128 is lower than recovery batch 1024
Sat Oct 31 00:16:25 2009
Errors in file /u01/app/oracle/admin/dczh/bdump/dczh1_ora_1136.trc:
Sat Oct 31 00:16:25 2009
Warning: OS async I/O limit 128 is lower than recovery batch 1024
Sat Oct 31 00:16:25 2009
Waiting for all non-current ORLs to be archived...

standby ora-00367 ora-19567

2009.11.01 10:08 上午 »Author: bosonmaster »
DATAGURAD之前也就是自己玩过一两次,这次实施的时候遇到的问题也不少。
在启动备库恢复的时候,
ALERT.LOG里如下错误:
Errors in file /u01/app/oracle/admin/dczh/bdump/dczh1_mrp0_1092.trc:
ORA-00367: checksum error in log file header
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: '/dev/vgora/rlvol_redo1_11_512'
Clearing online redo logfile 1 /dev/vgora/rlvol_redo1_11_512
Clearing online log 1 of thread 1 sequence number 1347
Sat Oct 31 00:16:25 2009
Errors in file /u01/app/oracle/admin/dczh/bdump/dczh1_mrp0_1092.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/dev/vgora/rlvol_redo1_11_512'
Clearing online redo logfile 1 complete
 
经查询
METALINK:352879.1文档,设置参数log_file_name_convert,不管你主库和备库是否一致,都要设置,我设置以后问题解决
 
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.7
This problem can occur on any platform.
This issue is seen starting in release 10gR2
Symptoms
Upon starting the Managed Recovery Process in a Standby Database the following Errors may be seen
 
Thu Oct 27 09:41:47 2005
Attempt to start background Managed Standby Recovery process (ora)
MRP0 started with pid=47, OS id=32094
Thu Oct 27 09:41:47 2005
MRP0: Background Managed Standby Recovery process started (ora)
Managed Standby Recovery not using Real Time Apply
Thu Oct 27 09:41:52 2005
Errors in file /app/oracle/admin/ora/bdump/ora_mrp0_32094.trc:
ORA-00313open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/oradata/ora/ora_rdo01c.log'
ORA-27037: unable to obtain file  status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/oradata/ora/ora_rdo01b.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
 
If the files are created then you may then receive the following errors
 
 
Thu  Oct 27 09:41:52 2005
Errors in file /app/oracle/admin/ora/bdump/ora_mrp0_32094.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/ora01/oradata/ora/ora_rdo01a.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 55
Thu Oct 27 09:41:53 2005
Completed: alter database recover managed standby database disconnect from
session.
 
 
You may also see following messages on MRP startup even with log_file_name_convert parameter set
 
 
ORA-00312: online log 11 thread 2: '+ARCH_1/p2brp_dr/onlinelog/group_11.285.609666683'
ORA-17503: ksfdopn:2 Failed to open file +ARCH_1/p2brp_dr/onlinelog/group_11.285.609666683
ORA-15012: ASM file '+arch_1.285.609666683' does not exist
ORA-00312: online log 11 thread 2: '+DATA_1/p2brp_dr/onlinelog/group_11.299.609666681'
ORA-17503: ksfdopn:2 Failed to open file +DATA_1/p2brp_dr/onlinelog/group_11.299.609666681
ORA-15012: ASM file '+data_1.299.609666681' does not exist
 
 
 
 
 
 
 
Cause
This is in fact an Enhancement to the Data Guard Technology introduced in 10.2.0.
 
The Goal here is to improve speed of Switchover and Failover. In previous Versions a Role Transition would require to clear the Online Redo Logfiles before it can become a Primary DatabaseNow we attempt to clear the Online Redo Logfiles when starting Managed Recovery.
 
If the Files exist then they will be cleared, but if they do not exist we report the Error, attempts to create the Online Redo Logfiles and starts Recovery. Even if this is not possible because of different Structure and log_file_name_convert is not set, MRP does not fail; it only raises these Errors.
 
As an extra Enhancement if the Online Redologs do exist you must specify the log_file_name_convert Parameter even if there is no difference in the Name. This has been implemented to reduce the chances that the Primary Online Redologs are cleared when MRP startsIt is the equivalent of asking - Are you sure you want the logs to be called this....
 
If the log_file_name_convert parameter is not set then the ORA-19527 is reported and the log file is not cleared at this time..
 
Solution
Solution to stop both of these errors is to ensure log_file_name_convert is set correctly.