RMAN duplicate - instance parameters
Hello all.
I want to refresh the test environment with new production backup in oracle database 10g.
we have standby configured and its in sync with prod. So we took standby database latest backup and going to use to refresh the test environment.
prod is a 2 node rac and test is also a two node rac.
prod use different asm disk group and test uses different asm disk group.
so after taking backup, moved the backups to test environment.
Took backup of test spfile.
shut down the test both rac nodes after editing the parameter "cluster_database=false" parameter in spfile.
i am little confused about the the parameters to be removed and not to be removed in pfile to start the auxiliary instance.
we can remove parameters related to rac and these parameters also
cluster_database_instances=2
*.cluster_database=TRUE
kindly let me know
what value i can give for the parameters since the location is different in prod and test and how the duplicate command handle these parameter to duplicate the database
control_files
db_create_file_dest=
db_create_online_log_dest_1
db_create_online_log_dest_2
and i am going to use duplicate target database to <aux_db_name>
Regards
Pradeep,
Refresh rac database is not like refresh standalone database. You need to follow below steps
Step 1) Take the full backup of production database
* Backup of database , controlfile and pfile to backup location
* Comment the all rac related parameters and add change the control_files,db_file_name_convert,log_file_name_convert parameters as per test environment
* scp all backupfiles to any of the server in test environment
Step 2)
* connect to database which you want to refresh in test env
* change the cluster_database=false (so that we can start the database exclusively for this instance only)
* shutdown immediate and startup restrict nomount
* drop dtabase
Step 3)
* Remove the database information from ocr file
srvctl remove database -d <db_name>
Step 4)
* startup nomount pfile=<location>
* connect to rman
rman auxiliary /
* use duplicate command to create a database
Step 5)
* shutdown the database and make changes in pfile as remove all comments for all rac related parameters then create spfile from pfile
* and startup database
* use srvctl add database -d <db_name>
* create second instance in second node also
Similar Messages
-
Another RMAN duplicate problem - RAC database to single instance
Hi,
I have a problem with the RMAN duplicate procedure and was hoping someone can help.
I would like to create a duplicate of our production RAC database on a separate, stand-alone, database server on another site. This duplicate will be used for intensive querying by another business unit who I don't want to have access to our production database.
My procedure goes like this:
1. Create a disk (not ASM) based backup of the datafiles and any archived redo logs:
"run {
allocate channel d1 type disk;
backup format '/u02/stage/df_t%t_s%s_p%p' database plus archivelog delete input;
release channel d1;
2. Tar and scp these files to the same location on the stand-alone database server.
3. In the meantime, work has been happening on the production database and further archived redo logs have been generated. I don't really care about these logs for the purposes of the duplicate however, I just want to duplicate to the point of the recent backup. To do this, I run the following SQL to determine the sequence number that I should be duplicating up to:
"select max(sequence#), thread# from v$archived_log where deleted='YES' group by thread#;"
4. Duplicate the production database to the stand-alone database (all the SQL Net stuff is working).
"run {
set until sequence (value returned by above SQL statement);
duplicate target database to XXX;
However, my problem arises because I don't know how to handle the fact that there are two threads. I understand that each thread relates to one of the RAC instances, I just don't know which one to specify for the duplicate. We have a database service which the client application connects through, and that service runs on on or other of the instances. Should I just care about the logs from the instance where the service is currently running?
Am I even approaching this is the correct way?
I look forward to any help that people may be able to offer.
Regards,
PhilHi Werner,
Thanks again for your help, there is still something wrong though. "list backup of archivelog all;" shows:
BS Key Size Device Type Elapsed Time Completion Time
3784 202.34M DISK 00:00:08 28-OCT-09
BP Key: 3784 Status: AVAILABLE Compressed: NO Tag: TAG20091028T111718
Piece Name: /u02/stage/df_t701435838_s3820_p1
List of Archived Logs in backup set 3784
Thrd Seq Low SCN Low Time Next SCN Next Time
1 9746 569095777 28-OCT-09 569150229 28-OCT-09
1 9747 569150229 28-OCT-09 569187892 28-OCT-09
1 9748 569187892 28-OCT-09 569231956 28-OCT-09
1 9749 569231956 28-OCT-09 569259816 28-OCT-09
2 7931 569095774 28-OCT-09 569187902 28-OCT-09
2 7932 569187902 28-OCT-09 569259814 28-OCT-09
BS Key Size Device Type Elapsed Time Completion Time
3787 1.04M DISK 00:00:02 28-OCT-09
BP Key: 3787 Status: AVAILABLE Compressed: NO Tag: TAG20091028T112222
Piece Name: /u02/stage/df_t701436142_s3823_p1
List of Archived Logs in backup set 3787
Thrd Seq Low SCN Low Time Next SCN Next Time
1 9750 569259816 28-OCT-09 569261110 28-OCT-09
2 7933 569259814 28-OCT-09 569261108 28-OCT-09
You can see that the highest sequence number is 9750 of thread 1, and that the Low and Next SCNs are 569259816 and 56926111. However, when I look at the output of the RMAN duplicate command:
contents of Memory Script:
set until scn 569505448;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 28-OCT-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=39 devtype=DISK
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 4 needs more recovery to be consistent
ORA-01110: data file 4: '/u02/sca-standby/data/users.260.623418479'
RMAN-03002: failure of Duplicate Db command at 10/28/2009 16:12:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 7936 lowscn 569411744 found to restore
RMAN-06025: no backup of log thread 2 seq 7935 lowscn 569321987 found to restore
RMAN-06025: no backup of log thread 2 seq 7934 lowscn 569261108 found to restore
RMAN-06025: no backup of log thread 1 seq 9758 lowscn 569471890 found to restore
RMAN-06025: no backup of log thread 1 seq 9757 lowscn 569440076 found to restore
RMAN-06025: no backup of log thread 1 seq 9756 lowscn 569411439 found to restore
RMAN-06025: no backup of log thread 1 seq 9755 lowscn 569378529 found to restore
RMAN-06025: no backup of log thread 1 seq 9754 lowscn 569358970 found to restore
RMAN-06025: no backup of log thread 1 seq 9753 lowscn 569321882 found to restore
RMAN-06025: no backup of log thread 1 seq 9752 lowscn 569284238 found to restore
RMAN-06025: no backup of log thread 1 seq 9751 lowscn 569261110 found to restore
you can see that something is setting the recovery SCN to 569505448 which higher even then any of the archived logs mentioned above. If I select current_scn from the production database, this gives me 569528258 which is closer to the value which RMAN is expecting to recover to than any of the archived redo logs.
Can you think what might be causing RMAN to try to recover to this value? and why does it appear to be ignoring the SET UNTIL SEQUENCE command?
Cheers,
Phil -
RMAN DUPLICATE FOR STANDBY FROM ACTIVE DATABASE fails
Hello
I'm trying to use RMAN DUPLICATE to create a standby database using Oracle 11.2.0.3 with PSU 6 on HP-UX.
Primary is 2 node RAC. Standby is also 2 node RAC.
Standby database instance is started in nomount mode.
I use:
duplicate target database for standby from active database
spfile
<some spfile parameters>
with PFILE I get:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 12:41:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/01/2013 12:41:13
RMAN-11003: failure during parse/execution of SQL statement: alter system set spfile= '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-01565: error in identifying file '/opt/oracle/db11203/dbs/spfileCU1.ora'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
With SPFILE I get;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/01/2013 13:06:34
RMAN-05501: aborting duplication of target database
RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause
But I do have RMAN connexion to target database.
Thanks for your help.Here is the output beginning of the script which clearly shows that I'm always connected to target database:
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Oct 1 13:05:47 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: CU (DBID=1143962925)
connected to auxiliary database: CU (not mounted)
RMAN> set echo on
2> run
3> {
4> configure device type disk parallelism 10;
5> allocate channel pr1 type disk;
6> allocate channel pr2 type disk;
7> allocate channel pr3 type disk;
8> allocate channel pr4 type disk;
9> allocate channel pr5 type disk;
10> allocate channel pr6 type disk;
11> allocate channel pr7 type disk;
12> allocate channel pr8 type disk;
13> allocate channel pr9 type disk;
14> allocate channel pr10 type disk;
15> allocate auxiliary channel st1 type disk;
16> allocate auxiliary channel st2 type disk;
17> allocate auxiliary channel st3 type disk;
18> allocate auxiliary channel st4 type disk;
19> allocate auxiliary channel st5 type disk;
20> allocate auxiliary channel st6 type disk;
21> allocate auxiliary channel st7 type disk;
22> allocate auxiliary channel st8 type disk;
23> allocate auxiliary channel st9 type disk;
24> allocate auxiliary channel st10 type disk;
25> duplicate target database for standby from active database
26> spfile -
Oracle 11.2.0.2 SE-One 64-bit
Oracle Linux 5.6 x86-64
Question I had never considered. When performing an rman duplicate database with no NEWNAME parameters in sight, how does rman know how to set new names? There is something more than just the init parm “db_create_file_dest”.
The setup:
Server SRVPRD,
- ASM instance
- database DBPRD , has files in diskgroups SAN and SMALL
Server SRVDEV
- ASM instance
- database DBSTG, has files in diskgroups LARGE and SMALL
- database DBDEV, has files in diskgroups DEV_LARGE and DEV_SMALL
Shell script on SRVDEV to replicate DBPRD to DBSTG. Script ftp’s the rman backups from SRVPRD, shuts down the instance DBSTG, deletes all of its files using asmcmd commands, then executes the following:
echo "connect catalog rman/********@rmcat" > /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect target sys/********@srvprd" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect auxiliary /" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "run {" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "set until time \"to_date('`date +%Y-%m-%d` 12:38:00','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "duplicate target database to DBSTGVB;" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "}" >> /backup/dbstgvb/dbstgvb_refresh.rman
$ORACLE_HOME/bin/rman < /backup/dbstgvb/dbstgvb_refresh.rman
It runs perfectly and the files that were in the +SAN diskgroup in prod are correctly placed in +LARGE, and the files that were in +SMALL are correctly placed in +SMALL.
Now a new requirement to start doing the same for DBDEV. Made a copy of the script and changed all references from DBSTG to DBDEV. Equivalent changes in the string of asmcmd commands that delete the files, specifying the correct specific disk groups.
With this one, instead of mapping files from the two disk groups in DBPRD to the two diskgroups in DBDEV, they all get put into the one disk group +DEV_SMALL.
On DBSTG, we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest string +SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
set until scn 2984496;
set newname for datafile 1 to
"+SMALL/dbstgvb/system01.dbf";
set newname for datafile 2 to
"+SMALL/dbstgvb/sysaux01.dbf";
set newname for datafile 3 to
"+SMALL/dbstgvb/undotbs01.dbf";
set newname for datafile 4 to
"+SMALL/dbstgvb/users01.dbf";
set newname for datafile 5 to
"+LARGE/dbstgvb/perfstat_01.dbf";
set newname for datafile 6 to
"+LARGE/dbstgvb/dw_tbs1.dbf";
restore
clone database
executing Memory Script
On DBDEV we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest string +DEV_SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
set until scn 2984496;
set newname for clone datafile 1 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 4 to new;
set newname for clone datafile 5 to new;
set newname for clone datafile 6 to new;
restore
clone database
executing Memory Script
So, I am missing exactly how it is that in the replicate to DBSTG, it is able to correctly identify that files coming from prod diskgroup SAN correctly mapped to diskgroup LARGE? And further, why that mechanism did not work to map to +DEV_LARGE when replicating to DBDEV. In DBDEV it seems to be controlled entirely by db_create_file_dest, but in DBSTG there seems to be something that I am missing that allows the greater complexity of mapping two diskgroups.Interesting side observation
In making sure all files ended up in the correct location I started noticing differences in the FQFN from the source db to the target. Doing an asmcmd 'ls -l' on both systems, I discovered things like this:
On the source db, we have
DW_TBS1.dbf => +SAN/DBPRD/DATAFILE/DW_TBS.278.755044731
while on the target it came out
dw_tbs1.dbf => +LARGE/DBSTG/DATAFILE/DW.259.821974713
or
STAGE_CUST_ACCT_I1.ora => +SAN/DBPRD/DATAFILE/STAGE_CUST_ACCT_I.262.754925519
vs
stage_cust_acct_i1.ora => +LARGE/DBSTG/DATAFILE/STG_CUST_ACCT_IDX.266.822009311
Obviously not an operational problem, but a curiosity about the algorithm to generate the base part of the FQFN, and why it generated different names on different systems. -
I was executing RMAN DUPLICATE and received this error?
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/08/2007 13:41:22
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01078: failure in processing system parameters
RMAN-04017: startup error description: LRM-00109: could not open parameter file
'/u01/app/oracle/product/10.2.0/dbs/initDPDEVUG.ora'
Anybody knows how to fix this error?I had this file only in CLONED databae $ORACLE_HOME/dbs. I copy this file into SOURCE database $ORACLE_HOME/dbs. Since duplicate initiation going from SOURCE to CLONED. May this is problem?
I am going to re start Clone process and let you know if this was the case -
Oracle 10.2.0.4 RMAN Duplicate without a Recovery Catalog
Production Backups are Tuesday - Sunday at 22:00:
RUN {
ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
CROSSCHECK ARCHIVELOG ALL;
CROSSCHECK BACKUP;
DELETE NOPROMPT COPY OF ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE-2';
DELETE NOPROMPT BACKUP;
BACKUP DATABASE PLUS ARCHIVELOG;
CROSSCHECK BACKUP;
RELEASE CHANNEL c1;
LIST BACKUPSET;
EOF
I have these files sent over to the development server on Wednesday, RMANbackup (log), backupset and the controlfile:
rcp -rp /backup/$1/flash_recovery/$2/RMANbackup/* kacdb4:/backup/common/flash_recovery/$2/RMANbackup
rcp -rp /backup/$1/flash_recovery/$2/backupset/* kacdb4:/backup/common/flash_recovery/$2/backupset
rcp -rp /backup/$1/flash_recovery/$2/controlfile/* kacdb4:/backup/common/flash_recovery/$2/controlfile
I run the RMAN Duplicate and the database gets created with no problems!
The question is: If I wait unit Thursday, to run the duplicate script, I get the traditional RMAN errors: RMAN-03002, RMAN-03015, RMAN-06026, RMAN-06023:
Starting restore at 20-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/20/2012 10:05:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
Is this because of the 'SYSDATE-2' in the RMAN runlist? Does RMAN connect back to the target and it does not find the logs, because they've been deleted, it aborts the duplicate? I've shipped over the backupset and controlfile of the scn I'm using in the duplicate runlist all is there? If I'm trying to cleanup the archive area, would'nt 'delete expired archivelog all' in my runlist, be better than using the 'SYSDATE-2'?
Or is it because of this database parameter:
control_file_record_keep_time= 7, should I set this to say 14?
Is it one of these RMAN configurations:
Retention Policy to Redundancy 1, should I set this to say 7?
Datafile Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space which is precious
Archivelog Backup Copies for Device Type Disk to 1, to say 3, this takes up disk space too
Archive deletion policy to none change this to the other option?
I've tested this a few times now, and always fails if the dupicate is not done the next day.
If I have to create a development database on a Friday from Tuesday's copy FROM TAPE, I will get the error, because the files are no longer on disk.
What can I do to ensure that I can create an RMAN duplicate any day of the week from Tuesday to Sunday?
Look forward to your answer.
Please let me know if I left any details out that you may need.
Sincerely,
Elizabeth BurnsHi Valentin,
Here is the good duplicate log from Monday 9/24:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120924.log
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:32 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:41 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Sep 24 18:07:43 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 24-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 24-SEP-12
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /usr/local/OLlinks/dupdb/system/system01.dbf
restoring datafile 00002 to /usr/local/OLlinks/dupdb/system/undotbs01.dbf
restoring datafile 00003 to /usr/local/OLlinks/dupdb/system/sysaux01.dbf
restoring datafile 00004 to /usr/local/OLlinks/dupdb/system/users01.dbf
restoring datafile 00005 to /usr/local/OLlinks/dupdb/data01/data1.dbf
restoring datafile 00006 to /usr/local/OLlinks/dupdb/index01/index1.dbf
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T1
01837_860txxs8_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_nnndf_TAG20120924T101837_860txxs8_.bkp tag=TAG
20120924T101837
channel aux1: restore complete, elapsed time: 00:00:47
Finished restore at 24-SEP-12
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858918 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858918 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858918 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
set until scn 211054288;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 24-SEP-12
starting media recovery
channel aux1: starting archive log restore to default destination
channel aux1: restoring archive log
archive log thread=1 sequence=1403
channel aux1: reading from backup piece /usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T1
01923_860tzfd7_.bkp
channel aux1: restored backup piece 1
piece handle=/usr/local/OLlinks/kedsp/flash_recovery/KEDSP/backupset/2012_09_24/o1_mf_annnn_TAG20120924T101923_860tzfd7_.bkp tag=TAG
20120924T101923
channel aux1: restore complete, elapsed time: 00:00:05
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc thread=1 sequenc
e=1403
channel clone_default: deleting archive log(s)
archive log filename=/usr/local/OLlinks/dupdb/flash_recovery/DUPDB/archivelog/2012_09_24/o1_mf_1_1403_861phcc3_.arc recid=1 stamp=79
4858923
media recovery complete, elapsed time: 00:00:02
Finished recover at 24-SEP-12
contents of Memory Script:
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora';
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUPDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '/usr/local/OLlinks/dupdb/redo01/redo0101.log', '/usr/local/OLlinks/dupdb/redo02/redo0102.log', '/usr/local/OLlinks/dup
db/redo03/redo0103.log' ) SIZE 50 M ,
GROUP 2 ( '/usr/local/OLlinks/dupdb/redo01/redo0201.log', '/usr/local/OLlinks/dupdb/redo02/redo0202.log', '/usr/local/OLlinks/dup
db/redo03/redo0203.log' ) SIZE 50 M ,
GROUP 3 ( '/usr/local/OLlinks/dupdb/redo01/redo0301.log', '/usr/local/OLlinks/dupdb/redo02/redo0302.log', '/usr/local/OLlinks/dup
db/redo03/redo0303.log' ) SIZE 50 M ,
GROUP 4 ( '/usr/local/OLlinks/dupdb/redo01/redo0401.log', '/usr/local/OLlinks/dupdb/redo02/redo0402.log', '/usr/local/OLlinks/dup
db/redo03/redo0403.log' ) SIZE 50 M ,
GROUP 5 ( '/usr/local/OLlinks/dupdb/redo01/redo0501.log', '/usr/local/OLlinks/dupdb/redo02/redo0502.log', '/usr/local/OLlinks/dup
db/redo03/redo0503.log' ) SIZE 50 M ,
GROUP 6 ( '/usr/local/OLlinks/dupdb/redo01/redo0601.log', '/usr/local/OLlinks/dupdb/redo02/redo0602.log', '/usr/local/OLlinks/dup
db/redo03/redo0603.log' ) SIZE 50 M ,
GROUP 7 ( '/usr/local/OLlinks/dupdb/redo01/redo0701.log', '/usr/local/OLlinks/dupdb/redo02/redo0702.log', '/usr/local/OLlinks/dup
db/redo03/redo0703.log' ) SIZE 50 M ,
GROUP 8 ( '/usr/local/OLlinks/dupdb/redo01/redo0801.log', '/usr/local/OLlinks/dupdb/redo02/redo0802.log', '/usr/local/OLlinks/dup
db/redo03/redo0803.log' ) SIZE 50 M ,
GROUP 9 ( '/usr/local/OLlinks/dupdb/redo01/redo0901.log', '/usr/local/OLlinks/dupdb/redo02/redo0902.log', '/usr/local/OLlinks/dup
db/redo03/redo0903.log' ) SIZE 50 M ,
GROUP 10 ( '/usr/local/OLlinks/dupdb/redo01/redo1001.log', '/usr/local/OLlinks/dupdb/redo02/redo1002.log', '/usr/local/OLlinks/dup
db/redo03/redo1003.log' ) SIZE 50 M
DATAFILE
'/usr/local/OLlinks/dupdb/system/system01.dbf'
CHARACTER SET WE8ISO8859P1
contents of Memory Script:
set newname for tempfile 1 to
"/usr/local/OLlinks/dupdb/temp/temp01.dbf";
switch clone tempfile all;
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/system/users01.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/data01/data1.dbf";
catalog clone datafilecopy "/usr/local/OLlinks/dupdb/index01/index1.dbf";
switch clone datafile all;
executing Memory Script
executing command: SET NEWNAME
renamed temporary file 1 to /usr/local/OLlinks/dupdb/temp/temp01.dbf in control file
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf recid=1 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf recid=2 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/system/users01.dbf recid=3 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/data01/data1.dbf recid=4 stamp=794858932
cataloged datafile copy
datafile copy filename=/usr/local/OLlinks/dupdb/index01/index1.dbf recid=5 stamp=794858932
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=794858932 filename=/usr/local/OLlinks/dupdb/system/users01.dbf
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=794858932 filename=/usr/local/OLlinks/dupdb/data01/data1.dbf
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=794858932 filename=/usr/local/OLlinks/dupdb/index01/index1.dbf
contents of Memory Script:
Alter clone database open resetlogs;
executing Memory Script
database opened
Finished Duplicate Db at 24-SEP-12
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Sep 24 18:09:39 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
User altered.
User altered.
User altered.
User altered.
Database closed.
Database dismounted.
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Database mounted.
Database altered.
Database altered.
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Here is the duplicate log from this morning:
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs-> more clone_database_from_common_20120926.log
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:31 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
SQL> spool /u01/app/oracle/KAC_SCRIPTS/dupdb/logs/DBShutdown.log
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> spool off
SQL> exit;
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:42 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
File created.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:45 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: KEDSP (DBID=3370721566)
connected to auxiliary database: DUPDB (not mounted)
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4>
5> set until scn 211054288;
6> DUPLICATE TARGET DATABASE TO dupdb
7> PFILE=/u01/app/oracle/product/10.2.0/db_1/dbs/initdupdb.ora
8> DB_FILE_NAME_CONVERT=('/usr/local/OLlinks/kedsp/system/','/usr/local/OLlinks/dupdb/system/','/usr/local/OLlinks/kedsp/temp/','/us
r/local/OLlinks/dupdb/temp/','/usr/local/OLlinks/kedsp/data01/','/usr/local/OLlinks/dupdb/data01/','/usr/local/OLlinks/kedsp/index01
/','/usr/
9> local/OLlinks/dupdb/index01/')
10> LOGFILE
11> GROUP 1 (
12> '/usr/local/OLlinks/dupdb/redo01/redo0101.log',
13> '/usr/local/OLlinks/dupdb/redo02/redo0102.log',
14> '/usr/local/OLlinks/dupdb/redo03/redo0103.log'
15> ) SIZE 50M,
16> GROUP 2 (
17> '/usr/local/OLlinks/dupdb/redo01/redo0201.log',
18> '/usr/local/OLlinks/dupdb/redo02/redo0202.log',
19> '/usr/local/OLlinks/dupdb/redo03/redo0203.log'
20> ) SIZE 50M,
21> GROUP 3 (
22> '/usr/local/OLlinks/dupdb/redo01/redo0301.log',
23> '/usr/local/OLlinks/dupdb/redo02/redo0302.log',
24> '/usr/local/OLlinks/dupdb/redo03/redo0303.log'
25> ) SIZE 50M,
26> GROUP 4 (
27> '/usr/local/OLlinks/dupdb/redo01/redo0401.log',
28> '/usr/local/OLlinks/dupdb/redo02/redo0402.log',
29> '/usr/local/OLlinks/dupdb/redo03/redo0403.log'
30> ) SIZE 50M,
31> GROUP 5 (
32> '/usr/local/OLlinks/dupdb/redo01/redo0501.log',
33> '/usr/local/OLlinks/dupdb/redo02/redo0502.log',
34> '/usr/local/OLlinks/dupdb/redo03/redo0503.log'
35> ) SIZE 50M,
36> GROUP 6 (
37> '/usr/local/OLlinks/dupdb/redo01/redo0601.log',
38> '/usr/local/OLlinks/dupdb/redo02/redo0602.log',
39> '/usr/local/OLlinks/dupdb/redo03/redo0603.log'
40> ) SIZE 50M,
41> GROUP 7 (
42> '/usr/local/OLlinks/dupdb/redo01/redo0701.log',
43> '/usr/local/OLlinks/dupdb/redo02/redo0702.log',
44> '/usr/local/OLlinks/dupdb/redo03/redo0703.log'
45> ) SIZE 50M,
46> GROUP 8 (
47> '/usr/local/OLlinks/dupdb/redo01/redo0801.log',
48> '/usr/local/OLlinks/dupdb/redo02/redo0802.log',
49> '/usr/local/OLlinks/dupdb/redo03/redo0803.log'
50> ) SIZE 50M,
51> GROUP 9 (
52> '/usr/local/OLlinks/dupdb/redo01/redo0901.log',
53> '/usr/local/OLlinks/dupdb/redo02/redo0902.log',
54> '/usr/local/OLlinks/dupdb/redo03/redo0903.log'
55> ) SIZE 50M,
56> GROUP 10 (
57> '/usr/local/OLlinks/dupdb/redo01/redo1001.log',
58> '/usr/local/OLlinks/dupdb/redo02/redo1002.log',
59> '/usr/local/OLlinks/dupdb/redo03/redo1003.log'
60> ) SIZE 50M
61> ;
62> }
63>
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=242 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 26-SEP-12
contents of Memory Script:
set until scn 211054288;
set newname for datafile 1 to
"/usr/local/OLlinks/dupdb/system/system01.dbf";
set newname for datafile 2 to
"/usr/local/OLlinks/dupdb/system/undotbs01.dbf";
set newname for datafile 3 to
"/usr/local/OLlinks/dupdb/system/sysaux01.dbf";
set newname for datafile 4 to
"/usr/local/OLlinks/dupdb/system/users01.dbf";
set newname for datafile 5 to
"/usr/local/OLlinks/dupdb/data01/data1.dbf";
set newname for datafile 6 to
"/usr/local/OLlinks/dupdb/index01/index1.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 26-SEP-12
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/26/2012 08:28:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
Recovery Manager complete.
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 26 08:28:53 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected.
alter user sys identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user system identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user dbsnmp identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
alter user sysman identified by "Sco_tch!1"
ERROR at line 1:
ORA-01109: database not open
ORA-01507: database not mounted
ORACLE instance shut down.
ORACLE instance started.
Total System Global Area 134217728 bytes
Fixed Size 2054448 bytes
Variable Size 79693520 bytes
Database Buffers 50331648 bytes
Redo Buffers 2138112 bytes
ORA-00205: error in identifying control file, check alert log for more info
alter database noarchivelog
ERROR at line 1:
ORA-01507: database not mounted
alter database open
ERROR at line 1:
ORA-01507: database not mounted
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production
oracle:dupdb@kacdb4:/u01/app/oracle/KAC_SCRIPTS/dupdb/logs->
Please let me know if you need anything else.
Sincerely,
Elizabeth -
Database refresh without using RMAN duplicate
Hi All,
I am planning to refresh my test instance to a PIT using RMAN backups from PROD. I would like to know the process without connecting to PROD database and without using RMAN duplicate command.
Thanks.imran khan wrote:
Can you please show the demo first then we will discuss on it more.. what if the folk wants to refresh it ten times then we have to change the database name ten times using NID?
>Can you please show the demo first then we will discuss on it more.. what if the folk wants to refresh it ten times then we have to change the database name ten times using NID?
1) You use nid only to change the dbid.
2) I have done this type of cloning much more than 50 times.
3) As Iordan Iotzov pointed out, in 11gR2 you can run DUPLICATE database without being connected to the PROD
Here is a sample code of how to do it assuming both file system are the same:
# -- RMAN Restore to another server
rman <<EOF2
CONNECT TARGET /;
STARTUP NOMOUNT
SET DBID 987654321;
CONNECT CATALOG rman/rman@rcvcat
RUN {
SET UNTIL SEQUENCE=5678 THREAD=1;
ALLOCATE CHANNEL ch0 DEVICE TYPE DISK;
RESTORE CONTROLFILE;
ALTER DATABASE MOUNT;
RUN
SET UNTIL SEQUENCE=5678 THREAD=1;
ALLOCATE CHANNEL ch0 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
RESTORE DATABASE;
RECOVER DATABASE;
EXIT;
EOF2:p -
ORA-01017 when RMAN duplicate from active database
Hello, ORACLE guru's!
I've got some trouble trying to duplicate DB via RMAN duplicate from active database.
The script is simple:
run
allocate channel ch1 device type disk;
allocate auxiliary channel aux1 device type disk;
duplicate target database to mydb from active database;
The problem is in this statement:
Starting backup at 15-JAN-14
channel ch1: starting datafile copy
copying current control file
Oracle instance started
Total System Global Area 10689474560 bytes
Fixed Size 2237776 bytes
Variable Size 4227861168 bytes
Database Buffers 6442450944 bytes
Redo Buffers 16924672 bytes
contents of Memory Script:
sql clone "alter system set db_name =
''mydb'' comment=
''Reset to original value by RMAN'' scope=spfile";
sql clone "alter system reset db_unique_name scope=spfile";
shutdown clone immediate;
executing Memory Script
sql statement: alter system set db_name = ''mydb'' comment= ''Reset to original value by RMAN'' scope=spfile
sql statement: alter system reset db_unique_name scope=spfile
Oracle instance shut down
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/15/2014 12:16:07
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ch1 channel at 01/15/2014 12:15:57
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server
RMAN>
RMAN>change:
export ORACLE_SID="mydb"
export ORACLE_HOME="/u/app/oracle/product/11.2/db_1"
FILE1 = "/u/app/oracle/product/11.2/db_1/bin/"
cat > $FILE1/sqlplus sys/karen as sysdba << EOF
startup nomount;
exit;
EOF
cat > $FILE1/rman target sys/karen@mytargetdb auxiliary sys/karen@mydb << EOF
run
allocate channel ch1 device type disk;
allocate auxiliary channel aux1 device type disk;
duplicate target database to mydb from active database;
EOF
tell us if it works and again, from what host are you running the script? -
Why do we need a connection to the Source DB for RMAN DUPLICATE ?
Version Info: 11.2.0.3/RHEL 5.8
We want to clone a Production DB to a test DB.
Prod DB size: 100gb
We are going to take an RMAN full backup (Hot Backup which includes Archivelogs ) and scp the backup pieces to the Test DB server.
In the Test server , we will be running RMAN DUPLICATE command after connecting like below
rman target sys/passwd@SID_OF_SOURCE_DB auxiliary /We have everything we need in test server to do the cloning ie. all the RMAN Backup pieces. Then why does RMAN connect to the source DB ?from [url http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm] here
Backup-based duplication without a target connection
RMAN creates duplicate files from pre-existing RMAN backups and copies. The DUPLICATE command must have been issued with the DATABASE clause. This form requires a connection to an auxiliary instance and a recovery catalog.
This mode is useful when the target database is not available or a connection to it is not desirable (as mandated by security policy restrictions or a firewall).
Backup-based duplication without connection to target and recovery catalog
RMAN creates duplicate files from RMAN backups and copies that were placed in a designated BACKUP LOCATION.http://dbaregistry.blogspot.com/2011/04/rman-duplicate-without-connecting-to.html
Edited by: swapnil kambli on May 21, 2013 1:36 AM -
Cleaning up ASM disk group after failed rman duplicate session?
I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
Thanks.Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
SQL> desc v$asm_file
Name Null? Type
GROUP_NUMBER NUMBER
FILE_NUMBER NUMBER
COMPOUND_INDEX NUMBER
INCARNATION NUMBER
BLOCK_SIZE NUMBER
BLOCKS NUMBER
BYTES NUMBER
SPACE NUMBER
TYPE VARCHAR2(64)
REDUNDANCY VARCHAR2(6)
STRIPED VARCHAR2(6)
CREATION_DATE DATE
MODIFICATION_DATE
This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in... -
关于Rman Duplicate from active databse 到一个新库中出现的问题
OS：
[oravis@prcsgidb1 dbs]$ uname -a
Linux xxxx 2.6.32-200.13.1.el5uek #1 SMP Wed Jul 27 21:02:33 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
DATABASE：单机
target: hzdbacoe 11.2.0.3
auxiliary: dbacoe 11.2.0.3
发生情景
将旧库home目录Clone到同机另一文件夹并做完所有操作后，欲进行duplicate
在新home目录中
1.新建pfile initdbacoe.ora如下
DB_NAME=dbacoe
DB_FILE_NAME_CONVERT=(/u03/apps/oracle/oradata/hzdbacoe/,/u03/app/oracle/oradata/dbacoe/)
LOG_FILE_NAME_CONVERT=(/u03/apps/oracle/oradata/hzdbacoe/,/u03/app/oracle/oradata/dbacoe/)
2.新建orapw file=orapwdbacoe.ora password=oracle
3.mkdir -p $ORACLE_BASE/oradata/dbacoe并赋好权限
4.根据该pfile起至 nomount阶段instance为dbacoe
5.在该目录的listener.ora中新建一个监听，并将dbacoe服务注册进入该监听，端口为1530
在原库所在环境变量中
修改tnsname.ora 加入dbacoe信息如下：
dbacoe =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxxx.xxx.xxx)(PORT = 1530))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dbacoe)
[]rman
RMAN>connect target sys/allen1218
connected to target database: HZDBACOE (DBID=2102554453)
RMAN>connect auxiliary sys/oracle@dbacoe
connected to auxiliary database: DBACOE (not mounted)
RMAN>duplicate target database to dbacoe from active database nofilenamecheck;(ps:之前第一次有运行过一次duplicate，未加nofilenamecheck，报错后加上）
结果在复制oradata文件时报错如下
Starting backup at 20121107 18:22:54
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=178 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=190 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=201 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=2 device type=DISK
channel ORA_DISK_1: starting datafile copy
copying current control file
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/07/2012 18:22:55
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/07/2012 18:22:55
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server
oradata文件夹属主信息如下
[oravis@prcsgidb1 oracle]$ ls -ltr
total 20
drwx------ 3 oravis dba 4096 Nov 7 14:54 product
drwxr-xr-x 2 oravis dba 4096 Nov 7 15:41 checkpoints
drwxr-x--- 3 oravis dba 4096 Nov 7 16:12 cfgtoollogs
drwx------ 3 oravis dba 4096 Nov 7 17:11 oradata
drwxrwxr-x 4 oravis dba 4096 Nov 7 17:23 diag
我知道错误非常明显，但我不知道是哪个username/password出错，这之间的过程只有建orapw 文件时才有password设置进入，之前的home也将属主均改为oravis了。找到原因了，还是官方文档看得不仔细
2.At the RMAN prompt, run CONNECT commands for the database instances required for your duplication technique:
◦For active database duplication, you must connect to the source database as TARGET and to the auxiliary instance as AUXILIARY. You must use the same SYSDBA password for both instances and must supply the net service name to connect to the AUXILIARY instance. A recovery catalog connection is optional
唉，把大量时间花在组织提问上了，希望大家引以为戒。有时候，更该去清洗一下思路，重新着手 -
RMAN duplicate from RAC with ASM to RAC with ASM
I'm still reading and trying to figure out how to duplicate...and I'm finding that there are some extra considerations you have to work with with doing a RAC system.
Does anyone have any good links to articles/docs that spell out what to do in this scenario?
I'm wanting to duplicate from tape backups, using NO connectivity to the source/target....
My tape backups do include the spfile and control files (autobackup) from the source.
Thank you in advance,
cayennedamorgan wrote:
Possibly you are confusing a database with a database.
A RAC database is a just a database. What is different is the instances, the clusterware, and the storage: For example ASM.
A backup is a backup is a backup.
Can you be more specific about what you are trying to do, on what hardware, operating system, version, and edition.
RMAN can not create an instance either RAC or stand-alone.Thank you for the reply.
I have my source system, OS = RHEL5, running Oracle 11Gr2...5 node RAC cluster.
I'm doing RMAN backups to tape...hourly arch. logs, Daily incremental lvl=1 backups and weekly incremental lvl=0
None of the tape backups have ever been tested for restoring...and I've never restored a database myself before, total noob here.
I have a test area I've set up. I have a 2 node RAC cluster, running 11Gr2 and OS=RHEL5.
The tape is accessible from both systems.
I am wanting to test the tape backups...and thought the RMAN DUPLICATE process would be the way to go.
I am wanting to NOT connect to the source database...trying to simulate somewhat of a disaster recovery scenario. I'm only wanting to use tape backup, and the test area for the auxiliary instance.
So far what I've seen I need to learn to do is something like:
1. Create a password file for new aux database to be duplicated to
2. Establish Net connectivity...
3. Create initial parameter file for aux instance
Due to a bug in note:334899.1, add this (because of RAC system)
norecovery_through_resetlogs=TRUE
4. Start aux instance NOMOUNT
Everything I'm reading though...is basically doing this from single instance to single instance...and what little info I've seen on doing it from RAC, indicates there are some differences. The "_no_recovery_through_resetlogs=TRUE" is one thing I found...but wondering what else.
Also, so many of the examples I'm finding...are doing the duplication connecting to the target/source...and also doing backups to disk rather than tape...
Right now, I'm at #1...trying to figure what to put into an init pfile...I'm seeing DB_name, which will be the same as the one I'm cloning from.
I'm not sure what else....
I'm wondering if this is necessary..since on the tape backups from the source...I backup the SPFILE...can that not be used somehow in this?
I'm seeing for the init file, examples show that I need to put in entries for control files and redo logs....if the source system was down and gone...how would I know where these were on the old system? This isn't documented anywhere....is there a way to do this if you didn't know.
If not..guess I need to go through all systems and document the layouts of where everything is located.
Also...most examples I'm finding, in addition to being single instance backup and restore/duplication...they are all using regular file systems....not much to go on with using ASM.
Anyway, I'm trying to learn here...and am having trouble finding examples to go from that match my setup.
Thank you in advance,
cayenne -
Oracle11gR2 RAC&DataGuard rman duplicate
RAC 環境の data guard でちょっと悩んでいます。
data guard というより、rman と tnsnames.ora の関係あたりです。
結果的に実行したいことは、rman での接続の後の duplicate だけです。
（プライマリ・データベースの複製）
rman での接続がそもそも正常でなく、何が原因か分からない状態です。
詳しい方いれば教えていただきたいと思います。
よろしくお願い致します。
▼
実行時の画面出力：
standby 側 db が open の時：
export ORACLE_SID=HPYMUSIC1
rman target / auxiliary sys/passw@west1_DGMGRL
[oracle@tokyo1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 16:48:32 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
補助データベース: WEST (DBID=3187536000)に接続されました
rman target sys/passw@west1_DGMGRL auxiliary /
[oracle@tokyo1 ~]$ rman target sys/passw@west1_DGMGRL auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 16:50:25 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: WEST (データベースID=3187536000)に接続されました
補助データベース: EAST (DBID=3804390391)に接続されました
rman target / auxiliary sys/passw@west1
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 16:51:53 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
補助データベース: WEST (DBID=3187536000)に接続されました
▼ 上記全てにおいて、以下の状態にして、その後、duplicate をしたいというだけなのですが。。
補助データベース: WEST (DBID=3187536000)に接続されました(マウントされていません)
↓
↓ それが、以下のようにできない。。
↓
○ standby db が offline であるとします。
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 OFFLINE OFFLINE
2 ONLINE OFFLINE
○ startup nomount します。
ps -ef|egrep -i ora_
export ORACLE_SID=HPYMUSIC1
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby.txt'
[oracle@osaka1 ~]$ ps -ef|egrep -i ora_
oracle 4487 4303 0 17:24 pts/1 00:00:00 egrep -i ora_
[oracle@osaka1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@osaka1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 水 8月 7 17:24:35 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL>
SQL> startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby.txt'
ORACLEインスタンスが起動しました。
Total System Global Area 814227456 bytes
Fixed Size 2217752 bytes
Variable Size 612370664 bytes
Database Buffers 192937984 bytes
Redo Buffers 6701056 bytes
SQL>
SQL>
● db open の時に成功していたコマンドラインが失敗してしまう。
[oracle@tokyo1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:27:36 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
[oracle@tokyo1 ~]$ rman target sys/passw@west1_DGMGRL auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:29:54 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04005: ターゲット・データベースからのエラー:
ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:30:07 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
● db open から stop し、starup nomount pfile したとします。
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 ONLINE ONLINE osaka1 Open
2 ONLINE OFFLINE
[oracle@osaka1 ~]$ srvctl stop database -d west
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 OFFLINE OFFLINE Instance Shutdown
2 ONLINE OFFLINE
ps -ef|egrep -i ora_
export ORACLE_SID=HPYMUSIC1
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby.txt'
[oracle@osaka1 ~]$ id
uid=54321(oracle) gid=54321(oinstall) 所属グループ=54321(oinstall),1101(oper),1201(asmdba),54322(dba)
[oracle@osaka1 ~]$ ps -ef|egrep -i ora_
oracle 6137 4303 0 17:44 pts/1 00:00:00 egrep -i ora_
[oracle@osaka1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@osaka1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 水 8月 7 17:45:40 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL> startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby.txt'
ORACLEインスタンスが起動しました。
Total System Global Area 814227456 bytes
Fixed Size 2217752 bytes
Variable Size 612370664 bytes
Database Buffers 192937984 bytes
Redo Buffers 6701056 bytes
SQL>
SQL>
↓
↓
↓ ▼ 結果、エラーになってしまう。
↓
↓
[oracle@tokyo1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:47:21 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
[oracle@tokyo1 ~]$ rman target sys/passw@west1_DGMGRL auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:47:33 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04005: ターゲット・データベースからのエラー:
ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
[oracle@tokyo1 ~]$ rman target / auxiliary sys/passw@west1
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 17:47:42 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804390391)に接続されました
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12514: TNS: リスナーは接続記述子でリクエストされたサービスを現在認識していません
● db open から stop し、srvctl start database -d west -o nomount したとします。
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 ONLINE ONLINE osaka1 Open
2 ONLINE OFFLINE
srvctl stop database -d west
[oracle@osaka1 ~]$ srvctl stop database -d west
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 OFFLINE OFFLINE Instance Shutdown
2 ONLINE OFFLINE
ps -ef|egrep -i ora_
export ORACLE_SID=HPYMUSIC1
srvctl start database -d west -o nomount
[oracle@osaka1 ~]$ ps -ef|egrep -i ora_
oracle 7521 4303 0 18:03 pts/1 00:00:00 egrep -i ora_
[oracle@osaka1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@osaka1 ~]$ srvctl start database -d west -o nomount
[root@osaka1 ~]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.west.db
1 ONLINE INTERMEDIATE osaka1 Dismounted
2 ONLINE OFFLINE
↓
↓
↓ ▼ 結果、変わらずエラーになってしまう。
↓
↓
[oracle@osaka1 ~]$ export ORACLE_SID=HPYMUSIC1
[oracle@osaka1 ~]$ rman target / auxiliary sys/passw@west1_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 18:05:35 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: WESTに接続されました(マウントされていません)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12528: TNS:リスナー: 該当するインスタンスはすべて、 新規接続をブロックしています
[oracle@osaka1 ~]$ rman target sys/passw@west1_DGMGRL auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 18:06:21 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04005: ターゲット・データベースからのエラー:
ORA-12528: TNS:リスナー: 該当するインスタンスはすべて、新規接続をブロックしています
[oracle@osaka1 ~]$ rman target / auxiliary sys/passw@west1
Recovery Manager: Release 11.2.0.1.0 - Production on 水 8月 7 18:06:31 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: WESTに接続されました(マウントされていません)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: 内部Recovery Managerパッケージの初期化に失敗しました。
RMAN-04006: 補助データベースのエラー: ORA-12528: TNS:リスナー: 該当するインスタンスはすべて、 新規接続をブロックしています
▼
tnsnames.ora は以下の状態で、tnsping はどの host からも通る状態。
east1_DGMGRL =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.141)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = east)
east1 =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.141)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = east)
(INSTANCE_NAME = HPYMUSIC1)
east2 =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.142)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = east)
(INSTANCE_NAME = HPYMUSIC2)
east =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.141)(PORT = 1521)
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.142)(PORT = 1521)
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = east)
west1_DGMGRL =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.143)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = west)
west1=
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.143)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = west)
(INSTANCE_NAME=HPYMUSIC1)
west2=
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.144)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = west)
(INSTANCE_NAME=HPYMUSIC2)
west=
(DESCRIPTION =
(ADDRESS_LIST=
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.143)(PORT = 1521)
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.144)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = west)
LISTENERS_east=
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.141)(PORT = 1521)
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.142)(PORT = 1521)
east2_DGMGRL =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.142)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = east)
west2_DGMGRL =
(DESCRIPTION =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.144)(PORT = 1521)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = west)
LISTENERS_west=
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.143)(PORT = 1521)
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.144)(PORT = 1521)
▼
hosts は以下のような状態
[root@tokyo1 etc]# more hosts
192.168.56.101 tokyo1.oracle11g.jp tokyo1
192.168.56.102 tokyo2.oracle11g.jp tokyo2
192.168.56.103 osaka1.oracle11g.jp osaka1
192.168.56.104 osaka2.oracle11g.jp osaka2
192.168.56.141 tokyo1-vip.oracle11g.jp tokyo1-vip
192.168.56.142 tokyo2-vip.oracle11g.jp tokyo2-vip
192.168.56.143 osaka1-vip.oracle11g.jp osaka1-vip
192.168.56.144 osaka2-vip.oracle11g.jp osaka2-vip
192.168.56.201 scan.oracle11g.jp scan
192.168.56.202 scan.oracle11g.jp scan
192.168.56.203 scan.oracle11g.jp scan
192.168.56.254 dns1.oracle11g.jp
▼
構成は以下のような状態
PRIMARY STANDBY【 dr 】
Clusterware 11g R2 Grid Infrastructure (11.2.0.1) 11g R2 Grid Infrastructure (11.2.0.1)
Cluster Nodes tokyo1, tokyo2 (2-node RAC) osaka1, osaka2 (2-node RAC)
Cluster Name grid-cluster dr-grid-cluster（都合 primary と同じ名称になっている）
SCAN scan.oracle11g.jp dr-scan.oracle11g.jp（都合 primary と同じ名称になっている）
SCAN listener Host/port SCAN VIPs (port 1521) SCAN VIPs (port 1521)
VIPs tokyo1-vip, tokyo2-vip osaka1-vip, osaka2-vip
DB_UNIQUE_NAME east west
DB_NAME HPYMUSIC HPYMUSIC
DB Instances HPYMUSIC1, HPYMUSIC2 HPYMUSIC1, HPYMUSIC2
DB LISTENER HPYMUSIC_LISTENER HPYMUSIC_LISTENER
DB Listener Host/port tokyo1-vip, tokyo2-vip (port 1521) osaka1-vip, osaka2-vip (port 1521)
DB STORAGE ASM ASM
File Management OMF ( Oracle Managed Files ) OMF ( Oracle Managed Files )
ASM diskgroup for DB files DATA DATA
ASM Diskgroup for FRA FRA
Recovery Files
ORACLE_HOME /u01/app/oracle/product/11.2.0/dbhome_1 /u01/app/oracle/product/11.2.0/dbhome_1
11g R2 RAC version 11.2.0.1 11.2.0.1
OS Oracle Enterprise Linux 6 (64 bit) Oracle Enterprise Linux 6 (64 bit)
ARCHIVELOGモード 有効 有効
FORCE LOGGINGモード 有効 有効
▼
listener.ora は以下の状態
（ 配置ディレクトリは２箇所:
/u01/app/11.2.0/grid/network/admin/listener.ora
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora ）
gridユーザでリスナー再起動：
[grid@tokyo1 ~]$ srvctl stop listener
[grid@tokyo1 ~]$ srvctl start listener
[grid@osaka1 ~]$ srvctl stop listener
[grid@osaka1 ~]$ srvctl start listener
LISTENER_west1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.143)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.103)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)
SID_LIST_LISTENER_west1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME=west)
(SID_NAME = HPYMUSIC1)
(ORACLE_HOME = $ORACLE_HOME)
LISTENER_east1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.141)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.101)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)
SID_LIST_LISTENER_east1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME=east)
(SID_NAME = HPYMUSIC1)
(ORACLE_HOME = $ORACLE_HOME)
LISTENER_west2 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.144)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.104)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)
SID_LIST_LISTENER_west2 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME=west)
(SID_NAME = HPYMUSIC2)
(ORACLE_HOME = $ORACLE_HOME)
LISTENER_east2 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.142)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.56.102)(PORT = 1521)
(IP = FIRST)
(ADDRESS_LIST =
ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)
SID_LIST_LISTENER_east2 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME=east)
(SID_NAME = HPYMUSIC2)
(ORACLE_HOME = $ORACLE_HOME)
Primary Node1
SID_LIST_HPYMUSIC_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=HPYMUSIC1)(GLOBAL_DBNAME=east)(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)))
Primary Node2
SID_LIST_HPYMUSIC_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=HPYMUSIC2)(GLOBAL_DBNAME=east)(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)))
Standby Node1
SID_LIST_HPYMUSIC_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=HPYMUSIC1)(GLOBAL_DBNAME=west)(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)))
Standby Node2
SID_LIST_HPYMUSIC_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=HPYMUSIC2)(GLOBAL_DBNAME=west)(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)))
▼
リソースの状態
[root@tokyo1 app]# /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
ora.DATA.dg
ONLINE ONLINE tokyo1
ora.FRA.dg
ONLINE ONLINE tokyo1
ora.LISTENER.lsnr
ONLINE ONLINE tokyo1
ora.asm
ONLINE ONLINE tokyo1 Started
ora.eons
ONLINE ONLINE tokyo1
ora.gsd
OFFLINE OFFLINE tokyo1
ora.net1.network
ONLINE ONLINE tokyo1
ora.ons
ONLINE ONLINE tokyo1
------------------------------------------------------【 CentOS5.9 】
切り分けの一貫で、os を CentOS5.9 にし、しかも Standalone db でテストしてみました。
他要因の警告が出ましたが、問題なく通過したかもしれません。。
Standalone でテストし、問題なさそうであれば、Oracle Linux 6 RAC でも検証してみようと思います。
▼ そもそも rman が機能していない？？
[oracle@tokyo1 ~]$ srvctl stop database -d east
[oracle@tokyo1 ~]$
[oracle@tokyo1 ~]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
ora.DATA.dg
ONLINE ONLINE tokyo1
ora.FRA.dg
ONLINE ONLINE tokyo1
ora.LISTENER.lsnr
ONLINE ONLINE tokyo1
ora.asm
ONLINE ONLINE tokyo1 Started
Cluster Resources
ora.cssd
1 ONLINE ONLINE tokyo1
ora.diskmon
1 ONLINE ONLINE tokyo1
ora.east.db
1 OFFLINE OFFLINE Instance Shutdown
[oracle@tokyo1 ~]$ export ORACLE_SID=HPYMUSIC
[oracle@tokyo1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 火 8月 13 16:15:10 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL> startup nomount
ORACLEインスタンスが起動しました。
Total System Global Area 839282688 bytes
Fixed Size 2217992 bytes
Variable Size 515901432 bytes
Database Buffers 314572800 bytes
Redo Buffers 6590464 bytes
[oracle@tokyo1 dbs]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 16:25:59 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EASTに接続されました(マウントされていません)
RMAN>
▼ ターゲット・データベース: EASTに接続されました(マウントされていません)
が出たので、方向を逆にしてテスト？？
○ 以下は問題になる場合
export ORACLE_SID=HPYMUSIC
rman target / auxiliary sys/passw@west
rman target / auxiliary sys/passw@west_DGMGRL
rman target sys/passw@west_DGMGRL auxiliary /
○ 以下は問題にならない場合？？
osaka1 から接続する。
export ORACLE_SID=HPYMUSIC
rman target / auxiliary sys/passw@east
rman target / auxiliary sys/passw@east_DGMGRL
rman target sys/passw@east_DGMGRL auxiliary /
rman target sys/passw@east_DGMGRL
[oracle@osaka1 dbs]$ export ORACLE_SID=HPYMUSIC
[oracle@osaka1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 火 8月 13 16:55:33 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL> startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby.txt'
ORACLEインスタンスが起動しました。
Total System Global Area 839282688 bytes
Fixed Size 2217992 bytes
Variable Size 515901432 bytes
Database Buffers 314572800 bytes
Redo Buffers 6590464 bytes
SQL>
[root@osaka1 admin]# su - oracle
[oracle@osaka1 ~]$ export ORACLE_SID=HPYMUSIC
[oracle@osaka1 ~]$ rman target / auxiliary sys/passw@east
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 16:58:29 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EASTに接続されました(マウントされていません)
補助データベース: EAST (DBID=3804991241)に接続されました
[oracle@osaka1 ~]$ rman target / auxiliary sys/passw@east_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 16:59:24 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EASTに接続されました(マウントされていません)
補助データベース: EAST (DBID=3804991241)に接続されました
rman target sys/passw@east_DGMGRL auxiliary /
[oracle@osaka1 ~]$ rman target sys/passw@east_DGMGRL auxiliary / ← ▼ これで ok？？
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 16:59:48 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804991241)に接続されました
補助データベース: EASTに接続されました(マウントされていません)
[oracle@osaka1 ~]$ rman target sys/passw@east_DGMGRL
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 17:00:17 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804991241)に接続されました
○ 実行ログ
[oracle@osaka1 ~]$ rman target sys/passw@east_DGMGRL auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on 火 8月 13 17:06:23 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ターゲット・データベース: EAST (データベースID=3804991241)に接続されました
補助データベース: EASTに接続されました(マウントされていません)
RMAN>
RMAN> DUPLICATE TARGET DATABASE FOR STANDBY NOFILENAMECHECK;
Duplicate Dbが開始されました(開始時間: 13-08-13)
リカバリ・カタログのかわりにターゲット・データベース制御ファイルを使用しています
チャネル: ORA_AUX_DISK_1が割り当てられました
チャネルORA_AUX_DISK_1: SID=7 デバイス・タイプ=DISK
メモリー・スクリプトの内容:
restore clone standby controlfile;
メモリー・スクリプトを実行しています
restoreが開始されました(開始時間: 13-08-13)
チャネルORA_AUX_DISK_1の使用
チャネルORA_AUX_DISK_1: データファイル・バックアップ・セットのリストアを開始しています
チャネルORA_AUX_DISK_1: 制御ファイルをリストア中です
チャネルORA_AUX_DISK_1: バックアップ・ピース/home/oracle/backup/Primary_bkp_for_stndby_03oh6kqr_1_1から読取り中です
チャネルORA_AUX_DISK_1: ピース・ハンドル=/home/oracle/backup/Primary_bkp_for_stndby_03oh6kqr_1_1 タグ=TAG20130813T122147
チャネルORA_AUX_DISK_1: バックアップ・ピース1がリストアされました
チャネルORA_AUX_DISK_1: リストアが完了しました。経過時間: 00:00:07
出力ファイル名=+DATA/west/controlfile/control01.ctl
出力ファイル名=+FRA/west/controlfile/control02.ctl
restoreが完了しました(完了時間: 13-08-13)
メモリー・スクリプトの内容:
sql clone 'alter database mount standby database';
メモリー・スクリプトを実行しています
SQL文: alter database mount standby database
RMAN-05529: 警告: DB_FILE_NAME_CONVERTは無効なASM名になりました。名前がディスク・グループにの み変更されます。
メモリー・スクリプトの内容:
set newname for tempfile 1 to
"+data";
switch clone tempfile all;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
"+data";
set newname for datafile 3 to
"+data";
set newname for datafile 4 to
"+data";
restore
clone database
メモリー・スクリプトを実行しています
実行コマンド: SET NEWNAME
制御ファイルで一時ファイル1の名前を+dataに変更しました
実行コマンド: SET NEWNAME
実行コマンド: SET NEWNAME
実行コマンド: SET NEWNAME
実行コマンド: SET NEWNAME
restoreが開始されました(開始時間: 13-08-13)
チャネルORA_AUX_DISK_1の使用
チャネルORA_AUX_DISK_1: データファイル・バックアップ・セットのリストアを開始しています
チャネルORA_AUX_DISK_1: バックアップ・セットからリストアするデータファイルを指定しています
チャネルORA_AUX_DISK_1: データファイル00001を+dataにリストアしています
チャネルORA_AUX_DISK_1: データファイル00002を+dataにリストアしています
チャネルORA_AUX_DISK_1: データファイル00003を+dataにリストアしています
チャネルORA_AUX_DISK_1: データファイル00004を+dataにリストアしています
チャネルORA_AUX_DISK_1: バックアップ・ピース/home/oracle/backup/Primary_bkp_for_stndby_01oh6kph_1_1から読取り中です
チャネルORA_AUX_DISK_1: ピース・ハンドル=/home/oracle/backup/Primary_bkp_for_stndby_01oh6kph_1_1 タグ=TAG20130813T122104
チャネルORA_AUX_DISK_1: バックアップ・ピース1がリストアされました
チャネルORA_AUX_DISK_1: リストアが完了しました。経過時間: 00:01:25
restoreが完了しました(完了時間: 13-08-13)
メモリー・スクリプトの内容:
switch clone datafile all;
メモリー・スクリプトを実行しています
データファイル1はデータファイル・コピーに切り替えられました
入力データファイル・コピー レコードID=5 スタンプ=823367322 ファイル名=+DATA/west/datafile/system.267.823367237
データファイル2はデータファイル・コピーに切り替えられました
入力データファイル・コピー レコードID=6 スタンプ=823367322 ファイル名=+DATA/west/datafile/sysaux.268.823367239
データファイル3はデータファイル・コピーに切り替えられました
入力データファイル・コピー レコードID=7 スタンプ=823367322 ファイル名=+DATA/west/datafile/undotbs1.269.823367239
データファイル4はデータファイル・コピーに切り替えられました
入力データファイル・コピー レコードID=8 スタンプ=823367322 ファイル名=+DATA/west/datafile/users.270.823367239
Duplicate Dbが完了しました(完了時間: 13-08-13)
RMAN> -
Duplicate Instances in cube_instances with same root_id , parent_Id
Environment - We are having a 2 node cluster installation of SOA SUITE 10.1.3.4, MLR-
We have a file poller (say ESB_poller) and for each record in the file we call a BPEL Process (say BPEL_parent) which call another BPEL process (say BPEL_child). BPEL_child calls a PL/SQL procedure which basicall does an insertion of each record in the DB.
PROBLEM - We have observed that when 2 to 3 large file containing 3000 records each is fed to the system, then sometimes, for 5 to 10 records we have 2 instances of BPEL_child process. They have the same root id and same parent id in CUBE_INSTANCE. One of them gives an error with primary key violation error while inserting in the DB. But the audit trail in BPEL Console for BPEL_parent shows only 1 instance of BPEL_child which has errored and hence our instance goes for exception handling (business perspective).
Could someone tell us,
1. WHY ARE THERE TWO INSTANCES OF BPEL_CHILD PROCESS?
2. UNDER WHAT SCENARIO WE SHOULD EXPECT THIS?
3. WHY AREN'T BOTH THE INSTANCE SHOWING IN BPEL CONSOLE?
4. HOW TO HANDLE THIS SCENARIO/ THE WORKAROUND?
NOTE : Call to child process is synch.
Fault policy is as follows for the process -
<Conditions>
<!-- Fault if wsdlRuntimeLocation is not reachable -->
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="ora-rethrow-fault"/>
</condition>
</faultName>
<!-- Fault if location port is not reachable-->
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="ora-rethrow-fault"/>
</condition>
</faultName>
</Conditions>Hi,
This is a problem with the clustered environment...add clusterGroupId to your file adapter activation agent to make sure only one activation agent is active at anytime in the clustered environment.
Have a luk at this link:Duplicate instance created in BPEL -
Why do we use RMAN DUPLICATE for cloning DB on a different server ?
DB version : 11.2.0.2, 10.2.0.5
I want to create a clone of my Production DB in a test server. In the past, I have taken hot backup of this production DB and restored and recovered it in a different server using plain RMAN commands.
After restoring the control file , mounting the DB and cataloging the backup pieces in the test server , I run
run {
restore database ;
recover database until time <time> ;
alter database open resetlogs ;
}In OTN , i came across long running discussions like
RMAN duplicate database
where they are trying to restore and recover using DUPLICATE command as shown below.
run
duplicate target database to RBS
nofilenamecheck
pfile=/tmp/aux.ora;
Can't they just use plain RMAN restore and recover commands as I did ? What advantage does RMAN DUPLICATE have over the plain commands ?RMAN DUPLICATE is designed to give to clone database a new database name and new database identifier:
>
If you copy a database with operating system utilities instead of the DUPLICATE command, then the DBID of the copied database remains the same as the original database. To register the copy database in the same recovery catalog with the original, you must change the DBID with the DBNEWID utility (see Oracle Database Utilities). In contrast, the DUPLICATE command automatically assigns the duplicate database a different DBID so that it can be registered in the same recovery catalog as the source database.
Maybe you are looking for
-
Hello, I am running SCOM 2012 R2 UR4. Is it possible to setup a Windows Server monitor to notify me when the state change goes from Healthy to Critical? I want to setup one alert to e-mail me regardless of the reason for the state change.
-
Hdisk0 and hdisk1 is showing 100% busy most of the time
Hi, hdisk0 and hdisk1 is showing 100% busy most of the time.During 100% busy database and application goes hang even a simple sql query or simple os command(ex: ls -lrt) takes long time to execute.whereas hdisk0 and hdisk1 not hit where oracle home a
-
Get Person who released PO before saved
Hi Experts!! We are implementing POST method of BADI ME_PROCESS_PO_CUST. From ME29N when the release happens, and when saved, this badi will be called and I can get the current data like the release status and so on through GET_DATA of IM_HEADER (whi
-
JBO-27020 when the view has two or more entities
I created a default view object for an entity and it did well. But when I append another entity in the view and try to update any field I get a JBO-27020 error (blablabla could not be resolved.). I4m using JDeveloper Release 2 (9.0.2.829). I read a l
-
i have no before owner to active my mini i pad . when i format ipad then i face a apple account . but know at this time no owner of the apple account . how i can fix it .... pls tell us