Redo is corrupted

Hi all,
If one of the logfiles is corrupted while RMAN backup is going on...
Then, what happens to the currently running backup?

Hi Jeevith,
If one of the logfiles is corrupted while RMAN backup is going on...Such an event can crash the instance which will end the rman backup as well.
Rgds,
Tycho

Similar Messages

Current Redo log corruption

Suppose the current online redo log is corrupted, is there any way to make database functional other than doing incomplete recovery?
Oracle documentation says we have to do incomplete recovery. Is Cancel based Incomplete recovery the only option.
If this database is also the primary database for A physical standby database how to synchronize the Standby database with Primary? Since we would be opening Primary with Resetlogs....

Incomplete Recovery upto the last (archive) redo log before the current one IS the only option.
Your current redo log would have some transactions in it. Also, the datafiles would have had some dirty blocks written to disk by DBWR. Therefore, the datafiles would be inconsistent until and unless you can apply the redo that goes with those changes. Since the redo cannot be applied from the corrupt file, the datafiles themselves must be reverted to a prior image -- upto the last redo that can be applied.
As for the standby, if you have Flashback configured, you can Flashback the Standby to the point 2 SCNs before the Primary Resetlogs.
See DataGuard Scenario 12.5 at
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049616
Else use Scenario 8.4 at
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1026480
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on Jul 22, 2009 12:13 AM

Redo log corruption

In a 2 node RAC Node1 crashes due to the online redo-log file corruption.
During this scenario...,Node2 should perform instance recovery; but since redo-log is corrupted, it cannot do the instance recovery.
what will happen at this point ? Will the other node2 continue working ?

please note that I hav'nt tested this to validate this ..
this is a theoritical answer based on what I believe how it might work ..
a) Node:2 attempts to perform an Instance Recovery by reading the Shared
Redo Log threads of Node:1
b) It runs into the same corrupt Redolog block messages and reports an
Internal error { ora-00600 / ora-07445 }
c) Depending on whether it was a fatal or non-fatal error , Node:2 might crash or
continue to work .. if it is the latter , everytime any access is needed to blocks
which still have those uncommitted transactions from Node:1 , you would
see an error / trace generated ..
Vishwa

REDO GOT CORRUPTED

Hai to everybody
can anubdy solve my problem
actually last night our one of our redo group 3 get corrupted
and all redo groups have 2 members .
we have cold backup of 7 days before and our database is in archive log mode.
so plz suggest me how to get out of this mess?

You didnt tell us that either you have cold backup is OS based or it is RMAN based?
Anyway i assume its OS based..
You may lost yours redo logs which is about to be archived but failed before archive if the corrupted log is current.
Shutdown force yours current states of database,restore cold backup via OS then mount the database and start recovery "recover database using backup controlfile until cancel" supply all archive logs whih you have,after that open database with resetlogs.
Khurram

Current redo log corrupted

I have 6 Tera byte of database. My current redo log is currpted. I dont want to go for incomplete recovery as my database size is too large.
what is the other option to recover the database
oracle version is 9i

This method wont work because I am talking about current online redo log
You can clear an inactive redo log group when the database is open or closed. The procedure depends on whether the damaged group has been archived.
To clear an inactive, online redo log group that has been archived, use the following procedure:
1. If the database is shut down, then start a new instance and mount the database:
STARTUP MOUNT
2. Reinitialize the damaged log group. For example, to clear redo log group 2, issue the following statement:
ALTER DATABASE CLEAR LOGFILE GROUP 2;

ORA-00354: corrupt redo log block header..urgent

Hi All,
i am running into an issue when trying to recover a datafile.
1). Logs are being applied to the datafile to recover but RMAN is throwing this error:
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF_1_13174_7SC4
P56W_.ARC'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 32768 change 6715041179 time 04/23/2012 13:
33:51
ORA-00334: archived log: 'H:\ORACLE_ARCHIVE_LOGS\RBS\ARCHIVELOG\2012_04_23\O1_MF
_1_13174_7SC4P56W_.ARC'
thanks in advance

bcm@bcm-laptop:~$ oerr ora 353
00353, 00000, "log corruption near block %s change %s time %s"
// *Cause: Some type of redo log corruption has been discovered. This error
//          describes the location of the corruption. Accompanying errors
//          describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
//          recovery up to the indicated change or time.
bcm@bcm-laptop:~$ oerr ora 354
00354, 00000, "corrupt redo log block header"
// *Cause: The block header on the redo block indicated by the accompanying
//          error, is not reasonable.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.

Current log group corruption

Check out whether u can solve this issue:
This is the error which I have faced in one of my clients place. The scenario goes like this
Because of some virus problem the server was abnormally shutdown. Next time when I tried to open the database I got this error:
SQL> startup
ORACLE instance started.
Total System Global Area 202447572 bytes
Fixed Size 453332 bytes
Variable Size 117440512 bytes
Database Buffers 83886080 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 6165 change 136535232 time
05/18/2006 13:03:22
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\NCRCL\REDO01.LOG'
The group happens to be the current group.
SQL> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIME
1 1 2480 104857600 1 NO CURRENT
136527225 18:MAY:06-12:11:08
2 1 2478 104857600 1 NO INACTIVE
136470398 18:MAY:06-10:10:28
3 1 2479 104857600 1 NO INACTIVE
136504477 18:MAY:06-11:48:21
The error says at SCN 136535232 there is one log corruption. So what we decided is to recover the database until change (136535225):
Sql> Recover database until change 136535226;
After giving this when we tried to open the database we got this error:
Sql> Alter database open resetlogs;
Error: File 1 needs more recovery to be consistent , can’t open the database.
Note : The client hasn’t implemented any kind of backup strategy.
Could you please solve the issue

ORA-00353: log corruption near block string change string time string
Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.
Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.
go through below link
Redolog Corrupted

How to damage online redo log for simulation

Dear All,
Kindly please help to inform me, is there any way to damage online redo log from database level (not from OS command like dd) ?
I need to do it for test case to enable db_block_checking and db_block_checksum (set both parameter to TRUE).
Is those parameter will help from redo log corruption ? that's why, i want to prove it.
Thanks
Anthony

user12215770 wrote:
My purpose is i want to verify that the db_block_checking and db_block_checksum can avoid redo corruption (the corruption caused by process in the database).Redo corruption could also occur due to other issues as http://docs.oracle.com/cd/E11882_01/server.112/e25513/initparams049.htm#REFRN10030 says:
>
Checksums allow Oracle to detect corruption caused by underlying disks, storage systems, or I/O systems. If set to FULL, DB_BLOCK_CHECKSUM also catches in-memory corruptions and stops them from making it to the disk.
>
You could try to use ORADEBUG POKE command to write directly in the SGA if you know how to find log buffer blocks ... About ORADEBUG please read http://www.juliandyke.com/Diagnostics/Tools/ORADEBUG/ORADEBUG.html.

DBMS_SCHEDULER.run_job problem

Hi friends.I have one problem. I use Oracle 10g(r2) in oracle enter.server. Also I can execute backupdb.sh script from terminal
success.But I created Job sheduler as
BEGIN
DBMS_SCHEDULER.CREATE_JOB
job_name => 'BACKUP_DB_JOB',
job_type => 'EXECUTABLE',
job_action => '/orahome/orastart/./backupdb.sh',
start_date => '13-jan-2010 6:32 PM',
repeat_interval => 'FREQ=DAILY'
END;
although i execute following
begin
DBMS_SCHEDULER.run_job (job_name=>'BACKUP_DB_JOB');
end;
then occur error [1]: (Error): ORA-27369: job of type EXECUTABLE failed with exit code: 274660 ORA-06512: at "SYS.DBMS_ISCHED", line 150 ORA-06512: at "SYS.DBMS_SCHEDULER", line 441 ORA-06512: at line 4
also i see detail information from dba_scheduler_job_run_details.ADDITIONAL_INFO described as
ORA-27369: job of type EXECUTABLE failed with exit code: 274660
STANDARD_ERROR="Oracle Scheduler error: Not running as extjob or extjobo."
there are for extjob following
ls -l $ORACLE_HOME/bin/extjob
-rwsr-x--- 1 root oinstall 64842 Oct 15 06:58 /orahome/oracle/product/10.2.0/db_1/bin/extjob
and
ls -l $ORACLE_HOME/rdbms/admin/externaljob.ora
-rw-rwxr-- 1 640 oinstall 1536 Jan 19 15:08 /orahome/oracle/product/10.2.0/db_1/rdbms/admin/externaljob.ora
why that error happen?

See the below forum for solution
Guide to External Jobs on 10g with dbms_scheduler e.g. scripts,batch files
Hope this helps,
Regards
http://www.oracleracexpert.com
Click here for [Block Corruption and recovery|http://www.oracleracexpert.com/2009/08/block-corruption-and-recovery.html]
Click here for [Redo log corruption and recovery|http://www.oracleracexpert.com/2009/08/redo-log-corruption-and-recovery.html]

ORA-600 in standby alert log

We have recently migrated our database from Solaris to Linux (RHEL5) and since this migration we are seeing weird errors related to archive log shipping to the remote standby site and a corresponding ORA-600 in the standby site.
What's interesting is everything gets resolved by itself, it always seems to happen during the heavy database load when there is frequent log switch happening (~3 min). So initially it tries to archive to the remote site and it fails with the following error in the primary alert log.
Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
ORA-00272: error writing archive log
Mon Jul 14 10:57:36 2008
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jul 14 10:57:36 2008
Errors in file /app/oracle/admin/UIIP01/bdump/uiip01_arc1_9772.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Jul 14 10:57:36 2008
ORACLE Instance UIIP01 - Archival Error. Archiver continuing.
And then we see a ORA-600 on standby database related to this which complains about redo block corruption.
Mon Jul 14 09:57:32 2008
Errors in file /app/oracle/admin/UIIP01/udump/uiip01_rfs_12775.trc:
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
Mon Jul 14 09:57:36 2008
And the trace file has this wonderful block corruption error..
Corrupt redo block 424432 detected: bad checksum
Flag: 0x1 Format: 0x22 Block: 0x000679f0 Seq: 0x000006ef Beg: 0x150 Cks:0xa2e5
----- Dump of Corrupt Redo Buffer -----
*** 2008-07-14 09:57:32.550
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kcrrrfswda.11], [4], [368], [], [], [], [], []
So ARC tries to resend this redo log again and it succeeds, end of the day all we have is a bunch of these ORA- errors in our alert logs, triggering off our monitors and these errors resolve themselves without any manual intervention, opened a tar with Oracle support as this is not affecting our primary database, they are in no hurry to get this one prioritized and also they are reluctant to accept that it's a bug that resolves itself.
Just wanted to get it out here to see if anyone experienced a similar problem, let me know if you need any more details.
As I said earlier this behaviour happens only during peak loads espceially when we have full 500M redo logs that are being archived.
Thanks in Advance.

Thanks Madrid!..
I scoured thru these metalink notes before looking for possible solutions and almost all of them were closed citing a customer problem related to OS, firewall, network, etc or some were closed saying requested data not provided.
Looks as if they were never successfully closed with a resolution.
I just want to assure myself that the redo corruption that standby is reporting will not haunt me later, when I am doing a recovery or even a crash recovery using redo logs?..
I have multiplexed my logs, just in case and have all the block checking parameters enabled on both primary and standby databases.
Thanks,
Ramki

Just a scenario

Hi All,
This is just a scenario.. I have 3 redo groups which are not multiplexed (I know its a bad idea), and suddenly due to some OS issues one of my redo gets corrupted, my backups policy involves hot backup for datafiles and also backups of my archives and my control files?
How to go ahead in this scenario so that my database can be put in open mode again?
Again, its just a scenario, but any ideas or any tips to forward in this situation would be really helpful from you guys
Thanks,
Ajinkya

>
This is just a scenario.. I have 3 redo groups which are not multiplexed (I know its a bad idea), and suddenly due to some OS issues one of my redo gets corrupted, my backups policy involves hot backup for datafiles and also backups of my archives and my control files?
How to go ahead in this scenario so that my database can be put in open mode again?
>
If you lose a complete online log group, it can have three possible states:
1. CURRENT (LGWR writes into it)
2. ACTIVE (still needed for instance recovery)
3. INACTIVE (you are lucky)
In 1. and 2., you need to do an incomplety recovery in order to make your database consistent again. You will lose all transactions that had their redo protocol in the lost group. That is why it is strongly recommend to mirror log groups.
In 3., you can recreate the logfile or even drop it (if you have 3 groups). In case that log group was not archived yet, you need to take a backup of your database then. You will suffer no data loss here.
Kind regards
Uwe
http://uhesse.wordpress.com

Unable connect oracle database problem

Hi ,
I ahve installed oracle 11g on windows 7 machine.It is working fine intially after some days when ai m connecting it is giving the below error.
ora-01033 oracle initialization or shutdown in progress.
After this I ahve done the below steps and corrosponding results.
1.shutdown abort
oracle instance shutdown
2.startup nomount
oracle instance started
below some statitics like total system global area..
3.alter database mount
database altered.
4.alter database open
database altered.
after these steps also still i am getting the problem .Please help me to resolve the problem.

925197 wrote:
This time the following error came.
SQL> startup nomount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 3373858816 bytes
Fixed Size 2257864 bytes
Variable Size 2348813368 bytes
Database Buffers 1006632960 bytes
Redo Buffers 16154624 bytes
SQL> alter database mount;
Database altered.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00333: redo log read error block 724 count 7470When you aborted database, may be redo is corrupted.
try : alter database recover database until cancel;
alter database open resetlogs; Regards
Mahir

Urgent recovery help needed

Hello I have 817 database on Solaris and I do not have cold back up of the db. The db is in NOARCHIVE mode. I tried to bounce the db but I cannot open the db as I get the following error:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 9224405 time 06/05/2006 18:42:20
ORA-00312: online log 3 thread 1: '/u01/oradata/etpdb1/redo03.log'
Here is more info:
SVRMGR> select * from V$logfile;
GROUP# STATUS MEMBER
1 /u01/oradata/etpdb1/redo01.log
2 /u01/oradata/etpdb1/redo02.log
3 /u01/oradata/etpdb1/redo03.log
SVRMGR> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHAN FIRST_TIM
1 1 0 5242880 1 YES UNUSED 0
2 1 0 5242880 1 YES UNUSED 0
3 1 1401 5120000 1 NO CURRENT 9223256 05-JUN-06
SVRMGR> alter database open resetlogs;
alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
Can anyone advise what can I do not to recover the db. Thanks

NO ArchiveLog -- Online Redo Log corrupted.
if you have multiplexing enabled copy the redo log of the other member
and then see if db would open with that.
http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14192/strategy002.htm#sthref122
Your case is probably
-> Whether the lost redo log group was current
You have very limited option other than to go back to what ever backups you have.
Engage oracle support is the best option as they may suggest other alternatives, there is a parameter ALLOWRESETLOGS_CORRUPTION but it has serious limitations check with Oracle first.
http://www.sidibe.net/allow_resetlog.html
Good Luck

PLS-00907

We're getting an intermittent PLS-00907 error in one of our applications and I've been assigned to track down the cause.
The Oracle version is 10.2.0.2 and the error text is
PLS-00907: cannot load library unit SCHEMA_NAME.TABLE_NAME (referenced by SCHEMA_NAME.PACKAGE_NAME)
All the references to this error I have found either had to do with compiling a package or the library unit named was either a package or procedure.
In this case the library unit named is a table and when I find the error in our log file, I can see that the application had previously successfully completed the same operation about an hour earlier and if I query the LAST_DDL_TIME from DBA_OBJECTS for the table, the package, and the package body, all three are earlier than the time when the application had successfully completed the task.
It has been our observation that once the error occurs once, it will happen intermittantly every four to six hours until we have the DBA flush the shared pool. After flushing the shared pool the problem goes away for about a week.
Does anyone have any ideas where I should start looking?
Edit: Another bit of information: The first non-comment line in the package source is a variable declaration :
variable_name TABLE_NAME.column_name%TYPE;Where "TABLE_NAME" is the same table name as in the error message.
Edited by: kendenny on Sep 28, 2009 1:13 PM

Try below solution.
Cause
Issue is caused by sequencing problem during the application of the patch
as discussed in bug 945478
Solution
To implement the solution, please execute the following steps:
1. Recompile the failing package:
for ex:-
alter package ABC_PACK compile;
alter package ABC_PACK compile body;
2. Restart the failed worker
Regards
Click here for [Block Corruption and recovery|http://www.oracleracexpert.com/2009/08/block-corruption-and-recovery.html]
Click here for [Redo log corruption and recovery|http://www.oracleracexpert.com/2009/08/redo-log-corruption-and-recovery.html]
http://www.oracleracexpert.com

Alter database clear unarchived logfile group... who, what?

I am the sole DBA for our site, all of them running RHEL 5, Oracle 11.2.0.3.
I recently (within the last hour), received a text message from one of our databases that poll the alert.log...
ORA-1031 signalled during: ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3
Unfortunately, the 'audit database' was not enabled (it is now!), and the trace file generated did not contain anything of use.
I know someone has been loading data since 1:30pm up until near the time I received this text, and I'm wondering if he is mucking in the system, or if this command can somehow be generated automatically by Oracle. If so, I certainly wouldn't expect an ORA-1031insufficient permissions error....
I checked my v$log, v$logfile, and did a log switch just to check if any possibility of redo log corruption, but all looks fine.
Has anyone else ever had random Oracle errors like this?....

Hi,
That's someone manually doing something when they really don't know what they are doing. I've only had to run that command once in 16 years as a dba. Oracle wouldn't ever run that itself.
Cheers,
Harry

Redo is corrupted

Similar Messages

Maybe you are looking for