Sekedar menambahkan., =================== Sebenarnya pak rohmad telah membahasnya dengan lengkap., munkin artikel di bawah ini hanya untuk menambahkan saja.,
ISSUE VERIFICATION =================== Sun Apr 08 22:34:28 2007 alter database open Sun Apr 08 22:34:29 2007 Beginning crash recovery of 1 threads parallel recovery started with 2 processes Sun Apr 08 22:34:30 2007 Started redo scan Sun Apr 08 22:34:35 2007 Errors in file d:\oracle\product\10.2.0\admin\kromdev\udump\kromdev_ora_2476.trc: ORA-00333: redo log read error block 6674 count 6144 ORA-00312: online log 2 thread 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\KROMDEV\REDO02.LOG' 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). SOLUTION / ACTION PLAN ======================= A database running in noarchivelog mode and the redo is not multiplex cannot be recover. We can try and force the database open to allow you to get an export and then rebuild the database. CAUTION! Using the following parameter is irreversible. You MUST rebuild the database once the parameter is used. This should only be used as a last resort, und er the guidance of a senior support analyst. Forcing the database open using this method is unsupported. This would allow you to export but not continue to use a database that has been force open. To ATTEMPT to force the database open, perform the following steps: 1. Add the parameter _ALLOW_RESETLOGS_CORRUPTION = TRUE to the init.ora file 2. STARTUP MOUNT the database 3. Issue the appropriate RECOVER DATABASE command: a) RECOVER DATABASE UNTIL CANCEL or b) RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL 4. Enter CANCEL to cancel recovery - there are NO archive logs applied. 5. Enter ALTER DATABASE OPEN RESETLOGS 6. Try selecting from a table - for example, SELECT SYSDATE FROM DUAL --- On Thu, 8/14/08, rohmadsan <[EMAIL PROTECTED]> wrote: From: rohmadsan <[EMAIL PROTECTED]> Subject: [indo-oracle] Re: ORA-00333 : redo log read error block To: [email protected] Date: Thursday, August 14, 2008, 2:52 PM Hallo ... Ini online redo log corrupt. 1. Coba lihat di alert log, itu file redo log yang mana? Kalau punya mirror, copy saja dari mirrornya. Query ini untuk melihat mirrornya: SQL> startup mount SQL> --- lihat file lain yang GROUP#-nya sama SQL> select * from v$logfile; Kalau ada mirror-nya, copy saja dari mirror ke file yang corrupt tadi. 2. Kalau tidak punya mirror. Apakah redo log file tersebut INACTIVE, ACTIVE, atau CURRENT? SQL> startup mount SQL> -- lihat, log itu masuk group mana SQL> select * from v$logfile; SQL> -- lihat, statusnya apa: INACTIVE, ACTIVE, atau CURRENT? SQL> select * from v$log; 3. Kalau INACTIVE, anda bisa men-dropnya SQL> -- Misalkan itu group 3 SQL> alter database drop logfile group 3; 4. Kalau statusnya ACTIVE atau CURRENT, ya wassalam :) Anda harus restore dari backup. Tapi, archivelog-nya anda disable, jadi ya hanya bisa restore dari last full backup. Ada work around, kita bisa memaksa database untuk naik. Mudah-mudahan bisa. Saya pernah membahasnya di sini http://rohmad. net/2008/ 05/05/startup- inconsistent- database/ Salam, Rohmad --- In indo-oracle@ yahoogroups. com, "forum_it82" <forum_it82@ ...> wrote: > > teman... > Mohon bantuannya nihhh > Oracle ku nggak bisa di startup > ada pesan > "ORA-00333 : redo log read error block 3974 count 8192" > > Solusinya gimana y? > Archivelog nggak aku aktifin > > mohon bantuan..... . > [Non-text portions of this message have been removed]
