When i try to connect the database this message appear to me :

ORA-01033: ORACLE initialization or shutdown in progress
then i write these commands:

SQL> shutdown immediate;
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.

Total System Global Area 1577058304 bytes
Fixed Size 1291948 bytes
Variable Size 587204948 bytes
Database Buffers 981467136 bytes
Redo Buffers 7094272 bytes
Database mounted.
ORA-00600: internal error code, arguments: kcratr1_lastbwr], [, ], [, [],
], [, []

so what the solution for this problem.

try to recover database manually with these commands:

SQL> startup mount;
SQL> recover database;
SQL> alter database open;

هذه هي النتيجة

SQL> RECOVER DATABASE;
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 1536 change 29601742 time 04/27/2009
22:14:17
ORA-00312: online log 3 thread 1:
'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORAC\REDO03.LOG'

use alter database open resetlogs; instead of alter database open;

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery

وطبعاً المشكلة أصلاً في أمر الــRecover

تم تعديل 28 أبريل 200916 سنة بواسطة islamic_boy600

To fix the issue, you can follow this action plan and upload the results :

1. Mount Database
2. Modify in ur spfile/or Pfile disable_logging parameter = false;
3. drop the corrupted redologfiles/loggroups and create new redologfiles/loggroups;

ALTER DATABASE DROP LOGFILE MEMBER 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORAC\REDO03.LOG';

4. make a valid cold backup.
Regards
Ahmed

this what i'm searching about
i have the same problem and i need to fix it very fast because i have to finish my project nearly
plz if you can give me a full solution

and here the error

SQL> ALTER DATABASE OPEN;
ALTER DATABASE OPEN
*
ERROR at line 1:
ORA-01110: data file 4: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF'
ORA-01115: IO error reading block from file 4 (block # 1)
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).

Subject: Ora-600 [Kcratr1_lostwrt] On Database Startup After Instance Crash

Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.6.0
This problem can occur on any platform.
Oracle 9i SymptomsThe following errors occurred on startup of the database after an instance crash; each startup attempt failed:


ORA-00600: internal error code, arguments: [kcratr1_lostwrt], [], [], [], [], [], [], []
ORA-600 signalled during: alter database open...


The trace file generated at the time of the ORA-600 [kcratr1_lostwrt] shows the following:

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kcratr1_lostwrt], [], [], [], [], [], [], []
Current SQL statement for this session:
alter database open

Call stack:


ksedmp ksfdmp kgerinv kgesinv ksesin kcratr1 kcratr kctrec kcvcrv adbdrv opiosq0 kpooprx kpoal8 ttcpip opitsk opiino opidrv sou2o opimai OracleThreadStart

ChangesAn instance crash had occurred prior to the occurrence of the errors at database startup.

CauseThe last block written by the Oracle software was lost when the instance crashed. On database startup, Oracle checks the last version of the block written to disk; if an old block is found, the ORA-600 [kcratr1_lostwrt] is raised.

Conditions to identify cause:

The following conditions matched Bug 2531469 "ORA-600 [ KCRATR1_LOSTWRT] DURING 'ALTER DATABASE OPEN' " closed as Not a Bug for the above stated cause:

- ORA-600 [kcratr1_lostwrt] with call stack (kcratr1 kcratr kctrec kcvcrv adbdrv)

- ORA-600 signalled during: ALTER DATABASE OPEN

- instance crash prior to database startup failing with ORA-600 [kcratr1_lostwrt] and ORA-600 signalled during: ALTER DATABASE OPEN



SolutionMount the database and try to recover through the online redo logs:


SQL>startup mount
SQL>recover database;
SQL>alter database open;


This is successful in many cases. If it is not, however:



1. if the database is in archivelog mode, restore a backup of the affected datafile and perform media recovery before starting the
database.

2. if the database is not in archivelog mode, restore a backup of the database taken prior to the instance crash.

Please refer to the following document for information regarding database restoration and recovery:

Oracle®9i Backup and Recovery Documentation Online Roadmap
Release 2 (9.2)
Part Number A97202-01