 Posted 9/8/2009 3:57:18 PM
|
|
|
|
Ora Error : ORA-16401: archivelog rejected by RFS
Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database.
Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes.ORA-16401 may be signalled incorrectly due to existence of
a remote entry, but not a local one. (RFS rejects the log)
Workaround:
Manually register the log entry using "register or replace"
option from the primary (alter database register or replace logfile ..) This is related to a bug.
Here is something that I came across regarding RAC and this error message: Instance crashed after the following error in the alert log file:
ORA-16401: archivelog rejected by RFS
SUCCESS: diskgroup ARCH was dismounted
Thu Jul 30 04:04:38 2009
Errors in file /u01/oracle/admin/prod/bdump/prod_lms1_12658.trc:
ORA-00600: internal error code, arguments: [504], [0x060011DA8], [80], [6], [mostly latch-free
SCN], [0], [0], [0x06000F408]
Thu Jul 30 04:04:40 2009
Errors in file /u01/oracle/admin/prod/bdump/prod_lms1_12658.trc:
ORA-00600: internal error code, arguments: [600], [], [], [], [], [], [], []
In the trace file:
----- Call Stack Trace -----
ksl_level_check kslgetl kcsadj1 kcmclscn ksxpwait kslwaitns kskthbwt kslwait kmgs_sleep_wait
kmgs_create_request kmgs_immediate_req ksmasg kghnospc kghalo ksmdacnk ksmdget kjbrextend
kjbralc kjbopen kclexpand kclobj kclaoliter
CauseThe cause of this problem has been identified and verified in an unpublished Bug 4466106:
the ORA-600 [504] [mostly latch-free SCN] can occur on some platforms in a RAC environment. Trace
files for the ORA-600 [504] will show the failing process holding one of the latches below at level 6:
KJC message pool free list
gcs opaque info freelist
gcs resource freelist
gcs shadows freelist
Also Bug 4997495 reports the ORA-600 [504] [mostly latch-free SCN] where the failing process hold other latches:
name-service request queue
name-service pending queue
name-service namespace bucket
name-service memory objects
name-service namespace objects
name-service request
Solution1. apply oneoff Patch 4466106 on top of 10.2.0.1 release if available for your platform
2. or apply 10.2.0.3 patchset where Bug 4997495 is fixed and then request the oneoff patch for
the unpublished Bug 4466106 (as fixed in 11.1.0.6).
3. or upgrade to 11.1.0.6 release where both bugs are fixed.
|
|
|
|