Skip to main content

How to Restore and Recover a Database on a New Host with a Different Directory Structure



How to Restore and Recover a Database on a New Host with a Different Directory Structure from Tape backup



Step1> Install oracle software (same version as old host) on new host
To perform binary installation you can refer below post

Step2> Apply required patches

Step3> set environmental variables
export ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome1
export PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_SID=ORCL1P

Step4> Create initfile
create init file under $ORACLE_HOME/dbs with db_name parameter in it.
cat $ORACLE_HOME/dbs/initORCL1P.ora
db_name=ORCL1P

Step5> invoke rman as follows
invoke RMAN connect to target and catalog database.
set dbid you want to restore
rman target /  catalog rman/xxxxxx@catalogdb
RMAN> set dbid=915313462;

Step6> restore spfile as pfile
run {
allocate  channel ch1 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_db.opt)';
allocate channel ch2 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_log.opt)';
RESTORE SPFILE to pfile '/u01/app/oracle/product/11.2.0.4/dbhome1/dbs/initORCL1P.ora';
} 

NOTE: scroll down to see the outcome of pfile restore

Step7> Modify init.ora file
modify the required  parameters of initORCL1P.ora.
followings are the minimum parameters that need to be modified
audit_file_dest
control_files
db_recovery_file_dest
log_archive_dest_1

Step8> Start the database with modified init file
start the database in nomount mode with modified initORCL1P.ora file
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 2672361472 bytes
Fixed Size                  2256232 bytes
Variable Size            2600469144 bytes
Database Buffers           50331648 bytes
Redo Buffers               19304448 bytes

Step9> restore controlfile
run {
allocate  channel ch1 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_db.opt)';
allocate channel ch2 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_log.opt)';
SET UNTIL TIME "to_date('10-JAN-2021 11:30:00','DD-MON-YYYY hh24:mi:ss')";
restore controlfile from autobackup;
} 

NOTE: scroll down to see the outcome of controlfile restore

Step10> mount the database
Once the controlfile is restored you can not mount the database
SQL> alter database mount;
Database altered.

Step11> rename redo logfiles
SQL>select * from v$logfile;
    GROUP# STATUS  TYPE    MEMBER                                      
---------- ------- ------- ---------------------------------------------
         1         ONLINE  /data1/oracle/ORCL1P/redo/redoG1M1.rdo      
         2         ONLINE  /data1/oracle/ORCL1P/redo/redoG3M1.rdo      
         3         ONLINE  /data1/oracle/ORCL1P/redo/redoG2M1.rdo   
  
SQL>alter database rename file '/data1/oracle/ORCL1P/redo/redoG1M1.rdo' to '/u01/data1/ORCL1P/redo/redoG1M1.rdo';
SQL>alter database rename file '/data1/oracle/ORCL1P/redo/redoG3M1.rdo' to '/u01/data1/ORCL1P/redo/redoG3M1.rdo';
SQL>alter database rename file '/data1/oracle/ORCL1P/redo/redoG2M1.rdo' to '/u01/data1/ORCL1P/redo/redoG2M1.rdo';
SQL>select * from v$logfile;

Step12> Find the list of datafiles
SQL> select file#,name from v$datafile;
     FILE# NAME
---------- --------------------------------------------------
         1 /data1/oracle/ORCL1P/system_01.dbf
         2 /data1/oracle/ORCL1P/sysaux_01.dbf
         3 /data1/oracle/ORCL1P/undotbs_01.dbf
         5 /data1/oracle/ORCL1P/TECBOS_01.dbf

Step13> Restore the database now.
run
{
allocate  channel ch1 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_db.opt)';
allocate channel ch2 DEVICE TYPE 'SBT_TAPE' PARMS  'ENV=(TDPO_OPTFILE=??_log.opt)';
allocate  channel ch3 DEVICE TYPE disk;
SET UNTIL TIME "to_date('11-JAN-2021 04:30:00','DD-MON-YYYY hh24:mi:ss')";
set newname for datafile  1 to '/u01/data1/ORCL1P/system_01.dbf';
set newname for datafile  2 to '/u01/data1/ORCL1P/sysaux_01.dbf' ;
set newname for datafile  3 to '/u01/data1/ORCL1P/undotbs_01.dbf';
set newname for datafile  5 to '/u01/data1/ORCL1P/TECBOS_01.dbf';
 restore database;
 switch datafile all;
 recover database;
 alter database open resetlogs;
 }

NOTE: scroll down to see the outcome of Database restore

Step14> Rename tempfile
SQL> select * from v$tempfile;
SQL> ALTER TABLESPACE TEMP ADD TEMPFILE 'new tempfile path filename' REUSE;

SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/data1/ORCL1P/temp_01.dbf' size 200M autoextend on;
Tablespace altered.


Outcome of Step6  restore spfile as pfile
allocated channel: ch1
channel ch1: SID=171 device type=SBT_TAPE
channel ch1: Data Protection for Oracle: version 8.1.0.2
allocated channel: ch2
channel ch2: SID=9 device type=SBT_TAPE
channel ch2: Data Protection for Oracle: version 8.1.0.2
Starting restore at 15-JAN-21
new media label is 72395 for piece c-915313470-20210111-01
channel ch1: starting datafile backup set restore
channel ch1: restoring SPFILE to PFILE
output file name=/u01/app/oracle/product/11.2.0.4/dbhome1/dbs/initORCL1P.ora
channel ch1: reading from backup piece c-915313470-20210111-01
channel ch1: piece handle=c-915313470-20210111-01 tag=TAG20210111T063156
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:01:05
Finished restore at 15-JAN-21
released channel: ch1
released channel: ch2

Outcome of Step9 restore controlfile

allocated channel: ch1
channel ch1: SID=246 device type=SBT_TAPE
channel ch1: Data Protection for Oracle: version 8.1.0.2
allocated channel: ch2
channel ch2: SID=247 device type=SBT_TAPE
channel ch2: Data Protection for Oracle: version 8.1.0.2
executing command: SET until clause
Starting restore at 17-JAN-21
channel ch1: looking for AUTOBACKUP on day: 20210111
channel ch2: looking for AUTOBACKUP on day: 20210111
channel ch1: AUTOBACKUP found: c-544393468-20210111-00
channel ch2: skipped, AUTOBACKUP already found
channel ch1: restoring control file from AUTOBACKUP c-544393468-20210111-00
channel ch1: control file restore from AUTOBACKUP complete
output file name=/u01/data1/ORCL1P/control/control_01.ctl
output file name=/u01/data1/ORCL1P/control/control_02.ctl
output file name=/u01/data1/ORCL1P/control/control_03.ctl
Finished restore at 17-JAN-21
released channel: ch1
released channel: ch2
RMAN>
RMAN> exit

Outcome of  Step13 Restore the database now

allocated channel: ch1
channel ch1: SID=11 device type=SBT_TAPE
channel ch1: Data Protection for Oracle: version 8.1.0.2
allocated channel: ch2
channel ch2: SID=9 device type=SBT_TAPE
channel ch2: Data Protection for Oracle: version 8.1.0.2
allocated channel: ch3
channel ch3: SID=12 device type=DISK
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 17-JAN-21
Starting implicit crosscheck backup at 17-JAN-21
Finished implicit crosscheck backup at 17-JAN-21
Starting implicit crosscheck copy at 17-JAN-21
Crosschecked 2 objects
Finished implicit crosscheck copy at 17-JAN-21
searching for all files in the recovery area
cataloging files...
no files cataloged
new media label is 72058 for piece db_ORCL1P_1061143038_2655_1_1
channel ch1: starting datafile backup set restore
channel ch1: specifying datafile(s) to restore from backup set
channel ch1: restoring datafile 00001 to /u01/data1/ORCL1P/system_01.dbf'
channel ch1: restoring datafile 00002 to /u01/data1/ORCL1P/sysaux_01.dbf'
channel ch1: restoring datafile 00003 to /u01/data1/ORCL1P/undotbs_01.dbf'
channel ch1: restoring datafile 00005 to /u01/data1/ORCL1P/TECBOS_01.dbf'
channel ch1: reading from backup piece db_ORCL1P_1061143038_2655_1_1
channel ch1: piece handle=db_ORCL1P_1061143038_2655_1_1 tag=PR_WEEKLY_INCR0
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:02:15
Finished restore at 17-JAN-21
datafile 1 switched to datafile copy
input datafile copy RECID=29 STAMP=1062076900 file name=/u01/data1/ORCL1P/dbfile/system_01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=30 STAMP=1062076900 file name=/u01/data1/ORCL1P/dbfile/sysaux_01.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=31 STAMP=1062076900 file name=/u01/data1/ORCL1P/dbfile/undotbs_01.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=32 STAMP=1062076900 file name=/u01/data1/ORCL1P/dbfile/TECBOS_01.dbf
Starting recover at 17-JAN-21
new media label is 72395 for piece db_ORCL1P_1061500640_2689_1_1
channel ch1: starting incremental datafile backup set restore
channel ch1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: /u01/data1/ORCL1P/dbfile/system_01.dbf
destination for restore of datafile 00002: /u01/data1/ORCL1P/dbfile/sysaux_01.dbf
destination for restore of datafile 00003: /u01/data1/ORCL1P/dbfile/undotbs_01.dbf
destination for restore of datafile 00005: /u01/data1/ORCL1P/dbfile/TECBOS_01.dbf
channel ch1: reading from backup piece db_ORCL1P_1061500640_2689_1_1
channel ch1: piece handle=db_ORCL1P_1061500640_2689_1_1 tag=PR_DAILY_INCR1
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:01:15
starting media recovery
channel ch2: starting archived log restore to default destination
channel ch2: restoring archived log
archived log thread=1 sequence=36892
channel ch2: restoring archived log
archived log thread=1 sequence=36893
channel ch2: restoring archived log
archived log thread=1 sequence=36894
channel ch2: restoring archived log
archived log thread=1 sequence=36895
channel ch2: restoring archived log
archived log thread=1 sequence=36896
channel ch2: restoring archived log
archived log thread=1 sequence=36897
channel ch2: restoring archived log
archived log thread=1 sequence=36898
channel ch2: restoring archived log
archived log thread=1 sequence=36899
channel ch2: restoring archived log
archived log thread=1 sequence=36900
channel ch2: restoring archived log
archived log thread=1 sequence=36901
channel ch2: restoring archived log
archived log thread=1 sequence=36902
channel ch2: restoring archived log
archived log thread=1 sequence=36903
channel ch2: restoring archived log
archived log thread=1 sequence=36904
channel ch2: restoring archived log
archived log thread=1 sequence=36905
channel ch2: restoring archived log
archived log thread=1 sequence=36906
channel ch2: reading from backup piece arch_ORCL1P_1061526864_2691_1_1
channel ch2: piece handle=arch_ORCL1P_1061526864_2691_1_1 tag=PR_DAILY_ARCH
channel ch2: restored backup piece 1
channel ch2: restore complete, elapsed time: 00:00:03
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36892.arc thread=1 sequence=36892
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36893.arc thread=1 sequence=36893
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36894.arc thread=1 sequence=36894
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36895.arc thread=1 sequence=36895
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36896.arc thread=1 sequence=36896
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36897.arc thread=1 sequence=36897
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36898.arc thread=1 sequence=36898
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36899.arc thread=1 sequence=36899
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36900.arc thread=1 sequence=36900
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36901.arc thread=1 sequence=36901
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36902.arc thread=1 sequence=36902
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36903.arc thread=1 sequence=36903
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36904.arc thread=1 sequence=36904
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36905.arc thread=1 sequence=36905
archived log file name=/u01/data1/ORCL1P/arc2/ORCL1P_1_997329966_36906.arc thread=1 sequence=36906
media recovery complete, elapsed time: 00:00:10
Finished recover at 17-JAN-21
database opened
new incarnation of database registered in recovery catalog
released channel: ch1
released channel: ch2
released channel: ch3

Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

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-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-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-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

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 Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
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