Erman Arslan's Oracle Forum › Database

redo is not consistent

Classic

List

Threaded

30 messages Options

Arsalan

redo is not consistent

Hello Arslan
have a nice day,

Oracle 11.2
os window 2012

After database abnormally down due to electricity, when i try to open database i face below problem

startup
database mounted.
ORA-01172:recovery of thread 1 stuck at block 1974713 of file 7
ORA-01151:use media recovery to recover block,restore backup if needs

Then I Did.

shut immediate;

startup mount;

recover database;

ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [7], [2363530], [31723658], [], [], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 7, block# 2363530, file offset is 2182168576 bytes)
ORA-10564: tablespace IRD_DATA_LARGE
ORA-01110: data file 7: 'D:\APP\ADMINISTRATOR\ORADATA\AFGPROD\IRD_DATA_LARGE01.DBF'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 542394

Please guide me

Thanks

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Hi Arsalan,

Please check the following MOS document and update me accordingly ->

Stuck recovery of database ORA-00600[3020] (Doc ID 283269.1)

Arsalan

Re: redo is not consistent

In reply to this post by Arsalan

Sir,

After physical server restart then i try to open database then i face new error

SQL> startup
ORACLE instance started.

Total System Global Area 1.3370E+10 bytes
Fixed Size 2405640 bytes
Variable Size 2051017464 bytes
Database Buffers 1.1312E+10 bytes
Redo Buffers 5033984 bytes
Database mounted.
ORA-00742: Log read detects lost write in thread %d sequence %d block %d
ORA-00312: online log 2 thread 1: 'E:\RECOVERY_AREA\REDO_DATA_2\REDO02.LOG'

Arsalan

Re: redo is not consistent

Sir the DB is down please guide me

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

You may try recovering your db with the current redolog and then opening your db.
Check the v$log and find the current redolog.
Then when you re in mount state, recover your database (using until cancel) by supplying the current redolog.. (probably redo2 in your case)

If the issue persist, update me with your OS (+ its version) + DB version + ASM/GRID version(if you are using ASM)

Arsalan

Re: redo is not consistent

After database start

RMAN> delete expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=482 device type=DISK
specification does not match any archived log in the repository

RMAN>

RMAN>

RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;

Starting backup at 05-AUG-20
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/05/2020 16:47:19
ORA-19563: header validation failed for file

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Check these notes ->

Backup Of Archivelogs Getting Error ORA-19563 (Doc ID 1589870.1)
RMAN Backup Returns Error ORA-19563 (Doc ID 944906.1)

Arsalan

Re: redo is not consistent

Good morning sir,

we don;t have oracle support it is expired
please give me step to solve the issue

our db is down for 2 days

thanks a lot

Arsalan

Re: redo is not consistent

sir

I can take backup of database but i can not take backup of archive log please help me

RMAN> backup database;

Starting backup at 06-AUG-20
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00008 name=D:\APP\ADMINISTRATOR\ORADATA\AFGPROD\IRD_INDEXES01.DBF
channel ORA_DISK_1: starting piece 1 at 06-AUG-20
piece handle=E:\RECOVERY_AREA\AFGPROD\AFGPROD\BACKUPSET\2020_08_06\O1_MF_NNNDF_TAG20200806T082715_HLPZWVPL_.BKP tag=TAG20200806T082715 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:10:06
Finished backup at 06-AUG-20
Starting Control File and SPFILE Autobackup at 06-AUG-20
piece handle=E:\RECOVERY_AREA\AFGPROD\AFGPROD\BKCONTROLFILE\CONT_FILEAFGPROD_C-2478170099-20200806-01 comment=NONE
Finished Control File and SPFILE Autobackup at 06-AUG-20
=====================================================================================================
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;

Starting backup at 06-AUG-20
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/06/2020 08:41:25
ORA-19563: header validation failed for file

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Collect a debug trace for your failing RMAN backup, then we will check..

Collect debug trace for RMAN,

Example:

rman target <username/password> debug trace='debug.trc'

Arsalan

Re: redo is not consistent

Hello sir,

this is log

debug.trc

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Collected info:

CHANNEL> begin :rc := sys.dbms_backup_restore.validateArchivedLog( recid => :recid, stamp => :stamp, fname => :fname, thread => :thread, sequence => :seq, resetlogs_change => :rstscn, first_change => :lowscn, blksize => :blksize, signal => :sigerr, terminal => :terminal); end;
DBGSQL: sqlcode = 19563
DBGSQL: B :rc = NULL
DBGSQL: B :recid = 138524
DBGSQL: B :stamp = 1047489696
DBGSQL: B :fname = E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_03\O1_MF_1_37777_HLJ22JT4_.ARC
DBGSQL: B :thread = 1
DBGSQL: B :seq = 37777
DBGSQL: B :rstscn = 2368972877
DBGSQL: B :lowscn = 3461796679
DBGSQL: B :blksize = 512
DBGSQL: B :sigerr = 1
DBGSQL: B :terminal = 0
DBGSQL: error: ORA-19563: header validation failed for file (krmkosqlerr)

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Is htat file present? -> E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_03\O1_MF_1_37777_HLJ22JT4_.ARC

Arsalan

Re: redo is not consistent

Yes sir we have this archive log

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Probably, that archivelog is corrupt;

If you want to backup your db+archivelogs in this kind of a situation, rename the archivelog at the os level and then ran these two rman commands:

crosscheck archivelog all;
delete noprompt expired archivelog all;

Then retry your backup.. (note that archived log will not be backed up.)

Arsalan

Re: redo is not consistent

I renamed the archive log after that i below command

archived log file name=E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_06\O1_MF_1_267_HLQMYQDB_.ARC RECID=138793 STAMP=1047737375
Crosschecked 448 objects

RMAN> delete noprompt expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=772 device type=DISK
specification does not match any archived log in the repository

RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;

Starting backup at 06-AUG-20
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 08/06/2020 14:11:05
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_03\O1_MF_1_37777_HLJ22JT4_.ARC
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

How did you renamed the file?
You should rename it from OS, using OS command.

Arsalan

Re: redo is not consistent

sir i renamed by right click on it is windows OS

ErmanArslansOracleBlog

Re: redo is not consistent

Administrator

Did you run crosscheck?

As I already said - >

crosscheck archivelog all;
delete noprompt expired archivelog all;

Arsalan

Re: redo is not consistent

yes i already don multitime

validation succeeded for archived log
archived log file name=E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_06\O1_MF_1_282_HLQV4YK0_.ARC RECID=138808 STAMP=1047744742
validation succeeded for archived log
archived log file name=E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_06\O1_MF_1_283_HLQV7OQV_.ARC RECID=138809 STAMP=1047744829
validation succeeded for archived log
archived log file name=E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_06\O1_MF_1_284_HLQV8PVM_.ARC RECID=138810 STAMP=1047744862
Crosschecked 286 objects

RMAN> delete noprompt expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=483 device type=DISK
specification does not match any archived log in the repository