Ora-1276 cannot add controlfile - rman duplicate asm database
Hi,
I am trying to duplicate an asm database olddb -> asm database dup in the same diskgroup. somehow got error 0ra-1276 Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
There is nothing in the asm directory +DISK1/dup/controllfile before I run the rman.
in the initdup.ora
control_files=+DISK1,+DISK1 <--- just the disk group, not the file name
db_name='dup'
db_file_name_convert=+DISK1,+DISK1/dup
log_file_name_convert=+DISK1,+DISK1
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Jun 18 20:58:06 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target sys/oracle@OLDDB
connect auconnected to target database: OLDDB (DBID=1142960293)
RMAN> xiliary /
connected to auxiliary database: DUP (not mounted)
RMAN> duplicate target database to dup
logfile group 1 ('+DISK1/dup') size 200k ,
group 2 ('+DISK1') size 200k;
2> 3>
Starting Duplicate Db at 2011/06/18 20:58:39
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=153 devtype=DISK
WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
contents of Memory Script:
set until scn 1613638;
set newname for datafile 1 to
"+DISK1";
set newname for datafile 2 to
"+DISK1";
set newname for datafile 3 to
"+DISK1";
set newname for datafile 4 to
"+DISK1";
set newname for datafile 6 to
"+DISK1";
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
Starting restore at 2011/06/18 20:58:42
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DISK1
restoring datafile 00002 to +DISK1
restoring datafile 00003 to +DISK1
restoring datafile 00004 to +DISK1
restoring datafile 00006 to +DISK1
channel ORA_AUX_DISK_1: reading from backup piece +DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=+DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731 tag=TAG20110522T000530
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:06
Finished restore at 2011/06/18 20:59:48
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
MAXINSTANCES 32
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '+DISK1/dup' ) SIZE 200 K ,
GROUP 2 ( '+DISK1' ) SIZE 200 K
DATAFILE
'+DISK1/dup/datafile/system.1674.754174727'
CHARACTER SET WE8ISO8859P1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/18/2011 20:59:48
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
RMAN>
thank you very much for your help.
thanks
andrew
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.Are you sure is it running under pfile?
Ok, connect to auxiliary intance and post
show parameter db_create
show parameter control_filesIn your pfile, Have you mentioned single quotes?
If your database with OMF then if you give it as below. as there is some work around
Control_files='+DISK1/DUP/controlfile/control01.ctl','+DISK1/DUP/controlfile/control02.ctl'
Check this too *Ora-1276 Error Recreating The Controlfile When Using +Asm [ID 303187.1]*
Similar Messages
-
ERROR ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
Hi,
SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -ctf I C:/temp/51030721/EXP2/DATA/SAPSSRC.STR C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/DDLORA.TPL C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.TSK ORA -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job completed
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195059
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195133
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: ABTREE created #20071018195134
(IMP) INFO: import of ABTREE completed (39 rows) #20071018195134
(DB) INFO: ABTREE~0 created #20071018195134
(DB) INFO: AKB_CHKCONF created #20071018195134
(IMP) INFO: import of AKB_CHKCONF completed (0 rows) #20071018195134
(DB) INFO: AKB_CHKCONF~0 created #20071018195134
(DB) INFO: AKB_INDX created #20071018195134
(IMP) INFO: import of AKB_INDX completed (0 rows) #20071018195134
(DB) INFO: AKB_INDX~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO~0 created #20071018195134
(DB) INFO: AKB_USAGE_INFO2 created #20071018195134
(IMP) INFO: import of AKB_USAGE_INFO2 completed (0 rows) #20071018195134
(DB) INFO: AKB_USAGE_INFO2~0 created #20071018195134
(DB) INFO: APTREE created #20071018195134
(IMP) INFO: import of APTREE completed (388 rows) #20071018195134
(DB) INFO: APTREE~0 created #20071018195134
(DB) INFO: APTREE~001 created #20071018195134
(DB) INFO: APTREET created #20071018195134
(IMP) INFO: import of APTREET completed (272 rows) #20071018195134
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195134
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: START OF LOG: 20071018195314
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#12 $ SAP
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: version R6.40/V1.4
Compiled Nov 30 2005 20:41:21
C:\usr\sap\BW1\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.cmd -l C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\ORA\NUC\DB/SAPSSRC.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP INDEX "APTREET~0")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error in exec_immediate()
DbSl Trace: ORA-1452 occurred when executing SQL statement (parse error offset=35)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "APTREET~0" ON "APTREET" ( "SPRAS", "ID", "NAME" ) TABLESPACE PSAPBW1 STORAGE (INITIAL 44981 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 1452)
error message returned by DbSl:
ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
(DB) INFO: disconnected from DB
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: job finished with 1 error(s)
C:\usr\sap\BW1\SYS\exe\run/R3load.exe: END OF LOG: 20071018195315
I'm getting this error "duplicate keys found". I'm finished installing the central instance and during the database instance, i got this error. I'm installing BW 3.5 on x64 windows server 2003 platform. I'm using NU kernel 6.40.
Thanks for your suggestions on how to resolve this error.
Reward points guaranteed.Issue solved by deleting central and database instance and started a new build. it finished without an error.
Thank you. -
Hi,
We are implementing OBIA 11.1.1.7.1 which comes with ODI for Fianance and Procurement analytics.When we do full load from EBS the load plan gets failed and it throws the below error
Caused By: java.sql.SQLException: ORA-20000: Error creating Index/Constraint : W_PARTY_D_U1 => ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found.
Please help us to resolve the same.
Thanks
RamaThis might need Patch:10402735
if helps mark -
ORA-22856: cannot add columns to object tables
Oracle 9i
==========
I tried to alter a table using a simple script.
ALTER TABLE tablename ADD col VARCHAR(50);
And it gave me the error: -
ORA-22856: cannot add columns to object tables
Can someone give me some direction on how to resolve this? The script executes fine on a test env.
Thanks in advanceThanks for replying...
exit Null? Type
BUS NUMBER
REP VARCHAR2(60)
COS NUMBER
REP VARCHAR2(50)
ACC NUMBER
ADJ VARCHAR2(2000)
BAS NUMBER
BIL VARCHAR2(360)
BIL VARCHAR2(50)
BIL VARCHAR2(3)
BIL VARCHAR2(50)
BLP VARCHAR2(240)
BLP NUMBER
BOO DATE
COM NUMBER
COM NUMBER
COM NUMBER(15)
COM NUMBER(15)
COM VARCHAR2(4000)
COM VARCHAR2(30)
CUR NUMBER
CUS VARCHAR2(240)
DEA VARCHAR2(240)
EVE VARCHAR2(240)
HEA VARCHAR2(240)
HEA VARCHAR2(240)
HEA VARCHAR2(240)
HEA VARCHAR2(240)
INC VARCHAR2(30)
INV DATE
MAN VARCHAR2(360)
ORD NUMBER
ORD VARCHAR2(240)
PAY VARCHAR2(240)
PAY NUMBER
HEL NUMBER
PEO VARCHAR2(150)
PER NUMBER
PER VARCHAR2(30)
PER NUMBER(15)
PRO VARCHAR2(240)
PRO VARCHAR2(240)
QUA NUMBER(15)
QUO NUMBER
QUO DATE
QUO DATE
QUO VARCHAR2(80)
RED VARCHAR2(240)
REP VARCHAR2(360)
REP VARCHAR2(30)
REP VARCHAR2(30)
REP VARCHAR2(150)
REP VARCHAR2(3)
REP VARCHAR2(150)
REP VARCHAR2(50)
ROL VARCHAR2(60)
SHI VARCHAR2(360)
SPL VARCHAR2(240)
STA DATE
TER DATE
TOT VARCHAR2(240)
TRX NUMBER
TRX VARCHAR2(240)
TRX VARCHAR2(20)
TRX VARCHAR2(30)
WAI VARCHAR2(240)
YEA NUMBER
MAN VARCHAR2(30)
BUF NUMBER
BUF VARCHAR2(60)
EMC NUMBER
EMC VARCHAR2(60)
INT NUMBER
INT VARCHAR2(60)
SUP NUMBER
SUP VARCHAR2(60)
BRM NUMBER
BRM VARCHAR2(60)
SUP NUMBER
SUP VARCHAR2(60)
REP NUMBER
REP VARCHAR2(60)
DIV NUMBER
DIV VARCHAR2(60)
SUP NUMBER
SUP VARCHAR2(60)
REG NUMBER
REG VARCHAR2(60)
SUP NUMBER
SUP VARCHAR2(60)
ARE NUMBER
ARE VARCHAR2(60)
DIS NUMBER
DIS VARCHAR2(60)
ROL VARCHAR2(240)
ACC NUMBER
BON NUMBER
COM VARCHAR2(240)
COM VARCHAR2(240)
REP NUMBER
BIL NUMBER
BAS NUMBER
TOT NUMBER
TOT NUMBER
OVE NUMBER
BLP NUMBER
QUO VARCHAR2(30)
FN_ NUMBER
FN_ VARCHAR2(10)
SAL NUMBER
RES NUMBER
CRE NUMBER
MAN VARCHAR2(100)
PER NUMBER
PLA NUMBER
PLA NUMBER
REV VARCHAR2(30)
REP VARCHAR2(150)
OU_ NUMBER
OU_ NUMBER
EXC VARCHAR2(1)
MAN NUMBER
INV NUMBER
REP NUMBER
UPL VARCHAR2(1)
COM NUMBER
SEQ NUMBER
QUO NUMBER
PRO VARCHAR2(10)
PRO NUMBER
PRO NUMBER
BI_ NUMBER
CUR NUMBER
YTD NUMBER
PAY NUMBER
PAY DATE
PAY VARCHAR2(1000)
PAY VARCHAR2(80)
PAI VARCHAR2(1)
HOL VARCHAR2(1)
SRP NUMBER
WAI VARCHAR2(1)
WAI VARCHAR2(1)
GBK VARCHAR2(10)
TRX DATE
PAY NUMBER(15)
FIX NUMBER
TER DATE
ADJ VARCHAR2(240)
PAY NUMBER
PRO DATE
OIC DATE
OIC NUMBER
OIC VARCHAR2(30)
OIC NUMBER
HEL NUMBER
COM NUMBER
TRA NUMBER
HDR VARCHAR2(30)
LIN VARCHAR2(30)
LIN DATE
SRC DATE
EM_ DATE
EM_ DATE
ORD VARCHAR2(30)
REP VARCHAR2(150)
BIL VARCHAR2(300)
PER VARCHAR2(240)
Excuse the incomplete column names. All datatypes are basic ones and there are no constraints defined on any of the columns (dw env). The table is partitioned. -
When executing 'duplicate target database for standby from active' the system tablespace/datafile (datafile 1) is not cloned. All other datafiles clone successfully. The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03135: connection lost contact
Here are the details:
Primary is 11.2.0.2 RAC database on an Exadata platform
Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
This is an ASM to ASM duplication.
This is not unique to this database. We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
We even issued an explicit SET NEWNAME command but RMAN ignored it.
We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
We also opened up the network firewall to allow permit any,any traffic.
We increased the max_server_processes
and added TCP.NODELAY=yes to the sqlnet.ora file.
There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
checked all alert files grid, asm, and dbhome - no abnormal messages.
We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodologyI successfully created the standby database using RMAN backup and recovery.
I started the managed recovery. Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
I get the following messages in the standby alert log...
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:19:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Nov 26 16:20:01 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:11 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:22 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:32 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
I don't see any MRP processes:
select process,
status,
thread#,
sequence#,
block#,
blocks
7 from v$managed_standby;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CLOSING 2 154363 1 132
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 145418 121 1
RFS IDLE 0 0 0 0
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
RFS IDLE 0 0 0 0
12 rows selected.
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
THREAD# SEQUENCE# APPLIED
2 154356 NO
2 154357 NO
1 145411 NO
2 154358 NO
2 154360 NO
2 154361 NO
1 145414 NO
1 145415 NO
2 154362 NO
2 154363 NO
1 145416 NO
11 rows selected.
I do have the archive logs that cover sequences 154158-154257
Crosschecked 38 objects
Crosschecked 62 objects
Finished implicit crosscheck backup at 26-NOV-13
Starting implicit crosscheck copy at 26-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
validation succeeded for archived log
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
Crosschecked 31 objects -
RMAN duplicate target database error
Hello,
I’m trying to use RMAN ‘duplicate target from active database’ to a remote host however I’m getting a confusing error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/19/2009 13:47:23
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on aux13 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
RMAN-03009: failure of backup command on aux14 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
Here’s my script:
connect target sys/<password>@node1;
connect auxiliary sys/<password>@node2;
spool log to '/u01/app/oracle/dba/duplicate111909.log'
run
allocate auxiliary channel aux11 device type disk;
allocate auxiliary channel aux12 device type disk;
allocate channel aux13 device type disk;
allocate channel aux14 device type disk;
duplicate target database to node2 from active database DB_FILE_NAME_CONVERT='+DATA1','+DATA2';
release channel aux14;
release channel aux13;
release channel aux12;
release channel aux11;
spool log off;
exit;
Node1 uses ASM disk group DATA1 and I intend to use ASM disk group DATA2 on node2. Has anyone seen this error before? I have tried various permutations of DB_FILE_NAME_CONVERT clauses but all error with ORA-19504. On a side note I was able to use ASMCMD cp command to copy a datafile from node1 DATA1 to node 2 DATA2. Also, if I use disk group DATA1 on node 2 then the RMAN duplicate command runs successfully, it only errors when using DATA2. And yes +DATA2 is mounted on node2:
SQL> select name, state from v$asm_diskgroup;
NAME STATE
DATA1 MOUNTED
DATA2 MOUNTED
Any and all ideas are welcome. I’m running out of things to check.
Thanks,
RJLFor a duplicate you don't need to give the DB_FILE_NAME_CONVERT especially if you go from a asm to asm diskgroup.
The place where it'll put all the files will be automatically done taking care of the init.ora file parameter db_create_file_dest, (db_create_online_log_dest_1) -
Tuning RMAN - duplicate active database with size 1.7TB
Dear Oracle experts!
We are going to have a project where we will migrate an ERP standalone database to RAC cluster database.
The source standalone db version is 11gR3 with the latest PSU patch.
The target database would be on the same version on a RAC cluster with ASM.
Of course we want to use RMAN for duplication. The source box and the target cluster nodes are different physical servers.
Being given that the database is around 1.7TB, I would like to ask you some kind of best practices what rman options we can leverage having less time for the actual data migration. In the past I did several RAC migration with 4 allocated channels. Here is a sample for the RMAN script:
run
allocate channel dev1 device type disk;
allocate channel dev2 device type disk;
allocate channel dev3 device type disk;
allocate channel dev4 device type disk;
allocate auxiliary channel dev5 device type disk;
allocate auxiliary channel dev6 device type disk;
allocate auxiliary channel dev7 device type disk;
allocate auxiliary channel dev8 device type disk;
duplicate target database to NEW_RAC
from active database
password file
spfile
set control_files='+FRA_DG/NEW_RAC/controlfile/control01.ctl','+DATA_DG/NEW_RAC/controlfile/control02.ctl'
set db_create_file_dest='+DATA_DG'
set db_create_online_log_dest_1='+FRA_DG'
set db_recovery_file_dest='+FRA_DG'
set db_recovery_file_dest_size='1G';
Of course there are many pre and post steps like configuring tnsnames for rman then creating undo tablespaces, rac services etc. I would like to ask you to focus on the main data migration part and let me know your suggestions.
Thank you in advance,
LaszloWe are going to have a project where we will migrate an ERP standalone database to RAC cluster database.This is what we do in similar situations :
1. Full RMAN backup of the source database, and subsequent archivelogs backup every 2 hours
2. Restore the full backup on the new server, changing file names (if necessary, as in your case)
3. Apply all archivelogs generated in the meantime
4. Archive the last log and stop the source database and Application Servers
5. Apply the last log on the new server, and start the database
6. Change what needed on Application Servers and start applications.
The above requires a few minutes downtime. I use the same procedure for database upgrades, and in this case the downtime is, more or less, half an hour. -
When to restore controlfile, rman is complaining database not mounted?
to restore controlfile, shouldn`t the database be in NOMOUNT status?
if yes, then why rman is complaining ORA-01507?
where I went wrong? Please advise.
C:\Documents and Settings\PhoenixBai>rman target / nocatalog
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Dec 14 10:35:51 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 234883972 bytes
Database Buffers 369098752 bytes
Redo Buffers 7135232 bytes
RMAN> restore controlfile until time 'sysdate-1.5/24';
Starting restore at 14-DEC-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 12/14/2010 10:36:12
ORA-01507: database not mounted
RMAN>it doesn`t. I tried long before this one.
the dilemma i am facing is that I need to recover to the time which was included in incarnation 2.
And to be able to reset database to incarnation 2, i need to startup MOUNT the database.
And once you startup mount the database RESTORE CONTROLFILE won`t work any more.
below is the standard procedure, documented on 10gR2 doc, but still, i am getting errors:
Why it is throwing errors? HOw can I fix?
RMAN> alter database mount;
database mounted
RMAN> list incarnation of database orcl;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORCL 1264908153 PARENT 1 30-AUG-05
2 2 ORCL 1264908153 PARENT 534907 07-DEC-10
3 3 ORCL 1264908153 CURRENT 56335397 14-DEC-10
RMAN> reset database to incarnation 2;
database reset to incarnation 2
RMAN> restore database until scn 56335390;
Starting restore at 14-DEC-10
using channel ORA_DISK_1
creating datafile fno=6 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\ETLTBS01.ORA
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
restoring datafile 00002 to E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
restoring datafile 00003 to E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
restoring datafile 00004 to E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
restoring datafile 00005 to E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\EXAMPLE01.DBF
channel ORA_DISK_1: reading from backup piece E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2
MF_NNND1_TAG20101213T132300_6JCCFO2X_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2010_12_13\O1_MF_NNND1_TAG20101213
O2X_.BKP tag=TAG20101213T132300
channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 14-DEC-10
RMAN> recover database until scn 56335390;
Starting recover at 14-DEC-10
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/14/2010 11:36:14
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until change 56335390
ORA-00283: recovery session canceled due to errors
ORA-38727: FLASHBACK DATABASE requires a current control file.Edited by: PhoenixBai on Dec 14, 2010 11:37 AM -
RMAN duplicate target database from active database - performance problem
Hello. I’m running into a major performance problem when trying to duplicate a database from a target located inside our firewall to an auxiliary located outside our firewall. Both target and auxiliary are located in the same equipment room just on different subnets. Previously I had the auxiliary located on the same subnet as the target behind the firewall and duplicating a 4.5T database took 12 hours. Now with the auxiliary moved outside the firewall attempting to duplicate the same 4.5T database is estimated to exceed 35 hours. The target is a RAC instance using ASM and so is the auxiliary. Ping, tnsping, traceroutes to and from target and auxiliary all indicate no problem or latency. Any ideas on things to consider while hunting for this elusive performance decrease?
Thanks in advance.It would obviously appear network related. Have you captured any network/firewall metrics? Are all components set to full duplex? Would it be possible to take the firewall down temporarily and then test the throughput? Do you encounter any latency if you were to copy a large file across the subnets?
You may want to check V$RMAN_BACKUP_JOB_DETAILS, V$BACKUP_SYNC_IO or V$BACKUP_ASYNC_IO when the backup is running. -
Hi All,
This is more a hypothetical then an actual problem. As part of one of my tasks, I had to do a database duplication using RMAN to another server. Part of the process was to ensure that backup files and archive logs were made available to the server where the database was to be duplicated. To achieve this, we did a NFS mount on the file system directory we needed and we kicked off the duplication job.
However, in a situation where the target database stores all it's backups in the Flash Recover Area in ASM, what would be the easiest way to provide those files to the server hosting the duplicated database?
Thanks.Hey Tychos,
Thanks for the reply, but unfortunately, we don't have a tape backup system in place for Oracle. But I will look into the 11g active duplication.
Thanks! -
Cannot add a row to a database using generated PHP - possible bug?
Sorry if this is the wrong forum, but it seems to straddle a few different technologies.
First, I followed this tutorial to generate PHP scripts for access to the databases:
http://directormx2.com/devnet/flex/articles/flashbuilder4_introspector_php.html
Next, I tried to add a button to add a row to the table. Here's my event handler, which seems to have no effect - even after restarting my program.
protected function buttonAdd_clickHandler(event:MouseEvent):void
var user:User = new User();
user.ID = 1000;
user.FIRST_NAME = "Test";
user.LAST_NAME = "User";
user.DISPLAY_NAME = "hey you";
user.COMPANY_ID = "2";
user.LOGIN_ID = "100";
user.LOGIN_PASSWORD = "xxx";
user.DEPARTMENT = "dept";
userService.createUser(user);
I discovered that if I right-clicked on Data/Services > UserService > createUser(item: User) : int, I could select "Test Operation..." and call the service function manually. I selected the "..." under Enter Value, entered the following data into the dialog, and verified that it was added to my database.
ID:200,
FIRST_NAME:"test",
LAST_NAME:"hey",
DISPLAY_NAME:"hey",
COMPANY_ID:2,
LOGIN_ID:100,
LOGIN_PASSWORD:"xx",
DEPARTMENT:"xxx"
What's weird to me here is that COMPANY_ID and LOGIN_ID are strings, not integers, and yet if I use quotes on these fields the data is rejected (the OK button is not available). I can't assign ints to user.COMPANY_ID or user.LOGIN_ID in my MXML code, since these are declared as strings. Maybe this has nothing to do with the problem, but it seems suspicious to me.
Any help would be greatly appreciated! If it's not blindindly obvious from my post, I'm not a PHP programmer, but am trying to build the simplest of RIAs. Thank you.SOLVED.
The answer is: When I took the server out of the pool to use it for another project, I configured my SAN to remove the LUNs that were shared between my Oracle VM servers. After reinstalling Oracle VM on that server, I failed to present the LUNs to it again. After fixing that, the server rejoined the pool with no problem. -
DUPLICATE DB : ORA-17629: Cannot connect to the remote database server
[oracle@ora11g1 ~]$ export ORACLE_SID=sales
[oracle@ora11g1 ~]$ rman target sys/sales@sales
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jun 5 13:00:15 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SALES (DBID=690066655)
RMAN> connect auxiliary sys/salestby2@salestby2
connected to auxiliary database: SALES (not mounted)
RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE SPFILE
2> SET DB_NAME= 'sales'
3> SET DB_UNIQUE_NAME= 'salestby2'
4> SET control_files='/u02/oradata/salestby2/control01.ctl','/u02/oradata/salestby2/control02.ctl'
5> SET DB_FILE_NAME_CONVERT='/u02/oradata/sales/','/u02/oradata/salestby2/'
6> SET LOG_FILE_NAME_CONVERT='/u02/oradata/sales/','/u02/oradata/salestby2/';
Starting Duplicate Db at 05-JUN-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=20 device type=DISK
contents of Memory Script:
backup as copy reuse
targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwsales' auxiliary format
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwsalestby2' targetfile
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesales.ora' auxiliary format
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesalestby2.ora' ;
sql clone "alter system set spfile= ''/u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfilesalestby2.ora''";
executing Memory Script
Starting backup at 05-JUN-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=58 device type=DISK
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/05/2013 13:05:26
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
continuing other job steps, job failed will not be re-run
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/05/2013 13:05:27
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/05/2013 13:05:27
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 serverWelcome to the oracle forums!
Please take some time to go through [url https://forums.oracle.com/forums/ann.jspa?annID=1535]FAQ PAGE
Always post 4 digit oracle version and OS details.
Post any query out put between \ \ tags
Mark your questions as answered if you get the answer
Password of SYS user on primary and standby must be same.Copy the password file from primary to standby server
scp $ORACLE_HOME/dbs/orapwv112 <oracle_user@auxiliary_host>:/u01/app/oracle/product/11.2/dbs/orapwdupv112 -
Failed RMAN Duplicate from NON-RAC to RAC-ASM
Hi All!
Is it possible to resume a failed RMAN Duplicate? Database is 10gR2.
Please advice...
Regards,
cmadiamOnce you fix the disk group name you can run the duplicatie, it should work fine.
Please refer the link
http://www.oracleracexpert.com/2009/10/migrate-database-to-asm-using-rman.html
Hope this helps,
Regards
http://www.oracleracexpert.com
Duplicate RAC DB using RMAN
http://www.oracleracexpert.com/2009/12/duplicate-rac-database-using-rman.html -
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 は以下の状態
( 配置ディレクトリは2箇所:
/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> -
关于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
唉,把大量时间花在组织提问上了,希望大家引以为戒。有时候,更该去清洗一下思路,重新着手
Maybe you are looking for
-
How do I add new songs/video to iPhone/iPod without doing a full-sync?
Hello everyone, My hard drive crashed a few months ago, and I did not have a back up. So I now have this jam packed iPhone and a brand new iTunes library. I recently downloaded some new songs to the library (like that Blackberry commercial 'All You N
-
Why no boot support for external USB HDs?
I found this after laying out cash on a Lacie 160gb Porsche drive - i Carbon Copy Cloned my startup disk onto the external, go to start-up disk in Sys Preferences, and choose the shiny new drive. It doesn't boot. So I search and find this: http://doc
-
SUBMIT button and VALUE clause
I have a jsp screen like below.It shows in a tabular form all the employee data. EMPLOYEE DETAILS EmpId_______ProcessEmpSalary_____ProcessEmpLeave 1 2 3 4 5 6 7 8 NEXT______PREV____LAST____FIRST Under ProcessEmpSalary ,ProcessEmpLeave of each employe
-
i have done a number of books successfully in aperture 3. I have done a book using instagram photoes. I have previewed the book in PDF and there are no errors. I sent the book off, with a confirmation fro apple that the book was sent. Then i get an e
-
Unable to install iOS 7.1.2 after download
unable to install iOS 7.1.2 after download despite repeated attempts..