Total Pageviews

Thursday, July 26, 2018

How to restore database if archivelog missing. ORA-00279,ORA-00289,ORA-00280,RMAN-06053,RMAN-06025.

SQL> recover database;
ORA-00279: change 83054010 generated at 07/05/2018 21:14:55 needed for thread 1
ORA-00289: suggestion :
C:\APP\ASHWANIK\FLASH_RECOVERY_AREA\DB11GDEV\ARCHIVELOG\2018_07_26\O1_MF_1_3_%U_
.ARC
ORA-00280: change 83054010 for thread 1 is in sequence #3

RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/26/2018 20:09:25
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 5 and starting SCN of 83060822 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 4 and starting SCN of 83054151 found to restore

Solution: Check the nearest log to sequence 4 and 5 available physically on disk. We have below logs avaiable.
C:\app\ashwanik\flash_recovery_area\db11gdev\ARCHIVELOG\2018_07_06\O1_MF_1_6_FMZ45LOQ_.ARC


RMAN> restore database until sequence 6;

Starting restore at 26-JUL-18
using channel ORA_DISK_1

skipping datafile 1; already restored to file G:\DB11GDEV\DB11GDEV\SYSTEM01.DBF
skipping datafile 2; already restored to file G:\DB11GDEV\DB11GDEV\SYSAUX01.DBF
skipping datafile 3; already restored to file G:\DB11GDEV\DB11GDEV\UNDOTBS01.DBF
skipping datafile 4; already restored to file G:\DB11GDEV\DB11GDEV\USERS01.DBF
skipping datafile 5; already restored to file G:\DB11GDEV\DB11GDEV\EXAMPLE01.DBF
skipping datafile 6; already restored to file G:\DB11GDEV\DB11GDEV\METALSDB.DBF
skipping datafile 7; already restored to file G:\DB11GDEV\DB11GDEV\METALSIDX.DBF
skipping datafile 9; already restored to file G:\DB11GDEV\DB11GDEV\USERS.DBF
skipping datafile 10; already restored to file G:\DB11GDEV\DB11GDEV\ORACLEFORENSICS.DBF
restore not done; all files read only, offline, or already restored
Finished restore at 26-JUL-18

Try to open the database:

RMAN> alter database open;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 07/26/2018 20:14:14
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

If above error received open the database to resetlogs.

RMAN> alter database open RESETLOGS;

database opened


No comments:

Post a Comment