EBS R11i  Rman DB backup error

Hi Friends,
platform AIX 5L
I am backing up my EBS R11i database using RMAN but I got error.
$ rman target /
Recovery Manager: Release 9.2.0.6.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: TEST (DBID=1969797320)
RMAN> backup database;
Starting backup at 10-DEC-08
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=39 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/10/2008 15:17:06
ORA-00600: internal error code, arguments: [525], [0x70000001137DD50], [5], [library cache], [5], [0x700000000025BF0], [device information], []
ORA-27041: unable to open file
IBM AIX RISC System/6000 Error: 25: Not a typewriter
Additional information: 16
RMAN> exit
What file is RMAN opening here > ORA-27041: unable to open file
Thanks a lot

Please refer to Note: 262997.1 - ORA-600 [525] / [510] and ORA-27041 When Running RMAN Backup On IBM AIX Platform
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=262997.1

Similar Messages

  • RMAN Hot Backup Errors.

    Hello Everyone
    I would appreciate if someone can assist me in resolving a problem. Starting from December of last year, we were able to take daily hot backups of our ORACLE 10g database server successfully with no issues. Presently we have been experiencing a number of errors in the logs, even though the script has not been changed. The main errors are as follows:
    RMAN-03009: failure of backup command on t1 channel at 05/08/2007 00:01:19
    ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
    In investigating the errors, it seemed to be associated to the tablespace not being put offline or backup mode cleanly, I assumed this was due to persons working later, so I scheduled the backup for a later time but I still got the same error in the log the following day. Can you assist me in resolving this problem please?

    Is the db running in ARCH mode?
    Error:     ORA 19602
    Text:     cannot backup or copy active file in NOARCHIVELOG mode
    Cause:     You tried to copy or backup a file that was not closed cleanly, and
         the database was in NOARCHIVELOG mode. This is not allowed because when
         restored, the file will require redo application before it is usable,
         and redo is not currently being saved beyond the contents of the online
         redo logs.
    Action:     Take the tablespace offline clean or close the database and retry the
         copy or backup. Take the tablespace offline clean or close the database
         and retry

  • Error Message from RMAN after backup

    Hello,
    I get this message when i try to backup a imported database:
    RMAN-00571: ==================================================
    =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ==================================================
    =========
    RMAN-03007: retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel tut
    RMAN-10035: exception raised in RPC: ORA-19502: write error on file "/ora_db/backup/SKR/test.bak", blockno 238593 (blocksize=512)
    ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
    Additional information: 238593
    Additional information: 1024
    Additional information: 239121
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
    The RMAN ist configured correctly because i can backup the database before importing the dumpfile.
    I tryed to set the Parameter SETSIZE but then i get a different error message.
    Discspace free: 50 GB
    I hope someone can help me.
    Thorsten

    OK,
    its already done, you have to set "setsize" (Thanks to th e helper).
    But why?

  • 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.

  • Got error when creating a standby DB from rman:  no backup or copy... Why?

    We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
    RMAN> RUN
    2> {
    3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
    4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
    5> DUPLICATE TARGET DATABASE for standby
    6> nofilenamecheck
    7> dorecover;
    8> }
    9>
    10> exit
    using target database control file instead of recovery catalog
    allocated channel: aux1
    channel aux1: sid=582 devtype=DISK
    allocated channel: aux2
    channel aux2: sid=584 devtype=DISK
    Starting Duplicate Db at 21-JUN-12
    contents of Memory Script:
    set until scn 12198261770353;
    restore clone standby controlfile;
    sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 21-JUN-12
    released channel: aux1
    released channel: aux2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    ===========================================================================
    The backups should have controlfile. There is rman show all display:
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
    Why and how to fix? Thanks for help!

    Here is the list of command:
    RMAN> list backup of controlfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5518 Full 4.57M DISK 00:00:07 17-JUN-12
    BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
    Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5522 Full 4.57M DISK 00:00:00 18-JUN-12
    BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
    Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5526 Full 4.57M DISK 00:00:01 19-JUN-12
    BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
    Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5530 Full 4.57M DISK 00:00:02 20-JUN-12
    BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
    Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    5534 Full 4.57M DISK 00:00:02 21-JUN-12
    BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
    Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
    Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
    ==================================================================
    I tried to catalog the controlfile:
    RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
    ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
    ====================================================================
    We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
    Thanks for help!

  • Error in RMAN TAPE BACKUP

    Dear Gurus,
    I got the following error in RMAN TAPE backup.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of delete command on default channel at 09/20/2011 02:36:58
    ORA-15028: ASM file '+ASMFLASH/gcprod/archivelog/2011_09_15/thread_2_seq_55857.2176.761912673' not dropped; currently being accessed
    RMAN>
    Recovery Manager complete.my RMAN BACKUP Script is:
    rman target sys/*****@gcprod1  nocatalog  << EOF
    spool log to $v_bdest/clean_catalog_TAPE.log append;
    run {
    allocate channel c1 type 'sbt_tape' parms
    'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    #crosscheck backupset;
    #crosscheck copy;
    #crosscheck archivelog all;
    # included on 21Jan2011 at 9:18 PM
    #delete noprompt expired backup;
    delete noprompt obsolete;
    #delete noprompt expired archivelog all;
    # included on 21Jan2011 at 9:18 PM
    release channel c1;
    exit
    EOFMy RMAN RETENTION POLICY IS:
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/product/10.2.0.1/db_1/dbs/snapcf_gcprod1.f';According to retention policy archivelogs of past 3 days should be present rest and all , i have written a script to delete and it is performing well from past 6 months, but now recently we got this error
    we have enough archivelog space.
    and the archive log pointing in this error is on 15th september archivelog.....today date is 20th september....
    My archive log was stored in asm .... i went there and saw that still 15th september archivelogs are present there.
    Please help me regarding this
    Regards,
    Vamsi.....

    For RMAN topics, please use: {forum:id=74}.

  • Rman hot backup script  gives error in R12.

    hi experts
    i m facing following prob when run the backup script. 1 day before the same script runs correctily but now  it gives me error at the allocatioion of channel rest of command run correctly.
    [root@testerp rman_log]# cat UAT_daily_rman_hot_bkp_01-11-14_140301.log
    -bash: /root/.bash_profile: Permission denied
    Recovery Manager: Release 11.1.0.7.0 - Production on Sat Jan 11 14:03:01 2014
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: UAT (DBID=2855851979)
    connected to recovery catalog database
    RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "end-of-file": expecting one of: "allocate, alter, advise, backup, beginline, blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, execute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, resync, repair, }, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
    RMAN-01007: at line 12 column 1 file: standard input
    RMAN>
    RMAN>
    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: "for"
    RMAN-01008: the bad identifier was: c2
    RMAN-01007: at line 1 column 18 file: standard input
    RMAN>
    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: "for"
    RMAN-01008: the bad identifier was: c3
    RMAN-01007: at line 1 column 18 file: standard input
    RMAN>
    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: "for"
    RMAN-01008: the bad identifier was: c4
    RMAN-01007: at line 1 column 18 file: standard input
    RMAN>
    Starting backup at 11-JAN-14
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=362 device type=DISK
    channel ORA_DISK_1: starting incremental level 1 datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00021 name=/d06/UAT/proddata/a_txn_data06.dbf
    input datafile file number=00392 name=/d06/UAT/db/apps_st/data/a_txn_data01.dbf
    input datafile file number=00401 name=/d06/UAT/db/apps_st/data/a_txn_data02.dbf
    input datafile file number=00402 name=/d06/UAT/db/apps_st/data/a_txn_data03.dbf
    input datafile file number=00022 name=/d06/UAT/proddata/a_txn_data07.dbf
    input datafile file number=00014 name=/d06/UAT/db/apps_st/data/a_txn_data04.dbf
    input datafile file number=00020 name=/d06/UAT/proddata/a_txn_data05.dbf
    input datafile file number=00011 name=/d06/UAT/db/apps_st/data/sysaux01.dbf
    input datafile file number=00018 name=/d06/UAT/db/apps_st/data/sysaux02.dbf
    input datafile file number=00023 name=/d06/UAT/proddata/a_txn_data08.dbf
    input datafile file number=00379 name=/d06/UAT/db/apps_st/data/undo01.dbf
    input datafile file number=00024 name=/d06/UAT/proddata/sysaux03.dbf
    input datafile file number=00025 name=/d06/UAT/proddata/sysaux04.dbf
    input datafile file number=00033 name=/d06/UAT/proddata/a_txn_ind11.dbf
    input datafile file number=00029 name=/d06/UAT/proddata/a_txn_ind09.dbf
    input datafile file number=00030 name=/d06/UAT/proddata/a_txn_ind10.dbf
    input datafile file number=00015 name=/d06/UAT/db/apps_st/data/a_txn_ind06.dbf
    input datafile file number=00026 name=/d06/UAT/db/apps_st/data/a_txn_ind07.dbf
    input datafile file number=00028 name=/d06/UAT/db/apps_st/data/a_txn_ind08.dbf
    input datafile file number=00393 name=/d06/UAT/db/apps_st/data/a_txn_ind01.dbf
    input datafile file number=00403 name=/d06/UAT/db/apps_st/data/a_txn_ind02.dbf
    input datafile file number=00404 name=/d06/UAT/db/apps_st/data/a_txn_ind03.dbf
    input datafile file number=00405 name=/d06/UAT/db/apps_st/data/a_txn_ind04.dbf
    input datafile file number=00406 name=/d06/UAT/db/apps_st/data/a_txn_ind05.dbf
    input datafile file number=00400 name=/d06/UAT/db/apps_st/data/a_media01.dbf
    input datafile file number=00353 name=/d06/UAT/db/apps_st/data/system08.dbf
    input datafile file number=00013 name=/d06/UAT/db/apps_st/data/system12.dbf
    input datafile file number=00352 name=/d06/UAT/db/apps_st/data/system09.dbf
    input datafile file number=00394 name=/d06/UAT/db/apps_st/data/a_ref01.dbf
    input datafile file number=00407 name=/d06/UAT/db/apps_st/data/a_ref02.dbf
    input datafile file number=00396 name=/d06/UAT/db/apps_st/data/a_summ01.dbf
    input datafile file number=00395 name=/d06/UAT/db/apps_st/data/a_int01.dbf
    input datafile file number=00008 name=/d06/UAT/db/apps_st/data/a_queue02.dbf
    input datafile file number=00027 name=/d06/UAT/db/apps_st/data/a_queue03.dbf
    input datafile file number=00031 name=/d06/UAT/db/apps_st/data/a_queue04.dbf
    input datafile file number=00399 name=/d06/UAT/db/apps_st/data/a_queue01.dbf
    input datafile file number=00001 name=/d06/UAT/db/apps_st/data/system01.dbf
    input datafile file number=00002 name=/d06/UAT/db/apps_st/data/system02.dbf
    input datafile file number=00003 name=/d06/UAT/db/apps_st/data/system03.dbf
    input datafile file number=00004 name=/d06/UAT/db/apps_st/data/system04.dbf
    input datafile file number=00005 name=/d06/UAT/db/apps_st/data/system05.dbf
    input datafile file number=00398 name=/d06/UAT/db/apps_st/data/a_archive01.dbf
    input datafile file number=00295 name=/d06/UAT/db/apps_st/data/system06.dbf
    input datafile file number=00351 name=/d06/UAT/db/apps_st/data/system07.dbf
    input datafile file number=00354 name=/d06/UAT/db/apps_st/data/system11.dbf
    input datafile file number=00288 name=/d06/UAT/db/apps_st/data/system10.dbf
    input datafile file number=00012 name=/d06/UAT/db/apps_st/data/apps_ts_tools01.dbf
    input datafile file number=00016 name=/d06/UAT/db/apps_st/data/a_ref03.dbf
    input datafile file number=00019 name=/d06/UAT/db/apps_st/data/MLSEIGL01.dbf
    input datafile file number=00032 name=/d06/UAT/db/apps_st/data/RMAN01.dbf
    input datafile file number=00397 name=/d06/UAT/db/apps_st/data/a_nolog01.dbf
    input datafile file number=00314 name=/d06/UAT/db/apps_st/data/portal01.dbf
    input datafile file number=00017 name=/d06/UAT/db/apps_st/data/a_int02.dbf
    input datafile file number=00006 name=/d06/UAT/db/apps_st/data/ctxd01.dbf
    input datafile file number=00010 name=/d06/UAT/db/apps_st/data/olap.dbf
    input datafile file number=00009 name=/d06/UAT/db/apps_st/data/odm.dbf
    input datafile file number=00007 name=/d06/UAT/db/apps_st/data/owad01.dbf
    channel ORA_DISK_1: starting piece 1 at 11-JAN-14
    [root@testerp rman_log]#
    backup script is below:
    in this script it returns error only at the channel allocaition rest of all backup command i run manually or with scirpt it runs correctly.4
    i m not able to know why it returns error only at challnel allocation 1 day before it runs correctly.
    [orauat@testerp rman_script]$ cat rman_backup.sh
    #!/bin/sh
    #ORACLE_SID=UAT
    #BACKUP_START_TIME='date +"%y""%m""%d"_"%H""%M""%S"'
    #ORACLE_HOME=/d06/UAT/db/tech_st/11.1.0
    #PATH=$PATH:${ORACLE_HOME}:${ORACLE_HOME}/bin
    #export ORACLE_SID
    #export ORACLE_HOME
    #export PATH
    /d06/UAT/db/tech_st/11.1.0/bin/rman catalog rman/rman007 target sys/sysuat <<EOF
    run
    allocate channel c1 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_Arch_%c_%U';
    sql 'alter system switch logfile';
    sql 'alter system switch logfile';
    sql 'alter system archive log current';
    delete expired archivelog all;
    crosscheck archivelog all;
    backup archivelog all;
    delete noprompt archivelog all completed before 'sysdate-4' backed up 1 times to disk;
    allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    backup incremental level 1 database;
    delete expired backup device type disk;
    delete obsolete device type disk;
    release channel c1;
    release channel c2;
    release channel c3;
    release channel c4;
    exit
    EOF
    regards
    pritesh ranjan

    yes the script is edited
    i have add some command line and edit it for take the full backup level=0 on the same directory with different formant name but location is same.
    can i take full backup level 0 and incremental backup level 1 in the same directory with the different format name.
    for exp:
    allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
    i allocate these three channel for incremental level 1 backup;
    the backup is done successfully without any error.
    after that i have change
    allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
    allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
    allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
    backup  database incremental level 0
    after doing the above changes it get the error. with the channel location.
    i have to schedule daily incremental backup level 1 and weekly full backup level 0.
    plz suggest me i have to take incremental 1 and full incremental level 0 backup on seperate directory for different format name.
    regards
    pritesh ranjan

  • Ebs r12 cloning using rman online backup

    dear all,
                 how are you guys? i have ebs r12  on multi node and i want to clone db tier and apps tier using rman online backup,can  anybody provide me the detail steps of cloning ebs(db tier and appstier ) using rman online backup and  directory structure on source and target database is also different.your help highly appreciated thanks in advance.
    regards.

    Hi,
    You cannot use RMAN to clone the Apps tier of the EBS and you may use RMAN only on the DB tier. For a complete backup, as mentioned by Hemant K Chitale, you will have to use the rapid clone utility.
    To perform a rapid clone using RMAN there are plenty of step by step instructions in google which may guide in addition to support.oracle.com, Let me google that for you
    Thanks &
    Best Regards,

  • 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.

  • 11g RMAN UNDO backup optimization

    Hi all?
    I have tested 11g RMAN UNDO backup optimization
    1st I fill the undo tablespace by sql manipulations and not commiting
    2nd backed undo_ts up by RMAN (size 24m)
    3rd I made a commit
    Then backed undo tablespace again but backup_size didn’t change     (24m)
    Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
    Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
    The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
    according to 11g undo optimization it had to
    SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
    SUM(BYTES)
    13172736
    SQL> begin
    for i in 1..100000 loop
    insert into testundo values(i);
    end loop;
    end;
    2 3 4 5 6
    PL/SQL procedure successfully completed.
    SQL> SQL> update testundo set
    id=2 where id>0;
    2
    update testundo set
    ERROR at line 1:
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
    SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
    SUM(BYTES)RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    10 Full *24.54M* DISK 00:00:04 10-JUN-10
    BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
    List of Datafiles in backup set 10
    File LV Type Ckp SCN Ckp Time Name
    6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    SQL> commit;
    Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    11 Full *24.54M* DISK 00:00:02 10-JUN-10
    BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
    Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
    List of Datafiles in backup set 11
    File LV Type Ckp SCN Ckp Time Name
    6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    SQL> alter system archive log current;
    System altered.
    SQL> commit;
    Commit complete.
    SQL> select count(*) from testundo;
    COUNT(*)
    100000
    SQL> delete from testundo;
    100000 rows deleted.
    SQL> commit;
    Commit complete.
    SQL> insert into testundo values(1);
    1 row created.
    SQL> commit;
    Commit complete.
    SQL> alter system flush buffer_cache;
    System altered.RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    13 Full *11.03M* DISK 00:00:01 10-JUN-10
    BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
    List of Datafiles in backup set 13
    File LV Type Ckp SCN Ckp Time Name
    6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    RMAN>
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 393375744 bytes
    Fixed Size 1300156 bytes
    Variable Size 352323908 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 6197248 bytes
    Database mounted.
    Database opened.
    SQL> RMAN> backup datafile 6;
    RMAN> list backup of datafile 6;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    14 Full *600.00K* DISK 00:00:02 10-JUN-10
    BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
    Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
    List of Datafiles in backup set 14
    File LV Type Ckp SCN Ckp Time Name
    6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
    Thanks in advance
    Turkel

    Hi Turkel,
    The space used for undo is also related to the undo retention setting.
    As it seems you do a test update and proceed with backups on:
    - 14:24:37 (-> 25M)
    - 14:25:41 (-> 25M)
    - 14:33:59 (-> 11M)
    - 15:28:43 (-> 600K)
    The first two backups probably are still within the undo retention period for the update.
    The third backup shows a partly empty undo (is your setting 900?).
    The last falls outside the retention period for the update resulting in the small backup size.
    Regards,
    Tycho

  • Restore a single tablespace from full backup erroring out

    Hi,
    I have backed up the full database using RMAN:
    $ rman catalog rman/rman@catdb target /
    RMAN> run {
    backup as compressed backupset
    format '<Full Path>/databkp/DATA_%d_%s_%p'
    database
    plus archivelog format '<Full Path>/arcbkp/ARC_%d_%s_%p';
    Backup was successful.
    Now dropped the tablespaces:
    SQL> alter tablespace rtestusr offline;
    SQL> drop tablespace RTESTUSR including contents and datafiles;
    Now trying to restore the tablespace RTESTUSR
    $ rman catalog rman/rman@catdb target /
    RMAN> restore tablespace rtestusr;
    Starting restore at 25-FEB-11
    starting full resync of recovery catalog
    full resync complete
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2011 14:28:47
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
    RMAN-06019: could not translate tablespace name "RTESTUSR"
    Also performed the Tablespace Point-in-time recovery:
    RMAN> run {
    2> set until time "to_date('2011-02-25:12:44:00','yyyy-mm-dd:hh24:mi:ss')";
    3> restore tablespace RTESTUSR;
    4> }
    executing command: SET until clause
    Starting restore at 25-FEB-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=46 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=45 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=44 devtype=DISK
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00006 to /dev2db/rmantst/db/oradata/rtest/rtestusr01.dbf
    channel ORA_DISK_1: reading from backup piece /dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1 tag=TAG20110225T114341
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2011 15:07:42
    ORA-19654: must use backup control file to switch file incarnations
    Please help.
    Thanks in advance.
    Regards,
    Bikram

    I think you misunderstand some concepts.
    1) drop tablespace RTESTUSR including contents and datafiles;
    is a valid command, it removes the named tablespace from the database. There's nothing wrong with the database (although it may be a logical (human) error). Restore/recovery is used to repair media failures. RMAN is right: 'RMAN-06019: could not translate tablespace name "RTESTUSR"', since there's no such tablespace in the actual database, the restore/recover process fails.
    2) Unfortunately you hide your database version. Up to 10gR2 tablespace point-in-time recovery cannot be used to recover dropped tablespaces, in 11gR1 and higher it's possible.
    And - TSPITR - requires a little bit more than 'set until ...'. Refer to the doumentation for your unknown database version.
    Werner

  • Creating Standby From RMAN Compressed backup taken on Primary ....

    I am creating a Standby from RMAN Compressed backup taken on Primary.
    On Primary, I have taken Compressed backup as follows:
    RMAN> run
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    allocate channel c3 type disk;
    BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG format '/dboracle/orbit_pr_bkp/primary_%U';
    backup current controlfile for standby format '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
    oracle@apl06635orbvu1:/dboracle/orbit_pr_bkp>ls -ltr
    total 51652
    -rw-r----- 1 oracle dba 11972608 Jan 7 13:45 primary_0tm1h32n_1_1
    -rw-r----- 1 oracle dba 15762432 Jan 7 13:45 primary_0sm1h32n_1_1
    -rw-r----- 1 oracle dba 16785920 Jan 7 13:45 primary_0rm1h32n_1_1
    -rw-r----- 1 oracle dba 1088000 Jan 7 13:45 primary_0um1h32v_1_1
    -rw-r----- 1 oracle dba 32768 Jan 7 13:45 primary_12m1h33r_1_1
    -rw-r----- 1 oracle dba 7143424 Jan 7 13:47 primary_cntl.bkp
    On Standby, I restored the control file as below:
    RMAN> restore standby controlfile from '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
    Starting restore at 10-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    output filename=/dboracle/orbit_dr/oradata/ORBIT_DR/controlfile/o1_mf_6lo6nwfr_.ctl
    output filename=/dboracle/orbit_dr/flash_recovery_area/ORBIT_DR/controlfile/o1_mf_6lo6nwky_.ctl
    Finished restore at 10-JAN-11
    But, When I am trying to restore the datafiles, RMAN is throwing error:
    RMAN> run {
    allocate channel d1 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
    allocate channel d2 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
    restore database;
    2> 3> 4> 5>
    released channel: ORA_DISK_1
    allocated channel: d1
    channel d1: sid=155 devtype=DISK
    allocated channel: d2
    channel d2: sid=151 devtype=DISK
    Starting restore at 10-JAN-11
    released channel: d1
    released channel: d2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 01/10/2011 05:38:56
    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
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    What would be the correct RMAN command?
    Regards, Anirban

    After your RESTORE the (standby) controlfile, you must MOUNT the database instance with "ALTER DATABASE MOUNT".
    You can also then query the controlfile with a "LIST BACKUP" or "LIST BACKUP SUMMARY" in RMAN to see if the deseired backups have been cataloged in the controlfile.
    Don't specify the format for the ALLOCATE CHANNEL when you RESTORE DATABASE. In fact, you don't need to ALLOCATE CHANNEL at all when the device type is the default value of DISK if your are on 10gR2 or above.
    Hemant K Chitale

  • 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

  • Oracle Secure Backup error: 'No such file or directory'

    Hi,
    could you help me to fix the following issue?
    RMAN> run {   ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=C:\windows\
    system32\orasbt.dll' ; backup database format 'CF_%d_%T_s%sp%pt%t'; }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: SID=8 device type=SBT_TAPE
    channel c1: Oracle Secure BackupStarting backup at 26-OCT-09
    channel c1: starting full datafile backup set
    channel c1: specifying datafile(s) in backup set
    input datafile file number=00001 name=C:\APP\AIME\ORADATA\ORCL\SYSTEM01.DBF
    input datafile file number=00002 name=C:\APP\AIME\ORADATA\ORCL\SYSAUX01.DBF
    input datafile file number=00003 name=C:\APP\AIME\ORADATA\ORCL\UNDOTBS01.DBF
    input datafile file number=00004 name=C:\APP\AIME\ORADATA\ORCL\USERS01.DBF
    input datafile file number=00005 name=C:\APP\AIME\PRODUCT\11.2.0\DBHOME_1\DATABA
    SE\TBS_5.F
    channel c1: starting piece 1 at 26-OCT-09
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on c1 channel at 10/26/2009 00:20:54
    ORA-19506: failed to create sequential file, name="CF_ORCL_20091026_s10p1t701223
    652", parms=""
    ORA-27028: skgfqcre: sbtbackup returned error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_cat_query: Query for piece CF_ORCL_20091026_s10p1t701223652 failed.
    (Oracle Secure Backup error: 'No such file or directory').
    Thanks,
    jun

    You can work entirely in Xcode by using the command-line tool template in C. Xcode > File > New > Project > Command-Line Tool > Next > Language: C > Next > Create.
    If you do want to work on the command line, you may as well just use the "clang" program instead. The "gcc" tool is just a compatibility tool for existing scripts that are expecting the actual "gcc" program. Apple hasn't used the real "gcc" for years. (Read up on the GPLv3 for more information.)
    The gcc/clang arguments are the same. The "-c" flag instructs the compiler to only compile a single .c file into a .o object file. It won't create an executable. If you are only compiling a single source file, just omit the "-c" flag and the compiler will create an executable named "a.out" that you can run by typing "./a.out". You can specify "-o <executable name>" if you want to specify a name. Once you get more than a handful of source files, using the terminal starts to become a hassle. At that point, you definitely want to start using Xcode.
    I'm not sure why you would try to compile "helloworlddot1.c" and then get an error message about "filename.c". Something else is wrong.
    If you are working in the Terminal, it is easiest to use the "cd" command to move into the same directory as your source files. Then you don't have to keep typing the full path.
    It is hard to say what the "best" community is. There are many to choose from.

  • 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.

Maybe you are looking for