Solution to Error 1033 and Error ORA 00600 in ORACLE

This error often occurs in the Oracle database after an illegal shutdown:

EXP-00056:ORACLE Errors 1033 Appear 
ORA-01033 : ORACLE initialization or shutdown in progress
 Users: 
 Password: 

Obviously, the database can't be started, but the database service can still be started, and the program can't connect to the database.

The first choice to find a problem to see the database BDUMP directory ALERT file specific report what error

In the last few lines, you will see:

Error reporting ORA-00600: Internal error code, parameters: [kcratr1_lostwrt], [], [], [], [], [], [], []

There is no need to study what this mistake means. Here are some ways to solve this problem:

oracle9/10g startup Error ORA-00600: Internal Error Code, Parameters: [kcratr1_lostwrt], [], [], [], [], [], [], []

The reason may be caused by illegal shutdown or power failure. Here are the problems and solutions:

C:\Documents and Settings\Administrator>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on  Sunday  5 Month  13 09:23:23 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Please enter a user name:/as sysdba

Connect to:

Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production

SQL> startup

ORA-01081: Unable to start ORACLE already running--Please close first

SQL> shutdown abort

The ORACLE routine has been closed.

SQL> startup

The ORACLE routine has started.

Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes

The database is loaded.
ORA-00600: Internal error code, parameters: [kcratr1_lostwrt], [], [], [], [], [], [], []

SQL> shutdown immediate

ORA-01109: Database not open

The database has been uninstalled.

The ORACLE routine has been closed.

SQL> startup mount

The ORACLE routine has started.

Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes

The database is loaded.

C:\Documents and Settings\Administrator>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on  Sunday  5 Month  13 09:23:23 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

0

Complete media recovery.

C:\Documents and Settings\Administrator>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on  Sunday  5 Month  13 09:23:23 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

1

The database has changed.

C:\Documents and Settings\Administrator>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on  Sunday  5 Month  13 09:23:23 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

2

By the way, the functions of several adump, bdump, cdump, dpdump, pfile and udump directories under Oracle:

audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP

You can know from the above:

adump: Audit information
bdump: The daemons trace and alert log, meaning alert_sid. log also exist in this directory
cdump: core trace, 1 is generally used to log applications unless there is something wrong with the database, there is basically no information
dpdump: Is to store some login information
pfile: Initialize parameter file initSID
udump: trace file for session after sql and trace for foreground manual trace
There are alert files in bdump, and trace file of some daemons
trace file of session after sql and trace in udump
cdump1 Place 1 core trace files like cdump1

wangfl

adump1 is like audit dump
bdump is background dump
udump is user dump
cdump is core dump

C:\Documents and Settings\Administrator>sqlplus
SQL*Plus: Release 9.2.0.1.0 - Production on  Sunday  5 Month  13 09:23:23 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

4