Standby database - RMAN level 0 - Recovery catalog - OEM.

We have configured rman level 0 backup from standby database on OEM. Job is running fine, but rman is not getting connected to recovery catalog. RMAN is connecting to target control file instead of recovery catalog. I understand we need to have DG broker configured for primary and standby for RMAN to connect recovery catalog if you run from OEM. We have configured the DG broker also. DG broker configuration is woriing fine. but Still Standby is not connecting the rman recovery catalog database.
Can anyone tell me what i should check.

Catalog database is same for primary and standby. It is not working for both the version. What are all the basic check i need to do to debug the issue.
THIS IS LOG FROM OEM it is not connecting to target. instead of it is connecting to target control file.
Recovery Manager: Release 11.2.0.3.0 - Production on Thu Sep 6 22:40:28 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: CAAPRD1 (DBID=524360237, not open)
using target database control file instead of recovery catalog
RMAN>
echo set on
RMAN> run {
2> allocate channel oem_backup_disk1 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
3> allocate channel oem_backup_disk2 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
4> allocate channel oem_backup_disk3 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
5> allocate channel oem_backup_disk4 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
6> allocate channel oem_backup_disk5 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
7> allocate channel oem_backup_disk6 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
8> allocate channel oem_backup_disk7 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAASTB1/level0/%U';
9> allocate channel oem_backup_disk8 type disk MAXOPENFILES 1 format '/local/oracle/orabackups/CAATB1/level0/%U';
10> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_DATA' database;
11> backup FILESPERSET 1 as BACKUPSET tag 'DAILY_LEVL0_ARCH' archivelog all not backed up;
12> release channel oem_backup_disk1;
13> release channel oem_backup_disk2;
14> release channel oem_backup_disk3;
15> release channel oem_backup_disk4;
16> release channel oem_backup_disk5;
17> release channel oem_backup_disk6;
18> release channel oem_backup_disk7;
19> release channel oem_backup_disk8;
20> }

Similar Messages

  • RMAN-20001: target database not found in recovery catalog

    I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
    RMAN> startup nomount;
    Oracle instance started
    Total System Global Area 209715200 bytes
    Fixed Size 1272864 bytes
    Variable Size 155190240 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 2920448 bytes
    RMAN> restore controlfile from autobackup;
    Starting restore at 08-SEP-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    recovery area destination: /u02/flash_recovery
    database name (or database unique name) used for search: TEST
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=/u02/control_files/TEST/control02.ctl
    output filename=/u03/oradata/TEST/control03.ctl
    Finished restore at 08-SEP-10
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
    I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.

    Hi BelMan,
    Here is output
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    56869 Full 11.20M DISK 00:00:00 08-SEP-10
    BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
    Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
    Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    56993 Full 11.20M DISK 00:00:00 08-SEP-10
    BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
    Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
    Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10

  • Connecting rman and creating recovery catalog

    I'm using oracle8i with Window/Nt
    i have two database U10 and U20.
    Using recovery manager, target db is U10 and recovery catalog of U10 is saved in U20.
    i followed method in oracle8i manual(Rman Part)
    when i attempt to connect rman, following message bothers me..
    C:\WINDOWS>RMAN CATALOG RMAN/RMAN@U20
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT.
    .INTO returns too many rows
    RMAN-06097: text of failing SQL statement: select user into :b1 from dual
    RMAN-06099: error occurred in source file: krmk.pc, line: 3842
    and when i attempt to create recovery catalog, i got a bunch of message
    RMAN> CREATE CATALOG TABLESPACE "RCVCAT"
    RMAN-06099: error occurred in source file: krmk.pc, line: 6549
    RMAN-06097: text of failing SQL statement: CREATE TABLE db
    db_key NUMBER NOT NULL, -- sequence generated primary key
    db_id NUMBER NOT NULL, -- kccfhdbi from controlfile
    -- updatable columns
    curr_dbinc_key NUMBER, -- current incarnation
    CONSTRAINT db_p PRIMARY KEY (db_key),
    CONSTRAINT db_u1 UNIQUE(db_id) -- ensure that db_id is unique
    tablespace "RCVCAT"
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-06433: error installing recovery catalog
    i'm so hectic... plz help me....

    Based on the following errors:
    RMAN-06004: ORACLE error from recovery catalog database: ORA-02112: PCC: SELECT..INTO returns too many rows
    RMAN-06097: text of failing SQL statement: select user into :b1 from dual
    It looks like the table dual has more than 1 row.
    select * from dual;
    What do you get?
    It should look like this:
    D
    X
    1 row selected.
    Your recovery catalog database may have a problem. You may need to start over and recreate the recovery catalog.
    null

  • Standby database is not completing recovery.

    All,
    I applied a PSU to 10.2.0.4 (8576156) patch this afternoon on both the primary and standby oracle_home(s). Upon starting up the standby database, I no longer see the “media recovery waiting” message in the alert log when an archive log is sent from the primary.
    Not sure if I have an issue with the patch or DG is configured or started.
    Perhaps another set of eyes can lead me to an issue I am not seeing.
    The standby database was started as follows:
    alter database RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
    Example alert log message before:
    Sun Sep 13 02:20:39 2009
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[2]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Sun Sep 13 02:20:47 2009
    Media Recovery Waiting for thread 1 sequence 52 (in transit) <<== NOTE
    Sun Sep 13 02:20:47 2009
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 52 Reading mem 0
    Mem# 0: /oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log
    Mem# 1: /oradat2/cwsiqa2/cwsiqa2_sb_redo04_b.log
    Example alert log message after:
    Primary database is in MAXIMUM PERFORMANCE mode
    Tue Sep 15 15:56:27 2009
    RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Tue Sep 15 15:56:27 2009
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    Tue Sep 15 15:57:05 2009
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[5]: Assigned to RFS process 29772
    RFS[5]: Identified database type as 'physical standby'
    Tue Sep 15 16:12:56 2009
    The same messages are listed in v$datagurd_status
    1* select message from v$dataguard_status
    SQL> /
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARC9: Becoming the 'no FAL' ARCH
    ARC9: Becoming the 'no SRL' ARCH
    ARC0: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery starting Real Time Apply
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 28316
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 28318
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 29693
    RFS[3]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 29691
    RFS[4]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[5]: Assigned to RFS process 29772
    RFS[5]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    I also have a “gap” that is not getting resolved.
    SQL> select * from v$archive_gap
    2 /
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 53 53
    SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT
    2* FROM V$ARCHIVED_LOG R, V$LOG L WHERE R.DEST_ID=2 AND L.ARCHIVED='YES'
    SQL> /
    LAST_SEQ_RECD LAST_SEQ_SENT
    54     58
    Any insight would be appreciated.

    Problem has been resolved.

  • Oracle EBS R12 - 11.2.0.2 - Logical Standby Database & RMAN backups

    Hi all,
    I have Oracle EBusiness Suite R12 running on 11.2.0.2. Our organization used to have most of the business in North America, South America and Europe; but now we are also in Australia, China and Indonesia. Previously running large reporting batch jobs and RMAN backups at night time in USA was feasible but now that is beginning to show up as performance issue for some countries.
    I was thinking would it make sense to have a Active Data Guard logical standby database on a separate server in the same US based data center where we have our main servers and use that logical standy database for reporting and RMAN backups. I am especially concerned about RMAN backups. Would I be able to make RMAN backups from the logical standy database and somehow use those to recover our primary database if some issue happens?
    Any thoughts/suggestions?
    Thanks all,

    Active Data Guard only deals with physical standbys. If you are using a logical standby you can always open the database without using Active Data Guard option.
    http://docs.oracle.com/cd/E11882_01/server.112/e25608/rman.htm#sthref846 says that:
    >
    Backups of logical standby databases are not usable at the primary database.

  • Error when trying to recover datafile from standby database to primary

    hi friends,
    getting problem with restoring datafile from backupset taken on standby database to primary database.
    os: windows server 2003
    db: oracle 11gR1(11.1.0.6)
    i've configured standby database on two different hosts.
    host1 - primary (db_uinque_name= prod)
    host2 - standby (db_uniue_name= prodsby)
    I've configure both database with recovery catalog. I take backup on standby database. users' datafile of primary database has been lost.i'm trying to restore from the backupsets taken on standby database.
    with the help of - http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/rman.htm#BAJCEFEG
    on primary
    c:\>rman target sys/password catalog rcat/password
    rman>list backup for db_unique_name prodsby;
    display the backupsets
    rman>restore datafile 4;
    Starting restore at 06-NOV-08
    starting full resync of recovery catalog
    full resync complete
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1051 device type=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/06/2008 12:12:18
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    also use to tag to restore the datafile
    rman>restore datafile 4 from tag='base0_prodsby';
    Starting restore at 06-NOV-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/06/2008 11:27:21
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    i'm getting above errors when try to restore the datafile.
    when i issue the following command.
    BACKUP AS COPY DATAFILE 4 AUXILIARY FORMAT 'C:\app\Administrator\oradata\prod\USERS01.DBF';
    Starting backup at 06-NOV-08
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1068 device type=DISK
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
    DBF
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
    15
    ORA-17628: Oracle error 19505 returned by remote Oracle server
    please friends, try to help me to solve the problem.
    Thanks,
    Vihang

    hi.
    Its not necessary its a otherway around to recover datafile from this backupset and apply archivelogs to make datafile consistent.
    yes, it ain't the right way to restore backup to primary location.
    so how would i connect to standby database with primary and recovery catalog.
    i need to connect to recovery catalog and primary site because i need to restore to primary location and recovery catalog contain all metadata and backupsets related information.
    i also tried the following steps from oracle documentation.
    Connect to the standby database as the target database:
    CONNECT TARGET sys@standby
    You are prompted for a password:
    target database Password: password
    Connect to the primary database as the auxiliary database:
    CONNECT AUXILIARY sys@primary
    You are prompted for a password:
    target database Password: password
    Back up the datafile on the standby host across the network to a location on the primary host. For example, suppose that /disk1/df2.dbf is the name of datafile 2 on the standby host. Suppose that /disk8/datafile2.dbf is the name of datafile 2 on the primary host. The following command would copy datafile 2 over the network to /disk9/df2copy.dbf:
    BACKUP AS COPY DATAFILE 2 AUXILIARY FORMAT '/disk9/df2copy.dbf';
    Starting backup at 06-NOV-08
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1068 device type=DISK
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
    DBF
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
    15
    ORA-17628: Oracle error 19505 returned by remote Oracle server
    getting this error.

  • I got the above error while i restore the standby database using RMAN backu

    Dear All,
    RMAN> crosscheck archivelog all;
    using target database controlfile instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=14 devtype=DISK
    specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
    Help need.i take the backup without catalog database.
    regards,
    DB

    rman> list backup;
    it shows lengthier but i showed only the corresponding
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3479    Full    17G        DISK        01:29:42     09-FEB-13
            BP Key: 3479   Status: AVAILABLE   Tag: 09FEB13_FULL_ESMSRV1_DB
            Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
      SPFILE Included: Modification time: 08-FEB-13
      List of Datafiles in backup set 3479
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
      2       Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
      3       Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
      4       Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
      5       Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
      6       Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
      7       Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
      8       Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
      9       Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
      10      Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
      11      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
      12      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
      13      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
      14      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
      15      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
      16      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
      17      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
      18      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
      19      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
      20      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
      21      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
      22      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
      23      Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
      39      Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3480    Full    17G        DISK        01:21:30     09-FEB-13
            BP Key: 3480   Status: EXPIRED   Tag: TAG20130209T200021
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
      SPFILE Included: Modification time: 08-FEB-13
      List of Datafiles in backup set 3480
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
      2       Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
      3       Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
      4       Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
      5       Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
      6       Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
      7       Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
      8       Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
      9       Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
      10      Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
      11      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
      12      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
      13      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
      14      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
      15      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
      16      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
      17      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
      18      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
      19      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
      20      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
      21      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
      22      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
      23      Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
      39      Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3481    Full    4M         DISK        00:00:03     09-FEB-13
            BP Key: 3481   Status: AVAILABLE   Tag: TAG20130209T212205
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
      Controlfile Included: Ckp SCN: 1759462488   Ckp time: 09-FEB-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3482    Full    0          DISK        00:00:01     09-FEB-13
            BP Key: 3482   Status: AVAILABLE   Tag: TAG20130209T212212
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
      SPFILE Included: Modification time: 08-FEB-13
    ls -l /oradatabkp
    root@drsrv1#ls -l /oradatabkp
    total 1108672
    drwxr-xr-x   2 ovsd       dba             96 Sep 27  2009 alert_bkp
    -rw-r--r--   1 oracle     dba            195 Mar 15  2007 create.sql
    drwxr-xr-x   2 oracle     dba           8192 Aug  7  2009 ctrl_bkp
    -rw-r--r--   1 root       sys        565114880 Apr 24  2007 drsrv1.tar
    drwxrwxrwx   2 root       sys             96 Jun 17  2011 drsrv2-ignitebkp
    drwxr-xr-x   4 root       sys             96 Apr 24  2007 esmsrv1
    -rw-r-----   1 root       sys        1613824 Feb 22  2007 esmsrv1stby.ctl
    -rw-r--r--   1 esmsrv1    dba           5120 Dec 31  2009 esmtables.dmp
    -rw-r--r--   1 esmsrv1    dba            538 Dec 31  2009 esmtables.log
    drwxrwxrwx   4 root       sys           8192 Mar 10  2009 export
    drwxr-xr-x   8 root       sys           8192 Apr 24  2007 finalbackup
    -rw-r--r--   1 oracle     dba           3820 Sep  5  2008 invalid.sql
    -rw-r--r--   1 esmsrv1    dba         303104 Dec 31  2009 kirdevports.dmp
    -rw-r--r--   1 esmsrv1    dba            591 Dec 31  2009 kirdevports.log
    drwxr-xr-x   2 root       root            96 Feb 12  2007 lost+found
    -rw-r--r--   1 oracle     dba          24954 Aug  9  2009 ovcontrol-090909.ctl
    drwxr-xr-x  22 root       sys           8192 Apr 24  2007 ovpi
    drwxr-xr-x   2 oracle     dba           8192 Aug  7  2009 pfile_bkp
    drwxrw-rw-   4 oracle     dba           8192 Feb 10 15:25 rman
    drwxr-xr-x  28 root       sys           8192 Feb  1 17:15 schedbkp
    drwxr-xr-x   2 oracle     dba           8192 Jul 11  2011 sdnnm
    -rw-r--r--   1 esmsrv1    dba           2196 Dec 31  2009 srirdevports.log
    drwxr-xr-x   2 oracle     dba             96 Mar 13  2009 statsreport
    -rw-r--r--   1 oracle     dba            966 Mar 15  2007 tbs.sql
    drwxr-xr-x   5 oracle     dba             96 Mar 16  2007 testov
    drwxr-xr-x   2 root       sys         442368 Mar 11  2009 trendadm_files
    root@drsrv1#ls -l /oradatabkp/rman
    total 37244448
    drwxr-xr-x   2 oracle     dba           8192 Feb 10 15:25 esmsrv1
    -rw-r-----   1 oracle     dba        19068198912 Feb  9 14:21 esmsrv1_full_db_09feb13
    drwxrw-rw-   2 oracle     dba           8192 Feb  9 21:36 openview
    -rw-r--r--   1 oracle     dba         920442 Feb  9 21:37 rmanbkp-all.log

  • RMAN in standby Database

    Hello all,
    We want to configure RMAN in physical standby database but getting below error
    [oracle@timsdr ~]$ rman catalog rmandr/rmandr@rman target system/password
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Feb 26 17:04:36 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: TIMS (DBID=3639374466, not open)
    connected to recovery catalog database
    RMAN> show all;
    RMAN configuration parameters are:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of show command at 02/26/2010 17:08:34
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
    RMAN>
    Standby DB is in mount mode.Pls give some idea..

    catalog rmandr/rmandr@rmanIs this catalog different from the one that the Production database is registered with ?
    Note : You cannot register the same database -- ie Production and Standby have the same DBID -- twice in a catalog.
    Yet your catalog reports that the database is not registered.
    Seemingly, Production is registered to a different catalog OR is not registered at all.
    If using the same Catalog you should
    a. NOT register the Standby
    b. STOP recovery on the Standby
    c. MOUNT STANDBY on the Standby
    and then RMAN BACKUP the Standby
    Once the Backup is completed, restart Recovery on the Standby.
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

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

  • Backup policy on Grid, using RMAN and Recovery Catalog.

    Hello Gurus,
    I'm trying to move ahead the new features of Oracle 10g in my company. So I've already created Grid Control and will deploy Agents/Targets during the next week. I also want to switch the backup process from the archaic exp/imp to RMAN with the Recovery Catalog.
    My question is such: could anybody suggest the best book or text with solutions and descriptions of backup policy, using the Grid, RMAN and Catalog? What I want to do is to create eventually the powerful and centralized storage of every database in a company and do all daily routine from there. But as long as I'm only in the very beginning I want to gain some knowledge before the bad experience, like crashed recovery catalog and no backups for all databases :-)))
    Definitely I'll keep existing imp/exp and hotbackup for a long time. I'm not going to substitute all our backup strategy with one catalog. I just want to understand what will be the best practice in the backup perspective.
    And at all, I wonder if you please could give me very brief answer to this question: Let's say I have a huge monster with 5 disks by 500Gb RAD0+1. Is it a bad idea to store all of them in one physical machine before they will tape to backup or it could make sense? For me it sounds a bit scary, but probably if all made with the brain it's not a bad idea?
    Please, send me to some valuable and good source (like Tom Kyte or Don Burleson) Unfortunately, I didn't find anything regard the backups itself. Only pretty much general thought.
    Thanks a lot in advance.
    M.

    great!
    thanks a lot!
    this is definitely valuable info and I'll read right away. but as far as understand they suggest to use Data Guard, Standby and RAC which are the best ways to prevent your environment from crash. But in reality (I mean in my company) nobody is going to move to RAC at this point and I'm not sure, that they will have a chance to do in the next year. they just aren't up to it.
    what I'm looking for is probably some tips and hints about backups in more or less big environment, but not as big as Oracle itself :-) unfortunately, i'm the only DBA in my surrounding. i mean, i have no friends or mentors DBAs that could seat with me in a pub and pass theirs knowledge from generation to generation :-)))
    but anyway, I'll devote this week-end to this link.
    thanks a lot!

  • Rman standby database error

    Hi All,
    I am getting the following error when trying to CONFIGURE STANDBY database using rman,db version 10.2.0.2(HP-UX 11.2),library link seems to be fine.
    do i have to relink the library to oracle on the stanby db host too? any suggestion please.
    connect target / catalog rman@xx auxiliary sys@aux
    RMAN> run {
    allocate channel c1 device type 'sbt_tape';
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE 'SBT_TAPE';
    duplicate target database for standby dorecover;}2> 3> 4>
    allocated channel: c1
    channel c1: sid=164 instance=WWPODSP1 devtype=SBT_TAPE
    channel c1: Data Protector A.06.00/331
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on aux1 channel at 05/09/2007 16:57:07
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 11
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'control_file_%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    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' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so';
    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 '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_WWPODSP1.f'; # default

    sorry here is the exact commands.
    rman TARGET / AUXILIARY sys/xxx@WWPODSS catalog rman@rman
    Recovery Manager: Release 10.2.0.2.0 - Production on Wed May 9 17:29:37 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: WWPODSP (DBID=669261963)
    recovery catalog database Password:
    connected to recovery catalog database
    connected to auxiliary database: WWPODSP (not mounted)
    RMAN> run
    2> {
    3> duplicate target database for standby dorecover;}
    Starting Duplicate Db at 09-MAY-07
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/09/2007 17:33:35
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 11
    RMAN>

  • RMAN-11001: alter database mount standby database

    I'm doing a duplicate for a standby database and I'm getting this error
    Oracle 8i Tru64
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: Duplicate Db
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03006: non-retryable error occurred during execution of command: sql
    RMAN-07004: unhandled exception during command execution on channel clone_defaul
    t
    RMAN-20000: abnormal termination of job step
    RMAN-11003: failure during parse/execution of SQL statement: alter database moun
    t standby database
    RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
    Recovery Manager complete.
    Any help please

    Check for parameter mismatches between parameter file and control file.
    Check your parameter file. Check db_name paramter in paramter file used in the standby database.

  • Doubt about database point in time recovery using rman

    Hi Everyone,
    I have been practising various rman restore and recovery scenarios . I have a doubt regarding database point in time recovery using rman. Imagine i have a full database backup including controlfile scheduled to run at 10 PM everyday. today is 20th dec 2013. imagine i want to restore the database to a prior point in time ( say 18th dec till 8 AM). so i would restore all the datafiles  from 17th night's backup and apply archives till 8 AM of 18th dec . in this scenario should i restore the controlfile too from 17th dec bkp ( i am assuming yes we should ) or can we use the current controlfile ( assuming it is intact). i found the below from oracle docs.
    Performing Point-in-Time Recovery with a Current Control File
    The database must be closed to perform database point-in-time recovery. If you are recovering to a time, then you should set the time format environment variables before invoking RMAN. The following are sample Globalization Support settings:
    NLS_LANG = american_america.us7ascii
    NLS_DATE_FORMAT="Mon DD YYYY HH24:MI:SS"
    To recover the database until a specified time, SCN, or log sequence number:
    After connecting to the target database and, optionally, the recovery catalog database, ensure that the database is mounted. If the database is open, shut it down and then mount it:
    2.  SHUTDOWN IMMEDIATE;
    3.  STARTUP MOUNT;
    4. 
    Determine the time, SCN, or log sequence that should end recovery. For example, if you discover that a user accidentally dropped a tablespace at 9:02 a.m., then you can recover to 9 a.m.--just before the drop occurred. You will lose all changes to the database made after that time.
    You can also examine the alert.log to find the SCN of an event and recover to a prior SCN. Alternatively, you can determine the log sequence number that contains the recovery termination SCN, and then recover through that log. For example, query V$LOG_HISTORY to view the logs that you have archived. 
    RECID      STAMP      THREAD#    SEQUENCE#  FIRST_CHAN FIRST_TIM NEXT_CHANG
             1  344890611          1          1      20037 24-SEP-02      20043
             2  344890615          1          2      20043 24-SEP-02      20045
             3  344890618          1          3      20045 24-SEP-02      20046
    Perform the following operations within a RUN command:
    Set the end recovery time, SCN, or log sequence. If specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment variables.
    If automatic channels are not configured, then manually allocate one or more channels.
    Restore and recover the database.
      The following example performs an incomplete recovery until November 15 at 9 a.m. 
    RUN
      SET UNTIL TIME 'Nov 15 2002 09:00:00';
      # SET UNTIL SCN 1000;       # alternatively, specify SCN
      # SET UNTIL SEQUENCE 9923;  # alternatively, specify log sequence number
      RESTORE DATABASE;
      RECOVER DATABASE;
    If recovery was successful, then open the database and reset the online logs:
    5.  ALTER DATABASE OPEN RESETLOGS;
    I did not quiet understand why the above scenario is using current controlfile as the checkpoint scn in the current controlfile and the checkpoint scn in the datafile headers do not match after the restore and recovery. Thanks in Advance for your help.
    Thanks
    satya

    Thanks for the reply ... but what about the checkpoint scn in the controlfile . my understanding is that unless the checkpoint scn in the controlfile and datafiles do not match the database will not open. so assuming the checkpoint scn in my current controlfile is 1500 and i want to recover my database till scn 1200. so the scn in the datafiles (which is 1200) is not not matching with the scn in the controlfile(1500). so will the database open in such cases.
    Thanks
    Satya

  • Registering Clone database in Recovery catalog

    Can we able to register the clone database in recovery catalog database without changing dbid?
    I don't want to use dbid utility.
    Is that any parameter?
    Regards,
    Latha

    Well you can register it without changing any parameters in oracle 10.2
    That does not mean you should do it.
    I would have answered as follows:
    It is not a good idea to register a clone database in the same recovery catalog as the original database as the recovery catalog uses the dbid to identify the database and having two databases with the same dbid essentially corrupts the recovery catalog.
    If you change the dbid then it is perfectly okay to store the cloned database in the same recovery catalog.

  • OEM fails to create Standby database

    Hi,
    I have been trying to create a standby database using the wizard in the OEM. However, it hangs when trying to create the directory structure and files on the standby server. Anybody know how it does this?
    Does anyone know why it isn't working on my system.
    I have watched for network traffic between the two systems and there doesn't appear to be any whilst it is supposedly creating the files
    Thanks

    Thanks sorry I hadn't checked for a while....
    Oracle Enterprise Manager 10g Database Control Release 10.1.0.3.0
    The standby database is on a remote server, can write to the remote server
    I tried both ASM and normal file allocations
    Trace Errors...Hmm, I just found lots relating to
    No username specified for WBEM fetchlet,
    Hopefully I fixed that now. Ah, no it's not.
    I also have another in emdctl.trc
    2005-07-13 21:53:46 Thread-1 WARN http: snmehl_connect: connect failed to (v20z2:1830): Connection refused (error = 146)
    Can't find out what this is, any idead? Could it be related?
    Other errors in emagent_perl.trc are old but some appear to relate to the clone operation.
    -: Fri Nov 4 10:25:08 2005: ERROR: db_clone.parseOutput(): ORA- ERROR! Exit! See output log.
    -: Fri Nov 4 10:25:08 2005: ERROR: db_clone.parseOutput(): ORA- ERROR! Exit! See output log.
    dgDatabases.pl: Thu Feb 9 01:18:02 2006: ERROR: dgutil.handleError()
    dgDatabases.pl: Thu Feb 9 01:18:02 2006: ERROR: SQL Error: ORA-12505: TNS:listener does not currently know of
    SID given in connect descriptor (DBD ERROR: OCIServerAttach)
    dgDatabases.pl: Sun Feb 12 11:40:04 2006: ERROR: dgutil.handleError()
    dgDatabases.pl: Sun Feb 12 11:40:04 2006: ERROR: SQL Error: ORA-12528: TNS:listener: all appropriate instances
    are blocking new connections (DBD ERROR: OCIServerAttach)
    dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: The Data Guard configuration must be enabled.
    dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: dgutil.handleError()
    dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: The Data Guard configuration must be enabled.
    I am working through the creation process manually on a test database. I don't want to trach my production database... I needed to bring it online earlier than planned and I hadn't solved the standby database problem at that time. Many other problems had been solved though!
    Thanks for the help

Maybe you are looking for

  • Error message while creating shopping cart

    Hi I am facing issues in SC creation. Getting error messages  u2018purchasing group for follow on document missing & u2018purchasing organization for follow on document missingu2019. Is it something to with RFC or authorizations arjman

  • Dip to color dissolve question

    Hi, I am using a dip to color dissolve between clips, dipping to white. My problem is that the pillarbox lines are also dipping. Is there any way to avoid this? Thanks.

  • How to call a method in the servlet from an applet

    I want to get the data for the applet from the servlet. How to call a method that exits in the servlet from the applet? I want to use http protocol to do this. Any suggestions? Please help. thanks

  • Dynamic connect to password protected site

    I want to write a bean or something, that will connect to URL with a username and password. Get some data from that page and save it to some file. I'm having problem with writing a code to connect to URL and use username and password to login. Any he

  • Support "notifications"?

    I have been getting a surprisiing volume of junk emails that purport to be from some "support" service.  Some are labeled "Apple Support" , some seem to come from Facebook and some are labeled "Gmail support."  Thankfully they are diverted to my junk