Error installing recovery catalog

Hi,
Inorder to implement RMAN in oracle 10g in windows environment I created a separate table space for rman and created a user as rman1;
then I issued the following commands :
GRANT connect, resource, recovery_catalog_owner TO rman1
grant create session to rman1;
grant create type to rman1;
then i entered into rman from dos prompt,
rman catalog=rman1/rman1@tc
from rman prompt I issued the command,
create catalog tablespace RMAN1;
then the following error occurs,
RMAN> create catalog tablespace RMAN1;
ORACLE error from recovery catalog database: ORA-01031: insufficient privileges
RMAN-00571: ====================
RMAN-00569: ===== ERROR MESSAGE STACK FOLLOWS ===========
RMAN-00571: ====================================
RMAN-06433: error installing recovery catalog
Due to this error I am unable to proceed further and let me know the solution.
Thanks in advance.
Regards,
A.Mohammed Rafi.

Hi,
Thanks for the help and the problem is solved.
Now I am facing another problem,
RMAN-03009: failure of catalog command on default channel
ORA-19657: cannot inspect current datafile D:\ORACLE\PRODUCT\10.1.0\DB_2\TC\EXAMPLE01.DBF
Could you please help me in this regard.

Similar Messages

  • Installing recovery catalog!!

    hello,
    can anybody tell that how to install recovery
    catalog on oracle8i?

    Hi,
    Here is the procedure for creating RMAN catalog:
    Installing RMAN Catalog:
    Install the recovery catalog schema in a different database (say RCAT) from the target database you will be backing up.
    Assume the following for the examples below:
    User SYS with password CHANGE_ON_INSTALL has SYSDBA privileges on the recovery catalog database RCAT.
    There is a tablespace called CATTBS on the recovery catalog database RCAT that stores the recovery catalog.
    There is a tablespace called TEMP in the recovery catalog database.
    To set up the recovery catalog schema:
    Start SQL*Plus and then connect with administrator privileges to the database containing the recovery catalog (RCAT). For example, enter:
    SQL> CONNECT sys/change_on_install@rcat
    Create a log file that you can use to check for errors. For example, enter:
    SQL> SPOOL create_rman.log
    Create a user and schema for the recovery catalog. For example, enter:
    SQL> CREATE USER rman IDENTIFIED BY rman
    2> TEMPORARY TABLESPACE temp
    3> DEFAULT TABLESPACE cattbs
    4> QUOTA UNLIMITED ON cattbs;
    Grant the RECOVERY_CATALOG_OWNER role to the schema owner. This role provides the user with privileges to maintain and query the recovery catalog.
    SQL> GRANT recovery_catalog_owner TO rman;
    Grant other desired privileges to the RMAN user.
    SQL> GRANT connect, resource TO rman;
    Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
    SQL> host
    % vi create_rman.log
    To create the recovery catalog:
    Connect to the database that will contain the catalog as the catalog owner. For example, from the operating system command line enter:
    % rman catalog rman/rman@rcat
    You can also connect from the RMAN prompt:
    % rman
    RMAN> connect catalog rman/rman@rcat
    Issue the create catalog command to create the catalog, specifying the CATTBS tablespace:
    RMAN> create catalog tablespace cattbs;
    Note that the creation of the catalog can take several minutes.
    Host out to the operating system to check the create_rman.log file for any errors before continuing. For example, a UNIX user can issue:
    RMAN> host;
    % vi create_rman.log
    Optionally, query the recovery catalog to see which tables were created:
    SQL> SELECT table_name FROM user_tables;
    Note: Database name, SYS password, tablespace names are for examples only. You can name change them.
    You all set!!!! Good luck.
    -Rama
    null

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

  • How to install Recovery Catalog

    Hi:
    How to install the recovery catalog? I used the following commands from the menu and it didn't work:
    connect rman/rman
    @?/rdbms/admin/catrman
    There is no catrman.sql exists.
    Thank you very much.

    If you are using Oracle8i, make sure your compatibility is set to at least 8.1.0 and you are connected to the catalog database. Then type create catalog; at the RMAN command line.

  • Errors installing recovery disk: No wifi

    I used the recovery disk; factory settings reboot.... And this happens. It only connects directly to the Internet; no wifi at all. And it won't do windows updates. Now I get this message. I am not sure what I need to do to fix this.
    You can see in the photos, there are errors with the Toshiba Modem and the Wifi 5100
    Toshiba sent me A300 series revovery disk for Vista Home Premium 64-bit; is that the correct one for A305 S6916 PSAGCU ?
    Solved!
    Go to Solution.
    Attachments:
    1.JPG ‏121 KB
    4.JPG ‏51 KB

    Satellite A305-S6916
    Those are the sorts of symptoms you might get if you restored to a hard disk with advanced-format technology. See my message about that.
    But you didn't say anything about changing the hard drive.
    -Jerry

  • 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

  • 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

  • Specification does not match any archive log in the recovery catalog

    Hi
    My rman backups sometimes fails with below error, any idea the reason ?
    run {
    allocate channel t1 type 'SBT_TAPE';
    backup
    incremental level 0
    format '/%d_%p_%t.%s/'
    maxsetsize = 8G
    (database);
    backup
    format '/%d_%p_%t_al.%s/'
    (archivelog from time 'SYSDATE-2');
    backup
    format '/%d_%p_%t_al.%s/'
    (archivelog until time 'SYSDATE-2' delete input);
    release channel t1;
    Starting backup at 2011-01-18 22:41:59
    current log archived
    channel t1: starting archive log backupset
    channel t1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=7348 recid=6260 stamp=740682001
    input archive log thread=1 sequence=7349 recid=6261 stamp=740702540
    input archive log thread=1 sequence=7350 recid=6262 stamp=740739604
    input archive log thread=1 sequence=7351 recid=6263 stamp=740746801
    input archive log thread=1 sequence=7352 recid=6264 stamp=740757602
    input archive log thread=1 sequence=7353 recid=6265 stamp=740768401
    input archive log thread=1 sequence=7354 recid=6266 stamp=740788921
    channel t1: starting piece 1 at 2011-01-18 22:42:04
    channel t1: finished piece 1 at 2011-01-18 22:42:29
    channel t1: backup set complete, elapsed time: 00:00:26
    Finished backup at 2011-01-18 22:42:29
    Starting backup at 2011-01-18 22:42:31
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 01/18/2011 22:42:31
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
    Recovery Manager complete.

    Hi Ora 83,
    What is the reason of this error ? The reason for the RMAN-20242 is there are no archivelogs which comply to the filter "until time 'SYSDATE-2'" at 18 Jan 22:42.
    Probably you run a purge command more frequent because the oldest logsequence available for backup was created at:
    2011 JAN 17 17 00 01 (=sequence=7348)
    and the latest at:
    2011 JAN 18 22 42 01 (=sequence=7354)
    according to your output.
    So for some reason the archivelogs created before 16th Jan 22:42 are not on the system as well as the archivelogs created between 16th Jan 22:42 and 17 Jan 17:00.
    Maybe there are none (you can check in the alertlog and let us know)?
    Regards,
    Tycho

  • RMAN-06428 recovery catalog is not installed

    RDBMS Version: 8.1.6
    Operating System and Version: sun sparc 5.8
    Error : RMAN-06428 RMAN-06428 recovery catalog is not installed
    Product (i.e. SQL*Loader, Import, etc.): RMAN
    Product Version: 8.1.6
    Hi,
    I hv a database running in unix box 1 (say 'FAST')
    and Im trying to install a recovery catalog database in unix box
    2
    (Rcat)
    1) in unixbox2..I hv created a new database, and I hv created a
    tablespace rcvcat and user rman .granted catalog_recovery_owner
    to rman.
    also I hv created a catalogue using this command
    create catalogue tablespace rcvcat;
    (no error logs generated)
    2)now when I try to connect to the catalogue I am getting an
    error
    what I did is, I tried connecting to rman of target database
    (FAST database)
    % rman target /catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    also I tried like this,
    % rman target system/manager@fast catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    I dont understand why it says recovery catalog not installed ,
    when I hv created one in rcat database.
    Can anyone help me how to connect to catalog and register my
    database (I mean from which machine I need to run the commands)
    Thanks
    Venkat

    You do have a problem. It seems your "Shift" key is stuck.
    Anyway, please read: [ID 188682.1],
    Have a nice day.

  • How to install the Recovery Catalog

    Hi:
    How to install the recovery catalog? I used the following commands from the menu and it didn't work:
    connect rman/rman
    @?/rdbms/admin/catrman
    There is no catrman.sql exists.
    Thank you very much.

    If you are using Oracle8i, make sure your compatibility is set to at least 8.1.0 and you are connected to the catalog database. Then type create catalog; at the RMAN command line.

  • Error on installing infoobject catalog from business content

    while performing Install from Administrator Workbench:Business Content I am getting error.
    I am trying to install Infoobject catalog 0MMIC_CHA01 and 0MMIC_KYF01 from business content
    The error messages appearing are as follows:
    Installation (simulation mode) of: InfoObject (IOBJ)
    Checking Objects with Type InfoObject
    Checking InfoObject 0BPARTNER
    Char. 0LEGALFORM is exclusively an attribute (cannot be a navigation attribute)
    Checking InfoObject 0CM_CDT1
    Char. 0CM_HIEID may not appear in compounding and attributes simultaneously
    Characteristic 0CM_CDT1 is used as Navigation Attribute of 0RT_SEAROLL, but characteristic
    IInstallation (simulation mode) of: ODS Object (ODSO)
    Installation (simulation mode) of: Update Rules (UPDR)

    Hi
    It seems although's are warnings and not errors. Instead of using Simulation just install the content.
    check out the below article
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50b1d20e-c1e8-2c10-d9b9-d48eb3a83d89?QuickLink=index&overridelayout=true
    Regards,
    Venkatesh

  • Error on installing Discoverer - Catalog

    I can't install the Discoverer Catalog.
    On installing this Modul I got the following Error:
    Error - oracle.dss.d4o.administration.D4OInstallationException: D4O-1124 Post-install verification failed, found the following invalid object(s): BISM_CALC_FILTER
    I need the Catalog to use the private and public connections in Discoverer.
    What can I do to install the Catalog?
    BI Applicationserver Version 10.1.2.3.0
    Database Version 10.2.0.3.0

    Hallo Steve
    Thank you for your answer. i have now installed the OLAP package, but when i startet your select I got the follwowing result:
    select comp_name, version, status from SYS.DBA_REGISTRY order by comp_name;
    JServer JAVA Virtual Machine     10.2.0.3.0     VALID
    OLAP Analytic Workspace     10.2.0.3.0     VALID
    OLAP Catalog                     10.2.0.3.0     INVALID
    Oracle Database Catalog Views     10.2.0.3.0     VALID
    Oracle Database Java Packages     10.2.0.3.0     VALID
    Oracle Database Packages and Types     10.2.0.3.0     VALID
    Oracle Enterprise Manager     10.2.0.3.0     VALID
    Oracle Expression Filter     10.2.0.3.0     VALID
    Oracle OLAP API     10.2.0.3.0     VALID
    Oracle Workspace Manager     10.2.0.1.0     VALID
    Oracle XDK      10.2.0.3.0     VALID
    What should i do?

  • Error installing rescue and recovery 4.3 on windows 7

    i have a sl410 with windows 7 ultimate(32bit) installed, but i failed to install  rescue and recovery 4.3 for many times,reporting"Error 25014. There was an error installing the Rescue and Recovery boot manager. Return code: 6".
    why?
    i found someone said about using a command line installation which will NOT install the RnR partition,but how to use  command line installation?i've got only the tvtvrnr43_1027sc.exe downloaded file and the tvtrnr43_1027.exe in C:\SWTOOLS\apps\rnr43sc\ directory,how can i input the comands like setup.exe /a /s?which command should i use?

    http://forum.lenovo.com/t5/ThinkVantage-Technologies/Rescue-and-Recovery-4-3-for-Windows-7-installat...

  • Recovery Catalog showing wrong Archive Destination

    Hi All,
    I am using Oracle 10g on Solaris 10.
    The problem I am facing is this, while taking backup using recover catalog..............
    Starting backup at 27-JUL-11
    current log archived
    released channel: ch00
    released channel: ch01
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 07/27/2011 11:16:47
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    This is because of the following reason
    RMAN> list archivelog all;
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    39401 1 1567 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1567_756523261.dbf
    39402 1 1568 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1568_756523261.dbf
    39403 1 1569 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1569_756523261.dbf
    39404 1 1570 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1570_756523261.dbf
    39405 1 1571 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1571_756523261.dbf
    39406 1 1572 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1572_756523261.dbf
    39407 1 1573 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1573_756523261.dbf
    39408 1 1574 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1574_756523261.dbf
    39409 1 1575 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1575_756523261.dbf
    39410 1 1576 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1576_756523261.dbf
    39411 1 1577 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1577_756523261.dbf
    39412 1 1578 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1578_756523261.dbf
    39413 1 1579 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1579_756523261.dbf
    39414 1 1580 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1580_756523261.dbf
    39415 1 1581 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1581_756523261.dbf
    39416 1 1582 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1582_756523261.dbf
    39417 1 1583 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1583_756523261.dbf
    39418 1 1584 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1584_756523261.dbf
    39419 1 1585 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1585_756523261.dbf
    39420 1 1586 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1586_756523261.dbf
    39421 1 1587 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1587_756523261.dbf
    39422 1 1588 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1588_756523261.dbf
    39423 1 1589 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1589_756523261.dbf
    39424 1 1590 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1590_756523261.dbf
    39425 1 1591 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1591_756523261.dbf
    39426 1 1592 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1592_756523261.dbf
    39427 1 1593 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1593_756523261.dbf
    39428 1 1594 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1594_756523261.dbf
    39429 1 1595 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1595_756523261.dbf
    39430 1 1596 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1596_756523261.dbf
    39431 1 1597 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1597_756523261.dbf
    39432 1 1598 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1598_756523261.dbf
    39433 1 1599 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1599_756523261.dbf
    39434 1 1600 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1600_756523261.dbf
    39435 1 1601 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1601_756523261.dbf
    39436 1 1602 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1602_756523261.dbf
    39437 1 1603 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1603_756523261.dbf
    39438 1 1604 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1604_756523261.dbf
    39439 1 1605 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1605_756523261.dbf
    39440 1 1606 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1606_756523261.dbf
    39441 1 1607 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1607_756523261.dbf
    39442 1 1608 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1608_756523261.dbf
    39443 1 1609 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1609_756523261.dbf
    39444 1 1610 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1610_756523261.dbf
    39445 1 1611 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1611_756523261.dbf
    39446 1 1612 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1612_756523261.dbf
    39447 1 1613 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1613_756523261.dbf
    39448 1 1614 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1614_756523261.dbf
    39449 1 1615 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1615_756523261.dbf
    39450 1 1616 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1616_756523261.dbf
    39451 1 1617 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1617_756523261.dbf
    39452 1 1618 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1618_756523261.dbf
    39453 1 1619 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1619_756523261.dbf
    39454 1 1620 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1620_756523261.dbf
    39455 1 1621 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1621_756523261.dbf
    39456 1 1622 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1622_756523261.dbf
    39457 1 1623 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1623_756523261.dbf
    39458 1 1624 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1624_756523261.dbf
    39459 1 1625 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1625_756523261.dbf
    39460 1 1626 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1626_756523261.dbf
    39461 1 1627 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1627_756523261.dbf
    39462 1 1628 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1628_756523261.dbf
    39463 1 1629 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1629_756523261.dbf
    39464 1 1630 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1630_756523261.dbf
    39465 1 1631 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1631_756523261.dbf
    39466 1 1632 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1632_756523261.dbf
    39467 1 1633 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1633_756523261.dbf
    39468 1 1634 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1634_756523261.dbf
    39469 1 1635 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1635_756523261.dbf
    39470 1 1636 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1636_756523261.dbf
    39471 1 1637 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1637_756523261.dbf
    39682 1 1638 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1638_756523261.dbf
    39689 1 1639 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1639_756523261.dbf
    40642 1 1640 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1640_756523261.dbf
    40643 1 1641 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1641_756523261.dbf
    40644 1 1642 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1642_756523261.dbf
    40645 1 1643 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1643_756523261.dbf
    40646 1 1644 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1644_756523261.dbf
    40647 1 1645 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1645_756523261.dbf
    40648 1 1646 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1646_756523261.dbf
    41310 1 1647 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1647_756523261.dbf
    41317 1 1648 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1648_756523261.dbf
    41373 1 1649 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1649_756523261.dbf
    41374 1 1650 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1650_756523261.dbf
    41375 1 1651 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1651_756523261.dbf
    41383 1 1652 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1652_756523261.dbf
    *38725 1 56 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf*
    *38946 1 57 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_57_757089402.dbf*
    *39000 1 58 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_58_757089402.dbf*
    *39022 1 59 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_59_757089402.dbf*
    *39243 1 60 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_60_757089402.dbf*
    *39297 1 61 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_61_757089402.dbf*
    *39703 1 62 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_62_757089402.dbf*
    *39704 1 63 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_63_757089402.dbf*
    *39705 1 64 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_64_757089402.dbf*
    *39933 1 65 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_65_757089402.dbf*
    *39991 1 66 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_66_757089402.dbf*
    *40023 1 67 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_67_757089402.dbf*
    *40024 1 68 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_68_757089402.dbf*
    *40025 1 69 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_69_757089402.dbf*
    *40254 1 70 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_70_757089402.dbf*
    *40308 1 71 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_71_757089402.dbf*
    *40345 1 72 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_72_757089402.dbf*
    *40570 1 73 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_73_757089402.dbf*
    *41329 1 74 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_74_757089402.dbf*
    I dont know from where recovery catalog is getting the information in bold.
    I have crosschecked and deleted archives and resynced the catalog several times. Immediatly after doing that the backup works fine, but the other day its the same thing all over again.
    Can some one tell me from where the catalog is getting this wrong infomation about archivelogs???
    By the way here is some more info about my target Database:
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oradb2/Archive/HCSPRD91
    Oldest online log sequence 1651
    Next log sequence to archive 1653
    Current log sequence 1653
    NAME TYPE VALUE
    archive_lag_target integer 0
    log_archive_config string
    log_archive_dest string
    log_archive_dest_1 string LOCATION=/oradb2/Archive/HCSPR
    D91
    log_archive_dest_10 string
    log_archive_dest_2 string
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    NAME TYPE VALUE
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    NAME TYPE VALUE
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 2
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    remote_archive_enable string true
    standby_archive_dest string ?/dbs/arch
    Regards .....

    Do you have any other DBs with the same DBID as the one you are backing up? Are they connect to the same RMAN catalog?
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • What's the recommended guideline on backing up a recovery catalog?

    while I understand "Benefits of Using the Recovery Catalog as the RMAN Repository" as stated in
    http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmquick.htm#442214
    as well as things to take note if using control file as the sole rman repository,
    as stated in "Monitoring the Overwriting of Control File Records" in http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#446924
    I do not understand why in Backup and Recovery Advanced User's Guide
    http://download.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmrepos.htm
    "Back Up the Recovery Catalog Often"
    Even if you have to restore the recovery catalog database using a control file autobackup, you can then use the full record of backups in your restored recovery catalog database to restore the target database without using a control file autobackup for the target database.
    =>probably implies that we can use another recovery catalog let's call it backupbackup to restore the recovery catalog
    "Choosing the Appropriate Method for Physical Backups"
    Follow these guidelines when developing an RMAN backup strategy for the recovery catalog database:
    * Run the recovery catalog database in ARCHIVELOG mode so that you can do point-in-time recovery if needed.
    * Set the retention policy to a REDUNDANCY value greater than 1.
    * Back up the database onto two separate media (for example, disk and tape).
    * Run BACKUP DATABASE PLUS ARCHIVELOG at regular intervals, to a media manager if available, or just to disk.
    * Do not use another recovery catalog as the repository for the backups.=> this contradicts the previous statement
    * Configure the control file autobackup feature to ON.
    so may I know what's the recommended guideline on backing up a recovery catalog? should we use another recovery catalog to keep the rman repositories of the the main primary catalog or just use a control file autobackup feature?
    thanks

    I understand the question and the confusion.
    Please note, however, that this forum is for discussing problems and errors with the documentation in general. Your question is related to a specific product and is, as far as I can tell, not a note about a documentation error or a correction.
    The appropriate place to discuss this is the Database (General) forum or - perhaps surprisingly - the RMAN forum. These can both be found by
    1) Clicking on the 'Forum Home' link at the top of this page;
    2) Scrolling down to the category 'Database' (a category is identified by a special row format that does not list the number of topics)
    3) Expanding the category by clicking on the 'More ...' link.
    4) Scrolling down to the "Database - General" or "Recovery Manager" forum and clicking on it's link.
    Note that forums have a search function that may be used to find answers if someone has already asked a similar question.

Maybe you are looking for

  • First Kernel Panic ever -- I would really apprec help on what this log mean

    While charging up my ipod, I forgot to eject it before turning off itunes -- then I turned Itunes back on, then got my first kernel panic. Is this something to be concerned about? The message I got was as follows: Sat Oct 17 09:25:31 2009 panic(cpu 0

  • How to include a Z-table in a Case

    Hello, we are trying to add a Z-table only to display data updated in the CRM system (as a log), and we can´t do this in the Web Client. We can´t see the records of the table. Do you have any cookbook or something like that? So we can achieve this is

  • Performance improvements on games in G4 400

    Hello everyone, I have a G4 400 with the 16 MB original card and 512 megs of ram. I also have a PB g4 Ti. I recently started playing Warcraft III with my son thru an airport connection. We used to play Starcraft in the same manner and the game rus we

  • Logic sampler, i need to put my e mu e4xt ultra samples into my logic pro

    i have my e mu 4xt ultra samples on my desk top. they show up as .e4b i need to convert them to .exs so they will line up in my logic sampler. how can i do this? aaron

  • Navigation back to UWL after completing the task.

    Hi All, I am new to the portal, I would like to know is there any way to navigate back to UWL after completing a task in UWL instead of seeing the action is completed screen? Thank you in advance. Regards, Ravi