redo is not consistent

[ErmanArslansOracleBlog]

rename it as PROBLEMATIC_ARCHIVELOG.ARC  then crosscheck and delete expired.

[Arsalan]

By renamed mention archive logfile did not solve the problem

so the DB was down i took backup  not archive log because if i use
backup database plus archivelog then it give use Error as i sent on previous message.

So my new question is.

1-I took backup by (backup database) and backup current controlfile;

2-I restored on new DB server and copy all archive log from source DB to new DB SERVER

start database recover command and open by  alter database open resetlogs.

so new db server is working normal,

can tell me what my mistake i did during restoration of database, or

Does our new db is data is consist or not

Thanks a lot

[ErmanArslansOracleBlog]

It is consistent. You cant just open an Oracle database that way without making it consistent. So it is.

This is a new question and it is out of the context isn't it?

So you restored your db from backup and then recovered it. Did you apply that problematic atchivelog too?
What mistake are you talking about? Please revise your question.

[Arsalan]

Yes i copy all archive log from source db to target include problematic archive

and started database recover command  AND OPEN DB  BY alter database open resetlogs

now db is working fine and AND it also take (backup database plus archivelog) please check the log

if it have any issue let me.

 Thanks a lot for always support on time.



rman_backup_Sun.LOG

[ErmanArslansOracleBlog]

Good.

So you copied the problematic archivelog to the new system and then you could back it up successfully.
So the archivelog was okay then.. Interesting.
Then this seems like a bug.
This may be related with a bug in the multisection style rman backup.
We have a bug record for that -> Bug 25042823 : ORA-19563 DURING DUPLICATE DATABASE TARGETLESS

Did you use exactly the same channel configuration in the new system while you are backing up this archivelog? Any changes in your backup command or rman configuration in the new system? (single channel , multi channel ect?)

[Arsalan]

Yes i used same channel and command  as i sent log of rman backup on new db server

please check logs


rman_backup_Sun.LOG

[ErmanArslansOracleBlog]

What is different between new and old server?
I terms of OS? Storage? Filesystem (cooked fs or ASM) that the archivelogs reside.

[Arsalan]

Both are same file system,

windows 2012 It Have 3 partition

oracle 11g r2

Both db sever have same path of archive log like

E:\Recovery_area\Afgprod\AFGPROD\ARCHIVELOG

No ASM,No storage

[ErmanArslansOracleBlog]

I think we renamed the wrong archivelog..
We should have renamed the last archivelog before the error and according the debug trace it is ->

E:\RECOVERY_AREA\AFGPROD\AFGPROD\ARCHIVELOG\2020_08_04\O1_MF_1_37777_HLLSH89M_.ARC

I 'm telling you this because Oracle Support Note named "Backup Of Archivelogs Getting Error ORA-19563 (Doc ID 1589870.1)" says so..

So probably somehow that archivelog confuses RMAN'S mind, and RMAN probably excepts to see its header in the next archivelog that it tries to backup.
This is what I understand from the Oracle Support note.
You can try this just to satisfy our curiosity.. Ofcourse iif you still have that problematic environment..

[Arsalan]

Thank you very much for on time support.

The problem have solved by your support.