RMAN Backup error with Symantec Backup Tool

Hi
My Environment
OS Windows server 2003 R2
Oracle 10G R2 10.2.03 2 node RAC
When i am taking backup maually in the command prompt with RMAN, it is successful, but when we are trying from Symantec Backup tool we are getting errors like
RMAN 03002 failur of Backup lus archivelog is problem,
RMAN 10015 error compiling PL/SQL programme
RMAN 10033 error during compilation of job step2
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer)
So please tell me why its giving the error with Symatntec and why when i am doing manually it is successfull.
What could be the solution, please we are taking daily and weekly backups with Symantec on HP tape library. Please suggest me to the needful.
Immediate reply highly apperciated
Thanks
Edited by: 873393 on Apr 17, 2012 10:09 AM

Hello,
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer) The ORA-04030 error message is interesting. It means that the OS doesn't have enough memory for Oracle.
So you may monitore the Memory usage of the Server during the Symantec Backup, and check for any activity. May be the Symantec Backup runs when other Batch Jobs use already a lot of memory . You may also have to extend the RAM of the Server.
Also, check for the RMAN script used by Symantec and compare with the "manual" script. May be, some options are used with Symantec and consume more resources on the Server.
Hope this help.
Best regards,
Jean-Valentin

Similar Messages

Never worked on Non-RMAN Backup tools

I have never worked on Non-RMAN backup tools. I have only worked on databases which are below 1 TB in size. If you have an Oracle 10GR2 Database which is 5 TB in size, would you still recommend RMAN for it?
Do third party tools use RMAN internally ie integrated to it?

My production DB is 800gb in size and it takes 3.5 hours to take a full backup in compressed mode. This means , it will take around 15 hours to backup a 5TB database !!
Hi Jack,
You are not obliged to do full backups with RMAN. You can use this strategy for example :
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#sthref412
You will have a fist full backup (image copy) to do but after that only incremental backups will be done. Much space is needed of course but it works well.
Best regards
Phil

RMAN error with Symantec tool

Hi
My Environment
OS Windows server 2003 R2
Oracle 10G R2 10.2.03 2 node RAC
When i am taking backup maually in the command prompt with RMAN, it is successful, but when we are trying from Symantec Backup tool we are getting errors like
RMAN 03002 failur of Backup lus archivelog is problem,
RMAN 10015 error compiling PL/SQL programme
RMAN 10033 error during compilation of job step2
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer)
So please tell me why its giving the error with Symatntec and why when i am doing manually it is successfull.
What could be the solution, please we are taking daily and weekly backups with Symantec on HP tape library. Please suggest me to the needful.
Immediate reply highly apperciated
Thanks

Hello,
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer) The ORA-04030 error message is interesting. It means that the OS doesn't have enough memory for Oracle.
So you may monitore the Memory usage of the Server during the Symantec Backup, and check for any activity. May be the Symantec Backup runs when other Batch Jobs use already a lot of memory . You may also have to extend the RAM of the Server.
Also, check for the RMAN script used by Symantec and compare with the "manual" script. May be, some options are used with Symantec and consume more resources on the Server.
Hope this help.
Best regards,
Jean-Valentin

Error with Nokia Configuration Tool with a E71.

Hi everyone, when using Nokia configuration tool, I tried many times to send a profile saved with a E71 to another E71 but each time I try I get the same error message. When trying to copy the PKI / Certificates group , the soft says "error 500 unexpected condition that prevented to request being fulfilled" ; the others groups work fine. I'm used to do this with the E51 and I've never encountered this problem. I have to program a lot of phones so it would be much easier for me if this method works.
Thank you for your help.

Hi Gabor,
If the issue is still alive, please try to connect your N97 device after launching the Nokia Configuration Tool, NCT should detect your N97 device and if there are no profiles created for N97 device, It will prompt you to create a new profile.
I dont see any issue in identifying the N97 device with NCT 6.0.
Please let me know if it does not help.
Thanks & Regards,
Raghava Reddy K

RMAN backup fails using OEM with no output error

I am trying to do a weekly automatic full backup of a database in noarchivelog mode using RMAN in Enterprise Manager. Every time I submit the backup job (even if I try to do an immediate backup) the job fails almost immediately. When I Iook at the job output for the failed attempt, it says that there is no output for the job. I believe I have all of the preferred credentials and priveleges correct. Does anyone have any ideas as to what the problem could be or maybe where I can find an error log for rman to get a better explanation of the error?
Thanks

please check in metalink.....
you find useful informations here:
RMAN backup using Oracle Secure Backup fails with ORA-19511 (sbt__rpc_connect)
Doc ID: Note:396046.1
Best Regards,
Shishir Tekade.
My Blog: http://shishirtekade.blogspot.com

RMAN backup in RAC failing with error ORA-19566

Hi all, i have 2 node RAC and i am trying to take rman backup of the database which is in ASM filesystem.
There is a corruption in SYSAUX file and rman is failing to take backup of the sysaux datafile and error thrown at the end like
piece handle=/home/oracle/orabackup/BLOOM_LVL0_20120627_1qnejueh_s58_p1 tag=TAG20120627T185538 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/27/2012 18:56:17
*ORA-19566: exceeded limit of 0 corrupt blocks for file +DATA/bloom/datafile/sysaux.257.775475317*
Then i tried to validate the backup in rman of the datafile sysaux nad fired the following query
SQL> SELECT * FROM v$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
3 32011 1 0 ALL ZERO
3 32049 40 0 ALL ZERO
3 32034 1 0 ALL ZERO
3 28964 1 1399837 LOGICAL
3 32015 2 0 ALL ZERO
and found all the blocks in the table WRH$_SQL_PLAN.
Then dropped the table, and tried to take backup of the database and it is failing again with the same error..
ANY SOLUTION TO TAKE BACKUP OF THE DATABASE.
anyhow we can SET MAXCORRUPT FOR DATAFILE 3 to value, but does this works all time...
Thanks in advance,
TEJAS

Both are good suggestions, but
Osama-mustafa wrote:
RMAN> blockrecover datafile 5 block 2684; -- Fix Eror That ship has already sailed:
TEJAS_DBA wrote:
And Yes this is the first time i am taking backup on the database.And:
Osama-mustafa wrote:
Or Skip Option
Like
RMAN> RUN{
2> SET MAXCORRUPT FOR DATAFILE 1,3 to 1;
3> BACKUP DATABASE;
4> }The OP was aware of this option and hopefully was able to get at least some sort of a backup eventually. But as for the dropped WRH$_SQL_PLAN, TEJAS is, I will use the word "braver" than most. And as often is the case, Dan Morgan offered the only bit of sensible advise.
Open an SR.
Good luck.

RMAN backup got failed with the error ORA-19566

Hi,
One of database, while taking backup using RMAN, it failed with the following error:
RMAN-03009: failure of backup command on DISK4 channel at 11/28/2012 09:47:29
ORA-19566: exceeded limit of 0 corrupt blocks for file <faile_name>
I used DBV to identify the number of blocks corrupted.
I referred the Metalink iD 457422.1 & 336133.1. But it did not help since the corrupted blocks have got object in it.
I could able to find the object as well. it is one of the table in the datafile.
I used 'ALTER TABLE ... MOVE..' command to see if that helps. But again getting the same error while taking the backup and corrupted blocks still exists.
DB Version : 10.2.0.5
OS Version : RHEL 5.6
Please help me out to get this fixed.

Here it is:
SQL> Select * from v$database_block_corruption ;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION_TYPE
13 3988352 128 0 ALL ZERO

Backupexec symantec rman backup

Hi
We have Oracle 10gR2 database on Linux with Oracle remote agent installed/configured. Database size is about 100GB. Backup exec 10 on another win2k3 backupserver with Oracle agent installed./configured.
Can we take manual rman backup with this tape drive on another linux server.

Hello,
Ora 00603 Oracle server session terminate by fatal error.
Ora 004030 out of process memory when trying to allocate 4120 bytes(pl/sql) MPCODE,BAMMA, BAM Buffer) The ORA-04030 error message is interesting. It means that the OS doesn't have enough memory for Oracle.
So you may monitore the Memory usage of the Server during the Symantec Backup, and check for any activity. May be the Symantec Backup runs when other Batch Jobs use already a lot of memory . You may also have to extend the RAM of the Server.
Also, check for the RMAN script used by Symantec and compare with the "manual" script. May be, some options are used with Symantec and consume more resources on the Server.
Hope this help.
Best regards,
Jean-Valentin

I am getting below error while taking RMAN backup.

Friends,
I am getting below error while taking RMAN backup.
The issue is related with a lock while trying to backup the controlfile.
The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Is there anyway to solve this issue?Thanks in advance.

Hi,
SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
FROM v$session s, v$enqueue_lock l
WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
no rows selected
Oracle version : 10.2.0.3
I am getting this error once in a month not everyday.
Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Please suggest me based on this..Thanks in advance..

Creating a new controlfile with datafiles in RMAN backup

Hi,
i am using oracle 10g (10.2.0.1) in RHEL5 server. i am trying to restore a RMAN backup from one server to another new server with new db name. i have taken out the spfile from RMAN autobackup and created pfile from it and edited the pfile with new dbname and directory structure and started the db in nomount with the new pfile. Now i have restored the controfile from the RMAN autobackup tried to put the database in mount state. But it failed due to the below error
RMAN-03002: failure of alter db command at 11/05/2012 21:44:56
ORA-01103: database name 'ORADB' in control file is not 'DEVDB'
Hence i shutdown the database and started the db in nomount with new pfile and tried to create the controlfile with the new db name,but it failed as it is looking for the datafiles.
ORA-01503: CREATE CONTROLFILE failed
ORA-01565: error in identifying file
'/u01/app/oracle/oradata/DEVDB/datafile/o1_mf_system_80jq0kfw_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
All my datafiles reside in my RMAN backup. How to get the datafiles from RMAN backup in the above scenario??
Regards,
007

Hello;
The location and filename and DBIS will be different, but you need something like this :
$ORACLE_HOME/bin/rman << EOF
CONNECT TARGET /
STARTUP NOMOUNT;
SET DBID 3754763357; #DBID of PROD database
RUN
   ALLOCATE CHANNEL c1 DEVICE TYPE disk format '/u01/oradata/backups';
   RESTORE CONTROLFILE FROM '/u01/oradata/backups/sb_t790762003_s85_p1';
   ALTER DATABASE MOUNT;
   SET NEWNAME FOR DATAFILE 1 TO '/u01/app/oracle/oradata/CLONE/system01.dbf';
    SET NEWNAME FOR TEMPFILE 1 TO '/u01/app/oracle/oradata/CLONE/temp01.dbf';
   RESTORE DATABASE;
   SWITCH DATAFILE ALL;
   RECOVER DATABASE;
   release channel c1;
ALTER DATABASE OPEN RESETLOGS; So you need "SET NEWNAME" for all your files
Full Example
http://www.visi.com/~mseberg/rman/restore_database_without_catalog.html
Best Regards
mseberg

Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

Hi Experts,
I am restoring production RMAN backup to UAT . Using below steps
1)rman target=/
2)RMAN> startup nomount;
3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
Starting restore at 05-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=3 device type=DISK
channel ORA_DISK_1: copied control file copy
output file name=+DATA_ACME/acme/controlfile/current.256.724845209
output file name=+DATA_ACME/acme/controlfile/current.257.724845209
Finished restore at 05-AUG-10
4) RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
new RMAN configuration parameters are successfully stored
6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
List of Files Unknown to the Database
=====================================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
List of Files Which Where Not Cataloged
=======================================
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
RMAN-07517: Reason: The file header is corrupted
8) RMAN> run {
2> set until sequence 1789 thread 2;
3> restore database;
4> recover database;
5> sql 'alter database open resetlogs';
6> }
executing command: SET until clause
Starting restore at 06-AUG-10
using channel ORA_DISK_1
Finished restore at 06-AUG-10
Starting recover at 06-AUG-10
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2803
channel ORA_DISK_1: restoring archived log
archived log thread=2 sequence=6051
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2804
channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/06/2010 23:10:38
ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
Thanks
Edited by: user11981514 on Aug 6, 2010 9:46 AM

Hi,
Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
Regards,
Vaibhav

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

Problem with rman backups

We upgraded, the rman catalog due to the following error:
PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.01 in RCVCAT database is not current PL/SQL package RMAN.DBMS_RCVMAN version 11.02.00.01 in RCVCAT database is not current
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql command at 01/17/2011 21:00:36
ORA-03114: not connected to ORACLEWe registered our database on the catalog again
problem we have now is that our backup fails with the following errors:
RMAN> connect target *
2> connect catalog *
3>
4> run {
5> crosscheck archivelog all;
6> }
7>
connected to target database: MAC (DBID=710471977)
connected to recovery catalog database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 06:00:29
ORA-03114: not connected to ORACLEany suggestions, as to how we can fix these errors

Must this be done fron the local machine where my backup scripts reside..
or must it be done on the catalog server?????
I ran the crosscheck command from the local machine without connecting to the catalog
here are the eroors I received:
oracle $ rman
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Jan 20 11:42:42 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target /
connected to target database: MAC (DBID=710471977)
RMAN> run{
2> crosscheck backup COMPLETED AFTER 'sysdate-1';
3> }
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
RMAN-12010: automatic channel allocation initialization failed
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/20/2011 11:43:48
RMAN-12010: automatic channel allocation initialization failed
ORA-03114: not connected to ORACLE

RMAN-20260 error while trying to delete a backup piece

Hello,
In my company we use Oracle 10g, backup managed by RMAN and integrated with TSM.
In order to remove the old backup files, there is a delete script to do this.
Basically this script:
connect to RMAN catalog
allocate channel for maintenance device type 'sbt_tape'
change backuppiece <file names from rc_backup_piece older than 35 days> delete;
When this command is run, this error is being generated:
RMAN-03002: failure of delete command at 01/18/2010 17:14:00
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20260: backup piece not found in the recovery catalog
RMAN-06092: error while looking up backup piece
Any ideas?
Thanks in advance.
Fer

Hy Tycho,
Yes, it's a tape backup.
This is the channel used to take the backup:
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/opt/tsm..../...opt)';
I tried this rman command with a file name that is 35 days older in rc_backup_piece:
list backuppiece <file name>;
I received this error:
RMAN-20260: backup piece not found in the recovery catalog;
How can this file be in the rc_backup_piece and not appear in the list backuppiece ?
Thanks a lot.
Fer

RMAN Backup error with Symantec Backup Tool

Similar Messages

Maybe you are looking for