ORACLE troubleshooting with error 1033 and error ORA-00600

This error is often returned when an Oracle database is shut down illegally:

EXP-00056: ORACLE error 1033 ORA-01033: ORACLE initialization or shutdown in progress User: password:

This is obviously because the database cannot be started, but the database service can still be started, while the program cannot connect to the database.

The first choice is to find the problem. Check the specific error message of the ALERT file under the BDUMP directory of the database.

In the last few lines, you will see:

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

This error does not need to be studied in detail. The following is a solution to this problem:

Oracle9/10g startup error ORA-00600: Internal error code, parameter: [kcratr1_lostwrt], [], [], [], [], [], [], [], []

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

C: \ Documents ents and Settings \ Administrator> sqlplusSQL * Plus: Release 9.2.0.1.0-Production on Sunday May 13 09:23:23 2007 Copyright (c) 1982,200 2, Oracle Corporation. All rights reserved.

Enter the username:/as sysdba

Connect:

Oracle9i Enterprise Edition Release 9.2.0.1.0 - ProductionWith the Partitioning, OLAP and Oracle Data Mining optionsJServer Release 9.2.0.1.0 - Production

SQL> startup

ORA-01081: unable to start ORACLE that is already running --- Close first

SQL> shutdown abort

The ORACLE routine has been disabled.

SQL> startup

The ORACLE routine has been started.

Total System Global Area 135338868 bytesFixed Size 453492 bytesVariable Size 109051904 bytesDatabase Buffers 25165824 bytesRedo Buffers 667648 bytes

The database has been loaded.
ORA-00600: Internal error code, parameter: [kcratr1_lostwrt], [], [], [], [], [], [], [], []

SQL> shutdown immediate

ORA-01109: the database is not open

The database has been detached.

The ORACLE routine has been disabled.

SQL> startup mount

The ORACLE routine has been started.

Total System Global Area 135338868 bytesFixed Size 453492 bytesVariable Size 109051904 bytesDatabase Buffers 25165824 bytesRedo Buffers 667648 bytes

The database has been loaded.

SQL> recover database;

Media recovery is completed.

SQL> alter database open;

The database has been changed.

SQL>exit;

By the way, the roles of several adump, bdump, cdump, dpdump, pfile, and udump directories in Oracle are as follows:

audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMPbackground_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMPuser_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMPcore_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP

You can see from the above:

Adump: Audit information
Bdump: trace and alert log of background processes, that is, alert_sid.log also exists in this directory.
Cdump: core trace, which is generally used to log applications. Unless a problem occurs in the database, there is basically no information.
Dpdump: stores some logon information.
Pfile: Initialize the parameter file initSID
Udump: the trace file of the session after the SQL trace is manually traced at the front end.
Bdump contains the alert file and trace file of some background processes.
In udump, the trace file of the session after SQL trace is generally placed.
Cdump generally stores some core trace files

Wangfl

Adump is generally audit dump
Bdump is a background dump.
Udump is user dump.
Cdump is core dump.

show parameter background_dump_dest;