Skip to main content

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time


<<Back to Oracle Backup & Recovery Main Page

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

Cause:- you have performed open resetlogs operation before the restore.

Solution:- Choose correct incarnation and perform the restore

RMAN> list incarnation;
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       ORCL1212 2146849107       PARENT  1          07-JUL-14
2       2       ORCL1212 2146849107       PARENT  1594143    09-MAY-19
3       3       ORCL1212 2146849107       PARENT  1704309    09-MAY-19
4       4       ORCL1212 2146849107       CURRENT 1865322    16-MAY-19

RMAN> RESET DATABASE TO INCARNATION 3;
database reset to incarnation 3

RMAN> RUN
{
  set until time= "to_date('16.05.2019 21:20:00','dd.mm.yyyy hh24:mi:ss')";
  RESTORE DATABASE;
  RECOVER DATABASE;
}

==========================================================================
Troubleshooting Log History

RMAN> RUN                    
{
  set until time= "to_date('16.05.2019 21:20:00','dd.mm.yyyy hh24:mi:ss')";
  RESTORE DATABASE;
  RECOVER DATABASE;
} 
executing command: SET until clause
Starting restore at 16-MAY-19
Starting implicit crosscheck backup at 16-MAY-19
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=12 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/16/2019 21:43:38
RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

RMAN> list incarnation;
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       ORCL1212 2146849107       PARENT  1          07-JUL-14
2       2       ORCL1212 2146849107       PARENT  1594143    09-MAY-19
3       3       ORCL1212 2146849107       PARENT  1704309    09-MAY-19
4       4       ORCL1212 2146849107       CURRENT 1865322    16-MAY-19
RMAN> RESET DATABASE TO INCARNATION 3 ;
database reset to incarnation 3
RMAN> list incarnation;
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       ORCL1212 2146849107       PARENT  1          07-JUL-14
2       2       ORCL1212 2146849107       PARENT  1594143    09-MAY-19
3       3       ORCL1212 2146849107       CURRENT 1704309    09-MAY-19
4       4       ORCL1212 2146849107       ORPHAN  1865322    16-MAY-19
RMAN> RUN
{
  set until time= "to_date('16.05.2019 21:20:00','dd.mm.yyyy hh24:mi:ss')";
  RESTORE DATABASE;
  RECOVER DATABASE;
}
executing command: SET until clause
Starting restore at 16-MAY-19
Starting implicit crosscheck backup at 16-MAY-19
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=12 device type=DISK
Crosschecked 11 objects
Finished implicit crosscheck backup at 16-MAY-19
Starting implicit crosscheck copy at 16-MAY-19
using channel ORA_DISK_1
Crosschecked 2 objects
Finished implicit crosscheck copy at 16-MAY-19
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /u01/app/oracle/fra/ORCL1212/autobackup/2019_05_16/o1_mf_s_1008451629_gfvgdgp5_.bkp
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl1212/system01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl1212/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl1212/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl1212/example01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/product/12.1/db_1/dbs/users01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fra/ORCL1212/backupset/2019_05_16/o1_mf_nnndf_DADAJI_gfvfks3k_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/fra/ORCL1212/backupset/2019_05_16/o1_mf_nnndf_DADAJI_gfvfks3k_.bkp tag=DADAJI
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 16-MAY-19
Starting recover at 16-MAY-19
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 8 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_8_gfvfp9qn_.arc
archived log for thread 1 with sequence 9 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_9_gfvfvw3z_.arc
archived log for thread 1 with sequence 10 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_10_gfvfwx7w_.arc
archived log for thread 1 with sequence 11 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_11_gfvgcym2_.arc
archived log for thread 1 with sequence 12 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_12_gfvgcynj_.arc
archived log for thread 1 with sequence 13 is already on disk as file /u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_13_gfvgcygp_.arc
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=7
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fra/ORCL1212/backupset/2019_05_16/o1_mf_annnn_DADAJI_ARCH_gfvfnrl2_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/fra/ORCL1212/backupset/2019_05_16/o1_mf_annnn_DADAJI_ARCH_gfvfnrl2_.bkp tag=DADAJI-ARCH
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_7_gfvhsd71_.arc thread=1 sequence=7
channel default: deleting archived log(s)
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_7_gfvhsd71_.arc RECID=27 STAMP=1008453068
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_8_gfvfp9qn_.arc thread=1 sequence=8
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_9_gfvfvw3z_.arc thread=1 sequence=9
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_10_gfvfwx7w_.arc thread=1 sequence=10
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_11_gfvgcym2_.arc thread=1 sequence=11
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_12_gfvgcynj_.arc thread=1 sequence=12
archived log file name=/u01/app/oracle/fra/ORCL1212/archivelog/2019_05_16/o1_mf_1_13_gfvgcygp_.arc thread=1 sequence=13
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-MAY-19
RMAN> alter database open resetlogs;
Statement processed
RMAN> list incarnation;
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       1       ORCL1212 2146849107       PARENT  1          07-JUL-14
2       2       ORCL1212 2146849107       PARENT  1594143    09-MAY-19
3       3       ORCL1212 2146849107       PARENT  1704309    09-MAY-19
4       4       ORCL1212 2146849107       ORPHAN  1865322    16-MAY-19
5       5       ORCL1212 2146849107       CURRENT 1865481    16-MAY-19

Comments

Post a Comment

Popular posts from this blog

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Modify Database Startup Mode (Startoption) in Clusterware Registry

<<Back to Oracle RAC Main Page How to Modify Database Startup Option Using srvctl In this post I will show you, how you can modify the database startup option / Database startup mode in clusterware registry using srvctl. There are some time requirement to change the startup option (from default  OPEN ) to  MOUNT, or "READ ONLY" eg if in case of Physical Standby Configuration Let us Check the Current Configuration $ srvctl config database -d ORCL Database unique name: ORCL Database name: Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_2 Oracle user: oracle Spfile: +DATA/ORCL/PARAMETERFILE/spfileORCL.ora Password file: +DATA/ORCL/PASSWORD/pwORCL Domain: Start options: open Stop options: immediate Database role: PHYSICAL_STANDBY Management policy: AUTOMATIC Server pools: Disk Groups: DATA,RECO Mount point paths: Services: Type: RAC Start concurrency: Stop concurrency: OSDBA group: oinstall OSOPER group: oinstall Database instances: ORCL1,...
Post a Comment
Read more

cluvfy Pre Check for RAC Oracle Installation (CVU)

<<Back to Oracle RAC Main Page runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose Cluster Verification Pre Installation check failed. Verifying Physical Memory ...FAILED (PRVF-7530) $./runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose Verifying Physical Memory ... Node Name     Available                 Required                  Status   ------------  ------------------------  ------------------------  ----------   node2         7.5443GB (7910784.0KB)    8GB (8388608.0KB)         failed   node1         7.5443GB (7910784.0KB)    8GB (8388608.0KB)      ...
Post a Comment
Read more