Saturday, October 22, 2011

ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [1433], [60] in standby database

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem:    ORA-00600: INTERNAL ERROR CODE, ARGUMENTS: [1433], [60] in standby database

 
Log files:
alert log.

Errors in file bdump/simp_rsm0_14044.trc:
Sat Sep 26 01:55:37 2009
Errors in file /bdump/simp_nsv1_14018.trc:
Sat Sep 26 01:55:39 2009
Errors in file /bdump/simp_reco_14002.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Sat Sep 26 01:55:40 2009
Errors in file /bdump/simp_reco_14002.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []

Sun Sep 27 20:00:37 2009
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Successfully opened standby log 5: '/arch/SIMP_srl0.f'
Sun Sep 27 20:00:49 2009
Fetching gap sequence in thread 1, gap sequence 34-50
Sun Sep 27 20:03:20 2009
FAL[client]: Failed to request gap sequence 
GAP - thread 1 sequence 34-50
DBID 4001809161 branch 698252856
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------
Sun Sep 27 22:05:24 2009
RFS[1]: Possible network disconnect with primary database
Redo Shipping Client Connected as PUBLIC

Solution:




Issue in standby is not able to fetch the missing files from the primary

Please make sure missing sequences are available in primary at default location.

You can also manually copy these files to standby and register them using:

SQL>ALTER DATABASE REGISTER LOGFILE '<file_name>';

e.g:

SQL>ALTER DATABASE REGISTER LOGFILE '/tmp/arc01.arc';

 



Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: