ORA-00353: during startup of instance from archiver process

When starting one of the databases we received the ORA-00353 error. It indicates that archiver process couldn’t archive one of the redo logs due to corruption. Oracle tried to read both the logmembers from the same group but they both were corrupted and instance crashes when trying to open it. ARC0: STARTING ARCH PROCESSES COMPLETE ARCH: Log corruption near block 88727 change 12629319 time ? … Continue reading ORA-00353: during startup of instance from archiver process

How to find and fix block corruption using RMAN?

One of the scenario we ran into when one of the data file reported there was block corruption as RMAN reported the following message in its logs. Note: This scenario was done on 9.2.0.1 running Linux. RMAN-03009: failure of backup command on ch1 channel at 07/02/2009 04:27:06 ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/oradata/TESTDB/TEST_data_01.dbf And the alert.log (alert_TESTDB.log) also had the following … Continue reading How to find and fix block corruption using RMAN?

How to check physical and logical data corruption using RMAN?

If you are not using RMAN to backup data and use technologies like NetApp snapshot which doesn’t check for physical and logical corruption, one can still use RMAN to check for physical and logical corruption in the datafiles and not back the data up. connect target / run { # set disk to be default device type CONFIGURE DEFAULT DEVICE TYPE TO DISK; # number … Continue reading How to check physical and logical data corruption using RMAN?

How to fix Online redo log corruption?

Today, due to a network issue the host (Solaries) lost contact with the NetApp filer and it corrupted some datafiles and redo log files. The solution was to recreate all indexes from the corrupted datafile in a new tablespace and drop the corrupted tablespace. The archived log process hung because it could not archive the log 464704 which got corrupted, the solution was to clear … Continue reading How to fix Online redo log corruption?