ORA-600 [kcratr_scan_lastbwr] logical bad block solution

ORA-600 [kcratr_scan_lastbwr] logical bad block solution database version: 11.2.0.3 problem phenomenon: Today when starting a test database, found that db cannot open, the ERROR is as follows: ERROR at line 1: ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [], [] solution: 1. Check alert Log Mon Jul 22 11:35:12 2013 alter database OPENBeginning crash recovery of 1 threads parallel recovery started with 3 processesStarted redo scanHex dump of (file 3, block 272) in Trace file/opt/oracle/diag/rdbms/ebai/trace/export datafile '/oracle/oradata/ebai/undotbs01.dbf' for each uption at rdba: 0x00c00110 (file 3, block 272) Reread (file 3, block 272) found same encrypt upt data (logically encrypt upt) Write verification failed for File 3 Block 272 (rdba 0xc00110) errors in file/opt/oracle/diag/rdbms/ebai/trace/ebai_ora_4930.trc (incident = 71353): ORA- 00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [] Incident details in:/opt/oracle/diag/rdbms/ebai/incident/incdir_71353/ebai_ora_4930_i71353.trcUse ADRCI or Support Workbench to package the incident. see Note 411.1 at My Oracle Support for error and packaging details. aborting crash recovery due to error 600 Errors in file/opt/oracle/diag/r Dbms/ebai/trace/ebai_ora_4930.trc: ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [], [], [] Errors in file/opt/oracle/diag/rdbms/ebai/trace/ebai_ora_4930.trc: ORA-00600: internal error code, arguments: [kcratr_scan_lastbwr], [], [], [], [], [], [], [], [], [], [], [] ORA-600 signalled during: alter database open... dumping diagnostic data I N directory = [cdmp_20130722113516], requested by (instance = 1, osid = 4930), summary = [incident = 71353]. mon Jul 22 11:36:11 2013 Sweep [inc] [71353]: completedSweep [inc2] [71353]: completed 2. You have already made it clear in the alert Log to analyze and solve the problem, in fact, you do not need to check the trace file. After a simple goole of surfing the Internet, there is a solution. Just pull it. Suse11sp2:/oracle/oraarch> sqlplus/as sysdba SQL * Plus: Release 11.2.0.3.0 Production on Mon Jul 22 14:45:49 2013 Copyright (c) 1982,201 1, Oracle. all rights reserved. connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> select status from v $ instance; STATUS--MOUNTED S QL> select open_mode from v $ database; OPEN_MODE--------------------MOUNTED SQL> recover database; Media recovery complete. SQL> alter database open; Database altered. SQL> select status from v $ instance; STATUS---open SQL> select open_mode from v $ database; OPEN_MODE--------------------READ WRITE 3, verify the processing effect to execute a clean close, and then open, not report an error, the problem is handled. SQL> alter system checkpoint; System altered. SQL> shutdown immediateDatabase closed. database dismounted. ORACLE instance shut down. SQL> startupORACLE instance started. total System Global Area 4125462528 bytesFixed Size 2234840 bytesVariable Size 956302888 bytesDatabase Buffers 3154116608 bytesRedo Buffers 12808192 bytesDatabase mounted. database opened. SQL>