Error :
=====
ORA-00600: internal error code, arguments: [krr_init_lbufs_1], [74]
Scenario:
=======
When we are applying the archives for recovering the database in the middle of a recovery we face this error after applying some of the archvies.
ORA-00279: change 568074198 generated at 03/13/2009 10:47:27 needed for thread 1
ORA-00289: suggestion :
/u02test/archivelogs/archivelog_test_1_2684_655528279.log
ORA-00280: change 556095143 for thread 1 is in sequence #2834
ORA-00278: log file '/u02test/archivelogs/
archivelog_test_1_2684_655528279.log'
no longer needed for this recovery
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [krr_init_lbufs_1], [74],[66],[43], [], [], [], [], [], [], [], []
ORA-01112: media recovery not started
Only 1 hit in metalink but fortunately a documented bypass ( from bug 7373196 evidently ).
Solution :
========
Bug in 64 bit 11.1.0.7 ...
Shut down the instance
Add the following parameter in pfile
_max_io_size=4194304
Now mount the same and start the recovery.
=====
ORA-00600: internal error code, arguments: [krr_init_lbufs_1], [74]
Scenario:
=======
When we are applying the archives for recovering the database in the middle of a recovery we face this error after applying some of the archvies.
ORA-00279: change 568074198 generated at 03/13/2009 10:47:27 needed for thread 1
ORA-00289: suggestion :
/u02test/archivelogs/archivelog_test_1_2684_655528279.log
ORA-00280: change 556095143 for thread 1 is in sequence #2834
ORA-00278: log file '/u02test/archivelogs/
archivelog_test_1_2684_655528279.log'
no longer needed for this recovery
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [krr_init_lbufs_1], [74],[66],[43], [], [], [], [], [], [], [], []
ORA-01112: media recovery not started
Only 1 hit in metalink but fortunately a documented bypass ( from bug 7373196 evidently ).
Solution :
========
Bug in 64 bit 11.1.0.7 ...
Shut down the instance
Add the following parameter in pfile
_max_io_size=4194304
Now mount the same and start the recovery.
No comments:
Post a Comment