How to Restore the RMAN backup on different Server with Same Database Name. During this article we will discuss the way how to Restore RMAN backup to completely different Server with Same Database Name. We will perform this restoration process with same directory structure as our production environment on Oracle 19c Database. The production server and new server area unit running on an equivalent package and RDBMS patch sets.
RMAN Restoration to New Server with Same Database Name and Same Directory :
You will got to restore a information to a replacement server due to the subsequent reasons:
- confirming your disaster recovery strategy.
- cloning a database to a new server for UAT or or PRE-PRODUCTION.
- moving the database to a new server.
Environment :
Production:
Platform : Red Hat Enterprise Linux Server release 7.8
Server Name : PROD-SERVER.localdomain, IP: 192.168.0.111
DB Version : Oracle 19.0.0.0.0
File system : Normal
Database Name : PROD
DB_UNIQUE_NAME : PROD
Oracle Home Path: /u01/app/oracle/product/19.0.0/dbhome_1/
New Server:
Platform : Red Hat Enterprise Linux Server release 7.8
Server Name : NEW-SERVER.localdomain, IP: 192.168.0.121
DB Version : Oracle 19.0.0.0.0
File system : Normal
Database Name : PROD
DB_UNIQUE_NAME : PROD
Oracle Home Path: /u01/app/oracle/product/19.0.0/dbhome_1/Backup the Production Database :
You need to take a RMAN full backup with all archive logs or while not archive logs, Current control files, pfile. We are able to take the RMAN Backup in 2 ways. In this case we use RMAN online full Backup plus archive logs. If your database is in ARCHIVELOG mode, you can take RMAN online backup. For an online backup, you’ll take backup the database and all archive logs when the database is up and running. For an offline backup you need to take shutdown the database :
1. Take RMAN full backup :
[oracle@PROD-SERVER ~]$ . oraenv
ORACLE_SID = [PROD] ? PROD
The Oracle base remains unchanged with value /u01/app/oracle
[oracle@PROD-SERVER ~]$
[oracle@PROD-SERVER ~]$
[oracle@PROD-SERVER ~]$ rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Mon Mar 29 12:22:41 2021
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD (DBID=480289968)
RMAN> run
2> {
3> allocate channel ch1 device type disk;
4> crosscheck archivelog all;
5> backup as compressed backupset database format '/u02/backup/rman/Fullback_%T_%U'
6> plus archivelog format '/u02/backup/rman/Archive_%T_%U';
7> backup current controlfile format '/u02/backup/rman/Controlback_%T_%U';
8> release channel ch1;
9> }
using target database control file instead of recovery catalog
allocated channel: ch1
channel ch1: SID=469 device type=DISK
validation succeeded for archived log
archived log file name=/u01/archive/1_20_1068451635.dbf RECID=16 STAMP=1068464072
validation succeeded for archived log
archived log file name=/u01/archive/1_21_1068451635.dbf RECID=17 STAMP=1068464073
Crosschecked 2 objects
Starting backup at 29-MAR-21
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=20 RECID=16 STAMP=1068464072
input archived log thread=1 sequence=21 RECID=17 STAMP=1068464073
input archived log thread=1 sequence=23 RECID=18 STAMP=1068467069
channel ch1: starting piece 1 at 29-MAR-21
channel ch1: finished piece 1 at 29-MAR-21
piece handle=/u02/backup/rman/Archive_20210329_0hvqv0ru_1_1 tag=TAG20210329T122430 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 29-MAR-21
Starting backup at 29-MAR-21
channel ch1: starting compressed full datafile backup set
channel ch1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/PROD/system01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/PROD/sysaux01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/PROD/undotbs01.dbf
input datafile file number=00007 name=/u01/app/oracle/oradata/PROD/users01.dbf
channel ch1: starting piece 1 at 29-MAR-21
channel ch1: finished piece 1 at 29-MAR-21
piece handle=/u02/backup/rman/Fullback_20210329_0ivqv0s1_1_1 tag=TAG20210329T122432 comment=NONE
channel ch1: backup set complete, elapsed time: 00:03:55
Finished backup at 29-MAR-21
Starting backup at 29-MAR-21
current log archived
channel ch1: starting compressed archived log backup set
channel ch1: specifying archived log(s) in backup set
input archived log thread=1 sequence=24 RECID=19 STAMP=1068467309
channel ch1: starting piece 1 at 29-MAR-21
channel ch1: finished piece 1 at 29-MAR-21
piece handle=/u02/backup/rman/Archive_20210329_0jvqv13e_1_1 tag=TAG20210329T122829 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 29-MAR-21
Starting backup at 29-MAR-21
channel ch1: starting full datafile backup set
channel ch1: specifying datafile(s) in backup set
including current control file in backup set
channel ch1: starting piece 1 at 29-MAR-21
channel ch1: finished piece 1 at 29-MAR-21
piece handle=/u02/backup/rman/Controlback_20210329_0kvqv13g_1_1 tag=TAG20210329T122831 comment=NONE
channel ch1: backup set complete, elapsed time: 00:00:01
Finished backup at 29-MAR-21
Starting Control File and SPFILE Autobackup at 29-MAR-21
piece handle=/u01/app/oracle/fast_recovery_area/PROD/autobackup/2021_03_29/o1_mf_s_1068467318_j62ynzl0_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 29-MAR-21
released channel: ch1
RMAN>2. Take pfile Backup :
SQL> create pfile from spfile;
File created.
SQL>Transfer the Backup and pfile to New Server :
Once Backup completed we need to Transfer the Backup files, password file, pfile from Production to New Server.
[oracle@PROD-SERVER rman]$ pwd
/u02/backup/rman
[oracle@PROD-SERVER rman]$ ls -ltrh
total 298M
-rw-r-----. 1 oracle oinstall 1.7M Mar 29 12:24 Archive_20210329_0hvqv0ru_1_1
-rw-r-----. 1 oracle oinstall 286M Mar 29 12:28 Fullback_20210329_0ivqv0s1_1_1
-rw-r-----. 1 oracle oinstall 167K Mar 29 12:28 Archive_20210329_0jvqv13e_1_1
-rw-r-----. 1 oracle oinstall 11M Mar 29 12:28 Controlback_20210329_0kvqv13g_1_1
[oracle@PROD-SERVER rman]$
[oracle@PROD-SERVER rman]$ scp * oracle@192.168.0.121:/u02/backup/rman/
The authenticity of host '192.168.0.121 (192.168.0.121)' can't be established.
ECDSA key fingerprint is SHA256:KMocJJVCjmc/7q+zR4GCXMem7J1es/f1BZc80N2BUz8.
ECDSA key fingerprint is MD5:6b:e7:43:9f:06:0a:74:16:20:a3:05:b1:23:84:bb:60.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.0.121' (ECDSA) to the list of known hosts.
oracle@192.168.0.121's password:
Archive_20210329_0hvqv0ru_1_1 100% 1656KB 12.8MB/s 00:00
Archive_20210329_0jvqv13e_1_1 100% 167KB 11.5MB/s 00:00
Controlback_20210329_0kvqv13g_1_1 100% 10MB 12.8MB/s 00:00
Fullback_20210329_0ivqv0s1_1_1 100% 286MB 15.9MB/s 00:18
spfile_bkp_20210329_0lvqv13l_1_1 100% 112KB 2.9MB/s 00:00
[oracle@PROD-SERVER rman]$
[oracle@PROD-SERVER rman]$ cd $ORACLE_HOME/dbs
[oracle@PROD-SERVER dbs]$ scp orapwPROD initPROD.ora oracle@192.168.0.121:$ORACLE_HOME/dbs/
oracle@192.168.0.121's password:
orapwPROD 100% 2048 81.9KB/s 00:00
initPROD.ora 100% 3584 1.3MB/s 00:00
[oracle@PROD-SERVER dbs]$Add entry in /etc/oratab :
[oracle@NEW-SERVER ~]$ vi /etc/oratab
[oracle@NEW-SERVER ~]$
[oracle@NEW-SERVER ~]$ cat /etc/oratab
#
# This file is used by ORACLE utilities. It is created by root.sh
# and updated by either Database Configuration Assistant while creating
# a database or ASM Configuration Assistant while creating ASM instance.
# A colon, ':', is used as the field terminator. A new line terminates
# the entry. Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
# $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively. The third field indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
PROD:/u01/app/oracle/product/19.0.0/dbhome_1:NRestore Database at New Server :
Once all the backup files have been completely transferred to the New Server you could start the activity. Atfirst, startup the database using pfile, restore controlfile from backup, then restore the database at the New Server.
1. Check the init.ora file and create required directories :
[oracle@NEW-SERVER ~]$ cd $ORACLE_HOME/dbs
[oracle@NEW-SERVER dbs]$ ls -ltrh
total 16K
-rw-r--r--. 1 oracle oinstall 3.1K May 14 2015 init.ora
-rw-r--r--. 1 oracle oinstall 1.2K Mar 30 04:12 initPROD.ora
-rw-r-----. 1 oracle oinstall 2.0K Mar 30 04:12 orapwPROD
-rw-rw----. 1 oracle oinstall 1.6K Mar 30 04:15 hc_PROD.dat
[oracle@NEW-SERVER dbs]$
[oracle@NEW-SERVER dbs]$ cat initPROD.ora
PROD.__data_transfer_cache_size=0
PROD.__db_cache_size=486539264
PROD.__inmemory_ext_roarea=0
PROD.__inmemory_ext_rwarea=0
PROD.__java_pool_size=0
PROD.__large_pool_size=4194304
PROD.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
PROD.__pga_aggregate_target=314572800
PROD.__sga_target=759169024
PROD.__shared_io_pool_size=33554432
PROD.__shared_pool_size=222298112
PROD.__streams_pool_size=0
PROD.__unified_pga_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/PROD/adump'
*.audit_trail='db'
*.compatible='19.0.0'
*.control_files='/u01/app/oracle/oradata/PROD/control01.ctl','/u01/app/oracle/fast_recovery_area/PROD/control02.ctl'
*.db_block_size=8192
*.db_name='PROD'
*.db_recovery_file_dest='/u01/app/oracle/fast_recovery_area'
*.db_recovery_file_dest_size=8256m
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRODXDB)'
*.local_listener='LISTENER_PROD'
*.log_archive_dest_1='LOCATION=/u01/archive'
*.log_archive_format='%t_%s_%r.dbf'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.open_cursors=300
*.pga_aggregate_target=300m
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=724m
*.undo_tablespace='UNDOTBS1'
Here we use same directory structure on New environment as our production environment.
[oracle@NEW-SERVER ~]$ mkdir -p /u01/app/oracle/admin/PROD/adump/
[oracle@NEW-SERVER ~]$ mkdir -p /u01/app/oracle/oradata/PROD/
[oracle@NEW-SERVER ~]$ mkdir -p /u01/app/oracle/fast_recovery_area/PROD/
[oracle@NEW-SERVER ~]$ mkdir -p /u01/archive/2. Startup the Database in nomount stage, restore the controlfile and mount the Database :
[oracle@NEW-SERVER ~]$ . oraenv
ORACLE_SID = [PROD] ? PROD
The Oracle base remains unchanged with value /u01/app/oracle
[oracle@NEW-SERVER ~]$
[oracle@NEW-SERVER ~]$ rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Tue Mar 30 04:25:27 2021
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area 759165480 bytes
Fixed Size 8901160 bytes
Variable Size 226492416 bytes
Database Buffers 520093696 bytes
Redo Buffers 3678208 bytes
RMAN> restore controlfile from '/u02/backup/rman/Controlback_20210329_0kvqv13g_1_1';
Starting restore at 30-MAR-21
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=427 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=/u01/app/oracle/oradata/PROD/control01.ctl
output file name=/u01/app/oracle/fast_recovery_area/PROD/control02.ctl
Finished restore at 30-MAR-21
RMAN> alter database mount;
released channel: ORA_DISK_1
Statement processed
RMAN> report schema;
Starting implicit crosscheck backup at 30-MAR-21
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=434 device type=DISK
Crosschecked 16 objects
Finished implicit crosscheck backup at 30-MAR-21
Starting implicit crosscheck copy at 30-MAR-21
using channel ORA_DISK_1
Finished implicit crosscheck copy at 30-MAR-21
searching for all files in the recovery area
cataloging files...
no files cataloged
RMAN-06139: warning: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name PROD
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1 0 SYSTEM *** /u01/app/oracle/oradata/PROD/system01.dbf
3 0 SYSAUX *** /u01/app/oracle/oradata/PROD/sysaux01.dbf
4 0 UNDOTBS1 *** /u01/app/oracle/oradata/PROD/undotbs01.dbf
7 0 USERS *** /u01/app/oracle/oradata/PROD/users01.dbf
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
---- -------- -------------------- ----------- --------------------
1 20 TEMP 32767 /u01/app/oracle/oradata/PROD/temp01.dbf
RMAN>*** If the backuppieces area unit residing in a new location at the new host you’ll got to catalog them else not needed to set catalog.
For example, your production backup location is ‘/u02/backup/rman/‘ and New server backup location is ‘/u02/backup/‘ then you can follow below command to set catalog. Here, in this case we have residing all backup files on your New Server in same location as of Production Server.
RMAN> catalog start with '/u02/backup/';Restore the Database :
RMAN> run
2> {
3> allocate channel ch1 device type disk;
4> restore database;
5> switch datafile all;
6> switch tempfile all;
7> release channel ch1;
8> }
released channel: ORA_DISK_1
allocated channel: ch1
channel ch1: SID=434 device type=DISK
Starting restore at 30-MAR-21
channel ch1: starting datafile backup set restore
channel ch1: specifying datafile(s) to restore from backup set
channel ch1: restoring datafile 00001 to /u01/app/oracle/oradata/PROD/system01.dbf
channel ch1: restoring datafile 00003 to /u01/app/oracle/oradata/PROD/sysaux01.dbf
channel ch1: restoring datafile 00004 to /u01/app/oracle/oradata/PROD/undotbs01.dbf
channel ch1: restoring datafile 00007 to /u01/app/oracle/oradata/PROD/users01.dbf
channel ch1: reading from backup piece /u02/backup/rman/Fullback_20210329_0ivqv0s1_1_1
channel ch1: piece handle=/u02/backup/rman/Fullback_20210329_0ivqv0s1_1_1 tag=TAG20210329T122432
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:02:47
Finished restore at 30-MAR-21
released channel: ch1
RMAN>Recover the Database :
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
1 48.02M DISK 00:00:28 29-MAR-21
BP Key: 1 Status: EXPIRED Compressed: YES Tag: TAG20210329T093726
Piece Name: /u02/backup/Archive_20210329_02vqun2n_1_1
List of Archived Logs in backup set 1
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 5 2018082 29-MAR-21 2041340 29-MAR-21
1 6 2041340 29-MAR-21 2041610 29-MAR-21
1 7 2041610 29-MAR-21 2042050 29-MAR-21
1 8 2042050 29-MAR-21 2042054 29-MAR-21
1 9 2042054 29-MAR-21 2042057 29-MAR-21
1 10 2042057 29-MAR-21 2042060 29-MAR-21
1 11 2042060 29-MAR-21 2042064 29-MAR-21
1 12 2042064 29-MAR-21 2042067 29-MAR-21
1 13 2042067 29-MAR-21 2042070 29-MAR-21
1 14 2042070 29-MAR-21 2042073 29-MAR-21
1 15 2042073 29-MAR-21 2042076 29-MAR-21
1 16 2042076 29-MAR-21 2042145 29-MAR-21
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
2 48.20M DISK 00:00:29 29-MAR-21
BP Key: 2 Status: EXPIRED Compressed: YES Tag: TAG20210329T094105
Piece Name: /u02/backup/Archive_20210329_04vqun9h_1_1
List of Archived Logs in backup set 2
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 5 2018082 29-MAR-21 2041340 29-MAR-21
1 6 2041340 29-MAR-21 2041610 29-MAR-21
1 7 2041610 29-MAR-21 2042050 29-MAR-21
1 8 2042050 29-MAR-21 2042054 29-MAR-21
1 9 2042054 29-MAR-21 2042057 29-MAR-21
1 10 2042057 29-MAR-21 2042060 29-MAR-21
1 11 2042060 29-MAR-21 2042064 29-MAR-21
1 12 2042064 29-MAR-21 2042067 29-MAR-21
1 13 2042067 29-MAR-21 2042070 29-MAR-21
1 14 2042070 29-MAR-21 2042073 29-MAR-21
1 15 2042073 29-MAR-21 2042076 29-MAR-21
1 16 2042076 29-MAR-21 2042145 29-MAR-21
1 17 2042145 29-MAR-21 2043109 29-MAR-21
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
4 26.00K DISK 00:00:01 29-MAR-21
BP Key: 4 Status: EXPIRED Compressed: YES Tag: TAG20210329T094537
Piece Name: /u02/backup/Archive_20210329_06vquni1_1_1
List of Archived Logs in backup set 4
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 18 2043109 29-MAR-21 2043251 29-MAR-21
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
14 1.62M DISK 00:00:01 29-MAR-21
BP Key: 14 Status: AVAILABLE Compressed: YES Tag: TAG20210329T122430
Piece Name: /u02/backup/rman/Archive_20210329_0hvqv0ru_1_1
List of Archived Logs in backup set 14
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 20 2144572 29-MAR-21 2145428 29-MAR-21
1 21 2145428 29-MAR-21 2145431 29-MAR-21
1 23 2245569 29-MAR-21 2247446 29-MAR-21
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
16 166.50K DISK 00:00:00 29-MAR-21
BP Key: 16 Status: AVAILABLE Compressed: YES Tag: TAG20210329T122829
Piece Name: /u02/backup/rman/Archive_20210329_0jvqv13e_1_1
List of Archived Logs in backup set 16
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 24 2247446 29-MAR-21 2247775 29-MAR-21
RMAN>
RMAN>
RMAN> run
2> {
3> allocate channel ch1 device type disk;
4> recover database until sequence 25;
5> release channel ch1;
6> }
allocated channel: ch1
channel ch1: SID=434 device type=DISK
Starting recover at 30-MAR-21
starting media recovery
channel ch1: starting archived log restore to default destination
channel ch1: restoring archived log
archived log thread=1 sequence=24
channel ch1: reading from backup piece /u02/backup/rman/Archive_20210329_0jvqv13e_1_1
channel ch1: piece handle=/u02/backup/rman/Archive_20210329_0jvqv13e_1_1 tag=TAG20210329T122829
channel ch1: restored backup piece 1
channel ch1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/archive/1_24_1068451635.dbf thread=1 sequence=24
media recovery complete, elapsed time: 00:00:01
Finished recover at 30-MAR-21
released channel: ch1
RMAN>Now open the Database :
You must need to open the Database with RESETLOGS.
RMAN> alter database open;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql statement command at 03/30/2021 05:23:10
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
RMAN> alter database open RESETLOGS;
Statement processed
RMAN>Check Datafiles and Tempfiles :
SQL> select DBID, NAME, DB_UNIQUE_NAME, DATABASE_ROLE, OPEN_MODE from v$database;
DBID NAME DB_UNIQUE_NAME DATABASE_ROLE OPEN_MODE
---------- --------- ------------------------------ ---------------- --------------------
480289968 PROD PROD PRIMARY READ WRITE
SQL>
SQL> select FILE_ID, FILE_NAME, TABLESPACE_NAME, BYTES/1024/1024/1024 "Size In GB" from dba_data_files;
FILE_ID FILE_NAME TABLESPACE_NAME Size In GB
---------- -------------------------------------------------- ------------------------------ ----------
7 /u01/app/oracle/oradata/PROD/users01.dbf USERS .004882813
4 /u01/app/oracle/oradata/PROD/undotbs01.dbf UNDOTBS1 .263671875
1 /u01/app/oracle/oradata/PROD/system01.dbf SYSTEM .869140625
3 /u01/app/oracle/oradata/PROD/sysaux01.dbf SYSAUX .517578125
SQL> select FILE_ID, FILE_NAME, TABLESPACE_NAME, BYTES/1024/1024/1024 "Size In GB" from dba_temp_files;
FILE_ID FILE_NAME TABLESPACE_NAME Size In GB
---------- -------------------------------------------------- ------------------------------ ----------
1 /u01/app/oracle/oradata/PROD/temp01.dbf TEMP .01953125
SQL>
SQL> col MEMBER for a60
SQL> select * from v$logfile;
GROUP# STATUS TYPE MEMBER IS_ CON_ID
---------- ------- ------- ------------------------------------------------------------ --- ----------
3 ONLINE /u01/app/oracle/oradata/PROD/redo03.log NO 0
2 ONLINE /u01/app/oracle/oradata/PROD/redo02.log NO 0
1 ONLINE /u01/app/oracle/oradata/PROD/redo01.log NO 0
SQL>I hope my written content will helped you. Your suggestions/feedback are most welcome from orakldba.com.
Keep learning… Have a great day!!!
Please comment here for your any query related to above content. You can write to mail me through : orakldba@gmail.com.
im restoring with rman backup on same host with different DB name but getting error while mounting db .
ORA-01103: database name ‘TEST1’ in control file is not ‘TEST3’
i restored above controlfile from source backup.
when i try to recreate controlfile from scracth with script , im getting error :
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
‘/u02/app/oracle/oradata/TEST3/system01.dbf’
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
files are already not there bcz untill database is not mounted , we cannot execute restore command …….. any idea for thos
Hi Rehan
The location ‘/u02/app/oracle/oradata/TEST3/system01.dbf’ is not created in secondary database.
create directory
mkdir -p /u02/app/oracle/oradata/TEST3/
again try to restore database again.
Thanks