Duplicate by RMAN
Hi,
on 10 gR2 can we duplicate from RMAN Backup using SET UNTIL TIME ?
I mean for example can I duplicate from the backups of 22 of January (my backups from 22 of Jan and 23 , 24 until first of february are available ).
If the backups are on tape should we do something extra ?
Thanks.
on 10 gR2 can we duplicate from RMAN Backup using SET UNTIL TIME ?
Ans: Yes, If you have full Backup + all algenerated archive logs after full backup till set until time.
If the backups are on tape should we do something extra ?
Ans: No, use that channel that you need to take the RMAN backup.
Regards
Asif Kabir
Similar Messages
-
Hi,
to duplicate a databse to an auxiliary DB, auxiliary should be in nomount.
please See 374069.1 note on metalink or Oracle® Data Guard
Concepts and Administration 10g Release 2 (10.2) B14239-04 page F-7.
But,
RMAN can not connect to an auxiliary oracle database when it is in nomount state. I created another
data base named orcl3. Impossible to conect to by RMAN as auxiliary for orcl2
and orcl3 :
orcl2 is in noumount :
C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
I did :
SQL>alter database mount
and now :
C:\Documents and Settings\ >rman target sys/pwd@orcl auxiliary sys/pwd@orcl2
Regards.
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:02:21 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target : ORCL (DBID=1155329895)
connected to auxiliaire : ORCL2 (DBID=608821149, non ouverte)
RMAN> exit
orcl3 is nomounted :
C:\Documents and Settings\a.user>rman target sys/pwd@orcl auxiliary
sys/pwd@orcl3
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 08:31:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connectÚ Ó la base de donnÚes cible : ORCL (DBID=1155329895)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: Úchec de l'initialisation du gestionnaire de rÚcupÚration interne
RMAN-04006: Error not connected to auxiliaire :ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Many thanks.Hi Damorgan,
you are true, RMAN connected :
C:\Documents and Settings\user>rman target sys/pwd@orcl auxiliary /
Recovery Manager: Release 10.2.0.1.0 - Production on Sam. Ao¹t 4 15:37:46 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target : ORCL (DBID=1155329895)
connected to auxiliary : ORCL2 (non mounted)
But :
When :
RMAN> run{
2> duplicate target database for standby
3> nofilenamecheck
4> dorecover;
5> }
canal ORA_AUX_DISK_1 : restauration de fichier de contr¶le
canal ORA_AUX_DISK_1 : copie du fichier de contr¶le copiÚe
fichier en entrÚe=C:\ORACLE\ORADATA\BACKUP\ORCL\CONTROL01.DBF
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL01.CTL
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL02.CTL
fichier de sortie=C:\ORACLE\ORADATA\ORCL2\CONTROL03.CTLFin de restore dans 04/08/07
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Failed in Duplicate DB 08/04/2007 15:43:10
RMAN-03015: une erreur s'est produite dans le script stockÚ Memory Script
RMAN-03009: Úchec de la commande sql sur le canal clone_default Ó 08/04/2007 15:43:10
RMAN-11003: erreur lors de l'analyse ou de l'exÚcution d'une instruction SQL : alter database mount standby database
ORA-01103: database name 'orcl' in control file is not 'orcle2'
Any idea ?? -
Duplicate Problems (RMAN is looking at the wrong backup)
We are running into a problem when we try to duplicate our database. Here is the process we use to duplicate:
delete old backup files (we only use RMAN for cloning so we don't need them)
set prod db environment variables<run rman
connect target sys/####;
backup database;
exit;
set test db environment variables<shutdown test database, rename test db folder (in case we missed getting something important out) create a new folder for test db.
start test db (nomount)
rman
connect target sys/####@PROD
connect auxiliary sys/####@TEST
run
allocate auxiliary channel disk1 type disk;
duplicate target database to TEST;
we get this error:
channel disk1: reading from backup piece E:\RMAN\PROD\BKUP_PROD_610891176_1
ORA-19870: error reading backup piece E:\RMAN\PROD\BKUP_PROD_610891176_1
ORA-19505: failed to identify file "E:\RMAN\PROD\BKUP_PROD_610891176_1"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
failover to previous backup
The backup file RMAN is trying to read is the backup from our previous clone. How can I tell RMAN to look at the backup we just made?
I've run "list backup;" and the most recent backup is shown there. We've run into this problem a couple of times now, but not everytime. I can't find any rhyme or reason for why it works or fails but the process is the same sometimes we can just wait a half-hour or an hour and it works. Anyone have any ideas that could help?
BTW - We aren't using a recovery catalog.http://dbataj.blogspot.com/2006/12/duplicating-database-with-recovery.html
-
ORA:01013 with Duplicate Database - RMAN
Hi,
I havea demo database on server1 and am creating a clone database on server2 with RMAN duplicate command. I have the catalog on server1 itself. I created the backups of the database and executed RMAN command from server2 with
server1 in open status and server2 in nomount state.
the command i ran was:
duplicate target database to clonedb
until logseq 338 thread 1
pfile=/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora
logfile
'/u01/app/oracle/oradata/clonedb/redo01.log' size 1m,
'/u01/app/oracle/oradata/clonedb/redo02.log' size 1m;
Please let me know how to overcome this error..
Thanks,
Raj
This is the error i got along with the log it created...
Starting Duplicate Db at 28-OCT-04
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=14 devtype=DISK
printing stored script: Memory Script
set until scn 130734;
set newname for datafile 1 to
"/u02/oradata/clonedb/system01.dbf";
set newname for datafile 2 to
"/u03/oradata/clonedb/undotbs01.dbf";
set newname for datafile 3 to
"/u02/oradata/clonedb/testtbs_01.dbf";
set newname for datafile 4 to
"/u02/oradata/clonedb/system02.dbf";
set newname for datafile 5 to
"/u02/oradata/clonedb/rmantbs_01.dbf";
restore
check readonly
clone database
executing script: 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 28-OCT-04
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 /u02/oradata/clonedb/system01.dbf restoring datafile 00002 to /u03/oradata/clonedb/undotbs01.dbf
restoring datafile 00003 to /u02/oradata/clonedb/testtbs_01.dbf
restoring datafile 00004 to /u02/oradata/clonedb/system02.dbf restoring datafile 00005 to /u02/oradata/clonedb/rmantbs_01.dbf
channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/full/DEMODB_20041027_05g3jeeq_1_1 tag=FULL params=NULL channel ORA_AUX_DISK_1: restore complete Finished restore at 28-OCT-04 sql statement: CREATE CONTROLFILE REUSE SET DATABASE "clonedb" RESETLOGS ARCHIVELOG
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 680
LOGFILE
GROUP 1 '/u01/app/oracle/oradata/clonedb/redo01.log' SIZE 1048576 ,
GROUP 2 '/u01/app/oracle/oradata/clonedb/redo02.log' SIZE 1048576
DATAFILE
'/u02/oradata/clonedb/system01.dbf'
CHARACTER SET WE8ISO8859P1
printing stored script: Memory Script
switch clone datafile all;
executing script: Memory Script
datafile 2 switched to datafile copy
input datafilecopy recid=1 stamp=540710832 filename=/u03/oradata/clonedb/undotbs01.dbf
datafile 3 switched to datafile copy
input datafilecopy recid=2 stamp=540710832 filename=/u02/oradata/clonedb/testtbs_01.dbf
datafile 4 switched to datafile copy
input datafilecopy recid=3 stamp=540710832 filename=/u02/oradata/clonedb/system02.dbf
datafile 5 switched to datafile copy
input datafilecopy recid=4 stamp=540710832 filename=/u02/oradata/clonedb/rmantbs_01.dbf
printing stored script: Memory Script
set until scn 130734;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 28-OCT-04
using channel ORA_AUX_DISK_1
starting media recovery
channel ORA_AUX_DISK_1: starting archive log restore to default destination channel ORA_AUX_DISK_1: restoring archive log archive log thread=1 sequence=337 channel ORA_AUX_DISK_1: restored backup piece 1 piece handle=/u05/backup/demodb/arch/arc_DEMODB_20041027_06g3jef2_1_1 tag=TAG20041027T134050 params=NULL channel ORA_AUX_DISK_1: restore complete archive log filename=/u02/oradata/clonedb/arch/1_337.arc thread=1 sequence=337 channel clone_default: deleting archive log(s) archive log filename=/u02/oradata/clonedb/arch/1_337.arc recid=1 stamp=540710834 media recovery complete Finished recover at 28-OCT-04
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '/u01/app/oracle/product/9.2.0.1.0/dbs/initclonedb.ora';
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/28/2004 06:28:26
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
Recovery Manager complete.HI,
# STBY:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 242208768 bytes
Fixed Size 2227176 bytes
Variable Size 184550424 bytes
Database Buffers 50331648 bytes
Redo Buffers 5099520 bytes
# PRIMARY:
RMAN> CONNECT TARGET sys/oracle@JOHN;
connected to target database: JOHN (DBID=1575580406)
RMAN> CONNECT AUXILIARY sys/oracle@JOHN_DB2;
Until this you did correct. now just in a run block, like
eg
run
allocate channel ....
allocate channel...
duplicate target database for standby from active database; -
How to duplicate by rman database?
dear sir, i read one article and follow step and 2nd auxiliary database i delete all dbf, ctl, log(redo) files ...then tryying to create dubplicate giving me error
can some one send steps of it
rgds
shahzadDatabase Duplication with RMAN
Use the RMAN DUPLICATE command to create a copy of the target database that you can use for testing. The command restores backups and copies of the primary database's files and creates a new database.
As part of the duplicating operation, RMAN manages the following:
Restores the target datafiles into the duplicate database and performs incomplete recovery using all available archived log and incremental backups.
Opens the duplicate database with the RESETLOGS option after incomplete recovery to create the online redo logs.
Generates a new, unique database identifier for the duplicate database.
Note also the following features of RMAN duplication. You can:
Skip read-only tablespaces with the SKIP READONLY clause (read-only tablespaces are included by default). You can also exclude any tablespace with the SKIP TABLESPACE clause so long as it is not the SYSTEM tablespace and does not contain rollback or undo data. If you omit tablespaces, then you can add them later.
Create your duplicate database in a new host. If the same directory structure is available, then you can use the NOFILENAMECHECK option and reuse the target datafile filenames for the duplicate datafiles.
Create your duplicate database by using the SET UNTIL command or UNTIL clause of the DUPLICATE command to recover it to a noncurrent time. By default, the DUPLICATE command creates the database using the most recent backups of the target database and then performs recovery to the most recent consistent point contained in the incremental and archived redo log backups.
Use the duplicate database without a recovery catalog.
Register the duplicate database in the same recovery catalog as the target database. This option is possible because the duplicate database receives a new database identifier during duplication. If you copy the target database using operating system utilities, then the database identifier of the copied database remains the same so you cannot register it in the same recovery catalog.
Figure 6-3 illustrates a case of database duplication. In this example, RMAN creates two duplicate database by using one set of datafile backups: one database on the local host and one database a remote host.
Figure 6-3 Creating a Duplicate Database from Backups
Text description of the illustration sbr81078.gif
The method you use to duplicate your database depends on whether you are creating your duplicate database on the same or a different host and whether the duplicate directory structure is the same as your target database directory structure. For example, in some cases you can keep the same directory structure and filenames in your duplicate database, while other times you must rename the files.
See Also:
Chapter 12, "Duplicating a Database with Recovery Manager" to learn how to make a duplicate database, and Oracle9i Recovery Manager Reference for DUPLICATE command syntax.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc2.htm#462471
Joel Pérez
http://www.oracle.com/technology/experts -
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 -
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 -
RMAN-00600 Error during Duplicate
RDBMS Version: 8.1.6
Operating System and Version: NT 4.0
Error Number (if applicable): RMAN-00600
Product: Recovery Manager
Product Version: 8.1.6
RMAN Duplicate Database Error (RMAN-00600)
While running the following command:
run {
allocate auxiliary channel ch1 type disk;
allocate auxiliary channel ch2 type disk;
duplicate target database to db1backup nofilenamecheck;
I get the following errors:
RMAN-03022: compiling command: Duplicate Db
RMAN-00571: =========================================================
RMAN-00569: ================ ERROR MESSAGE STACK FOLLOWS ============
RMAN-00571: =========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code: 600
RMAN-03013: command type: Duplicate Db
RMAN-00600: internal error, arguments [14036] [-11] [29] [
CHARACTER SET %s
] [WE8ISO8859P1]
Any ideas as to what may be causing this? I have successfully backed up the target database, the connections to the target and auxiliary databases are fine, and I'm using a controlfile vs. a catalog.
Mike McAndrew
[email protected]
nullHi
Duplicate databases with RMAN is not as simple as it seems, look at message colled "Duplicate database error with RMAN"
This maybe could help you.
Anyway, I saw the message:
"internal error, arguments [14036] [-11] [29] [CHARACTER SET %s] [WE8ISO8859P1] "
What NLS configuration have you?
A10!
null -
Duplicate RMAN backup output to multiple destinations
Hi
We run Oracle 10.2, we have a requirment to duplicate the rman backup to three destinations at the same time, given that FRA is defined, following is the backup script:
rman
connect target /
backup as compressed backupset database plus archivelog delete imput;
Of course this will backup to FRA only.
The requirment is to duplicate the rman backup output to FRA , /orabackup1 and /orabackup2 in the same one command, i.e, without running the backupo three times.
What change would be needed in the script syntax?See Re: RMAN backup to two locations
-
Error while trying to duplicate a database
I've got the following problem with rman-duplicate (oracle 10gR2) (see also: [this thread|http://forums.oracle.com/forums/thread.jspa?messageID=4446855#4446855])
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/22/2010 10:49:05
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
- followed by the list of all datafiles
I've made a full backup of the target database right before the duplicate. Rman reports (list backup; crosscheck backup) the availability of all database backups with all its datafiles.
Unfortunately in my case the reported very strange "shutdown abort"-"startup" - workaround doesn't work.
Has anyone any other hints - or is it just a serious bug (which would prevent me from further time-wasting trials ...).
friedhelmHashmi wrote:
Post your duplicate database command with error.Here is teh whole procedure (script):
RUN
SET until time "to_date('22/07/2010 10:10:00','DD/MM/YYYY HH24:MI:SS')";
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
SET NEWNAME FOR DATAFILE 1 TO '/oracle/oradata/VG41VWT/system01.dbf';
SET NEWNAME FOR DATAFILE 34 TO '/oracle/oradata/VG41VWT/domea_ftr_imt_10.dbf';
SET NEWNAME FOR TEMPFILE 1 TO '/oracle/oradata/VG41VWT/temp01.dbf';
DUPLICATE TARGET DATABASE TO VG41VWT
LOGFILE
GROUP 1
'/oralogs/redolog/VG41VWT/logVG41VWT1.log',
'/oralogs/redolog/VG41VWT/logVG41VWT2.log',
'/oralogs/redolog/VG41VWT/logVG41VWT3.log'
) SIZE 10000K,
GROUP 2
'/oramirr/redolog/VG41VWT/logVG41VWT1.log',
'/oramirr/redolog/VG41VWT/logVG41VWT2.log',
'/oramirr/redolog/VG41VWT/logVG41VWT3.log'
) SIZE 10000K;
exit
The Error-Message is:
executing command: SET NEWNAME
Starting restore at 22-jul-10 14:24
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/22/2010 14:24:04
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 34 found to restore
etc.
EDIT:
Now I realize that there is a "released channel" - message just before the Error message. But I don't think this is the reason for the trouble, but part of the ERROR-treatment.
Thanks
f.
Edited by: user8964905 on 22.07.2010 05:55
Edited by: user8964905 on 23.07.2010 01:43 -
RMAN-11001: alter database mount standby database
I'm doing a duplicate for a standby database and I'm getting this error
Oracle 8i Tru64
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel clone_defaul
t
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter database moun
t standby database
RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
Recovery Manager complete.
Any help pleaseCheck for parameter mismatches between parameter file and control file.
Check your parameter file. Check db_name paramter in paramter file used in the standby database. -
RMAN-05520: database name mismatch, auxiliary instance has ORADB
Hi,
i am using Oracle 10g (10.2.0.1.0) in RHEL 5 server. i am trying to duplicate my primary database(ORADB) to standby database with name DEVDB in different server. I have taken an RMAN backup and transferred to standby server and now i am trying to duplicate with the below commands
[oracle@rhel5 data]$ rman target / auxiliary sys/oracle@DEVDB
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Mar 9 16:11:52 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORADB (DBID=2542358497, not open)
connected to auxiliary database: ORADB (not mounted)
RMAN>
RMAN>
RMAN> duplicate target database to DEVDB
2> ;
Starting Duplicate Db at 09-MAR-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=151 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/09/2013 16:14:02
RMAN-05520: database name mismatch, auxiliary instance has ORADB, command specified DEVDB
My primary db pfile has
*.db_name='ORADB'
*.db_unique_name='ORADB'
My standby db has
*.db_name='ORADB'
*.db_unique_name='DEVDB'
Regards,
007Hello again;
Agreed. You have at least two issues.
Generally I change the SID
export ORACLE_SID=DEVDB
Then I start NOMOUNT using an INIT file.
Then this should be correct
connected to target database: ORADB (DBID=2542358497, not open)
connected to auxiliary database: ORADB (not mounted)h2. Later
I think I was wrong I would like to change my answer. I looked back and found my old notes and things are not as I stated above.
I used an INIT file ( standby side ) for cloning as follows :
db_name=RECOVER2
instance_name=RECOVER2
control_files=("/u01/app/oracle/oradata/RECOVER2/control01.ctl", "/u01/app/oracle/flash_recovery_area/RECOVER2/control02.ctl")
db_recovery_file_dest=/u01/app/oracle/flash_recovery_area
db_recovery_file_dest_size=4070572032
compatible=11.2.0.0.0
core_dump_dest='/u01/app/oracle/diag/rdbms/recover2/RECOVER2/cdump'
db_block_size=8192
audit_file_dest=/u01/app/oracle/admin/RECOVER2/adump
undo_tablespace=UNDOTBS1
undo_management = AUTO
undo_retention=10800So for the duplicate I don't set DB_UNIQUE_NAME
I Backed up the target database as shown here with the ‘backup current controlfile for standby format’ command:
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/RECOVER2/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/RECOVER2/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/RECOVER2/sb_t%t_s%s_p%p';
release channel d1;
}I did a startup the standby as follows : ( Notice you are correct about the SID and I was incorrect )
export ORACLE_SID=RECOVER2
/home/oracle:SRECOVER2 >sysplus "/ as sysdba"
Connected to an idle instance.
SQL> startup nomount pfile='/u01/app/oracle/admin/RECOVER2/pfile/initRECOVER2.ora';I started RMAN like this :
/home/oracle:SRECOVER2 >export ORACLE_SID=RECOVER2
rman target sys/password@recover2 auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Sep 10 13:35:29 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECOVER2 (not mounted)So you connect to the Primary, but the auxiliary should show "not mounted"
Finally I issue the duplicate command
RMAN> run {
2> allocate channel C1 device type disk;
3> allocate auxiliary channel C2 device type disk;
4> duplicate target database for standby nofilenamecheck;
5> }Best Regards
mseberg
Edited by: mseberg on Mar 9, 2013 10:39 AM -
RMAN backup in ORACLE RAC database
Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.Duplicate thread
RMAN configuration in ORACLE RAC database
Khurram -
Error in duplicating dataguard, RMAN-04006: error from auxiliary,ORA-12514
Hi All,
Trying to duplicate using rman and facing below issue
rman TARGET sys/oracle@pawsdb AUXILIARY sys/oracle@adpaws
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jun 19 20:47:09 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PAWSDB (DBID=3014417093)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
TNS on aux looks like this
ADPAWS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.210.23.227)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = adpaws)
Listener under grid home (ASM) on aux looks like this
# listener.ora Network Configuration File: /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /home/oracle/app/oracle/product/11.2.0/grid)
(SID_NAME = adpaws)
(GLOBAL_DBNAME= adpaws.example.com)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = cuscmetl.hillscte.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
ADR_BASE_LISTENER = /home/oracle/app/oracle
output of lsnrctl on aux looks like this
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 19-JUN-2012 20:53:49
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date 19-JUN-2012 20:53:42
Uptime 0 days 0 hr. 0 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /home/oracle/app/oracle/product/11.2.0/grid/network/admin/listener.ora
Listener Log File /home/oracle/app/oracle/diag/tnslsnr/cuscmetl/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=cuscmetl.hillscte.com)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "adpaws.example.com" has 1 instance(s).
Instance "adpaws", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
TNS on target is also configured properly, both are tnsping successful from each other, running this command from aux server results in failure
Please help
thanksThanks for reply, below are the last 50 lines from listener log
<msg time='2012-06-19T21:10:13.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56363)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:13.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:13 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56364)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56366)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:18.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:18 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56367)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.126-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56368)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:23.159-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:23 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56369)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.125-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56371)) * establish * etldb * 0
</txt>
</msg>
<msg time='2012-06-19T21:10:28.160-05:00' org_id='oracle' comp_id='tnslsnr'
type='UNKNOWN' level='16' host_id='server2.server.com'
host_addr='10.210.23.227'>
<txt>19-JUN-2012 21:10:28 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))(SERVICE_NAME=etldb)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.210.23.229)(PORT=56372)) * establish * etldb * 0
</txt>
</msg> -
Rman connect - requires different privilegies than sqlplus?
Hello!
Linux x86, Oracle 10.2.0.2
Im going to do an Duplicate (connect target sys/bla@bla catalog rman/bla@bla auxillary /
catalog and aux works fine, however i willl get insufficent privilegies on the target connect
Host A: New Host to duplicate to
Host B: Old Host
Backupset: On Tape
I can connect (sqlplus) with sys from Host A to Host B, and vice versa. But i cant connect to Host B within rman from host A. Port 1521 is opened, and since sqlplus connection works i just assums that rman works aswell, no?
Thank you for any direction with this!PaulTill2508 wrote:
RMAN shouldnt require different privs to do this.
Can you try reversing where you run the rman duplicate from, so,
On host A (where the source of the duplicate is):
rman target / catalog rman/bla@bla auxillary sys/bla@bla_auxThanks
PaulHello, i cant do reverse either, same error message:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-01031: insufficient privilegesI tried the other things as well but did not work.
sybrand_b wrote:
as sysdba is implicit with rman and doesn't need to be added.
However if the user doesn't have sysdba ora-1031 will result.
Sybrand Bakker
Senior Oracle DBAsys is always sysdba correct?
Thankful for more help
Maybe you are looking for
-
NVL and replace date when date field is null from table
I am trying to replace a field with a date default when it is null and it is not working I was wondering if someone could give me a clue to what I am doing wrong Here is the part of the select statement: NVL (o.mass_production_date__c, TO_DATE ('1900
-
HT4623 Please help , I cant do anything on my I-Pad , Can not connect to server .
I Cant do anything on my I-Pad all of a sudden , says cant connect to server
-
Help needed in Upgrading 10g reports to OBIEE 11g
Hi folks, We have a set of BI Answer reports which were developed in OBIEE 10g(10.1.3.4.1). We would like to upgrade it to OBIEE 11g. Could anyone please help me out in solving this. Thanks in advance. Regards, Arun
-
Secure link to iTunes store failed Win 7x64 Professional
Microsoft Windows 7 x64 Business Edition Service Pack 1 (Build 7601) Dell Inc. OptiPlex 960 iTunes 11.2.0.115 QuickTime 7.7.5 Network Connectivity Tests: Firewall Information Windows Firewall is on. iTunes is NOT enabled in Windows Firewall. Connecti
-
SSL Cert Setup on the Palm Pre
I am having issues setting up my companies email on the Palm Pre. We use an SSL cert and for some reason I get Certificate Error. Is the time and date wrong. I looked at many blogs with other people having this issue and they say a root cert needs