Thanks for the question, Alfins.
Asked: January 14, 2016 - 4:04 am UTC
Last updated: January 14, 2016 - 6:39 am UTC
Version: 12
Viewed 1000+ times
You Asked
Dear Expert,
I have done restore a control file, datafile and some archivelog that was needed to recover database in single database environment.
I restored them from full backup cluster database enviroment.
The surrent status for target is :
RMAN> run {
allocate channel ch00 device type 'SBT_TAPE';
send 'NB_ORA_SERV= vrbackup, NB_ORA_CLIENT=vpoossdb01x';
restore database preview summary from tag = HOT_DB_BK_LEVEL0;
release channel ch00;
} 2> 3> 4> 5> 6>
using target database control file instead of recovery catalog
allocated channel: ch00
channel ch00: SID=12 device type=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.6 (2014102721)
sent command to channel: ch00
Starting restore at 14-JAN-16
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
10 B 0 A SBT_TAPE 04-JAN-16 1 1 NO HOT_DB_BK_LEVEL0
9 B 0 A SBT_TAPE 04-JAN-16 1 1 NO HOT_DB_BK_LEVEL0
List of Archived Log Copies for database with db_unique_name OPOSSIN
=====================================================================
Key Thrd Seq S Low Time
------- ---- ------- - ---------
96 1 48 A 04-JAN-16
Name: /u01/apps/oracle/product/12.2/dbs/opossrdb_1_48_896102962.arc
94 1 49 A 04-JAN-16
Name: /u01/apps/oracle/product/12.2/dbs/opossrdb_1_49_896102962.arc
97 2 41 A 02-JAN-16
Name: /u01/apps/oracle/product/12.2/dbs/opossrdb_2_41_896102962.arc
98 2 42 A 04-JAN-16
Name: /u01/apps/oracle/product/12.2/dbs/opossrdb_2_42_896102962.arc
RMAN-05119: recovery can not be done to a consistent state.
Media recovery start SCN is 10158418
Recovery must be done beyond SCN 10160582 to clear datafile fuzziness
validation succeeded for backup piece
Finished restore at 14-JAN-16
released channel: ch00
Could you help me to find out why this db cannot be recover and opened ?
Or is there another way to force the DB open with archivelogs which have been restored?
Thanks
and Connor said...
One (or more) of your datafiles is at least at SCN 10160582, so you need to bring the others to at least that level..otherwise you are not in a consistent state.
Its similar to the old SQL PLus message "File x needs more recovery" error we used to get.
You need to recover more (which probably means you need more archive logs to apply).
A nice write up here
http://www.pythian.com/blog/rman-infatuation/
Is this answer out of date? If it is, please let us know via a Comment