ORACLE error 1033 and ORA-00600 error Solution

This error often occurs in Oracle data after an illegal shutdown:

EXP-00056: ORACLE error 1033 appears
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, but 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.

You can see the last few lines

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

 

You don't need to study the meaning of this error. The solution is as follows:

 

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> sqlplus

SQL * 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-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 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 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo 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 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo 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;

 

 

Bytes --------------------------------------------------------------------------------------------------------------------

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 \ 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 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;