RMAN - Connect target / Hang

Hello,
Last three days we have our backup failed due to strange error.
We have this backup script running from same Shell script almost last three years. It was working fine till last Friday and suddenly stop working.
We have db upgraded before three months ago from 10.2.0.3 to 10.2.0.4. as far as i know there is no other db changes or OS changes
If i try to connect directly to catalog it's work fine
rman Recovery Manager: Release 10.2.0.4.0 - Production on Tue Jul 13 15:26:59 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect catalog XXX/XX@RMAN_XXX
connected to recovery catalog database
Than it's connect to the catalog fine.
But when i try to connect to the target it's hand forever.
rman Recovery Manager: Release 10.2.0.4.0 - Production on Tue Jul 13 15:29:45 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target /
Hang
hang
hang
Here is the backup logs
Backup Logs :
XXXXX Online Backup WITH CATALOG Started At : Monday, July 12, 2010 7:00:15 PM CDT
Started running on Mon Jul 12 19:00:15 CDT 2010
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Jul 12 19:00:15 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN>
DB version : oracle 10.2.0.4
Catalog : 10.2.0.3
Os : SunOS 5.10
Experts , please put some lights .
Thanks in advance

NO clue in Alert log.
We have enough space for backup
Here is the output
12263: door_info(7, 0xFFFFFD7FFFDF2AD0) = 0
12263: door_call(7, 0xFFFFFD7FFFDF2B30) = 0
12263: getgid() = 19900 [19900]
12263: getuid() = 623 [623]
12263: getpid() = 12263 [12240]
12263: brk(0x0663CC20) = 0
12263: brk(0x06648C20) = 0
12263: brk(0x06648C20) = 0
12263: brk(0x0664CC20) = 0
12263: brk(0x0664CC20) = 0
12263: brk(0x06650C20) = 0
12263: so_socket(PF_INET, SOCK_DGRAM, IPPROTO_IP, "", SOV_DEFAULT) = 21
12263: bind(21, 0x0664C5F0, 16, SOV_SOCKBSD) = 0
12263: getsockname(21, 0xFFFFFD7FFFDF67D0, 0xFFFFFD7FFFDF6810, SOV_DEFAULT) = 0
12263: getpeername(21, 0xFFFFFD7FFFDF67D0, 0xFFFFFD7FFFDF6810, SOV_DEFAULT) Err#134 ENOTCONN
12263: getsockopt(21, SOL_SOCKET, SO_SNDBUF, 0xFFFFFD7FFFDF6904, 0xFFFFFD7FFFDF6900, SOV_DEFAULT) = 0
12263: getsockopt(21, SOL_SOCKET, SO_RCVBUF, 0xFFFFFD7FFFDF6904, 0xFFFFFD7FFFDF6900, SOV_DEFAULT) = 0
12263: fcntl(21, F_SETFD, 0x00000001) = 0
12263: ioctl(21, FIONBIO, 0xFFFFFD7FFFDF69A8) = 0
12263: brk(0x06650C20) = 0
12263: brk(0x06658C20) = 0
12263: access("/var/tmp/.oracle", F_OK) = 0
12263: chmod("/var/tmp/.oracle", 01777) Err#1 EPERM [ALL]
12263: so_socket(PF_UNIX, SOCK_STREAM, 0, "", SOV_DEFAULT) = 22
12263: access("/var/tmp/.oracle/sprocr_local_conn_0_PROC", F_OK) = 0
12263: connect(22, 0xFFFFFD7FFFDF0668, 110, SOV_DEFAULT) = 0
12263: fcntl(22, F_SETFD, 0x00000001) = 0
12263: sigaction(SIGPIPE, 0xFFFFFD7FFFDF0870, 0xFFFFFD7FFFDF0960) = 0
12263: ioctl(22, FIONBIO, 0xFFFFFD7FFFDF1DD8) = 0
12263: write(22, " 0\0\0\001\001\001\001\0".., 48) = 48
12263: pollsys(0x0664A540, 2, 0x00000000, 0x00000000) = 1
12263: pollsys(0x0664A540, 2, 0x00000000, 0x00000000) = 1
12263: read(22, " 0\0\0\001\001\001\001\0".., 32768) = 48
12263: write(22, " 4\0\0\001\002\001010101".., 52) = 52
12265: read(13, 0x06512FA6, 2064) (sleeping...)
12240: read(12, 0x012F1056, 2064) (sleeping...)
12263: pollsys(0x0664A540, 2, 0x00000000, 0x00000000) (sleeping...)
12240: Received signal #2, SIGINT, in read() [caught]
12240: read(12, 0x012F1056, 2064) Err#91 ERESTART
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: kill(12263, SIGURG) = 0
12263: Received signal #21, SIGURG, in pollsys() [caught]
12263: siginfo: SIGURG pid=12240 uid=623
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12263: pollsys(0x0664A540, 2, 0x00000000, 0x00000000) Err#91 ERESTART
12240: setcontext(0xFFFFFD7FFFDD8410)
12263: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12263: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12263: lwp_sigmask(SIG_SETMASK, 0x9FBED057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12263: setcontext(0xFFFFFD7FFFDF0A10)
12240: Received signal #2, SIGINT, in read() [caught]
12240: read(12, 0x012F1056, 2064) Err#91 ERESTART
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: setcontext(0xFFFFFD7FFFDD8410)
12240: Received signal #2, SIGINT, in read() [caught]
12240: read(12, 0x012F1056, 2064) Err#91 ERESTART
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: setcontext(0xFFFFFD7FFFDD8410)
12240: Received signal #2, SIGINT, in read() [caught]
12240: read(12, 0x012F1056, 2064) Err#91 ERESTART
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: lwp_sigmask(SIG_SETMASK, 0x9FBEF057, 0x0000FFF7) = 0xFFBFFEFF [0x0000FFFF]
12240: setcontext(0xFFFFFD7FFFDD8410)
12263: pollsys(0x0664A540, 2, 0x00000000, 0x00000000) (sleeping...)
12240: read(12, 0x012F1056, 2064) (sleeping...)

Similar Messages

RMAN connect target /@XE not possible?

I tried something (Backup/recovery) with RMAN on XE successfully.
Now I have to use:
RMAN Target SYS/pwd@XE nocatalog and got:
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-12170: TNS:Connect timeout occurred
same error on using:
RMAN> connect target /@XE
But sqlplus /@XE as sysdba works fine.
No TCP/IP included in RMAN?
Any ideas ?!!!

sorry got RMAN from my other 10gR2EE install following in the PATH.
wondering that RMAN not available on windows (made first test on linux).
RMAN should be included...

RMAN cannot connect target

RMAN> connect target
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-04063: package body "SPS.DBMS_BACKUP_RESTORE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SPS.DBMS_BACKUP_RESTORE"
RMAN-04015: error setting target database character set to WE8MSWIN1252

905377 wrote:
RMAN> connect target
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-04063: package body "SPS.DBMS_BACKUP_RESTORE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SPS.DBMS_BACKUP_RESTORE"
RMAN-04015: error setting target database character set to WE8MSWIN1252Hi,
Same error again,
>
C:\Documents and Settings\Administrator>rman
Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jan 3 15:57:53 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target system/spsadmin@SPS
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-04063: package body "SPS.DBMS_BACKUP_RESTORE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SPS.DBMS_BACKUP_RESTORE"
RMAN-04015: error setting target database character set to WE8MSWIN1252
RMAN> exit
>
Some how i have in my notepad, how have resolved last time. Check below work around
SQL> Select owner,trigger_name,triggering_event,status from dba_triggers where triggering_event like '%LOGON%' ;
OWNER TRIGGER_NAME
TRIGGERING_EVENT
STATUS
SYS DB_LOGON
LOGON
ENABLED
SQL> alter trigger sys.db_logon disable;
Trigger altered.
Then check for invalid objects, and recompile them @?/rdbms/admin/utlrp.sql
next
C:\Documents and Settings\Administrator>rman target /
Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jan 3 16:18:40 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: SPS (DBID=1754608551)
RMAN> list backup of database;
using target database control file instead of recovery catalog
List of Backup Sets
===================
C:\Documents and Settings\Administrator>
Re: why looping chain of synonyms occur
Edited by: CKPT on Apr 16, 2012 11:27 AM

Getting ORA-01031 while connect target

Hi,
I'm trying to perform a rman duplictate.
I've created the orapwd file and setted the remote_login_passwordfile parameter as "EXCLUSIVE". I also have configured the connection to the target database on the tnsnames.ora file
I'm getting this error:
[server]> rman
RMAN> CONNECT TARGET system/iwjIGPE@TARGET_DB
RMAN-00571: ======================================
RMAN-00569: ==== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ======================================
ORA-01031: insufficient privileges
RMAN> exit
Recovery Manager complete.
.... But I can connect remotely though sqlplus:
[server]> sqlplus system/iwjIGPE@TARGET_DB
SQL*Plus: Release 11.2.0.2.0 Production on Thu Sep 13 13:04:32 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
SQL> exit
thanks for your help!

Hi again!
I'm trying to follow the steps you propose:
[server]> rman target sys/c9vhLZT0@TARGET_DB auxiliary /
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Sep 13 13:29:07 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: ===================================
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS =========
RMAN-00571: ===============================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01017: invalid username/password; logon denied
I'm sure that the password is correct. I've re-created the password file and the error continues.
I'm still able to connect from sqlplus ...
[server]> echo $ORACLE_SID
AUX
[server]> sqlplus
SQL*Plus: Release 11.2.0.2.0 Production on Thu Sep 13 13:31:35 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name: sys@TARGET_DB as sysdba
Enter password:
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
SQL >
I've granted the sysdba role to system:
SYS @ TARGET_DB > select * from v$pwfile_users;
USERNAME SYSDB SYSOP SYSAS
SYS TRUE TRUE FALSE
SYSTEM TRUE FALSE FALSE
I'm not able to connect either with sys not with system users
Thanks a lot
Edited by: user11978261 on Sep 13, 2012 4:41 AM

Unable to connect target /

Hi,
I have Oracle 10gR2 10.2.0.3 db on Solaris. I use EM to backup the db to the disk. I was able to connect to the db but today I am getting an error.
$ . oraenv
ORACLE_SID = [prod_db]
rman
Recovery Manager: Release 10.2.0.3.0 - Production on Mon May 28 10:33:33 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect target /
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
I have recreated the password file and also checked the password_parameter in the init.ora
SQL> show parameter password
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP
SYS TRUE TRUE
SQL> select username, account_status from dba_users where username in ('SYSMAN',
'DBSNMP','MGMT_VIEW');
2
USERNAME ACCOUNT_STATUS
MGMT_VIEW OPEN
SYSMAN OPEN
DBSNMP OPEN
I can connect
rman> connect TARGET SYS/password@prod_db
Can anyone advise. Thanks

Werner,
Thanks for the reply. The user I am connect as is a part of the dba group.
$ cat /etc/group
oinstall::200:
dbaprod::201:oraprod
operprod::202:oraprod
webprod::300:webprod
I login as oraprod and . oraenv prod_db
rman
connect target /
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges

Rman connect auxiliary displays wrong database

I am trying to use the new 11g duplicate from active database feature. I am running into the following error and can't figure out what is wrong.
RMAN> connect target sys/xxxxx@ebsprod
connected to target database: EBSPROD (DBID=3420264532)
RMAN> connect auxiliary sys/xxxxx@abc
connected to auxiliary database: EBSPROD (not mounted)
RMAN>
The auxiliary database shows the same DB name as the target. The correct auxiliary name is ABC in this case. The DB is started in nomount with the correct name. The new init.ora is correct as well. What is it looking at? Any help would be greatly appreciated.

The correct auxiliary name is ABC in this case. The DB is started in nomount with the correct name. The new init.ora is correct as well.show us the requested db_name parameter, init.ora and tnsnames.ora
RMAN displays the value of db_name
db_unique_name and instance_name doesnt matter here

RMAN connection problem

When I'm trying to connect rman target database as below::--
sid is rbldb (version is 10.2.0.4.0)with 4.4 patch set
============
1:--(IN THE BELOW CASE CONNECTION FAILS)
RMAN> connect target backup/backup@rbldb
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
2:--(IN THE BELOW CASE CONNECTION SUCCESSFUL)
RMAN> connect target backup/backup
connected to target database: RBLDB (DBID=658865330)
RMAN>
means when i m using @ simbole the rman connection gives error (insufficient privileges)
if i don't put that then get connected......

if you are in the same server where your target db resides with proper dba authenication then connect string not require,
RMAN> connect target
if you want to connect from remote machine or using connect string password file require
RMAN> conn target sys/oracle@STRING

RMAN duplicate target using set until telling me it can not find data files

I have RMAN scripts that I use freqently to clone a database from DB (production) to another (non-prod). These work just fine. I use the set until so that I can tell it at what point I want the new DB to be created from the backups of the source.
I had a request to go back a few weeks and the backup files (I do compressed backups to disk) were on tape. I had my backup person restore my backup directory for the source DB as it looked on a certain day (May 28). I have an 8 day retention policy and so the backup files that were restored showed files all the way back to 5/20 ( includes the point I want to use in my set until clause).
However, whenever I try to execute the rman clone, it tells me for each datafile:
RMAN-06023: no backup or copy of datafile 1 found to restore
Like I said, I am able to do this for a current backup that is on disk. I moved the backup files to the source db server and it works fine. However, from these files restored from tape it errors.
Here is the RMAN script:
spool log to c:\temp\clone_CSPROD_CSPRSUM1.log;
#connect to catalog <catalog info>
# target is the source and auxiliary is destination
#connect target <put in source info here>
#connect auxiliary /
run {
allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
##Archivelog number get from sql archive log list command
#set until sequence 831;
set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
duplicate target database to CSPRSUM1 nofilenamecheck
logfile
group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
Exit
Here is the output:
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog <redacted info>>
2> # target is the source and auxiliary is destination
3> #connect target <redacted info>
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> #set until sequence 831;
14> set until time "to_date('2011-05-25 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
starting full resync of recovery catalog
full resync complete
allocated channel: d1
channel d1: SID=534 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=532 device type=DISK
allocated channel: d4
channel d4: SID=531 device type=DISK
allocated channel: a1
channel a1: SID=530 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 15-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 260398799;
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";
set newname for datafile 5 to
"+data";
set newname for datafile 6 to
"+data";
set newname for datafile 7 to
"+data";
set newname for datafile 8 to
"+data";
set newname for datafile 9 to
"+data";
set newname for datafile 10 to
"+data";
set newname for datafile 11 to
"+data";
set newname for datafile 12 to
"+data";
set newname for datafile 13 to
"+data";
set newname for datafile 14 to
"+data";
set newname for datafile 15 to
"+data";
set newname for datafile 16 to
"+data";
set newname for datafile 17 to
"+data";
set newname for datafile 18 to
"+data";
set newname for datafile 19 to
"+data";
set newname for datafile 20 to
"+data";
set newname for datafile 21 to
"+data";
set newname for datafile 22 to
"+data";
set newname for datafile 23 to
"+data";
set newname for datafile 24 to
"+data";
set newname for datafile 25 to
"+data";
set newname for datafile 26 to
"+data";
set newname for datafile 27 to
"+data";
set newname for datafile 28 to
"+data";
set newname for datafile 29 to
"+data";
set newname for datafile 30 to
"+data";
set newname for datafile 31 to
"+data";
set newname for datafile 32 to
"+data";
set newname for datafile 33 to
"+data";
set newname for datafile 34 to
"+data";
set newname for datafile 35 to
"+data";
set newname for datafile 36 to
"+data";
set newname for datafile 37 to
"+data";
set newname for datafile 38 to
"+data";
set newname for datafile 39 to
"+data";
set newname for datafile 40 to
"+data";
set newname for datafile 41 to
"+data";
set newname for datafile 42 to
"+data";
set newname for datafile 43 to
"+data";
set newname for datafile 44 to
"+data";
set newname for datafile 45 to
"+data";
set newname for datafile 46 to
"+data";
set newname for datafile 47 to
"+data";
set newname for datafile 48 to
"+data";
set newname for datafile 49 to
"+data";
set newname for datafile 50 to
"+data";
set newname for datafile 51 to
"+data";
set newname for datafile 52 to
"+data";
set newname for datafile 53 to
"+data";
set newname for datafile 54 to
"+data";
set newname for datafile 55 to
"+data";
set newname for datafile 56 to
"+data";
set newname for datafile 57 to
"+data";
set newname for datafile 58 to
"+data";
set newname for datafile 59 to
"+data";
set newname for datafile 60 to
"+data";
set newname for datafile 61 to
"+data";
set newname for datafile 62 to
"+data";
set newname for datafile 63 to
"+data";
set newname for datafile 64 to
"+data";
set newname for datafile 65 to
"+data";
set newname for datafile 66 to
"+data";
set newname for datafile 67 to
"+data";
set newname for datafile 68 to
"+data";
set newname for datafile 69 to
"+data";
set newname for datafile 70 to
"+data";
set newname for datafile 71 to
"+data";
set newname for datafile 72 to
"+data";
set newname for datafile 73 to
"+data";
set newname for datafile 74 to
"+data";
set newname for datafile 75 to
"+data";
set newname for datafile 76 to
"+data";
set newname for datafile 77 to
"+data";
set newname for datafile 78 to
"+data";
set newname for datafile 79 to
"+data";
set newname for datafile 80 to
"+data";
set newname for datafile 81 to
"+data";
set newname for datafile 82 to
"+data";
set newname for datafile 83 to
"+data";
set newname for datafile 84 to
"+data";
set newname for datafile 85 to
"+data";
set newname for datafile 86 to
"+data";
set newname for datafile 87 to
"+data";
set newname for datafile 88 to
"+data";
set newname for datafile 89 to
"+data";
set newname for datafile 90 to
"+data";
set newname for datafile 91 to
"+data";
set newname for datafile 92 to
"+data";
set newname for datafile 93 to
"+data";
set newname for datafile 94 to
"+data";
set newname for datafile 95 to
"+data";
set newname for datafile 96 to
"+data";
set newname for datafile 97 to
"+data";
set newname for datafile 98 to
"+data";
set newname for datafile 99 to
"+data";
set newname for datafile 100 to
"+data";
set newname for datafile 101 to
"+data";
set newname for datafile 102 to
"+data";
set newname for datafile 103 to
"+data";
set newname for datafile 104 to
"+data";
set newname for datafile 105 to
"+data";
set newname for datafile 106 to
"+data";
set newname for datafile 107 to
"+data";
set newname for datafile 108 to
"+data";
set newname for datafile 109 to
"+data";
set newname for datafile 110 to
"+data";
set newname for datafile 111 to
"+data";
set newname for datafile 112 to
"+data";
set newname for datafile 113 to
"+data";
set newname for datafile 114 to
"+data";
set newname for datafile 115 to
"+data";
set newname for datafile 116 to
"+data";
set newname for datafile 117 to
"+data";
set newname for datafile 118 to
"+data";
set newname for datafile 119 to
"+data";
set newname for datafile 120 to
"+data";
set newname for datafile 121 to
"+data";
set newname for datafile 122 to
"+data";
restore
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
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
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 15-JUN-11
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/15/2011 11:21:42
RMAN-01005: not all datafiles have backups that can be recovered to scn 260398799
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 122 found to restore
RMAN-06023: no backup or copy of datafile 121 found to restore
RMAN-06023: no backup or copy of datafile 120 found to restore
RMAN-06023: no backup or copy of datafile 119 found to restore
RMAN-06023: no backup or copy of datafile 118 found to restore
RMAN-06023: no backup or copy of datafile 117 found to restore
RMAN-06023: no backup or copy of datafile 116 found to restore
RMAN-06023: no backup or copy of datafile 115 found to restore
RMAN-06023: no backup or copy of datafile 114 found to restore
RMAN-06023: no backup or copy of datafile 113 found to restore
RMAN-06023: no backup or copy of datafile 112 found to restore
RMAN-06023: no backup or copy of datafile 111 found to restore
RMAN-06023: no backup or copy of datafile 110 found to restore
RMAN-06023: no backup or copy of datafile 109 found to restore
RMAN-06023: no backup or copy of datafile 108 found to restore
RMAN-06023: no backup or copy of datafile 107 found to restore
RMAN-06023: no backup or copy of datafile 106 found to restore
RMAN-06023: no backup or copy of datafile 105 found to restore
RMAN-06023: no backup or copy of datafile 104 found to restore
RMAN-06023: no backup or copy of datafile 103 found to restore
RMAN-06023: no backup or copy of datafile 102 found to restore
RMAN-06023: no backup or copy of datafile 101 found to restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
RMAN-06023: no backup or copy of datafile 98 found to restore
RMAN-06023: no backup or copy of datafile 97 found to restore
RMAN-06023: no backup or copy of datafile 96 found to restore
RMAN-06023: no backup or copy of datafile 95 found to restore
RMAN-06023: no backup or copy of datafile 94 found to restore
RMAN-06023: no backup or copy of datafile 93 found to restore
RMAN-06023: no backup or copy of datafile 92 found to restore
RMAN-06023: no backup or copy of datafile 91 found to restore
RMAN-06023: no backup or copy of datafile 90 found to restore
RMAN-06023: no backup or copy of datafile 89 found to restore
RMAN-06023: no backup or copy of datafile 88 found to restore
RMAN-06023: no backup or copy of datafile 87 found to restore
RMAN-06023: no backup or copy of datafile 86 found to restore
RMAN-06023: no backup or copy of datafile 85 found to restore
RMAN-06023: no backup or copy of datafile 84 found to restore
RMAN-06023: no backup or copy of datafile 83 found to restore
RMAN-06023: no backup or copy of datafile 82 found to restore
RMAN-06023: no backup or copy of datafile 81 found to restore
RMAN-06023: no backup or copy of datafile 80 found to restore
RMAN-06023: no backup or copy of datafile 79 found to restore
RMAN-06023: no backup or copy of datafile 78 found to restore
RMAN-06023: no backup or copy of datafile 77 found to restore
RMAN-06023: no backup or copy of datafile 76 found to restore
RMAN-06023: no backup or copy of datafile 75 found to restore
RMAN-06023: no backup or copy of datafile 74 found to restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 72 found to restore
RMAN-06023: no backup or copy of datafile 71 found to restore
RMAN-06023: no backup or copy of datafile 70 found to restore
RMAN-06023: no backup or copy of datafile 69 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restore
RMAN-06023: no backup or copy of datafile 66 found to restore
RMAN-06023: no backup or copy of datafile 65 found to restore
RMAN-06023: no backup or copy of datafile 64 found to restore
RMAN-06023: no backup or copy of datafile 63 found to restore
RMAN-06023: no backup or copy of datafile 62 found to restore
RMAN-06023: no backup or copy of datafile 61 found to restore
RMAN-06023: no backup or copy of datafile 60 found to restore
RMAN-06023: no backup or copy of datafile 59 found to restore
RMAN-06023: no backup or copy of datafile 58 found to restore
RMAN-06023: no backup or copy of datafile 57 found to restore
RMAN-06023: no backup or copy of datafile 56 found to restore
RMAN-06023: no backup or copy of datafile 55 found to restore
RMAN-06023: no backup or copy of datafile 54 found to restore
RMAN-06023: no backup or copy of datafile 53 found to restore
RMAN-06023: no backup or copy of datafile 52 found to restore
RMAN-06023: no backup or copy of datafile 51 found to restore
RMAN-06023: no backup or copy of datafile 50 found to restore
RMAN-06023: no backup or copy of datafile 49 found to restore
RMAN-06023: no backup or copy of datafile 48 found to restore
RMAN-06023: no backup or copy of datafile 47 found to restore
RMAN-06023: no backup or copy of datafile 46 found to restore
RMAN-06023: no backup or copy of datafile 45 found to restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 41 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to 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
RMAN> Exit
Recovery Manager complete.
Edited by: kerrygm on Jun 15, 2011 11:36 AM

Maybe making progress.
I got into RMAN and did a List backup command. In looking at the output, I see that it does have the 5/20 backup showing. Here is part of the output:
BS Key Type LV Size Device Type Elapsed Time Completion Time
965689 Full 19.86M DISK 00:00:01 16-JUN-11
BP Key: 967942 Status: AVAILABLE Compressed: NO Tag: TAG20110616T231223
Piece Name: F:\BACKUPS\CSPROD\C-368871413-20110616-01
SPFILE Included: Modification time: 16-JUN-11
SPFILE db_unique_name: CSPROD
Control File Included: Ckp SCN: 369596068 Ckp time: 16-JUN-11
BS Key Size Device Type Elapsed Time Completion Time
966218 403.84M DISK 00:00:00 20-MAY-11
BP Key: 967842 Status: AVAILABLE Compressed: YES Tag: TAG20110520T231012
Piece Name: F:\BACKUPS\CSPROD\A1\CSPROD_ARCH_5844
List of Archived Logs in backup set 966218
Thrd Seq Low SCN Low Time Next SCN Next Time
1 2112 237027300 20-MAY-11 237046947 20-MAY-11
1 2113 *237046947* 20-MAY-11 237059284 20-MAY-11
1 2114 237059284 20-MAY-11 237216514 20-MAY-11
1 2115 237216514 20-MAY-11 237709545 20-MAY-11
1 2116 237709545 20-MAY-11 237722825 20-MAY-11
1 2117 237722825 20-MAY-11 237730431 20-MAY-11
1 2118 237730431 20-MAY-11 237860199 20-MAY-11
I then changed my rman script to use the *237046947* SCN number that says it is from 5/20. I them kicked off my rman script and got the following result.
Spooling started in log file: c:\temp\clone_CSPROD_CSPRSUM1.log
Recovery Manager11.1.0.7.0
RMAN> #connect catalog 'rmancat/rmancat@rmancat';
2> # target is the source and auxiliary is destination
3> #connect target sys/<pwd>@csprod
4> #connect auxiliary /
5>
6> run {
7> allocate auxiliary channel d1 type disk format 'F:\backups\CSPROD\d1\CSPROD_DATA_%s';
8> allocate auxiliary channel d2 type disk format 'F:\backups\CSPROD\d2\CSPROD_DATA_%s';
9> allocate auxiliary channel d3 type disk format 'F:\backups\CSPROD\d3\CSPROD_DATA_%s';
10> allocate auxiliary channel d4 type disk format 'F:\backups\CSPROD\d4\CSPROD_DATA_%s';
11> allocate auxiliary channel a1 type disk format 'F:\backups\CSPROD\a1\CSPROD_arch_%s';
12> ##Archivelog number get from sql archive log list command
13> set until sequence 237046947;
14> ##set until time "to_date('2011-05-20 08:00:00', 'YYYY-MM-DD HH24:MI:SS')";
15> duplicate target database to CSPRSUM1 nofilenamecheck
16> logfile
17> group 1('+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log') size 50m,
18> group 2('+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log') size 50m,
19> group 3('+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log') size 50m;
20> }
allocated channel: d1
channel d1: SID=532 device type=DISK
allocated channel: d2
channel d2: SID=533 device type=DISK
allocated channel: d3
channel d3: SID=531 device type=DISK
allocated channel: d4
channel d4: SID=555 device type=DISK
allocated channel: a1
channel a1: SID=534 device type=DISK
executing command: SET until clause
Starting Duplicate Db at 17-JUN-11
RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only.
contents of Memory Script:
set until scn 373021170;
set newname for datafile 1 to
"+data";
set newname for datafile 2 to
Starting restore at 17-JUN-11
channel d1: starting datafile backup set restore
channel d1: specifying datafile(s) to restore from backup set
channel d1: restoring datafile 00003 to +DATA
channel d2: restoring datafile 00122 to +DATA
channel d2: reading from backup piece F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149
channel d3: starting datafile backup set restore
channel d3: specifying datafile(s) to restore from backup set
channel d3: restoring datafile 00002 to +DATA
channel d3: restoring datafile 00020 to +DATA
channel d4: restoring datafile 00120 to +DATA
channel d4: reading from backup piece F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147
channel d1: piece handle=F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 tag=TAG20110616T230013
channel d1: restored backup piece 1
channel d1: restore complete, elapsed time: 00:01:15
channel d4: piece handle=F:\BACKUPS\CSPROD\D2\CSPROD_DATA_6147 tag=TAG20110616T230013
channel d4: restored backup piece 1
channel d4: restore complete, elapsed time: 00:03:15
channel d2: piece handle=F:\BACKUPS\CSPROD\D4\CSPROD_DATA_6149 tag=TAG20110616T230013
channel d2: restored backup piece 1
channel d2: restore complete, elapsed time: 00:03:35
channel d3: piece handle=F:\BACKUPS\CSPROD\D1\CSPROD_DATA_6146 tag=TAG20110616T230013
channel d3: restored backup piece 1
channel d3: restore complete, elapsed time: 00:04:55
Finished restore at 17-JUN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CSPRSUM1" RESETLOGS ARCHIVELOG
MAXLOGFILES 23
MAXLOGMEMBERS 3
MAXDATAFILES 1021
MAXINSTANCES 8
MAXLOGHISTORY 584
LOGFILE
GROUP 1 ( '+DATA/CSPRSUM1/onlinelog/redo1a.log', '+FRA/CSPRSUM1/onlinelog/redo1b.log' ) SIZE 50 M ,
GROUP 2 ( '+DATA/CSPRSUM1/onlinelog/redo2a.log', '+FRA/CSPRSUM1/onlinelog/redo2b.log' ) SIZE 50 M ,
GROUP 3 ( '+DATA/CSPRSUM1/onlinelog/redo3a.log', '+FRA/CSPRSUM1/onlinelog/redo3b.log' ) SIZE 50 M
DATAFILE
'+DATA/csprsum1/datafile/system.1535.754067379'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=754067676 file name=+DATA/csprsum1/datafile/sysaux.1536.754067379
datafile 121 switched to datafile copy
input datafile copy RECID=120 STAMP=754067677 file name=+DATA/csprsum1/datafile/waapp.1653.754067403
datafile 122 switched to datafile copy
input datafile copy RECID=121 STAMP=754067677 file name=+DATA/csprsum1/datafile/cu_custom.1549.754067381
contents of Memory Script:
set until scn 373021170;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 17-JUN-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/csprsum1/datafile/system.1535.754067379'
released channel: d1
released channel: d2
released channel: d3
released channel: d4
released channel: a1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/17/2011 15:14:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 3818 and starting SCN of 372868482 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3817 and starting SCN of 372685133 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3816 and starting SCN of 372593528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3815 and starting SCN of 372374385 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3814 and starting SCN of 372325053 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3813 and starting SCN of 372316138 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3812 and starting SCN of 372249619 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3811 and starting SCN of 371775981 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3810 and starting SCN of 371643855 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3809 and starting SCN of 371614442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3808 and starting SCN of 371432892 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3807 and starting SCN of 371121955 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3806 and starting SCN of 371047786 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3805 and starting SCN of 371029095 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3804 and starting SCN of 371018252 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3803 and starting SCN of 370947755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3802 and starting SCN of 370857440 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3801 and starting SCN of 370814417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3800 and starting SCN of 370797061 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3799 and starting SCN of 370756569 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3798 and starting SCN of 370746833 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3797 and starting SCN of 370746693 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3796 and starting SCN of 370746568 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3795 and starting SCN of 370746068 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3794 and starting SCN of 370745451 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3793 and starting SCN of 370733767 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3792 and starting SCN of 370674629 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3791 and starting SCN of 370501026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3790 and starting SCN of 370498513 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3789 and starting SCN of 370497977 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3788 and starting SCN of 370497635 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3787 and starting SCN of 370497319 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3786 and starting SCN of 370496938 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3785 and starting SCN of 370495428 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3784 and starting SCN of 370491173 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3783 and starting SCN of 370390074 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3782 and starting SCN of 370385574 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3781 and starting SCN of 370385310 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3780 and starting SCN of 370385044 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3779 and starting SCN of 370368486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3778 and starting SCN of 370333960 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3777 and starting SCN of 370330980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3776 and starting SCN of 370327876 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3775 and starting SCN of 370174433 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3774 and starting SCN of 370148373 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3773 and starting SCN of 370147821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3772 and starting SCN of 370147623 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3771 and starting SCN of 370141528 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3770 and starting SCN of 369711271 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3769 and starting SCN of 369621694 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 3768 and starting SCN of 369595614 found to restore
RMAN> Exit
Recovery Manager complete.
What I am not sure is if the SCN I used in my set until sequence command was from 5/20, when I look at the backup pieces that it is reading to restore from, they appear to be from backup files taken from June.
(e.g channel d1: reading from backup piece F:\BACKUPS\CSPROD\D3\CSPROD_DATA_6148 -- this is a 6/16 backup file).
Also, as you can see it was not able to do a media recovery.
Thanks in advance for your help.

RMAN-06429: TARGET database is not compatible with this version of RMAN

he Hi,
how can i solve this issue . how i will upgrade the Rman. My production database details are below
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
while i'm configuring rman i'm getting below error . please help me.
C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
rgds,
john

Johnvd wrote:
Hi Hemant,
i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
how its happening is there any where i have to change the path.
Regards,
johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
If you are using windows, run the following commands in command prompt and then copy/paste the output:
echo 5ORACLE_HOME%
echo %PATH%
If you are using unix, run the following commands in terminal and then copy/paste the output:
echo $ORACLE_HOME
echo $PATH
Regards
Gokhan

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,
RJL

For 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)

Sessions/connections gets hang during update and select operations.

A table with 3 million records, which has customer details data.
Everyday application is executing select and update queries on that table.
Sessions/connections gets hang during update and select operations.
After checking ADDM report, following are the findings:
Please suggest the solutions
Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 145.22 active sessions, 99.77% of total activity.
SQL statements were found waiting for row lock waits.
Recommendation 1: Application Analysis
Estimated benefit is 145.22 active sessions, 99.77% of total activity.
Action
Significant row contention was detected in the TABLE
"AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
row contention in the application logic using the given blocked SQL.
Related Object
Database object with ID 82155.
Rationale
The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The session with ID 50 and serial number 34525 in instance number 1 was
the blocking session responsible for 100% of this recommendation's
benefit.
Symptoms That Led to the Finding:
Wait class "Application" was consuming significant database time.
Impact is 145.22 active sessions, 99.77% of total activity.
Finding 2: Top SQL Statements
Impact is 46.39 active sessions, 31.87% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
Recommendation 1: SQL Tuning
Estimated benefit is 46.39 active sessions, 31.87% of total activity.
Action
Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 974vg65j29pmv.
UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "974vg65j29pmv" was executed 212 times and had
an average elapsed time of 2494 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "974vg65j29pmv".

**addm report **
          ADDM Report for Task 'TASK_7526'
Analysis Period
AWR snapshot range from 5003 to 5004.
Time period starts at 08-JUL-13 11.00.27 AM
Time period ends at 08-JUL-13 12.00.45 PM
Analysis Target
Database 'AVAYADB' with DB ID 2878789264.
Database version 11.2.0.1.0.
ADDM performed an analysis of instance avayadb, numbered 1 and hosted at
NG-LA04AVAYA01.
Activity During the Analysis Period
Total database time was 563062 seconds.
The average number of active sessions was 155.63.
Summary of Findings
   Description         Active Sessions      Recommendations
                       Percent of Activity
1 Row Lock Waits      155.44 | 99.88       1
2 Top SQL Statements 26.67 | 17.14        1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: Row Lock Waits
Impact is 155.4 active sessions, 99.88% of total activity.
SQL statements were found waiting for row lock waits.
   Recommendation 1: Application Analysis
   Estimated benefit is 155.44 active sessions, 99.88% of total activity.
   Action
      Significant row contention was detected in the TABLE
      "AVAYA.AIRTEL_CUSTOMER_MASTER" with object ID 82155. Trace the cause of
      row contention in the application logic using the given blocked SQL.
      Related Object
         Database object with ID 82155.
   Rationale
      The SQL statement with SQL_ID "974vg65j29pmv" was blocked on row locks.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The session with ID 167 and serial number 6084 in instance number 1 was
      the blocking session responsible for 100% of this recommendation's
      benefit.
   Symptoms That Led to the Finding:
      Wait class "Application" was consuming significant database time.
      Impact is 155.45 active sessions, 99.88% of total activity.
Finding 2: Top SQL Statements
Impact is 26.66 active sessions, 17.14% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
   Recommendation 1: SQL Tuning
   Estimated benefit is 26.67 active sessions, 17.14% of total activity.
   Action
      Investigate the UPDATE statement with SQL_ID "974vg65j29pmv" for
      possible performance improvements. You can supplement the information
      given here with an ASH report for this SQL_ID.
      Related Object
         SQL statement with SQL_ID 974vg65j29pmv.
         UPDATE AVAYA.AIRTEL_CUSTOMER_MASTER SET PREFERRED_LANGUAGE = :1
         WHERE ( AIRTEL_CUSTOMER_MASTER.MSISDN = :2 )
   Rationale
      The SQL spent only 0% of its database time on CPU, I/O and Cluster
      waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
      Look at performance data for the SQL to find potential improvements.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "974vg65j29pmv" was executed 707 times and had
      an average elapsed time of 794 seconds.
   Rationale
      Waiting for event "enq: TX - row lock contention" in wait class
      "Application" accounted for 100% of the database time spent in
      processing the SQL statement with SQL_ID "974vg65j29pmv".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Additional Information
Miscellaneous Information
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.

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

Connect target / getting ORA-12560

Hi,
Can I issue:
RMAN TARGET / in CMD where I have only Oracle software installed in my machine -indeed I saw this in a tutorial in the internet !-.
If so, why could be the problem if I'm getting ORA-12560 error.
Saad,

RMAN TARGET /
The command illustrate that RMAN connecting to a target DB. So is your DB service up which you are trying to connect.
Edited by: shrikant on Mar 14, 2011 12:03 AM

Internet Connect Consistently Hangs On Startup

Anytime the computer is shut down and has to be restarted, Internet Connect always hangs without fail. It appears to actually connect, but quickly thereafter, I get the prompt that tells me that it's unexpectedly quit. When I try again, I'm successful. All disconnects and connections thereafter work until I shut my computer down and have to restart.
I've gone so far as to reinstall from the DVD, backing up, and selectively reinstalling third party apps, but the problem persists. Anyone else encountering this problem, which came bundled with my new 20" G5 iMac and Tiger?

Hi, WildBill —
I hope you'll forgive if it takes me a moment to get acquainted. It's been a long time since I used Internet Connect.
How are you using it — Bluetooth, AirPort, PPoE, VPN, etc.? (I'm wondering whether something like a signal delay or connection problem may factor in to the behavior...)
Have you tried logging in to a temporary, "test" user account (with administrative privileges) in an effort to determine whether the problem is restriced to your user account or system-wide? This and other general troubleshooting tactics are described in KnowledgeBase Article Mac OS X: How to troubleshoot a software issue.
When you say "I get the prompt that tells me that it's unexpectedly quit" —are we talking about the application actually "crashing" ? If so, have you used Console to look in ~/Library/Logs/ for an Internet Connect.crash.log? This may help to identify the specific sequence that's causing the problem.
Looking forward to hearing back from you.
Hope this helps... and
Good luck!
Dean

RMAN-20001: target database not found in recovery catalog

I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
RMAN> startup nomount;
Oracle instance started
Total System Global Area 209715200 bytes
Fixed Size 1272864 bytes
Variable Size 155190240 bytes
Database Buffers 50331648 bytes
Redo Buffers 2920448 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /u02/flash_recovery
database name (or database unique name) used for search: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Finished restore at 08-SEP-10
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.

Hi BelMan,
Here is output
BS Key Type LV Size Device Type Elapsed Time Completion Time
56869 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
56993 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10

RMAN - Connect target / Hang

Similar Messages

Maybe you are looking for