RMAN backup on a RAC env

We have a 2 camera database Oracle Enterprise Linux version 11204 node.

Please can you advice as to why my RMAN backup, ongoing assessment of the default value, so as ive defined the location of backup as below?

RMAN > show channel;

RMAN settings for database with db_unique_name GEOHUBPR are:

CONFIGURE CHANNEL DEVICE TYPE DISK CONNECT 1 ' *';

CONFIGURE THE CHANNEL 2 DEVICE TYPE DISK CONNECT ' *';

CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / mnt/san/odanfs/rman_backup/%D_%U.bak';

run

{

SAVE as COMPRESSED BACKUPSET TAG 'geohubpr_L0_db' SIZE EXTRA 0 DATABASE;

BACKUP to COMPRESSED BACKUPSET TAG 'geohubpr_L0_arc' ARCHIVELOG ALL NOT SAVED;

}

Kind regards

There is a syntax error, you must add the word "database":

RMAN > backup incremental level 1 CUMULATIVE as Tablet backupset TAG 'geohubpr_L1_db' format ' / mnt/san/odanfs/rman_backup/%D_%U.bak' DATABASE;

Also include the archives in your backup

Concerning

Tags: Database

Similar Questions

  • RMAN channels on a RAC env

    Hello

    We have a 2 RAC on Oracle Database Appliance version 11204 Linux Enterprise node.

    I do below, and I get an error. Please advice.

    RMAN > CONFIGURE DEVICE TYPE DISK PARALLELISM 2 TYPE backup BACKUPSET.

    new RMAN configuration settings:

    SET UP THE DEVICE TYPE DISK PARALLELISM 2 TYPE OF BACKUP BACKUPSET.

    new RMAN configuration settings are stored successfully

    RMAN > set UP CHANNEL 1 DEVICE TYPE DISK CONNECT 'sys/***@rac1 ';

    new RMAN configuration settings:

    CONFIGURE THE CHANNEL 2 DEVICE TYPE DISK CONNECT ' *';

    new RMAN configuration settings are stored successfully

    RMAN > set UP CHANNEL 2 DEVICE TYPE DISK CONNECT 'sys/***@rac2 ';

    new RMAN configuration settings:

    CONFIGURE THE CHANNEL 2 DEVICE TYPE DISK CONNECT ' *';

    new RMAN configuration settings are stored successfully

    RMAN > delete the backup.

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the delete command at the 10:45:44 14/05/2014

    RMAN-12001: could not open the channel ORA_DISK_1

    RMAN-10008: could not create context channel

    RMAN-10003: unable to connect to the target database

    ORA-12154: TNS: could not resolve the connect identifier specified

    It seems the problem is the connection of the AMT:

    AMT: could not resolve the connect identifier specified

    Could you try a tnsping and sqlplus using the same connection that you operate on RMAN?

    I've used this in a CAR without problem:

    Configure default device the disk type;

    Configure channel 1 device type disk connect ' sys/***'@rac1;

    Configure the switch type 2 disc connect 'sys/***'@rac2 ';

    Configure the switch type 3 disk connect 'sys/***'@rac3 ';

    Run {}

    backup incremental level 0 as compressed backupset database more archivelog delete all entries;

    }

    Concerning

  • RAC RMAN backup

    Hello

    DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.

    -OCR
    -Voting record
    -Talespaces Snapshot
    -Archivelog (hourly)
    -Backup incremental level 0 (SUNDAY)
    -backup incremental level 1 (Mon - Sat)
    -Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)

    Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?

    Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?
    [root@db01~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  2.9G  814M  79% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  225M  3.5G   6% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  379M  3.4G  11% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  8.7G  2.6G  78% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
/dev/mapper/36001ec9000d5ea810000061349015d98
                      1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  887M  2.9G  24% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  261M  3.5G   7% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  355M  3.4G  10% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  6.5G  4.8G  58% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /

Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: F1 (DBID=1245145263)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup

level0 ()
run {
  allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
  allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
  backup incremental level 0 tag = weeklyfull database channel c1 
  plus archivelog tag = ARCH_$TODAY delete all input channel c2;
  release channel c1;
  release channel c2;
}

run {
  allocate channel c1 type disk;
  delete noprompt obsolete;
  release channel c1;
}
    Bundle of thanks.

    Kind regards

    Published by: 910385 on February 24, 2012 03:00

    Hi 910385,
    The error on the node db02

    ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

    is caused by your installation.
    You have a /rman of mount point visible only on the node db01.
    The controlfile autobackup setting triggers the creation of a backup of the controlfile:
    -during the rman backup (this seems to work only on db01)
    -in the case of a structural change in the database (eg. Adding a data file).
    Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
    You must change the configuration and put the backup on a shared disk that is seen by the two systems.
    Strangely, you have a shared file system:

    10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

    Better would be to make a second for rman...
    Kind regards
    Tycho

  • How to use backups RMAN to restore a RAC database to single instance on another host?

    How to use backups Rman to restore a RAC database to single instance on another host?

    I tried to copy these inline for you:

    ------------




    Backups RMAN disk HowTo restore database RAC to single Instance on another node (Doc ID 415579.1)

    Down

  • RMAN backup and restore into Production KEEPS RAC and DATA

    Hi gurus of the Oracle

    We need the expert advice for tune and cross check the RMAN Script for Production environment below below

    Please suggest any corrections or comments on below mention scripts which will be executed on RAC and Production DATA GUARD environment

    LINUX RHEL 5.5 64-bit
    ORACLE GRID Infrastructure R2 Version 11.2.0.3.0 (we use ASM Cluster File system)
    ORACLE11g R2 Version 11.2.0.3.0

    We planned for basically rman backup drive using control file target instead of recovery catalog database

    We will have Data Guard Setup between 2 remote sites of database and two remote sites have running the local 2-node RAC database

    =========================RMAN_Full_Backup.sh=========================================================================
    #! / bin/bash
    . /Home/orarac/.bash_profile
    logloc = 'date' + rman_backup_lvl0_orcldb_ %m %y hour %M %S %d ".log
    # Start rman backup
    Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
    run
    {
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
    include current controlfile
    tag 'datafile_full ';
    }

    run
    {
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    overlap archivelog all;
    SQL 'alter system archive log current';
    backup ARCHIVELOG all delete them all input FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_ARCHIVELOG_%D_%M_%Y'
    tag 'archivelog_full ';
    }
    cross-checking of backup;
    delete noprompt obsolete;
    Save the list of database;
    EXIT;
    EXPRESSIONS OF FOLKLORE
    ==================================================================================================
    =========================================RMAN_Inc_Backup.sh ===========================================
    #! / bin/bash
    . /Home/orarac/.bash_profile
    logloc = 'date' + rman_backup_lvl1_orcldb_ %m %y hour %M %S %d ".log
    # Start rman backup
    # use only the following line if this script is run via the root CRON
    Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF

    Run {}
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    database backup incremental level 1 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL1_%D_%M_%Y'
    include current controlfile
    tag 'datafile_Incr ';
    }
    Run {}
    allocate channels ch1 type disk maxpiecesize = 1024 M;
    allocate channel ch2 type disk maxpiecesize = 1024M;
    overlap archivelog all;
    SQL 'alter system archive log current';
    backup ARCHIVELOG all delete them all input FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_ARCHIVELOG_%D_%M_%Y'
    tag 'archivelog_full ';
    }
    cross-checking of backup;
    delete noprompt obsolete;
    backup from the list;
    EXIT;
    EXPRESSIONS OF FOLKLORE
    -bash - $3.2
    ====================================================================================================
    ===================================RMAN_DB_Restore.sh====================================================
    -bash-3, $ 2 cat /home/orarac/RMAN_Scripts/RMAN_DB_Restore.sh
    #! / bin/bash
    . /Home/orarac/.bash_profile
    logloc = 'date' + rman_restore_orcldb_ %m %y hour %M %S %d ".log
    # use only the following line if this script is run via the root CRON
    Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
    Run {}
    BOOTABLE MEDIA FORCE;
    RESTORE THE DATABASE;
    RECOVER THE DATABASE;
    ALTER DATABASE OPEN;
    }
    EXIT;
    EXPRESSIONS OF FOLKLORE
    ====================================================================================================

    Concerning
    Hitgon

    Thank you mseberg

    This command is the full backup or a backup of level 0?

    full backup as compressed backupset
    data include current controlfile more archivelog deletion entry;

    We use command below for the full backup of database.
    database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
    include current controlfile
    tag 'datafile_full ';

    We use the command below to the increment backup
    database backup incremental level 1 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL1_%D_%M_%Y'
    include current controlfile
    tag 'datafile_Incr ';

    What is the different when we use
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

    or

    full backup as backupset compressed database include controlfile current more archivelog delete all input;

    Concerning
    Hitgon

  • Copy the RAC ASM RMAN backups

    Hi, I have a database (RHEL 5.8) RAC 2 nodes with shared ASM storage. RMAN makes daily backups on this ASM storage too. How could copy backups of the ASM to another place? I use version 10 gr 2 db, and there is no 'cp' command in asmcmd.

    How could copy backups of the ASM to another place? I use version 10 gr 2 db, and there is no 'cp' command in asmcmd.

    You can use RMAN to do it.

    Use the command

    RMAN>  backup backupset from ... format '' ;

    Example here:
    Re: Move ASM backups to disks

    Using the tag:
    Re: RMAN to the ASM and network file system

    Published by: Levi Pereira on April 4, 2013 11:39

  • Consistent test 'copy' of RMAN backup outside the ASM (RAC)

    Hello!
    We create consistent backup RMAN in our CARS (ASM with FRA) environment.
    Safeguard measures looks like:
    alter system set cluster_database=false scope=spfile sid='HAC4';
    
srvctl stop database -d HAC
    Then we begin the RMAN backup script as (database is closed to the ground before):
    run {
    
startup mount;
    
allocate channel t1 type disk format '/u01/rman_backup/HAC/cold_backup/HAC_%U';
    
allocate channel t2 type disk format '/u01/rman_backup/HAC/cold_backup/HAC_%U';
    
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/rman_backup/HAC/cold_backup/HAC_%F_ctl';
    
backup as copy database include current controlfile;
    
}
    After backup, we realize:
    alter system set cluster_database=true scope=spfile sid='HAC4';
    
shutdown immediate;
    and later
    srvctl start database -d HAC
    This backup backup files are placed on the area of local disk accessed by noeud4, where HAC4 SID is on.
    We transfer the backup files to tape on an hourly basis...

    Now, we want to test this backup.
    Scenario:
    Because we have consistent backup, we think we can restore her (from files on this disc) and him ALONE!
    Our problem is that while restoration is the use of the DSO files, so we're not sure is our backup.

    So, how to prevent the RMAN restore/recovery process of using any ASM file - just to use our consistent backup data?

    Please a few example script for this...

    Our config:
    Oracle 10gR2.0.4 PS3 (NCPS, ASM database),
    Linux Rhel IA64 5.3 on 'raw devices' (no raw disks)

    THX
    Damir

    Hello

    What I realized is that you want to test the image copy backup you took earlier and test this to restore the database, as it is.

    Now, if I see your script, it shows that you have restored control file and then you tried to recover the database.

    But when you make the copy of the image of the database, and you want to restore, then you have to try to restore the database first. I don't see any "restore order" in your script.

    RMAN > restore database from tag = "";

    Firstly, this will restore the data files.

    Then, use

    RMAN > restore database;

    Then, open the database.

    Kind regards
    Vermorel

  • content managed rman backup crushing and selection procedure of the tape media

    Hello Experts.

    I have a question about the backupset rman tape media manage tape of the osb.

    [ENV]

    Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

    1 Appendix backup on OS crontab

    -Each backup full day at 00:00 AM

    2 rman view all:

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    using the control file of the target instead of recovery catalog database

    RMAN settings for database with db_unique_name TESTDW are:

    CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

    CONFIGURE BACKUP OPTIMIZATION # by default

    CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

    SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    3 rman backup scirpts

    Run {}

    allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

    allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

    allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

    Backup section size 900g database;

    output channel c01;

    output channel c02;

    output channel c03;

    output channel c04;

    }

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

    and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

    So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

    Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

    Why OSB does not have the expired status of rman content on tape media?

    -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

    Q2 > selection procedure for the tape media all backup rman

    Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

    Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

    If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

    Advanced thanks.

    If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

    the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

    Yes.

    I use the catalog of recovery on a different database and backup script has catalog db connection string.

    And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

    Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

    After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

    Kind regards

    Mitja

  • Restore the RMAN backup on another server

    Hello

    ENV: Oracle 10 g 2 64 bit, RHEL 5.8 64 bit on ASM, Database size = ~ 1.3 to

    Backup RMAN of PROD will FRA and then backed up to tape. I have limited access to the PROD because it is maintained by 3rd party.

    My client is planning to move this database on their own datacenter (from the 3rd party data center). For test purposes, I asked DBA of 3rd party to provide us with an export of drawings required data pump. Export takes about 8 hours, and the import takes the same time to the new location. To copy the files exported to new locations takes another few hours (over the network). The total size of the dump file is around 500 GB. Thus, a whole cycle of Export-Import-copy takes about ~ 20 + Hrs.

    I want to try another option to reduce the time required for the updating of the database of PROD and which is "use RMAN backup of PROD ' and restore it on the data center server. RMAN full backup takes ~ 4hrs PROD and the restoration should be at the same time (new server has better and faster HW, storage with a SSD). I found this thread very useful on the Oracle Forms on this topic:

    Restore backup RMAN on another server

    This thread contains very good example for a restoration of database on the file system.

    I have a bit of confusion because my database uses ASM. The default location of the backups in PROD is FRA (on ASM == > db_recovery_file_dest = + FRA ). If I understand correctly, the RMAN backup must be in the same place where he was on the PROD Server - i.e. the diskgroup FRA.

    If I get a copy of the part 3 RMAN backup, how would I copy on FRA?

    OR can / should I just change the init parameter "db_recovery_file_dest" on the new server to point to the file system directory where the backup (say "/ ora_backup") and RMAN will pick up and restore the database?

    Please advise!

    Best regards

    You can restore the backup files to any location, then you must configure the channel using the "CONFIGURE CHANNEL device type disk format 'new location ';

    This thread will help

    Restore from a different location from the original location of RMAN backup

  • How to find the total size of the RMAN backup files?

    Hello

    env: Oracle 10 g 2, RHEL 64 bit

    My customer has a production database where rman backups are taken: level 0 backup every Sunday and level 1, Monday to Saturday.

    I have very limited access to this database of production because it is managed by a third party, and they don't give me my required info (don't know why). I don't have access to the rman repository. To connect to the database that I have to connect to a staging server, then connect to the database server. I have no access to Enterprise Manager. So in short, my access is limited. I want to collect information on the total size of the files of rman backup - both for level 1 to level 0 backups separately. I understand that this info can be retrieved from the rman repository. Is there a dictionary views/tables of data where I can get this info?

    Best regards

    Hello

    Have you tried to check forum this:https://forums.oracle.com/thread/1097939

    HTH

  • Error of RMAN backup full

    Hi all

    I take a daily ful backup DB backup directly on the Strip.

    Due to a problem yesterday I deleted 2 days old files to archive my server.
    Today, I got following error message in my log RMAN backup.

    I'm surprised, how is it, RMAN are looking for an old file to archive, when I take a full backup.

    Can someone answer me above concern

    My version of DB is 11.2.0.3
    OPERATING SYSTEM: AIX 6.1

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the backup command to the 2013/05/29 04:28:54
    RMAN-06059: expected found archived newspaper, loss of archived newspaper compromised recoverability
    ORA-19625: error identification of file /prdarch/prdarch1/PALLMO_83504_696657779.arc
    ORA-27037: unable to get file status
    IBM AIX RISC System/6000 error: 2: a file or a directory in the path name does not exist.
    Additional information: 3

    The script that is used for the backup:
    run
    {
    allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
    SQL 'alter system archive log current';
    overlap archivelog all;
    backup
    filesperset 5
    (database) format "df_ % %%p s_ t_";
    SQL 'alter system archive log current';
    ARCHIVELOG backup all the format "af_ % %%p s_ t_";
    output channel t1;
    }


    Thanks in advnace

    any backup archivelog

    The BACKUP ARCHIVELOG command is independent of the BACKUP DATABASE command.
    This command waits all archivelogs known are available and can be backed up. In fact, your backup logs should show the same old archivelogs (most recent) being backed up every day!

    If you use non-RMAN commands to purge the archivelogs, RMAN knows not the archivelogs aren't available. He'll wait although they are present. You must run

    CROSSCHECK ARCHIVELOG ALL;
DELETE EXPIRED ARCHIVELOG ALL;

    for RMAN to identify them as having been purged and remove them from its "list of the archivelogs expected."

    If you simply, have BACKUP ARCHIVELOG ALL and not to operate the ARCHIVELOG DELETE of RMAN, how do you maintain the archivelog file system space?

    How long have you been running this backup script? How were you purge archivelogs earlier?

    Hemant K Collette

  • RMAN backup failed

    Hello

    Please help me we have shecduled the rman backup rman, his get failed

    Recovery Manager: Release 10.2.0.4.0 - Production on Sun Mar 18 16:40:18 2012

    Copyright (c) 1982, 2007, Oracle. All rights reserved.

    connected to target database: mmmmm (DBID = 3739042331)

    RMAN > run {}
    2 > allocate channel d1 type 'sbt_tape' MAXOPENFILES 1 parms 'ENV = (TDPO_PROFILE = C:\Program Files\Tivoli\TSM\AgentOBA\tdpo.opt)';
    3 > backup
    4 > extra strength 2 cumulative
    5 > tag friday_level_2
    6 > format 'df_t % t_s %%p s_p ".
    7 > database include current controlfile;
    8 > sql 'alter system switch logfile;
    9 > sql 'alter system archive log current;
    10 > backup
    11 > archivelog all
    12 > entry deleted;
    13 > output channel d1;
    {14 >}
    15 >
    using the control file of the target instead of recovery catalog database
    allocated channel: d1
    channel d1: sid = 535 devtype = SBT_TAPE
    channel d1: for Oracle Data Protection: version 6.3.0.0

    From backup 18 March 12
    channel d1: additional start-up 2 datafile backupset
    channel d1: specifying datafile (s) in backupset
    input datafile fno = name = 00009 E:------. DBF
    input datafile fno = name 00004 = E:------. DBF
    input datafile fno = 00028 name = F:\DBF
    input datafile fno = name 00029 = F:. DBF
    .
    .
    .
    .
    .
    .
    .
    .
    channel d1: starting piece 1 to 18 March 12
    output channel: d1
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on the channel of the d1 at 18/03/2012-16:40:24
    ORA-19502: error on the 'df_t778264820_s9391_p1' file, blockno writing 1 (blocksize = 512)
    ORA-27030: skgfwrt: sbtwrite2 returned error
    ORA-19511: error received from layer media manager, error text:
    ANS0326E (RC41) this node has exceeded the maximum number of mount points.

    Complete recovery manager.


    In a server more

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on the channel of d1 to 18/03/2012-15:25:15
    ORA-19502: error on the file "df_t778260307_s61252_p1", blockno writing 16641 (blocksize = 512)
    ORA-27030: skgfwrt: sbtwrite2 returned error
    ORA-19511: error received from layer media manager, error text:
    ANS0326E (RC41) this node has exceeded the maximum number of mount points.



    Please someone help me...

    Published by: Lingan Poirier on March 18, 2012 16:49

    Hello

    The session will be closed automatically... don't worry about this.

    Who set up the NŒUD on TSM... because it's a NODE parameter.

    On the TSM SERVER

    QUERY NODE  F=D

UPDATE NODE  MAXNUMMP=<#>

    Kind regards
    Levi Pereira

    Published by: Levi Pereira on March 18, 2012 14:32

  • RMAN backup disrupted because of failure

    DB version: 11.2.0.2
    Platform: Sun solaris 5.10

    During the race
    backup database plus archivelog;
    our server got DB decommissioned due to a power failure.

    In the log file, I see that after all the data files are listed as «enter a file datafile = xxx "...»
    We got the message 'done' as
    channel ch00: starting piece 1 at 13-MAR-12
channel ch00: finished piece 1 at 13-MAR-12
    So, this means that a level 0 DB Backup is available. Right?
    It looks like all newspaper Archives are saved, then RMAN successfully has the backup of all data files, while he was trying to backup logs arch created after the full backup, then the power went off. Am I wrong?

    These are the shortcuts out of the log RMAN backup
    Starting backup at 13-MAR-12
current log archived
channel ch00: starting archived log backup set
channel ch00: specifying archived log(s) in backup set
input archived log thread=1 sequence=5104 RECID=2944 STAMP=777804213
input archived log thread=1 sequence=5105 RECID=2947 STAMP=777806830
input archived log thread=1 sequence=5106 RECID=2950 STAMP=777809240
.
.
.
.
.

channel ch00: starting piece 1 at 13-MAR-12
channel ch00: finished piece 1 at 13-MAR-12
piece handle=rman_ORCL_LEVEL0_FULL_5an5pu3m_1_1_777844854.rmbk tag=ORCL1_LEVEL0_FULL comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 00:15:45
channel ch00: deleting archived log(s)
archived log file name=+DG_ARCH/orcl_arch/orcl_5104_1_769896013.arc RECID=2944 STAMP=777804213
archived log file name=+DG_ARCH/orcl_arch/orcl_5105_1_769896013.arc RECID=2947 STAMP=777806830
archived log file name=+DG_ARCH/orcl_arch/orcl_5106_1_769896013.arc RECID=2950 STAMP=777809240
.
.
.
.

Finished backup at 13-MAR-12

Starting backup at 13-MAR-12
channel ch00: starting incremental level 0 datafile backup set
channel ch00: specifying datafile(s) in backup set
input datafile file number=00006 name=+DG1/gridxxx/datafile/data_01_01.dbf
input datafile file number=00010 name=+DG1/gridxxx/datafile/data_01_04.dbf
input datafile file number=00013 name=+DG1/gridxxx/datafile/data_01_07.dbf
input datafile file number=00025 name=+DG3/gridxxx/datafile/data_03_05.dbf
input datafile file number=00028 name=+DG4/gridxxx/datafile/data_04_01.dbf
.
.
.
.
.
input datafile file number=00031 name=+DG4/gridxxx/datafile/data_04_04.dbf
channel ch00: starting piece 1 at 13-MAR-12
channel ch00: finished piece 1 at 13-MAR-12
piece handle=rman_ORCL_LEVEL0_FULL_5bn5pv1l_1_1_777845813.rmbk tag=ORCL1_LEVEL0_FULL comment=API Version 2.0,MMS Version 5.0.0.0
channel ch00: backup set complete, elapsed time: 04:29:35
Finished backup at 13-MAR-12

Starting backup at 13-MAR-12
current log archived
channel ch00: starting archived log backup set
channel ch00: specifying archived log(s) in backup set
input archived log thread=1 sequence=5132 RECID=3008 STAMP=777845828
input archived log thread=1 sequence=5133 RECID=3011 STAMP=777846764
input archived log thread=1 sequence=5134 RECID=3014 STAMP=777847595
input archived log thread=2 sequence=2595 RECID=3007 STAMP=777845618
input archived log thread=2 sequence=2596 RECID=3009 STAMP=777845834
input archived log thread=2 sequence=2597 RECID=3010 STAMP=777846245
input archived log thread=2 sequence=2598 RECID=3012 STAMP=777847027
input archived log thread=2 sequence=2599 RECID=3013 STAMP=777847590
channel ch00: starting piece 1 at 13-MAR-12

---- Power outage at this point

    Hello

    So, this means that a level 0 DB Backup is available. Right?

    Yes you are right that this db of level 0 backup is available.

    It looks like all newspaper Archives are saved, then RMAN successfully has the backup of all data files, while he was trying to backup logs arch created after the full backup, then the power went off. Am I wrong?

    It seems that all archive logs are backed up, all the data files are saved. Archive logs generated during the full backup had begun, but it is not finished.

    Query the status column in V$ RMAN_BACKUP_JOB_DETAILS views to see accurate results.

    Talip Hakan Öztürk
    http://taliphakanozturken.WordPress.com/

  • Car cloning + asm_cold RMAN backup

    Hello

    I have a db v11.2 RAC, that uses asm and saved using rman (backup, back up to asm diskgroup d cold).

    is there any document on how to clone this db on the same cluster or remote cluster?
    If I clone on the same cluster so I guess I should give it a new name too...


    pouvez cloning change db characterset as well?

    Edited by: user9198889 January 6, 2011 08:49

    Hopes of the documents below will help,

    Need to Document/steps of cloning RAC 11 g.
    http://download.Oracle.com/docs/CD/E14072_01/RAC.112/e10718/clonerac.htm
    http://blogs.Oracle.com/AlejandroVargas/gems/RMANDUPDBPRACTICE.PDF

    Thank you

  • RMAN backup control file

    HII I am working on oracle 10g 10.2.0.4.0 on solaris 10 have an asm and rac configuration (2 node rac).

    I only have a single control file--+DATA_DG1/ftssdb/controlfile/current.270.664476369

    I'm back up these files to control with rman

    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / backup/rman_node1/%F';



    c 31850833-20100909-00 is one supported by piece of control file.

    now, suddenly, a system of administration deleted this file control... How can I recover my database using rman backup?

    RMAN > SET 3386862614 DBID
    RMAN > RUN {
    RESTORE AUTOMATIC BACKUP CONTROLFILE;
    }
    or
    RMAN > SET 3386862614 DBID
    RMAN > RUN {
    CONTROLFILE AUTOBACKUP FORMAT SET
    FOR DEVICE TYPE DISK TO ' / backup/rman_node1/%F';
    RESTORE AUTOMATIC BACKUP CONTROLFILE;
    }

    check out the link:
    http://arjudba.blogspot.com/2008/05/How-to-restore-controlfile-from-backup.html

    Published by: rajeysh on Sep 9, 2010 16:37

Maybe you are looking for

  • Disable the notification of annoying mail?

    Every so often, AOL Mail displays a message that my AOL password for one of my accounts has not been entered correctly. This is not true, as I am able to access the e-mail in all my accounts. I think it is a question of AOL, as has happened on more t

  • Why have I not hyperlink adware joining the secure Web pages

    in the last two days, I noticed that there are hyperlinks on certain keywords and a whole bunch of Web sites where they were before and should not be never. they are all ads for something whether it's clothes or decrease your invoice of electricity o

  • AutoComplete doesn't work does not even after troubleshooting

    AutoComplete in my navigation bar has been broken for a while. I tried all the suggestions on the firefox help site, but it was not fixed. I am currently in firefox 3.6 since I always use a mac 10.4.11, I don't think I can update beyond this version.

  • DV6-6b51ea: the problematic driver, Universal serial bus installation does not

    Hi, is it possible to also help me find the right drivers? This is the id of the hardware: Universal Serial Bus (usb) controller: PCI\VEN_1033 & DEV_0194 & SUBSYS_1658103C & REV_04 PCI\VEN_1033 & DEV_0194 & SUBSYS_1658103C PCI\VEN_1033 & DEV_0194 & C

  • iPhone battery life 6.  I'm the only one who thinks she's affected

    MY iPhone before big 6 is now requiring a more frequent battery recharging.  Since the latest iOS update, I'm sure it's eating power more quickly. APple overload the iPad2 with each update.  They do the same thing with the 6?