RMan and perflib error.

We are running db backups every night using Legato and RecoveryManager.
When running backup last night, Rman.exe hung with Dr.Watson error.
Messages in alert file:
Thu May 13 20:15:45 2004
allocated device type: "SBT_TAPE", name: ""
Thu May 13 20:15:47 2004
allocated device type: "SBT_TAPE", name: ""
Thu May 13 20:15:48 2004
allocated device type: "SBT_TAPE", name: ""
Thu May 13 20:15:49 2004
allocated device type: "SBT_TAPE", name: ""
Thu May 13 20:15:49 2004
set limit for device type: "SBT_TAPE", name: ""
device limit "k-bytes per piece" set to 2097160
Thu May 13 20:15:49 2004
set limit for device type: "SBT_TAPE", name: ""
device limit "k-bytes per piece" set to 2097160
Thu May 13 20:15:49 2004
set limit for device type: "SBT_TAPE", name: ""
device limit "k-bytes per piece" set to 2097160
Thu May 13 20:15:49 2004
set limit for device type: "SBT_TAPE", name: ""
device limit "k-bytes per piece" set to 2097160
Thu May 13 20:26:02 2004
Errors in file D:\Oracle\admin\omss\rdbms80\trace\ORA00212.TRC:
Ora00212.TRC:
Dump file D:\Oracle\admin\omss\rdbms80\trace\ORA00212.TRC
Thu May 13 20:26:02 2004
ORACLE V8.0.5.2.1 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V4.0, OS V5.101, CPU type 586
Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production
With the Partitioning and Objects options
PL/SQL Release 8.0.5.2.0 - Production
Windows NT V4.0, OS V5.101, CPU type 586
Instance name: omss
Redo thread mounted by this instance: 1
Oracle process number: 16
pid: d4
*** 2004.05.13.20.26.02.406
*** SESSION ID:(25.14457) 2004.05.13.20.26.02.250
FATAL ERROR IN TWO-TASK SERVER: error = 12571
*** 2004.05.13.20.26.02.406
ksedmp: internal or fatal error
Current SQL statement for this session:
select act from x$ksusex where sid=:1 and serial=:2
...followed by stack dump.
I have also found a entry in application event viewer re:
perflib, which occured just before RMan.exe error:
"The Open Procedure for service "OracleOMSS_HOME80" in DLL "oraperf.dll" failed. Performance data for this service will not be available. Status code returned is DWORD 0."
After dismissing Dr.Watson error this morning, backup run through with no problems.
Excactly same situation occured last week.
I cannot find any Rman error logs?
Pls, any ideas or pointers would be appreciated!
ania

It is an interesting question how Oracle manages the undo for read-only.
I might look at :
ORA-1555 Using Automatic Undo Management - How to troubleshoot [ID 389554.1]
or
http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/undo002.htm#BJFFIACJ
ORA-01555 "Snapshot too old" - Detailed Explanation [ID 40689.1]
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:1441804355350
Best Regards
mseberg
It is possible
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 02/24/2011 14:24:42
ORA-01555: snapshot too old: rollback segment number 20 with name "_SYSSMU20_328
6862503$" too small
RMAN-06031: could not translate database keyword
ORA-01555 Snapshot too old
ORA-01555: snapshot too old
h3. Would forget the why and fix the issue
increase size of UNDOTBS1
Edited by: mseberg on Nov 9, 2012 7:21 AM

Similar Messages

RMAN-06004:ORACLE error from recovery catalog ... ORA-00904: : invalid ...

Good Morning All,
One of our RMAN backups is failing with the following error message. Any suggestions would be greatly appreciated.
==================================================================================================
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Edited by: ORA_UMAIR on Dec 31, 2008 7:51 AM

This Oracle Database is 9.2.0.6.0. Here is the complete log file. The RMAN script that I am using ran successfully many times before.
====================================================================================================
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: CUSTPR (DBID=525071053)
RMAN>
RMAN> #########################################################################
2> # LEVEL 0 BACKUP #
3> #########################################################################
4>
5> # Configure backups to be written to disk.
6> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
old RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters:
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Set the retention policy to a recovery window of 7 days. This ensures that
2> # RMAN retains all backups needed to recover the database to any point in time
3> # in the last 7 days. You can use the DELETE OBSOLETE command to delete
4> # backups that are no longer required by the retention policy. To exclude a
5> # backup from consideration by the policy, you can use KEEP option with the
6> # BACKUP command.
7> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
old RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to use two disk channels for backup, restore, recovery, and
2> # maintenance operations.
3> CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
old RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write disk backups to the /backup directory.
2> # The format specifier %t is replaced with a 4-byte timestamp, %s with the
3> # backup set number, and %p with the backup piece number.
4> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to back up the control file after each backup.
2> CONFIGURE CONTROLFILE AUTOBACKUP ON;
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Configure RMAN to write controlfile autobackups to the /backup directory.
2> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Enable the backup optimization feature introduced in 9i to make sure that
2> # RMAN won't backup an archivelog or datafile if there already exists a backup
3> # of that file. The FORCE option can be used to override optimization on a
4> # specific BACKUP command.
5> CONFIGURE BACKUP OPTIMIZATION ON;
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN>
RMAN> # Use the SHOW ALL command to see the current configuration settings.
2> SHOW ALL ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_bkp_cf%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/admin/custpr/%d_bkp_cf%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome2/custprdb/9.2.0/dbs/snapcf_custpr.f'; # default
RMAN>
RMAN> # The following commands are run each day to start the backup cycle.
2> # The steps are:
3> # - Take an incremental level 0 backup of the database. A level 0 backup is
4> # a complete backup of the entire file which can be used as the basis
5> # for a subsequent incremental backup.
6> # - Backup all archivelogs that have not already been backed up.
7> # - Delete on-disk archivelogs older than seven days.
8>
9> BACKUP INCREMENTAL LEVEL 0 FORMAT '/backups/admin/custpr/%d_bkp_df%t_Set%s_Piece%p'
10> DATABASE maxsetsize 33G
11> PLUS ARCHIVELOG FORMAT '/backups/admin/custpr/%d_bkp_al%t_Set%s_Piece%p'
12> delete all input;
Starting backup at 12/30/2008 22:01:40
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: 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=8008 recid=7910 stamp=674638862
input archive log thread=1 sequence=8009 recid=7911 stamp=674671207
input archive log thread=1 sequence=8010 recid=7912 stamp=674697380
input archive log thread=1 sequence=8011 recid=7913 stamp=674780433
input archive log thread=1 sequence=8012 recid=7914 stamp=674784211
input archive log thread=1 sequence=8013 recid=7915 stamp=674863288
input archive log thread=1 sequence=8014 recid=7916 stamp=674863300
channel ORA_DISK_1: starting piece 1 at 12/30/2008 22:01:41
channel ORA_DISK_1: finished piece 1 at 12/30/2008 22:03:47
piece handle=/backups/admin/custpr/CUSTPR_bkp_al674863300_Set3083_Piece1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:07
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/custpr/arch/arch_custpr_8008.log recid=7910 stamp=674638862
archive log filename=/custpr/arch/arch_custpr_8009.log recid=7911 stamp=674671207
archive log filename=/custpr/arch/arch_custpr_8010.log recid=7912 stamp=674697380
archive log filename=/custpr/arch/arch_custpr_8011.log recid=7913 stamp=674780433
archive log filename=/custpr/arch/arch_custpr_8012.log recid=7914 stamp=674784211
archive log filename=/custpr/arch/arch_custpr_8013.log recid=7915 stamp=674863288
archive log filename=/custpr/arch/arch_custpr_8014.log recid=7916 stamp=674863300
Finished backup at 12/30/2008 22:03:47
Starting backup at 12/30/2008 22:03:47
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/30/2008 22:03:47
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> ##BACKUP ARCHIVELOG ALL FORMAT '%d_bkp_al_%t_Set%s_Piece%p' delete input;
2>
3> # DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
4>
5> # check if database can be restored
6> # RESTORE DATABASE VALIDATE;
7>
8> # check if controlfile can be restored
9> ##RESTORE CONTROLFILE to '/backups/admin/custpr/custpr_bkp_cntlfile.ctl' VALIDATE;
10>
11> # check if archivelogs for the past two weeks can be restored
12> # RESTORE ARCHIVELOG FROM TIME 'SYSDATE-7' VALIDATE;
13>
14> # - Verify all backups on backup media are intact
15> # CROSSCHECK BACKUP OF DATABASE;
16>
17> # - Display a list of files that need to be backed up based on the retention
18> # policy. For this case study, files that don't have at least 1 backups
19> # will be reported.
20> REPORT NEED BACKUP;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 12/30/2008 22:03:48
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> # - delete un-necessary backups. This command deletes backups based on the
2> # retention policy.
3> ######### commented out DELETE OBSOLETE - TSM not configured to delete on 68
4> #########DELETE OBSOLETE;
5>
6> # - get complete list of existing backups
7> LIST BACKUP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 12/30/2008 22:03:49
RMAN-06004: ORACLE error from recovery catalog database: ORA-00904: : invalid identifier
RMAN>
RMAN> #-end of file-
2> **end-of-file**
RMAN>
Recovery Manager complete.

Simple Problems of oracle 8i using Rman and so.................

I am Shan here. I am DBA student for oracle 8i. I have a problem with a backup and recoverys article which is Rman. If you can not help for this then please tell me a contact of that person who can help me. If u can then it is on..
1- I create a user RMAN. I grant him a quota on rman and on rman_temp tablespace; grant him a dba, sysdba, recovery_catalog_owner role. Then I connect it to target. Then I create catalog, then register database then type a command of list (LIST COPY OF DATABASE and LIST BACKUP OF DATABSE) it shows me nothing. ok.
Then I take a whole backup of a database with the command
Run {
Allocate channel c1 type disk;
Backup
Format d:\backup\whole_%d_%s_%p.bak
(Database) ;}
This command shows me allocating channel and then processing backup Then this commend ended successfully. And it shows me files physically of my desire path. Then I query a command of LIST for showing me my backup details (LIST BACKUP OF DATABSE). But it shows me nothing. No details about my backup. But the file is still physically there at my given path.
This is the same story with copy command it physically create a file there but do not show it with LIST COPY OF DATABASE command.
It is not a story of a single Computer I changed it and do the same stuff with the others but the result is same. But I got desire results on one Computer but next day I got another problem with this Computer. I type a command of list backup it shows me the results. It has two backup pieces. I tried to delete them with change command by allocating channel for delete type disk. And then change backupset 605(backup set no) delete;. It shows me that he deleted that file form path but when I query of list backup it show me the same results which it show me before delete. Then I tried to delete second set which is still there I would not allow me to delete that set and give a error that catalog does not have the information about that file but list command show me both pieces. I do manual resync catalog command but no difference on results.
Then I take another whole backup at another place, and query to get its information but list command does not show the results. It shows me the old results. Then I take a backup of a single data file and query but the result is same.
I also tried to delete that copy data file by change command but it says that recovery catalog do not have the information about that file.
2- If we allocate more then one channels for backup on a same drive what will be the behavior of those channels.
Will them not working parallel. And tell me that it is true that channels will work parallel when they are writhing information on different drives (different drive means that two different hard drives physically).
Syntax of all commands is writen,I tallied it by book.<<<<<<<<<<<<<<<<3- What is O stands for in crosscheck command? A stands for available U Stands for Unavailable and O Stands for? In a status column.
4- Please tell me a single command to delete all tables of a user. (Single command..)
We are using ORACLE 8i (8.1.7.0.0) Version for practice.
Give its solution by mail
[email protected]

I have briefly used sql*ldr in linux and yes, it does support exit codes

RMAN and Point IN time recovery

1. We have a table with bad data.
2. We know that data was entered via the GUI exactly one week ago.
3. I have an RMAN database full back-up that was taken the same day but before the table was screwed.
4. the database in archivelog mode.
5. we will be happy to restore the database in the condition before the change occured
5. when I restore database via RMAN, and do:
recover UNTIL TIME '16-MAR-2005';
Oracle restore bad data, and if I put time or scn I get a message that the database incarnation is wrong!
Is there any other way to do it?
TIA

Thanks Laurent! I was able to restore it only until Mar. 17?
1. RMAN> reset database to incarnation 2;
2. RMAN> restore database until time "timestamp '2005-03-15 00:00:00.00'";
RMAN-03002: failure of recover command at 03/29/2005 19:44:11
RMAN-06555: datafile 1 must be restored from backup created before 15-MAR-05
3. My backup was created on Mar. 16, :
RMAN> restore database until time "timestamp '2005-03-17 00:00:00.00'";
RMAN-03002: failure of restore command at 03/29/2005 19:46:55
RMAN-06026: some targets not found - aborting 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
4. RMAN>Restore database; OK
5. RMAN>Recover database; internal error!
RMAN-03002: failure of recover command at 03/29/2005 20:08:02
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile 'G:\ORACLE\ORA10G\FLASH_RECOVERY_DATA\ORCLSRMA\CONTROLFILE\2005_03_2
3\O1_MF_1_14_14442T9B_.ARC'
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3021], [1], [15], [2], [0], [419057]
, [0], [416789]
6. RMAN> recover database until time "timestamp '2005-03-17 00:00:00.00'"; OK
7.RMAN> recover database until time "timestamp '2005-03-17 00:00:00.00'"; OK
8. RMAN> alter database open resetlogs; OK
9. RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORCLSRMA 2671268838 PARENT 1 09-MAR-04
2 2 ORCLSRMA 2671268838 PARENT 318842 01-MAR-05
3 3 ORCLSRMA 2671268838 ORPHAN 380529 25-MAR-05
5 5 ORCLSRMA 2671268838 CURRENT 409286 29-MAR-05
4 4 ORCLSRMA 2671268838 ORPHAN 416789 25-MAR-05

RMAN-10011: synchronization error while polling for rpc 8, action=startdefa

Could anybody explain what is this error message caused by?
TIA
The entire spool below:
051107064744: NetBackup RMAN Backup Started
ORACLE_SID=db02
backup_type=cold
number_of_channels=2
Started by: Oracle
051107064745: Checking database status
051107064745: Database status: OPEN
051107064745: Getting database password
051107064746: Checking database password
051107064746: Database password: Valid
051107064746: Checking Database mode
051107064746: Database mode: NOARCHIVELOG
051107064746: Shutdown no archive
051107064838: RMAN BACKUP STARTED
Recovery Manager: Release 10.1.0.4.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: db02 (DBID=3504436532)
RMAN> connect catalog *
2> run
3> {
4> sql 'alter session set sort_area_size=12582912';
5> sql 'alter session set sort_area_retained_size=1048576';
6> allocate channel t1 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
7> format 'df_%d_%p_%u_%t';
8> set limit channel t1 maxopenfiles=1;
9> allocate channel t2 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
10> format 'df_%d_%p_%u_%t';
11> set limit channel t2 maxopenfiles=1;
12> backup database filesperset=64
13> include current controlfile;
14> sql 'alter database open';
15> release channel t1;
16> release channel t2;
17> }
18>
connected to recovery catalog database
starting full resync of recovery catalog
full resync complete
sql statement: alter session set sort_area_size=12582912
sql statement: alter session set sort_area_retained_size=1048576
allocated channel: t1
channel t1: sid=160 devtype=SBT_TAPE
channel t1: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
allocated channel: t2
channel t2: sid=159 devtype=SBT_TAPE
channel t2: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
Starting backup at 11-MAY-07
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00005 name=/oradata/10gid/u01/grid102/grid102/mgmt.dbf
input datafile fno=00006 name=/oradata/10gid/u01/grid102/grid102/mgmt_ecm_depot1.dbf
input datafile fno=00007 name=/oradata/10gid/u01/grid102/grid102/system02.dbf
input datafile fno=00004 name=/oradata/10grid/u01/grid102/grid102/users01.dbf
channel t1: starting piece 1 at 11-MAY-07
channel t2: starting full datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00008 name=/oradata/10ggrid/u01/grid102/grid102/mngmecm02.dbf
input datafile fno=00001 name=/oradata/10ggrid/u01/grid102/grid102/system01.dbf
input datafile fno=00002 name=/oradata/10ggrid/u01/grid102/grid102/undotbs01.dbf
input datafile fno=00003 name=/oradata/10ggrid/u01/grid102/grid102/sysaux01.dbf
channel t2: starting piece 1 at 11-MAY-07
channel t2: finished piece 1 at 11-MAY-07
piece handle=df_GRID102_1_19ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
channel t2: backup set complete, elapsed time: 00:06:05
channel t2: starting full datafile backupset
channel t2: specifying datafile(s) in backupset
including current controlfile in backupset
channel t2: starting piece 1 at 11-MAY-07
channel t2: finished piece 1 at 11-MAY-07
piece handle=df_GRID102_1_1aihed24_622277700 comment=API Version 2.0,MMS Version 5.0.0.0
channel t2: backup set complete, elapsed time: 00:00:35
channel t1: finished piece 1 at 11-MAY-07
piece handle=df_GRID102_1_18ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
channel t1: backup set complete, elapsed time: 00:06:48
Finished backup at 11-MAY-07
Starting Control File and SPFILE Autobackup at 11-MAY-07
piece handle=c-3404436532-20070511-00 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 11-MAY-07
sql statement: alter database open
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-10010: error while checking for RPC completion
RMAN-10011: synchronization error while polling for rpc 8, action=startdefault
Recovery Manager complete.
051107065708: RMAN BACKUP FAILED, RMAN exit status=1
051107065708: Cleaning log file (removing passwords)
051107065709: Error Log Check
051107065837: Rman Stat Generator
051107065956: Backup Html Generator
051107065956: NetBackup RMAN Backup Finished
######################################################

Check on metalink:
RMAN-10011: synchronization error while polling for rpc 3, action=startdefault
Note:429572.1
Werner

RMAN Parameter configuration errors

I am trying to run the following script to set configuration parameters for rman:
rman <<!!
connect rcvcat rman/${RMAN_PWD}@${RMANCAT}
connect target /
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 15 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/app/oracle
/backups/RMAN/${SID}/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u03/app/oracle/backups/RMAN/${SID}
/backup_db_%d_S_%s_P_%p_T_%t' MAXPIECESIZE 1024m;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/u03/app/oracle/backups/RMAN/${SID}
/backup_db_%d_S_%s_P_%p_T_%t' MAXPIECESIZE 1024m;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/flash_recovery_area/${SI
D}/snapcf_ev.f';
for some reason I get the errors...
for CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "backup": expecting one of: ";"
RMAN-01007: at line 1 column 42 file: standard input
and for CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "backup"
RMAN-01008: the bad identifier was: DELETION
RMAN-01007: at line 1 column 22 file: standard input
I can't find anything wrong with the syntax in the script, but I'm fairly new to this stuff so I could just be missing something. Does anyone know what could be causing these errors?

I just realized that I was running this script against 9i instances. The script is meant to be run against 10g instances and worked fine when I did so. I guess I'll have to adjust the script accordingly for 9i.

Ld.so.1: rman: fatal: relocation error:

I am facing the below error while executing rman
rman target /ld.so.1: rman: fatal: relocation error: file /u01/home/oracle/product/10.2.0.4.0/bin/rman: symbol kgskactlat_a_: referenced symbol not found
Killed
I tried to unset LD_LIBRARY_PATH and reset it by oraenv but to no luck.
Also manually set LD_LIBRARY_PATH to $ORACLE_HOME/lib. There too no luck.
Can someone tell me where am I missing.

Thanks but still no luck.
echo $LD_LIBRARY_PATH_64
export LD_LIBRARY_PATH_64=$LD_LIBRARY_PATH
echo $LD_LIBRARY_PATH_64/u01/home/oracle/product/10.2.0.4.0/lib:/lib:/usr/lib:/usr/local/lib
rman target /ld.so.1: rman: fatal: relocation error: file /u01/home/oracle/product/10.2.0.4.0/bin/rman: symbol kgskactlat_a_: referenced symbol not found
Killed
Thanks

RMAN-20999: internal error on standby....help

Hey guys,
A little background of events of what happened:
1) data guard got broken
2) rebuild data guard
in the rebuild process I took the /backup mount point from primary database NFS mounted it to the alternate database.(The reason I did that was because it was going to take too much time to transfer over the backups from the primary to the alternate).
During this process while /backup1 was NFS mounted, i had to add "alter system set event='10298 trace name context forever, level 32'scope= spfile ; " to my spfile.
3) finished the data guard rebuild
4) NFS unmounted /backup from primary (take out alter system set event='10298 trace name context forever, level 32'scope= spfile ; from spfile)
5)bounce database and re sync data guard
5) data guard is in sync and everything is fine
Now comes the trouble..
went to the standby side and went to run rman.
here it is:
RMAN> @connect.rman
RMAN> connect target *
connected to target database: AFCD1D1 (DBID=3242165457, not open)
RMAN> connect catalog *
connected to recovery catalog database
RMAN> **end-of-file**
RMAN> resync catalog;
starting partial resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 12/08/2011 15:05:16
RMAN-20999: internal error
RMAN>
so I thought maybe the primary database needs to do a full re sync.
I did that still no help
I also search on oracle support, couldn't find anything useful.
Just to play with it
-I went to the primary db-recreated the standby controlfile
-went to the standby , shut db down. copied the standby controlfile over to the standby server
-restarted the dataguard
Data Guard is in sync
went to rman and same issue.
Any help would be appreciated!!
PS. The rman backups were working before data guard was broken.
Edited by: 867954 on Dec 8, 2011 12:45 PM

RMAN-20999: internal errorInternal errors require help from Oracle support. They have the tools to trace the problem.
Werner

RMAN-01009: syntax error:

I need your help in resolving error, while executing following command.
RMAN> backup database plus archivelog tag='Weekly_full_backup' keep until time 'sysdate+7';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "double-quoted-string, equal, single-quoted-string"
RMAN-01008: the bad identifier was:
RMAN-01007: at line 1 column 74 file: standard input

I mange to take backup with following command, earlier the problem was that oracle do not allow backup with KEEP option in F.R Area. Which is default in my case.
But it does not include archivelog backup, which i want.
RMAN> BACKUP DATABASE FORMAT '/u01/app/oracle/level_0_backup/sba_full_bk_%U' TAG weekly_full_backup KEEP UNTIL TIME 'SYSDATE + 7' LOGS;
Starting backup at 23-FEB-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=3200 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=3267 devtype=DISK
backup will be obsolete on date 01-MAR-12
archived logs required to recover from this backup will expire when this backup expires
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=/u01/app/oracle/oradata/sba/users01.dbf
input datafile fno=00006 name=/u01/app/oracle/oradata/sba/rman01.dbf
input datafile fno=00007 name=/u01/app/oracle/oradata/sba/eobi01.dbf
channel ORA_DISK_1: starting piece 1 at 23-FEB-12
channel ORA_DISK_2: starting compressed full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00005 name=/u01/app/oracle/oradata/sba/stream_tbs.dbf
input datafile fno=00001 name=/u01/app/oracle/oradata/sba/system01.dbf
input datafile fno=00003 name=/u01/app/oracle/oradata/sba/sysaux01.dbf
input datafile fno=00002 name=/u01/app/oracle/oradata/sba/undotbs01.dbf
channel ORA_DISK_2: starting piece 1 at 23-FEB-12
channel ORA_DISK_2: finished piece 1 at 23-FEB-12
piece handle=/u01/app/oracle/level_0_backup/sba_full_bk_nhn41gjp_1_1 tag=WEEKLY_FULL_BACKUP comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:02:05
channel ORA_DISK_1: finished piece 1 at 23-FEB-12
piece handle=/u01/app/oracle/level_0_backup/sba_full_bk_ngn41gjp_1_1 tag=WEEKLY_FULL_BACKUP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:06:10
Finished backup at 23-FEB-12
Starting Control File and SPFILE Autobackup at 23-FEB-12
piece handle=/u01/app/oracle/flash_recovery_area/SBA/autobackup/2012_02_23/o1_mf_s_775996395_7ncmww2t_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 23-FEB-12

Build dataguard two more questions. password prompt and certificate error

The fiirt two data guard instances are built. One is running fine the second I'm getting this error in the primarys alert log. it looks like it is a certificate error but I'm having a hard time nailing it down.
BTW: Instance is 11.2.0.1
Thread 1 advanced to log sequence 318 (LGWR switch)
Current log# 6 seq# 318 mem# 0: +DATA/sfs01/onlinelog/group_6.4762.769266689
SSL Client: Server DN doesn't contain expected SID name
Archived Log entry 706 added for thread 1 sequence 317 ID 0x799622d4 dest 1:
Thu Mar 22 12:46:48 2012
SSL Client: Server DN doesn't contain expected SID name
The third and final data guard instance I'm building is 3T and taking forever to restore. Two questions:
1) Can I suspend rman and restart it.
2) when I restart rman how do I keep it from prompting me for the password. I would prefer to put a nohup on a shell script.
Here is the script. Right now I'm running it manually but would relly to run with nohup so I can go get lunch.
rman target SYS@sor01_primary auxiliary / << EOF
run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
allocate auxiliary channel C3 device type disk;
allocate auxiliary channel C4 device type disk;
allocate auxiliary channel C5 device type disk;
duplicate target database for standby nofilenamecheck;
release channel C1;
release channel C2;
release channel C3;
release channel C4;
release channel C5;
EOF

Hello (certificate error is vague. By that I mean whoever wrote that error message)
Can I suspend rman and restart it? I believe no, stop and restart should work.
Something like this, I use an env file can post if it helps :
#!/bin/bash
. /u01/app/oracle/dba_tool/env/DATABASE.env
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target SYS@sor01_primary auxiliary << EOF
run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
allocate auxiliary channel C3 device type disk;
allocate auxiliary channel C4 device type disk;
allocate auxiliary channel C5 device type disk;
duplicate target database for standby nofilenamecheck;
release channel C1;
release channel C2;
release channel C3;
release channel C4;
release channel C5;
}My env file ( yours will be different ) use env to check you compare to your profile
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0.2
export ORACLE_SID=STANDBY
export ULIMIT=unlimited
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/network/lib
export LIBPATH=$LD_LIBRARY_PATH:/usr/lib
export TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/etc:/etc/X11/xserver/C:.
export PATHI run from the cron which is similar to nohup as far as env goes.
Best Regards
mseberg
Edited by: mseberg on Mar 22, 2012 2:32 PM
Edited by: mseberg on Mar 22, 2012 2:41 PM

Rman/PERL scripts errors

I am trying to automate the backups and disk maintenence on a test machine using a "Host Command" in the 10g EM environment. If I run the script from the command on the target host the scripts completes successfully.
This is the script:
ORACLE_HOME=/u01/app/oracle/product/9.2.0
export ORACLE_HOME
ORACLE_SID=coeusdba.
export ORACLE_SID
rman <<EOF
connect target sys<password>@coeusdba;
connect catalog <user>/<password>@recv;
replace script coeusdba_full_bkp {
allocate channel Channel1 type disk format '/u03/orabkp/coeusdba/b_%u_%p_%c';
backup
( database include current controlfile );
backup ( archivelog all delete input );
run { execute script coeusdba_full_bkp;}
EOF
/u01/app/oracle/product/9.2.0/dbs/scripts/coeusdba_new.sh
exit
When I execute the same script from a 10g EM "Host Command" job the script fails at the PERL command step with the following output:
Recovery Manager: Release 9.2.0.7.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN>
RMAN>
connected to target database: COEUSDBA (DBID=1916078485)
RMAN>
RMAN>
connected to recovery catalog database
RMAN> 2> 3> 4> 5> 6> 7> 8>
replaced script coeusdba_full_bkp
RMAN>
RMAN>
executing script: coeusdba_full_bkp
allocated channel: Channel1
channel Channel1: sid=10 devtype=DISK
Starting backup at NOV-01-2005 10:32:32
channel Channel1: starting full datafile backupset
channel Channel1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00006 name=/u02/oradata/coeusdba/users01.dbf
input datafile fno=00002 name=/u03/oradata/coeusdba/undotbs01.dbf
input datafile fno=00004 name=/u03/oradata/coeusdba/index01.dbf
input datafile fno=00005 name=/u03/oradata/coeusdba/tools01.dbf
input datafile fno=00007 name=/u03/oradata/coeusdba/xdb01.dbf
input datafile fno=00001 name=/u02/oradata/coeusdba/system01.dbf
input datafile fno=00003 name=/u02/oradata/coeusdba/drsys01.dbf
channel Channel1: starting piece 1 at NOV-01-2005 10:32:33
channel Channel1: finished piece 1 at NOV-01-2005 10:33:28
piece handle=/u03/orabkp/coeusdba/b_3rh2l4q1_1_1 comment=NONE
channel Channel1: backup set complete, elapsed time: 00:00:55
Finished backup at NOV-01-2005 10:33:28
Starting backup at NOV-01-2005 10:33:29
current log archived
channel Channel1: starting archive log backupset
channel Channel1: specifying archive log(s) in backup set
input archive log thread=1 sequence=49 recid=200 stamp=573215609
channel Channel1: starting piece 1 at NOV-01-2005 10:33:32
channel Channel1: finished piece 1 at NOV-01-2005 10:33:33
piece handle=/u03/orabkp/coeusdba/b_3sh2l4rr_1_1 comment=NONE
channel Channel1: backup set complete, elapsed time: 00:00:02
channel Channel1: deleting archive log(s)
archive log filename=/u04/arch/coeusdba/1_49.dbf recid=200 stamp=573215609
Finished backup at NOV-01-2005 10:33:35
Starting Control File and SPFILE Autobackup at NOV-01-2005 10:33:35
piece handle=/u04/orabkp/coeusdba/ctl_file_bkps/c-1916078485-20051101-00 comment=NONE
Finished Control File and SPFILE Autobackup at NOV-01-2005 10:33:38
released channel: Channel1
RMAN>
RMAN>
Recovery Manager complete.
syntax error at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/warnings.pm line 306, near "{^"
syntax error at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/warnings.pm line 311, near "{^"
BEGIN failed--compilation aborted at /u01/app/oracle/product/9.2.0/EM10g_1/perl/lib/5.6.1/English.pm line 38.
BEGIN failed--compilation aborted at /u01/app/oracle/product/9.2.0/dbs/scripts/rmanc.pl line 20
Is anyone having this problem in 10g and if so , can you provide me with some insight with respect to resolution?

The .sh script calls a perl script that parses the output of the report obsolete command in rman and deletes the obsolete datasets from disk. This shell completes from the command line with no errors. Here is the .sh and the perl script. Like I said the odd thing is that this shell executes successfully from the command line. Thanks for your interest in looking at this.
cat coeusdba_new.sh
/u01/app/oracle/product/9.2.0/dbs/scripts/rmanc.pl target sys/<password>@coeusdba catalog rmantest/<password>@recv redundancy 2
rmanc.$ cat rmanc.pl
#!/usr/bin/perl -w
# NAME
# rmanc.pl - delete obsolete backups and copies
# DESCRIPTION
# This perl script automates deletion of obsolete datafilecopies and
# backup pieces. It uses perl strin manipulation to process the output of the RMAN
# "report obsolete" command and creates rm commands to delete the files
# NOTES
# Some customization is necessary.
# Adapted from Oracle 8i rman1.sh Unix shell script.
# benmalek 03/08/2003 - Modified to delete backup sets and datafilecopies only
# Does not touch backup records.
use strict;
#use English;
#$ENV{ORACLE_OWNER}='oracle';
#$ENV{ORACLE_HOME}='/disk01/app/oracle/product/9.2.0';
$ENV{NLS_DATE_FORMAT}='DD-MON-YYYY:HH24:MI:SS';
&PrintEnv;
sub Usage {
my ($arg1, @arg2) = @_;
my $base_name = `basename $0`;
chop($base_name);
CASE: {
if (!defined($arg1)) {last CASE; }
if ($arg1 =~ /\S/) {print ("\nUnknown argument or incorrect value for: $arg1\n\n"); last CASE; }
my $example1 = 'rmanc.pl target sys/orclpass@orcl catalog rman/rmanpass@rec redundancy 5';
my $example2 = 'rmanc.pl target sys/orclpass@orcl nocatalog redundancy 5';
my $usage_txt =
" Usage: $base_name [option] ...
option: [target CNCTSTR] [catalog CNCTSTR | nocatalog] [params 'PARMS'] [redundancy NUMBER]
Option Description
target CNCTSTR Connect to the target db using CNCTSTR.
catalog CNCTSTR Connect to catalog db using CNCTSTR.
nocatalog Don't use a recovery catalog.
parms 'PARMS' Use PARMS string for SBT_TAPE maintenance channel.
You can use single or double quotes depending on
your needs. In the rman script, single-quotes
will be used.
redundancy NUMBER Set redundancy of backups to NUMBER.
The catalog or nocatalog option must be specified. All others are optional
The target option must also be specified
Examples:
$example1
$example2 ";
print ("$usage_txt \n");
die "Exiting subroutine 'Usage'.\n";
# Initialize default connect string variables:
my $target=""; # force user to supply target option
my $catalog=""; # force user to supply catalog option;
my $parms="";
my $redun=""; # force user to supply redundancy option;
# process target and catalog arguments
my $args = @ARGV;
while ( $args > 0 ) {
ARGS: {
if (($ARGV[0] eq "target") && defined($ARGV[1]))
{$target="$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if (($ARGV[0] eq "catalog" || $ARGV[0] eq "rcvcat") && defined($ARGV[1]))
{ $catalog="$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if ($ARGV[0] eq "nocatalog") { $catalog="$ARGV[0]"; last ARGS;}
if (($ARGV[0] eq "parms") && defined($ARGV[1])) { $parms = "$ARGV[0] $ARGV[1]"; shift(@ARGV); last ARGS;}
if (($ARGV[0] eq "redundancy") && defined($ARGV[1]) && !($ARGV[1] =~ /\D/))
{$redun=$ARGV[1]; shift(@ARGV); last ARGS;}
&Usage($ARGV[0]);
shift(@ARGV);
$args= @ARGV;
if ((!defined($catalog) || $catalog eq "") || (!defined($target) || $target eq "") || (!defined($redun) || $redun eq "" )) {&Usage;}
#print (" target=$target \n catalog=$catalog \n parms=$parms \n redundancy=$redun\n");
# Get a list of obsolete disk files to delete:
my @rman_out=`rman $target $catalog << EOF
report obsolete redundancy=$redun device type disk;
exit;
EOF`;
# debug
print ("############################################\n");
print ("Output of REPORT OBSOLETE REDUNDANCY=$redun\n");
print @rman_out;
print ("############################################\n");
#my $command = `rman $target $catalog << EOF
# report obsolete redundancy=$redun device type disk;
# exit;
# EOF"
#open (RMAN, "$command |" );
#my @rman_out=<RMAN>;
# Extract the names of the obsolete files to delete
my $line;
my @files;
my @dates;
my @pieces;
foreach $line (@rman_out) {
if (($line =~ /Backup Piece/) && ($line =~ /\S/)) {
my @fields=split (/\s+/, $line);
my $nelem=@fields;
push(@pieces, $fields[$nelem-3]);
push(@dates, $fields[$nelem-2]);
push(@files, $fields[$nelem-1]);
# Verify files exists
my $i=0;
foreach $line (@files) {
if (-e $line) {
print ("Deleting backup piece or file copy: $pieces[$i] $dates[$i] $line\n");
system("rm $line");
} else {
# print ("file $line does not exist. \n");
$i = $i + 1;
sub PrintEnv{
my $var;
foreach $var (sort keys %ENV) {
print "$var: \"$ENV{$var}\".\n"
pl

RMAN-01009: syntax error: found "cancel"

Hi!
I am playing with rman on my test machine and I encountered error that I can't resolve.
I've tried to restore/recover datafiles executing this commands:
$ sqlplus "/as sysdba"
SQL>startup mount
RMAN> restore database
(everything went well)
RMAN> recover database until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "cancel": expecting one of: "logseq, scn, sequence, time"
RMAN-01007: at line 1 column 24 file: standard input
I've executed this command on several occasions and never had a problem, but now syntax error.
Just don't know why syntax error?!
OS: Centos 5
DB: 11.1.0.7.0
Thanks for any help,
Marko

RMAN> alter database recover database using backup controlfile until cancel;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "recover": expecting one of: "mount, open"
RMAN-01007: at line 1 column 16 file: standard input
RMAN> recover database;
Starting recover at 05-FEB-09
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/05/2009 00:11:30
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oradata/testdb/redo/testdb/onlinelog/o1_mf_3_4qfwj5fn_.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
I am trying to execute:
RMAN> sql 'alter database open resetlogs';
sql statement: alter database open resetlogs
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 02/05/2009 00:09:18
RMAN-11003: failure during parse/execution of SQL statement: alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
This is the reason why I am trying to execute cancel-based recovery.

RMAN script gives error when scheduled

Hi,
I have this rman script....
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TPRD,OB2BARLIST=test TPRD)';
backup incremental level <incr_level>
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
database;
backup
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
archivelog all;
backup
format 'test TPRD<TPRD_%s:%t:%p>.dbf'
current controlfile;
When this script is executed to run at the present moment, it gives no problems. However, when this script is scheduled and when executed at the scheduled time, it gives the following error:
RMAN> CONNECT TARGET *
2> run {
3> allocate channel 'dev_0' type 'sbt_tape'
4> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TPRD,OB2BARLIST=test TPRD,OB2BARHOSTNAME=+server.com+)';
5> backup incremental level
6> format
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "format": expecting one of: "equal, integer"
RMAN-01007: at line 6 column 1 file: C:/ob2.cmdfile.12274.c1e9.rman
[Major] From: ob2rman@+server.com+ "TPRD" Time: 2-11-2009 13:35:16
The database reported error while performing requested operation.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "format": expecting one of: "equal, integer"
RMAN-01007: at line 6 column 1 file: C:/ob2.cmdfile.12274.c1e9.rman
[Major] From: ob2rman@+server.com+ "TPRD" Time: 2-11-2009 13:35:16
Oracle Recovery Manager completed with errors.
Does anyone know what the problem is and why it only gives the error when it is scheduled and not otherwise?
Thanks in advance.

Hi user629987,
The error comes from the following line
backup incremental level <incr_level>(found "format": expecting one of: "equal, integer"
see link:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96565/rcmsynta9.htm#78484)
Can you replace it with
backup incremental level 0and retry?
Might be you have to adjust your format string to avoid <, > and : characters.
Regards,
Tycho

Rman backup validate error

DBGSQL: RCVCAT> begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; [10:37:16.635]
DBGSQL: sqlcode = 6550 [10:37:16.635]
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command restore : 600
RMAN-00600: internal error, arguments [9302] [6550] [begin dbms_rcvman.findSpfileBackup( allCopies => TRUE, rmanCmd => dbms_rcvman.restoreCmd_t); end; ] [] []
RMAN-06004: ORACLE error from recovery catalog database: ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'FINDSPFILEBACKUP'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
pls any one help me out
Thanks!

Since you say nothing about your OS and database version and we also don't know,which command produces this error, only a vague guess is possible, COULD be
Bug 7633694: RESTORE SPFILE LS-00306: WRONG NUMBER OR TYPES OF ARGUMENTS 'FINDSPFILEBACKUP' .
IF this bug is hit possible workarounds are:
1) Don't use a 11gR1 catalog
2) don't use spfile,keep a text based pfile
3) upgrade to 11gR2 (IF your OS is Linux or Solaris)
Werner

RMAN-00600: internal error, arguments [8201]

Hi,
on 10g R2 on a win 2003 server we had follwing error for RMAN backup :
RMAN-00600: internal error, arguments [8201] [] [] [] []we looked at metalink note : 412786.1
that says :
There is mismatch between the information stored in the Controlfile and rman Catalogand did RMAN> resync catalog; that did not resolve the problem.
We created another RMAN schema which means a new catalog. Then it is difficult to believe
that the new catalog was not syncronized with control file. But again exactly the same error :
RMAN-00600: internal error, arguments [8201] [] [] [] []
Why again the same error with a new catalog ?
Thanks.

Thank you Werner. I read the discussion. How about this work arround in Bug No. 5916459 :
Workaround ========== . Modify ?/admin/recover.bsq as follows and upgrade recovery catalog schema .
using UPGRADE CATALOG command.
FROM
SELECT nvl(oldest_flashback_time, MAXDATEVAL) INTO fbUntiltime FROM fb
WHERE dbinc_key = this_dbinc_key; .
TO .
SELECT nvl(oldest_flashback_time, MAXDATEVAL) INTO fbUntiltime FROM fb
WHERE dbinc_key = this_dbinc_key AND db_unique_name = this_db_unique_name; . I need some details to apply it.

RMan and perflib error.

Similar Messages

Maybe you are looking for