Rman duplicate vs staging area vs network mount location
Which option would put the least amount of load on the network.
Thanks.
Running version 11.2.0.1 on Windows Server 2003 R2
Fair point. You cannot yet compress the database with FROM ACTIVE DATABASE. So the staging area would be better if that is your concern. But in any event RMAN is the way to go as mseberg stated. Using a network mount is pretty much the same as FROM ACTIVE DATABASE, it is all going over the network if you are just going to copy the files. But putting the compressed RMAN backup into the network mount area so that you can access it at the standby site will do both for you then :^)
I just find the FROM ACTIVE DATABASE the easiest (I'm lazy) and people have been berating us about having to have lots of extra disk space in both places.
Larry
Similar Messages
-
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> -
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. -
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. -
The RMAN Duplicate Command Fails During The Recover.
This exact script works fine in our lab. We are using Oracle 10.2.0.4.0.
The hot backup for standby is also a script which runs without error in both the lab and
the production machine.
I am obviously missing something.
Any help would be greatly appreciated.
Thanks,
Jeff
=================
RMAN BACKUP SCRIPT
=================
RMAN> run
2> {
3> allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
4> backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
5> backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
6> backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
7> release channel c1;
8> }
released channel: ORA_DISK_1
allocated channel: c1
channel c1: sid=578 devtype=DISK
Starting backup at 22-JAN-13
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
including standby control file in backupset
channel c1: starting piece 1 at 22-JAN-13
channel c1: finished piece 1 at 22-JAN-13
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_05o02f01_1_1 tag=TAG20130122T144104 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:02
Finished backup at 22-JAN-13
Starting backup at 22-JAN-13
channel c1: starting compressed full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/oradata/apoint/users01.dbf
input datafile fno=00001 name=/u01/oradata/apoint/system01.dbf
input datafile fno=00002 name=/u01/oradata/apoint/undotbs01.dbf
input datafile fno=00003 name=/u01/oradata/apoint/sysaux01.dbf
channel c1: starting piece 1 at 22-JAN-13
channel c1: finished piece 1 at 22-JAN-13
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_06o02f05_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
channel c1: backup set complete, elapsed time: 00:22:35
channel c1: starting compressed full datafile backupset
channel c1: specifying datafile(s) in backupset
including standby control file in backupset
channel c1: starting piece 1 at 22-JAN-13
channel c1: finished piece 1 at 22-JAN-13
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_07o02gah_1_1 tag=1NETCMN1_3261_BK4STDBY comment=NONE
channel c1: backup set complete, elapsed time: 00:00:07
Finished backup at 22-JAN-13
Starting backup at 22-JAN-13
current log archived
channel c1: starting archive log backupset
channel c1: specifying archive log(s) in backup set
input archive log thread=1 sequence=463 recid=5 stamp=805323439
input archive log thread=1 sequence=464 recid=6 stamp=805331764
input archive log thread=1 sequence=465 recid=7 stamp=805387242
input archive log thread=1 sequence=466 recid=8 stamp=805387245
input archive log thread=1 sequence=467 recid=9 stamp=805388633
channel c1: starting piece 1 at 22-JAN-13
channel c1: finished piece 1 at 22-JAN-13
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_08o02gaq_1_1 tag=TAG20130122T150354 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:36
Finished backup at 22-JAN-13
released channel: c1
RMAN> exit
Recovery Manager complete.
=====================
RMAN DUPLICATE SCRIPT
=====================
RMAN> run
2> {
3> allocate auxiliary channel c1 device type disk;
4>
5> duplicate target database for standby dorecover nofilenamecheck;
6> release channel c1;
7> }
allocated channel: c1
channel c1: sid=299 devtype=DISK
Starting Duplicate Db at 21-JAN-13
contents of Memory Script:
set until scn 143395851;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JAN-13
channel c1: starting datafile backupset restore
channel c1: restoring control file
channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1
channel c1: restored backup piece 1
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_03o008gn_1_1 tag=1NETCMN1_6874_BK4STDBY
channel c1: restore complete, elapsed time: 00:00:04
output filename=/u01/oradata/apoint/control01.ctl
output filename=/u02/oradata/apoint/control02.ctl
output filename=/u03/oradata/apoint/control03.ctl
Finished restore at 21-JAN-13
sql statement: alter database mount standby database
contents of Memory Script:
set until scn 143395851;
set newname for tempfile 1 to
"/u01/oradata/apoint/temp01.dbf";
switch clone tempfile all;
set newname for datafile 1 to
"/u01/oradata/apoint/system01.dbf";
set newname for datafile 2 to
"/u01/oradata/apoint/undotbs01.dbf";
set newname for datafile 3 to
"/u01/oradata/apoint/sysaux01.dbf";
set newname for datafile 4 to
"/u01/oradata/apoint/users01.dbf";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
renamed temporary file 1 to /u01/oradata/apoint/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 21-JAN-13
channel c1: starting datafile backupset restore
channel c1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oradata/apoint/system01.dbf
restoring datafile 00002 to /u01/oradata/apoint/undotbs01.dbf
restoring datafile 00003 to /u01/oradata/apoint/sysaux01.dbf
restoring datafile 00004 to /u01/oradata/apoint/users01.dbf
channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1
channel c1: restored backup piece 1
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_BK4STDBY_02o0076b_1_1 tag=1NETCMN1_6874_BK4STDBY
channel c1: restore complete, elapsed time: 00:21:32
Finished restore at 21-JAN-13
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy recid=5 stamp=805323205 filename=/u01/oradata/apoint/system01.dbf
datafile 2 switched to datafile copy
input datafile copy recid=6 stamp=805323205 filename=/u01/oradata/apoint/undotbs01.dbf
datafile 3 switched to datafile copy
input datafile copy recid=7 stamp=805323206 filename=/u01/oradata/apoint/sysaux01.dbf
datafile 4 switched to datafile copy
input datafile copy recid=8 stamp=805323206 filename=/u01/oradata/apoint/users01.dbf
contents of Memory Script:
set until scn 143395851;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 21-JAN-13
starting media recovery
channel c1: starting archive log restore to default destination
channel c1: restoring archive log
archive log thread=1 sequence=462
channel c1: reading from backup piece /u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1
channel c1: restored backup piece 1
piece handle=/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_6874_LOGS4STDBY_04o008gu_1_1 tag=TAG20130121T183822
channel c1: restore complete, elapsed time: 00:00:03
archive log filename=/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch thread=1 sequence=462
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/oradata/apoint/system01.dbf'
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/21/2013 20:53:44
RMAN-03015: error occurred in stored script Memory Script
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/u03/oradata/apoint/DB_ARCHIVE_LOGS/apoint_1_688761648_462.arch'
ORA-16145: archival for thread# 1 sequence# 462 in progress
RMAN> exitJeff;
I think the issue is in your backup. If you compare your command with mine, you may or may not see the issue, but this is how I got this to work.
Yours
RMAN run
allocate channel c1 device type disk format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_BK4STDBY_%U';
backup current controlfile for standby format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_CNTRL4STDBY_%U';
backup as compressed backupset check logical tag='1NETCMN1_3261_BK4STDBY' database include current controlfile for standby;
backup archivelog from sequence 463 format '/u03/oradata/apoint/DB_BACKUPS/1NETCMN1_3261_LOGS4STDBY_%U';
release channel c1;
Mine
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Your duplicate is very close to what I use :
Yours
RMAN> run
allocate auxiliary channel c1 device type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel c1;
Mine
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}Short notes :
http://www.visi.com/~mseberg/duprman.html
Best Regards
mseberg -
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) -
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 -
Oracle EE 11.2.0.2 RMAN Duplicate interesting issue - is it a bug?
Hi,
Oracle EE 11.2.0.2 RHEL 5.7 x86 64-bit RACOne Node database (3 - nodes).
I was working on a process to refresh out test environment with prod database backup from tape and i have done it many times. Most of our environment is in 10gR2 and have few on 11.2.0.2 RACOne Node databases. The recovery basics in Oracle world is to use archive log sequence + 1 (provided we know before hand the backups metadata) and it works as expected until 10g but with 11.2.0.2 RMAN duplicate, i stumbled upon an issue where RMAN is trying to restore an older controlfile auto backup and then rolling forward from there. Its easy to explain with an example..
1) I have an archivelog backup, say sequence 20 to 30 on Feb 22nd @ 10pm and a controlfile autobackup at this time c-20120222
2) I have a FULL backup + archive log until sequence 50 on Feb 23nd@ 6pm and a controlfile autobackup at this time c-20120223
3) I am using RMAN duplicate to refresh UAT with Feb 23rd backup and use "set until sequence 51 thread 1"I am using following RMAN commands to do the duplicate on UAT server (executed on UAT server)
rman target sys/***@PROD_DB auxiliary /
RMAN> run
2> {
3> allocate auxiliary channel c1 device type disk;
4> allocate auxiliary channel c2 device type disk;
5> allocate auxiliary channel c3 device type disk;
6> set until sequence 51 thread 1;
7> duplicate target database to UAT_DB;
8> }RMAN duplicate automates all that we do manually but the recovery mechanism is same. In the above scenario, it connects to target database, gets the backup metadata and restores controlfile from c-20120223 , restores the datafiles and recovers till sequence 50 . This has been the scenario until 10g in every RMAN duplicate process i have tried and is expected from Oracle.
Issue:
In 11gR2 (11.2.0.2), for the same duplicate scenario above, it is restoring the controlfile from autobackup c-20120222 and restoring the datafiles from Feb 23rd backup, recovering till sequence 50 and doing the duplicate process. The thing to note here is that the controlfile autobackup c-20120222 does not have any record of the FULL backup that occured on Feb 23 rd and since RMAN duplicate is having a connection to target database, it knows the backup metadata and hence it is able to complete the recovery.
For clarification, Thread 1 & 2 of RAC One Node is not an issue here for sure. Did anyone experience this issue? Any insight into this would be greatly appreciated.
Thanks,
ShivaAJ,
I have already tried that scenario, i renamed the c-20120222 and kicked off the same duplicate process but it failed and it kept on "fail-over to previous backup" which is expected. The thing is, RMAN look's for the control file autobackups from newest to oldest (unless you gave a point in time) and duplicate command is not doing it.
Tycho,
I agree there are new features but to support them a change in recovery mechanism is something i would disagree that Oracle would do. Active Duplication is not based on backups, so that is out of question here. For backup-based duplication, we can try with connections to target or targetless, catalog or catalogless or none. I have already given an example with the target (same with target + catalog) and i expect the same behavior with only catalog connection. Now, i have tested the example without connecting to target or catalog and below are my observations...
For the same backups i mentioned in the very first email, i got the following info....
rman target /
Recovery Manager: Release 11.2.0.2.0 - Production on Fri Feb 24 12:35:54 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RMANTEST (DBID=3789692530)
RMAN> list backup of archivelog sequence 95;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
11 2.50K DISK 00:00:00 23-FEB-12 18:05:40
BP Key: 11 Status: AVAILABLE Compressed: YES Tag: TAG20120222T094240
Piece Name: /u01/app/oracle/exp/rmantest_stl/full_backup/rmantest_stl_0bn3upkg_1_1.arch
List of Archived Logs in backup set 11
Thrd Seq Low SCN Low Time Next SCN Next Time
1 95 346280 23-FEB-12 18:05:10 346302 23-FEB-12 18:05:30I got the scn_to_timestamp for the NEXT_SCN of sequence 95, which should correpond tothe "Next Time" that is the timestamp for the Archive log sequence 96.
SQL> select scn_to_timestamp(346302) as timestamp from dual;
TIMESTAMP
23-FEB-12 18.05.30.000000000 PMNow, i gave the following for targetless & catalogless duplication...
rman auxiliary /
RMAN> run
2> {
3> set until time "to_date('23-FEB-12 18:05:30','DD-MON-YY HH24:MI:SS')";
4> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
5> }RESULT: Same ISSUE but this time IT FAILED with the error i expected. It went ahead and restored the c-20120222 autobackup control file and tried to restore the datafiles but, as we
know, this control file autobackup does not have record of Feb 23rd + archive log backup, so it FAILS. This is exactly what i told in my first email.
Error Log File:
contents of Memory Script:
sql clone "alter system set control_files =
''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776081841'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776081841'' comment=
''Set by RMAN'' scope=spfile";
sql clone "alter system set db_name =
''RMANTEST'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile from '/u01/app/oracle/exp/rmantest_stl/c-20120222';
alter clone database mount;
Errors in memory script
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01507: database not mounted
ORA-06512: at "SYS.X$DBMS_RCVMAN", line 13371
ORA-06512: at line 1
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 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
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/24/2012 10:18:04
RMAN-05501: aborting duplication of target databaseSo, my next test was not to give any Point In Time, that is just issue the duplicate without SET UNIL clause and this time, and this time it behaved, it restored the control file from c-20120223 and completed the duplicate process. So what does this tell us? We cannot do a POINT IN TIME duplicate using RMAN DUPLICATE????
rman auxiliary /
RMAN> run
2> {
3> duplicate database to rman01s backup location '/u01/app/oracle/exp/rmantest_stl';
4> }
contents of Memory Script:
sql clone "alter system set control_files =
''+RMAN01D_DATA/rman01s_stl1/controlfile/current.270.776089489'', ''+RMAN01D_RECO/rman01s_stl1/controlfile/current.263.776089489'' comment=
''Set by RMAN'' scope=spfile";
sql clone "alter system set db_name =
''RMANTEST'' comment=
''Modified by RMAN duplicate'' scope=spfile";
shutdown clone immediate;
startup clone force nomount
restore clone primary controlfile from '/u01/app/oracle/exp/rmantest_stl/c-20120223';
alter clone database mount;
}Just checking if anyone stumbled upon these findings. An Oracle SR is already in place, so just waiting for an update from them.
Thanks,
Shiva -
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-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
andrewRMAN-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]* -
How bad is it to have 4 network mounts for home folders?
I am the tech curriculum guy at a middle school and also manage the servers. I am not an expert at all. Learn enough to make it work efficiently. We got a new server (intel). I am in the process of migrating all the users, groups, home folders and data etc. Had some problems so I called Apple, in my discussion with the tech support there (3-4 hours solving problems) one of the techs questioned my setup. Here is what I used to do:
Server one has all the users in workgroup manager. The home folders for the 6th, 7th and 8th graders are on two separate drive bays on server one. Each grade level folder is a network mount. I then have the faculty home folders on a server two. There is also a shared folder called "Stuff" which mounts for all users and has clipart, movies etc. It is basically a read only mount. The faculty home folders are network mounts of their home folders.
I service between 400 and 500 students a day in the lab, it is quite busy, with anywhere from 60 to 90 users logged on at one time. My thinking last year was that if I could spread out the home folders on different drives, the students wouldn't all be hitting the same drive for saves, data etc. So that one drive wouldn't be spinning its brains out to keep everyone going. That is why I have the 4 network mounts for the home folders. One for each grade level (6,7,8) and the faculty.
My new server has three drives, two of them for home folders. The drives are 750 gb each. He (apple tech) suggested I create a folder in each drive, set it as the network mount and within that folder put two sets of home folders. So, then I would only have two network mounts, but retain my four sets of home folders that would be within the network mounts.
I guess my question is, which is better, to have the 4 network mounts with separate home folder locations on 2 different servers, or consolidate the home folders into 2 network mounts on one server.
He said that the more network mounts, the longer it takes to get computers started up.
Any expert advice here would be greatly appreciated.
Thanks, hope I explained this well enough.
Intel Imac Mac OS X (10.4.8) Lab- Education Intel iMacs - PPC eMacsI don't think the logins take too long, we may wait 30 seconds or so for the students to login. We have had problems when 60 kids leave and 60 more come in, some login and after the username and password are entered, the login begins then locks. The Apple tech guy thought that could be aggravated by the 4 network mounts. I just sort of thought that with students and teachers accessing 4 different hard drives, that it wouldn't tax one drive as much. I agree that a longer login is a small price to pay for faster working speeds.
-
Network mounts no longer show up on desktop
Ever since I installed 10.5 my network mounts would show up on my desktop. Now, for some reason, they don't. One mount shows up under /Users/bob/Documents/smb and the other one shows up under /Volumes/blah. They used to show up on the desktop, but no more. Any ideas??
I checked finder settings and Connected Servers is checked. Not sure what to do now.
Thanks!I think I just found out why- Go to finder->preferences->general->check connected servers and see if that helps.
I have an external HD connected to my extreme and it wouldn't show up on the desktop after upgrade to 10.5. After above it shows up.
Also, used tip from another post and went to system preferences->system->accounts->select account, login items, drag disk to login area (I had to go back to the finder and go to folder of AE HD and ctrl click and choose original view and then drag to auto login)
not sure if I am dorked up or upgrade missed something but now I have AE HD on desktop and can use pics from that drive on iphoto -
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 -
Hi:
I was doing a 11g database clone on linux using rman duplicate. After runing 40min, it stopped and got the following errors. All the file permission are the same 777, one third of files have been copied.
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
failover to previous backup
released channel: aux1
released channel: aux2
released channel: aux3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/30/2012 08:28:07
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archived log found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 12312 and starting SCN of 23167256063 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12311 and starting SCN of 23167250994 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12310 and starting SCN of 23167245674 found to restore
Thanks and regards.Files from source database:
-rwxrwSrwx 1 root root 48653824 May 29 20:57 db_t784587134_s1208_p1
-rwxrwSrwx 1 root root 48594944 May 29 20:57 db_t784587149_s1209_p1
-rwxrwSrwx 1 root root 7761920 May 29 20:57 db_t784587150_s1210_p1
-rwxrwSrwx 1 root root 4062945280 May 29 21:23 db_t784587170_s1211_p1
-rwxrwSrwx 1 root root 1124147200 May 29 21:07 db_t784587170_s1212_p1
-rwxrwSrwx 1 root root 2049015808 May 29 21:16 db_t784587725_s1213_p1
-rwxrwSrwx 1 root root 4012630016 May 29 21:36 db_t784588310_s1214_p1
-rwxrwSrwx 1 root root 4620419072 May 29 21:43 db_t784588726_s1215_p1
-rwxrwSrwx 1 root root 3724255232 May 29 21:52 db_t784589461_s1216_p1
-rwxrwSrwx 1 root root 1818624 May 29 21:43 db_t784589896_s1217_p1
-rwxrwSrwx 1 root root 2071040 May 29 21:52 db_t784590427_s1218_p1
There are about 30 dbf files on source database, 10 dbf files on target database now. -
Staging Area with OWB 10.2 - necessary or not?
Hi to all,
I have read so much about Staging Area and OWB 10.2 that I am totally confused: Some documents and powerpoints in the web say you do not need one, others say you need one. The thing is I am planning a DWH and now I am not sure if a staging area is necessary or not, because the mappings do the ETL jobs internal so I am not sure about the staging area. Most of my data sources are Tables/Views/MViews in a database.
Thank you very much for any help concerning this question!
Regards
ThomasWould you prefer the answer that you MAY need one? Then again, you may just WANT one!
For example, if you are building against a high transaction volume, busy 24/7 OLTP system then you may find that you need a local snapshot in order to do a complete build with a consistent set of source data for all your numbers to be consistent.
Then again, you also may just find that bringing over just delta data into a local snapshot makes for much more efficient load rather than running against huge full remote tables if they are not well partitioned and/or indexed.
Then again, complex joins run against a remote system may run more efficiently if you bring the data across with simple table dumps into a staging area that you can index to optimize your queries rather than have to deal with poor performance of complex joins over a dblink. Especially if you need to perform complex joins accross more than one db link to multiple source source systems. How big a cartesion product do you want bouncing around the network to perform that sort of scenario? Sure, maybe you can do it - but how much are you going to impact performance across the boards doing things like that?
Is the source system already stresed to the max and sitting on a vintage piece of equipment, but your shiny new DW environment is blessed with tons of resources that will make the ETL run faster by several factors if you first copy the data over locally?
So, do you need a staging area?
Fact is that there is no generic correct answer to this question.
You have to look at the specifics of your data requirements and your environment to answer that question. There are costs and benefits to having a staging area, and you have to determine which way the cost/benefit analysis comes out for your specific project.
Mike
Maybe you are looking for
-
How to call a function module from a transformation
Hi, Could somebody please let me know how I can call an abap function module from a transformation (abap xslt program). I know how to call the class methods from transformation, but how do i call a function module..? Thanks, Shashi. Edited by: Shashi
-
Tracking of messages in PI????
Hi, I am wondering something whether this can be possible in PI or not. In PI, if anybody asks us regarding the number of messages process through PI. Then we would need to count the number of messages in SXI_MONITOR or in SXMB_MONI. Here my que
-
SRM Active Substitute and Approval Email
Hi I was wondering if anyone could help with an issue I have for SRM Approvals. I have Two shopping carts set up that have had an approval email sent to a user. This user though is not on site so I have set up and Active substitute for the User. I
-
IPod Video won't sync Video with iTunes
After installing the latest version of iTunes and putting an hour's worth of video into it, I plugged my new iPod in. The iPod synced with my music and my pictures, but not my videos(mpg), even though I'd already set the preferences to automatically
-
DHCP server + IP multipath
hi, I have configured a solaris 10 box that runs a dhcp server with ha networking using multipathing: ifconfig dmfe0 thehostname netmask + broadcast + group mygroup -failover deprecated up ifconfig dmfe0 addif hahostname + broadcast + failover up ifc