Rman target error

hi,
while i'm target the database i'm getting following error. pls help me target the database
RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME Recovery Manager:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recovery": expecting one of: "append, at, auxil
iary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, noc
atalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 1 column 46 file: standard input

hi nick,
i had done that but still its not connecting and its coming to next line pls chk the below output from rman. pls help me
C:\>rman
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Aug 8 10:47:54 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN> connect catalog rman01/rman01@test
connected to recovery catalog database
RMAN> RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME Recovery Manager:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recovery": expecting one of: "append, at, auxil
iary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, noc
atalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
RMAN-01007: at line 1 column 46 file: standard input
RMAN> RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME
2>

Similar Messages

Rman target db connect error

Hai al,
am getting this error when connecting rman target db :
[oratest@oracle7 9.2.0]$ rman target rman/rman@STD1
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. 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-01031: insufficient privileges
[oratest@oracle7 9.2.0]$ rman target system/manager@STD1
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. 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-01031: insufficient privileges
am connecting using SYS also,, failed with the above error.. SYS is authenciated
at the OS Level and not through password.. do we need to create password..
So having a password file is mandatory for RMAN ?
Kai

Thanks Syed for sharing the info.. can u help me in the folloeing :
MY DB Is runnign in noarchive log mode.. my DB Is runing now... no way we can take backup of DB runnin in noarchivelog mode..
[oratest@oracle7 ~]$ rman target sys/oracle5
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: STD1 (DBID=3092273924)
RMAN>
RMAN>
RMAN> connect catalog rman/rman@STD1
connected to recovery catalog database
RMAN>
RMAN>
RMAN>
RMAN>
RMAN>
RMAN> run
2> {
3> allocate channel c1 type DISK;
4> backup database;
5> }
allocated channel: c1
channel c1: sid=9 devtype=DISK
Starting backup at 23-MAR-08
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 03/23/2008 17:38:59
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
Please clarify ?
THanks
Kai

RMAN-04005: error from target database:

Hi,
when I want register my target by
]$ rman catalog prdrman/prdrman@PRD target sys/manager@DEV
I receive this :
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
Do you have any idea ?
Many thanks before.

Here are some further hints from documentation:
ORA-01031: insufficient privileges
When : SQL> connect sym/sym as SYSDBA
Additional : init.ora remote_login_passwordfile=EXCLUSIVE or SHARED
Cause : Username/password is not correct (if the user is added by granting
SYSDBA to the user, this user is added to the passwordfile with the
password from the data dictionary)
or:
Password file has
-> incorrect name orapw<name_of_database>
-> is not in $ORACLE_HOME/dbs
-> has wrong privileges
They should be -rwSr-----
For example:
-rwSr----- 1 server sdb 1536 Mar 25 08:12 orapwv901
Solve : You can set the correct privileges (Unix) by issueing
$ chmod 4640 passwordfile
As a last resort, recreate the password file and remind to add
additional privileged (sysdba or sysoper) users

RMAN-06010: error while looking up datafile: 82

Iam building dataguard - Physical Standby database by using the RMAN duplicate command and we are not using the recovery catalog but control file.
Iam getting the following error while running the duplicate command.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";
RMAN-06010: error while looking up datafile: 82
Actually we dropped the datafile(tablespace) before taken the backup but it is giving error though we are using the latest control file.
I do not see this file is available in the database as we dropped it successfully.
Could some one let me know what could be the problem and how to resolve it.
Your early response is greatly appreciated.
Note:
backup script -- It went successfully.
# Script to be used to backup the production in preparation of creating a DataGuard instance
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting backup on O01FLX3"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/full_backup_run_$dt.log
connect target /
configure device type disk clear;
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run{
change archivelog all validate;
backup current controlfile for standby format '/tmp/stby_snapcf_O01FLX3.f';
backup database format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.bak';
sql 'alter system archive log current';
backup archivelog all format '/dflx02/flx/o01flx3dump/rman/O01FLX3_%s_%p_%T_%t.arc';
EXIT
EOF
duplicate Script:
#!/bin/ksh
# Script to create standby database for production.
YYYY=`date +"%Y"`
mmdd=`date +"%m%d"`
hh=`date +"%H"`
mm=`date +"%M"`
ss=`date +"%S"`
hhmmss=${hh}${mm}${ss}
dt=${YYYY}${mmdd}_${hhmmss}
echo "Starting dataguard instance on O01FLX3DR"
$ORACLE_HOME/bin/rman nocatalog <<EOF >> /dflx02/flx/oracle/log/cr_stdby_O01FLX3$dt.log
connect target /
connect auxiliary sys/xxxxxx@O01FLX3DR
configure channel device type disk maxpiecesize 4G;
configure device type disk backup type to compressed backupset parallelism 8;
run {
set until time "to_date('20080217:19:00', 'YYYYMMDD:HH24:MI')";
duplicate target database for standby dorecover nofilenamecheck;
exit;
EOF
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3";

Thank you for your reply. Actually Iam not renaming the datafile but building the
dataguard instance and some how control file is looking for old datafile that was deleted.
Actually both primary and dataguard instances are running on 10.2.0.3 . Oracle control file is listing the datafile 82 as old deleted file, while building the dataguard.
---- This file was deleted long time back but still oracle control file is looking for this file while building the dataguard. Iam using the latest control file.
set newname for datafile 82 to
"/dflx02/flx/o01flx3rbs/rbs02_02.O01FLX3"
When I listed the datafile 82, it is showing the correct datafile.
RMAN> list backup of datafile 82;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
50234 Incr 2 26.93M DISK 00:04:03 18-FEB-08
BP Key: 101470 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51757_1_20080218_647031779.bak
List of Datafiles in backup set 50234
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953177017970 18-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
BS Key Type LV Size Device Type Elapsed Time Completion Time
50334 Incr 2 27.76M DISK 00:04:16 19-FEB-08
BP Key: 101587 Status: AVAILABLE Compressed: YES Tag: DATABASE_BACKUP
Piece Name: /dflx02/flx/o01flx3dump/rman/O01FLX3_51857_1_20080219_647119328.bak
List of Datafiles in backup set 50334
File LV Type Ckp SCN Ckp Time Name
82 2 Incr 7953257549488 19-FEB-08 /dflx02/flx/o01flx3ndx15/flx_ndx3_18.O01FLX3
So Iam thinking that there should be a problem in control file and let me know how to resolve it.
Please let me know if you have any questions.
Thanks for your help.
Suresh.D

Restore spfile from rman backup ---- error.

Hi,
I am trying to execute recovery on new machine ...
I have done the following steps..
I have one database as ora10g2 as peroduction database on one machine as hosta
I have created a catalog on another machine cora10g2 (hostb)
I have taken a full backup from hosta as per following ...
the following command execute from hosta machine.
$ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
Backup completed ...
Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
I have done the following setting ...on host b
set oracle_sid=DUP
and execute following command ...
rman target / catalog rman/rman@cora10g2
RMAN> set dbid 2760732370
executing command: SET DBID
database name is "BAAN10G2" and DBID is 2760732370
RMAN>
RMAN>
RMAN> startup force nomount ;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 1977112 bytes
Variable Size 67114216 bytes
Database Buffers 83886080 bytes
Redo Buffers 6406144 bytes
RMAN>
RMAN>
RMAN>
RMAN> show all ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
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 '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN>
RMAN>
RMAN> list backup of spfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
2420 Full 7.33M DISK 00:00:01 14-JUN-07
BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
SPFILE Included: Modification time: 14-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2509 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2694 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2760 Full 80.00K DISK 00:00:01 15-JUN-07
BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
Piece Name: /rman/spfile/spfile.ora
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2769 Full 7.33M DISK 00:00:02 15-JUN-07
BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
SPFILE Included: Modification time: 15-JUN-07
RMAN>
RMAN>
RMAN> restore spfile from autobackup ;
Starting restore at 19-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=35 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=34 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=33 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070619
channel ORA_DISK_1: looking for autobackup on day: 20070618
channel ORA_DISK_1: looking for autobackup on day: 20070617
channel ORA_DISK_1: looking for autobackup on day: 20070616
channel ORA_DISK_1: looking for autobackup on day: 20070615
channel ORA_DISK_1: looking for autobackup on day: 20070614
channel ORA_DISK_1: looking for autobackup on day: 20070613
channel ORA_DISK_1: no autobackup in 7 days found
channel ORA_DISK_2: looking for autobackup on day: 20070619
channel ORA_DISK_2: looking for autobackup on day: 20070618
channel ORA_DISK_2: looking for autobackup on day: 20070617
channel ORA_DISK_2: looking for autobackup on day: 20070616
channel ORA_DISK_2: looking for autobackup on day: 20070615
channel ORA_DISK_2: looking for autobackup on day: 20070614
channel ORA_DISK_2: looking for autobackup on day: 20070613
channel ORA_DISK_2: no autobackup in 7 days found
channel ORA_DISK_3: looking for autobackup on day: 20070619
channel ORA_DISK_3: looking for autobackup on day: 20070618
channel ORA_DISK_3: looking for autobackup on day: 20070617
channel ORA_DISK_3: looking for autobackup on day: 20070616
channel ORA_DISK_3: looking for autobackup on day: 20070615
channel ORA_DISK_3: looking for autobackup on day: 20070614
channel ORA_DISK_3: looking for autobackup on day: 20070613
channel ORA_DISK_3: no autobackup in 7 days found
channel ORA_DISK_4: looking for autobackup on day: 20070619
channel ORA_DISK_4: looking for autobackup on day: 20070618
channel ORA_DISK_4: looking for autobackup on day: 20070617
channel ORA_DISK_4: looking for autobackup on day: 20070616
channel ORA_DISK_4: looking for autobackup on day: 20070615
channel ORA_DISK_4: looking for autobackup on day: 20070614
channel ORA_DISK_4: looking for autobackup on day: 20070613
channel ORA_DISK_4: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2007 18:00:13
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN>
I am not able to restore spfile from rman backup ;;;

Hi,
I would like to know few things
1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

RMAN Backup error:ORA-04030: out of process memory

Hi,
Our RMAN backup is failing with below error:
===========================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 05:31:33
ORA-04030: out of process memory when trying to allocate 82444 bytes (pga heap,control file i/o buffer)
=============================
Please suggest
Thanks and Regards

We upgrade our catalog database(Linux) to 10.2.0.4 and our target database is 10.2.0.3(Windows),
we executed upgrade catalog twice and then when we again tried to execute the below command
rman sys/syspwd@targetdb catalog rman/rman@rmancat
Recovery Manager: Release 10.2.0.4.0 - Production on Sat May 22 15:10:36 2010
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current
connected to target database: WEBCT (DBID=3699379059)
connected to recovery catalog database
RMAN>
=======================
Still we are getting this error
and our backup falied with below errors:
======================
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current connected to target database: WEBCT (DBID=3699379059) connected to recovery catalog database
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/22/2010 15:09:44
ORA-06550: line 1, column 14:
PLS-00306: wrong number or types of arguments in call to 'VALIDATEARCHIVEDLOG'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
==========================
Please suggest

RMAN script errors out for some DB's

I have a single RMAN script that uses env variables to execute RMAN for two databases. It runs fine. I cloned the two DB's (changed DBID's), all four are on the same host. Now I try to use same script for all four. I receive an error when trying to run against the cloned databases. Here is script:
spool log to full.log append;
connect catalog rman/xxxxxx@iasrman
connect target /
run {
sql 'ALTER SYSTEM SWITCH LOGFILE';
backup incremental level 0 database diskratio=0 plus archivelog delete input;
And here is error, it stops same place everytime, input appreciated.
Recovery Manager: Release 9.2.0.5.0 - 64bit Production
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: PRSMQ02 (DBID=944525168)
RMAN> 2> 3> 4>
sql statement: ALTER SYSTEM SWITCH LOGFILE
Starting backup at 30-MAY-07
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=20 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=19 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=18 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=17 devtype=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: sid=11 devtype=DISK
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=25 recid=25 stamp=623931644
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting archive log backupset
channel ORA_DISK_2: specifying archive log(s) in backup set
input archive log thread=1 sequence=26 recid=26 stamp=623931644
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s59_s1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_25.arc recid=25 stamp=623931644
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931649_s60_s1 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_2: deleting archive log(s)
archive log filename=/q02/archive/prism/log_prsmq02_26.arc recid=26 stamp=623931644
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: starting incremental level 0 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00009 name=/q02/oradata01/prsmdata/Data_13.dbf
input datafile fno=00016 name=/q02/oradata01/prsmdata/Data_20.dbf
input datafile fno=00025 name=/q02/oradata01/prsmdata/Data_04.dbf
input datafile fno=00005 name=/q02/oraindx01/prsmdata/Index_11.dbf
input datafile fno=00020 name=/q02/oradata01/prsmdata/Tools02.dbf
input datafile fno=00022 name=/q02/oraindx01/prsmdata/index_12.dbf
channel ORA_DISK_1: starting piece 1 at 30-MAY-07
channel ORA_DISK_2: starting incremental level 0 datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00010 name=/q02/oradata01/prsmdata/Data_14.dbf
input datafile fno=00015 name=/q02/oradata01/prsmdata/Data_19.dbf
input datafile fno=00024 name=/q02/oradata01/prsmdata/Data_03.dbf
input datafile fno=00003 name=/q02/oratmp01/prsmdata/rbs01.dbf
input datafile fno=00001 name=/q02/orasys01/prsmdata/system01.dbf
input datafile fno=00012 name=/q02/orasys01/prsmdata/system02.dbf
channel ORA_DISK_2: starting piece 1 at 30-MAY-07
channel ORA_DISK_3: starting incremental level 0 datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
input datafile fno=00008 name=/q02/oradata01/prsmdata/Data_12.dbf
input datafile fno=00014 name=/q02/oradata01/prsmdata/Data_18.dbf
input datafile fno=00023 name=/q02/oradata01/prsmdata/Data_02.dbf
input datafile fno=00028 name=/q02/oradata01/prsmdata/Data06.dbf
input datafile fno=00019 name=/q02/oratmp01/prsmdata/rbs02.dbf
input datafile fno=00021 name=/q02/orasys01/prsmdata/DRSYS.dbf
channel ORA_DISK_3: starting piece 1 at 30-MAY-07
channel ORA_DISK_4: starting incremental level 0 datafile backupset
channel ORA_DISK_4: specifying datafile(s) in backupset
input datafile fno=00007 name=/q02/oradata01/prsmdata/Data_11.dbf
input datafile fno=00013 name=/q02/oradata01/prsmdata/Data_17.dbf
input datafile fno=00018 name=/q02/oradata01/prsmdata/Data_01.dbf
input datafile fno=00006 name=/q02/oradata01/prsmdata/Tools01.dbf
input datafile fno=00002 name=/q02/oradata01/prsmdata/Users01.dbf
input datafile fno=00026 name=/q02/oradata01/prsmdata/Data05.dbf
channel ORA_DISK_4: starting piece 1 at 30-MAY-07
channel ORA_DISK_5: starting incremental level 0 datafile backupset
channel ORA_DISK_5: specifying datafile(s) in backupset
input datafile fno=00004 name=/q02/oradata01/prsmdata/Data_15.dbf
input datafile fno=00011 name=/q02/oradata01/prsmdata/Data_16.dbf
input datafile fno=00017 name=/q02/oradata01/prsmdata/Data_22.dbf
input datafile fno=00027 name=/q02/oradata01/prsmdata/Data_05.dbf
channel ORA_DISK_5: starting piece 1 at 30-MAY-07
channel ORA_DISK_1: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s1 comment=NONE
channel ORA_DISK_1: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s1 comment=NONE
channel ORA_DISK_2: starting piece 2 at 30-MAY-07
channel ORA_DISK_3: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s1 comment=NONE
channel ORA_DISK_3: starting piece 2 at 30-MAY-07
channel ORA_DISK_4: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s1 comment=NONE
channel ORA_DISK_4: starting piece 2 at 30-MAY-07
channel ORA_DISK_5: finished piece 1 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s1 comment=NONE
channel ORA_DISK_5: starting piece 2 at 30-MAY-07
channel ORA_DISK_2: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s2 comment=NONE
channel ORA_DISK_2: starting piece 3 at 30-MAY-07
channel ORA_DISK_1: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s2 comment=NONE
channel ORA_DISK_1: starting piece 3 at 30-MAY-07
channel ORA_DISK_4: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s2 comment=NONE
channel ORA_DISK_4: starting piece 3 at 30-MAY-07
channel ORA_DISK_5: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s2 comment=NONE
channel ORA_DISK_5: starting piece 3 at 30-MAY-07
channel ORA_DISK_3: finished piece 2 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s2 comment=NONE
channel ORA_DISK_3: starting piece 3 at 30-MAY-07
channel ORA_DISK_2: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s3 comment=NONE
channel ORA_DISK_2: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s3 comment=NONE
channel ORA_DISK_4: starting piece 4 at 30-MAY-07
channel ORA_DISK_1: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s3 comment=NONE
channel ORA_DISK_1: starting piece 4 at 30-MAY-07
channel ORA_DISK_2: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s62_s4 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:53:23
channel ORA_DISK_5: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s3 comment=NONE
channel ORA_DISK_5: starting piece 4 at 30-MAY-07
channel ORA_DISK_3: finished piece 3 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s3 comment=NONE
channel ORA_DISK_3: starting piece 4 at 30-MAY-07
channel ORA_DISK_4: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s4 comment=NONE
channel ORA_DISK_4: starting piece 5 at 30-MAY-07
channel ORA_DISK_1: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s61_s4 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:59:04
channel ORA_DISK_3: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s63_s4 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 01:00:10
channel ORA_DISK_5: finished piece 4 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s65_s4 comment=NONE
channel ORA_DISK_5: backup set complete, elapsed time: 01:00:25
channel ORA_DISK_4: finished piece 5 at 30-MAY-07
piece handle=/iasrman/q02/prsmq02/prsmq02_df623931654_s64_s5 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 01:01:40
Finished backup at 30-MAY-07
Starting backup at 30-MAY-07
current log archived
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 05/30/2007 11:22:38
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE

connect target /You need to inform the connection string to target database.
Can to be explicitly or with 'export sid' in your script.

RMAN-03015: error occurred in stored script Memory Script

getting this error during
target db is 10202 & aux is 10204 ?
duplicate target database to dcxt;
RMAN> connect TARGET SYS/spurs_04@capq;
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.03 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.03 in TARGET database is not current
connected to target database: CAPQ (DBID=2420849281)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select action from gv$session where sid=:1 and serial#=:2 and inst_id=:3
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-10041: Could not re-create polling channel context following failure.
RMAN-10024: error setting up for rpc polling
RMAN-10005: error opening cursor
RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 05/21/2010 15:32:29
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
oracle:tuldcorpadb01:dcxt$
Edited by: DBA2008 on May 21, 2010 3:37 PM

never mind, i resolved this by switching duplicate db to 10203....and adjusting log_arch_dest .....

RMAN duplicate errors

Hi:
I was doing a 11g database clone on linux using rman duplicate. After runing 40min, it stopped and got the following errors. All the file permission are the same 777, one third of files have been copied.
ORA-27041: unable to open file
Linux-x86_64 Error: 13: Permission denied
Additional information: 9
failover to previous backup
released channel: aux1
released channel: aux2
released channel: aux3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/30/2012 08:28:07
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archived log found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 12312 and starting SCN of 23167256063 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12311 and starting SCN of 23167250994 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 12310 and starting SCN of 23167245674 found to restore
Thanks and regards.

Files from source database:
-rwxrwSrwx 1 root root 48653824 May 29 20:57 db_t784587134_s1208_p1
-rwxrwSrwx 1 root root 48594944 May 29 20:57 db_t784587149_s1209_p1
-rwxrwSrwx 1 root root 7761920 May 29 20:57 db_t784587150_s1210_p1
-rwxrwSrwx 1 root root 4062945280 May 29 21:23 db_t784587170_s1211_p1
-rwxrwSrwx 1 root root 1124147200 May 29 21:07 db_t784587170_s1212_p1
-rwxrwSrwx 1 root root 2049015808 May 29 21:16 db_t784587725_s1213_p1
-rwxrwSrwx 1 root root 4012630016 May 29 21:36 db_t784588310_s1214_p1
-rwxrwSrwx 1 root root 4620419072 May 29 21:43 db_t784588726_s1215_p1
-rwxrwSrwx 1 root root 3724255232 May 29 21:52 db_t784589461_s1216_p1
-rwxrwSrwx 1 root root 1818624 May 29 21:43 db_t784589896_s1217_p1
-rwxrwSrwx 1 root root 2071040 May 29 21:52 db_t784590427_s1218_p1
There are about 30 dbf files on source database, 10 dbf files on target database now.

RMAN Clone Errors

Hello,
We use Commvault for our backup software. I can successfully clone one application's PROD instance on server1 to TEST on server2.
However, for another application, attempting the same process of cloning the app's PROD instance on server1 to TEST on server2, I'm getting RMAN errors.
The prod database is ISLP and test database is ISLT. I've set the parameters:
o alter system set db_file_name_convert = '/u02/oradata/ISLP', '/u02/oradata/ISLT'
o alter system set log_file_name_convert= '/u01/oradata/ISLP', '/data/oracle/ISLT'
Again the destination is on a second server.
The error message I receive is:
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/09/2013 12:48:55
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_2b.log conflicts with a file used by the target database
RMAN-05001: auxiliary file name /u02/oradata/ISLP/redo_ISLP_1b.log conflicts with a file used by the target database
RMAN>
Recovery Manager complete.
I don't understand why RMAN keeps trying to create new redo log files in a directory that is not specified by the log_file_name_convert parameter. I also don't understand why this exact same process works for cloning one applications database but not this application. I would appreciate any help. Thank you. Here is the RMAN script being executed by Commvault.
Rman Script:
[run {
set newname for datafile '/u02/oradata/ISLP/infosilem_ISLP_01.dbf' to '/u02/oradata/ISLT/infosilem_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/sysaux_ISLP_01.dbf' to '/u02/oradata/ISLT/sysaux_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/system_ISLP_01.dbf' to '/u02/oradata/ISLT/system_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/tools_ISLP_01.dbf' to '/u02/oradata/ISLT/tools_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/undo_ISLP_01.dbf' to '/u02/oradata/ISLT/undo_ISLP_01.dbf';
set newname for datafile '/u02/oradata/ISLP/users_ISLP_01.dbf' to '/u02/oradata/ISLT/users_ISLP_01.dbf';
allocate auxiliary channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=/opt/galaxy/Base64/libobk.so,BLKSIZE=262144,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1,ThreadCommandLine= RESTORE -jm 142 -a 2:0 -cl 137 -ins 150 -at 22 -j 700481 -jt 700481:3:1 -bal 0 -rcp 0 -ms 1 -p 2 -cn s-dbint -vm Instance001)"
TRACE 0;
set until time = "TO_DATE('05/08/2013 09:00:00','MM/DD/YYYY HH24:MI:SS')" ;
duplicate target database to 'ISLT'
exit;
]

You haven't defined a log_file_name_convert for /u02/oradata/ISLP/
Possibly, the database has multiplexed redo log files, one member each in /u01/oradata/ISLP and one member each in /u02/oradata/ISLP.
Hemant K Chitale

Deletion of archive log using RMAN Target in Oracle 10g

Hi All,
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@dbMy Query is can I use
RMAN> delete noprompt expired archivelog all;as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*

Hello;
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@db
Are you trying to connect it through Grid control ? If connecting through a script, then please post its contents.
Make sure you are not connecting to the target database using "nocatalog".
rman target sys/<pwd_of_target>@<target_db> catalog <catalog_schema>/<catalog_schema_pwd>@<catalog_db>
My Query is can I use
RMAN> delete noprompt expired archivelog all;
as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Are these archives backed up ? The above command only updates the RMAN repository if in case the archives were delete manually at OS level.
I would recommend you to backup these archives and then delete them.
RMAN>backup archivelog all not backedup 1 times delete input;If these archives are already backed up and have not been deleted from the disk, then you can use the below command
RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';where "n" is the number of days behind the current date. Make sure to verify if these archives have been backed up before deleting.
Regards,
Shivananda

Starting Rman getting error PL/SQL package not current

I come across a problem. My server is windows 2003 and Oracle is 10g Release 2.
My previous DBA install Oracle 10g R1, 10gR2 and Oracle Data Warehouse Builder 10g on the same server at different Oracle_Home. When I came to this work. I tried to use Rman for backup. When i went to server command line, type Rman, Rman target /. the error message was:
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.02 in TARGET database is not current and PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.02 in TARGET database is not current.
I found the solution from oracle_metalink ( Note:429499.1). I followed note to use Oracle Universal Installer to move the 10.2.0.2 home. Then I can start Rman. Then I fixed some other small errors. I came back to loginto Rman. The system told me the same errors. I used Oracle Installer to check the Oracle_Home. Only two home exist. One is 10gR2 10.2.0.2. Another one is data warehouse builder with version 10.2.0.3. So it seems that 10gR2 Home is not current. How can I remove this Oracle_Home? If I remove it off, database will be dead. So if I remove oracle data warehouse builder, will it make two PL/SQL package for Rman current? or I have to remove DW builder first, then patch 10gR2 Home to 10.2.0.3? Please help. Thanks.

damorgan:
No. it is not related to oracle_home and oracle_sid. It is related to PATH setting. I have solved the problem. Thanks for your comment.

RMAN-target database not found

Hello All:
we have rman config (0 level bkp) for our PROD backup, rman catalog is on a different server. running OK. heaving 0 level backup of our PROD.... no issue.
Now we have one more PROD db implemented recently for payroll on seperate server, so we decided to have rman backup of this also.
we set that rman script to here also and made the neccessary changes.
It is heaving backup, archive backup ... no issue ...
but it error while "RMAN Catalog resync"
that part from script is
## RMAN Catalog resync ##
rman log=/u01/bkp/logs/backup_resync.log << EOF
connect catalog rman/rman@rman
connect target /
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/bkp/backup/ctrl_%F';
resync catalog;
EOF
and the error on log file "backup_resync.log" getting:
Recovery Manager: Release 11.1.0.6.0 - Production on Fri Aug 10 04:25:04 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: ORCL (DBID=2588904899)
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 08/10/2012 04:25:29
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN>
Recovery Manager complete.
plese suggest on this, i googled, saying to register the catalog, tried but no luck....
thanks in ADV
Edited by: DOA on 9 Aug, 2012 10:16 PM
Edited by: DOA on 9 Aug, 2012 10:17 PM

Hello vreddy,
Thanks for the reply...
I am bit new with the rman word....
I tried command on server where catalog exist (stating: my PROD and catalog exist on different different server)
(orcl is my PROD db name)
rman target / catalog ORCL
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Aug 10 10:57:29 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: RMAN (DBID=1583459273)
recovery catalog database Password:
asking for some password, which password here we need to supply ?
for more clear picture I also execute command on catalog side:
SQL> select name,DBID,RESETLOGS_TIME from rc_database order by 1;
NAME DBID RESETLOGS
PROD 4247251480 12-MAY-04
RMAN 1583455429 02-JAN-09
db ORCL is not there in the list....

RMAN script error in UNIX

I have db10.2.0.3 on SUN Solaris 10.
I have a rman script called backup_aps2
This is the content
#!/usr/bin/csh -fvx
rman target / <<EOF
configure controlfile autobackup on;
run
recover copy of database with tag 'incr_update';
backup incremental level 1 for recover of copy with tag 'incr_update'
database;
EOFI got this error when I ran it:
test% ./backup_aps2
rman target / << EOF
/tmp/shXXXXXX: Permission deniedPlease help!
Thanks a lot!

Not an Oracle problem.
A 'here-document' is automatically turned in a temporary file.
The default directory for temporary files is /tmp.
As per the error message, you apparently didn't read, you have no permission to create files in this directory.
You can change the location of your temporary files for your session by setting the TMP and TMPDIR variables to an appropiate value.
Sybrand Bakker
Senior Oracle DBA

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
thanks

Thanks 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 target error

Similar Messages

Maybe you are looking for