RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법

제품 : RMAN
작성날짜 : 2001-05-28
RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법
===============================================
1) UNREGISTER 하고자 하는 Database를 RMAN CATALOG에서 확인한다.
SELECT * FROM RC_DATABASE;
2) UNREGISTER하고자 하는 DATABASE에 속한 BACKUPSET들을 모두 제거한다.
- 제거하고자 하는 BACKUPSET을 알아내는 방법
RMAN> list backupset of database;
- BACKUPSET을 제거하는 방법
RMAN> allocate channel for delete type disk;
RMAN> change backupset XXX delete;
* 위에서는 DISK에대해 CHANNEL을 설정하였지만 TAPE에 대해 CHANNEL설정을
하려면 아래와 같은 COMMAND를 수행한다.
RMAN> allocate channel for delete type 'sbt_tape';
또한 XXX는 'list backupset of database'의 결과 중에서 'LIST OF KEY'의
값을 의미한다.
3) 다음과 같은 PROCEDURE를 RECOVERY CATALOG에서 수행함으로써 DATABASE를 UNREGISTER한다.
execute dbms_rcvcat.unregisterdatabase (db_key, db_id)
* DB_KEY와 DB_ID는 다음과 같은 QUERY문에서 알아낼 수 있다.
SVRMGR> select * from rc_database;
EXAMPLE:
========
Unregistering ORCL database:
1) The following will list the backupset for the database that we want to
uncatlog.
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ---------
RMAN-06233: 858 1 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 2 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 3 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 4 Full 16-SEP-98 253487 16-SEP-98
==================================
2) The following will show allocation of a delte channel, deleting the
backupset, and running the list command to confirm that the backupsets were
removed. The delete command will remove the backupsets from the backup location.
RMAN> allocate channel for delete type disk;
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete
RMAN-08500: channel delete: sid=10 devtype=DISK
RMAN> change backupset 858 delete;
RMAN-03022: compiling command: change
RMAN-03023: executing command: change
RMAN-08073: deleted backup piece
RMAN-08517: backup piece handle=C:\ORANT\DATABASE\RMANORCLBACKUP\DF_344180532_30
_1 recid=27 stamp=344180538
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ----------
================================
3) From the recovery catalog:
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAMERESETLOGS_ RESETLOGS
584 585 868345165 ORCL 192881 18-AUG-98
1 row selected.
SVRMGR> execute dbms_rcvcat.unregisterdatabase(584,868345165);
Statement processed.
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAME RESETLOGS_ RESETLOGS
0 rows selected.

Similar Messages

  • Unregistering of a database from RMAN Catalog

    Hello,
    We had set up RMAN backup though RMAN Catalog for one of our database.
    We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
    1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
    2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
    We know that the tapes don't have the backup of this database.
    Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
    Thanks!

    Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
    I have another question though -
    We have compressed backup for one of the database/
    If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
    BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
    select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
    Question - How to check the compressed size of the backupset from the Catalog tables/views?
    Thanks for your help on this!
    Thanks!
    ,

  • How to get RMAN catalog information from Target database?

    Hi,
    How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
    Thanks

    If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
    The RMAN backup script would have the connection identifier for the Catalog.
    Hemant K Chitale

  • RMAN catalog fails to show target database information when in nomount mode

    Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
    Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
    :->rman catalog cde01_rman4/xxxxxxx@prman10g target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: EGVBFI2 (DBID=4238332493, not open)
    connected to recovery catalog database
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
    84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
    RMAN>
    However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
    :->rman catalog cde01_rman4/xxxxxx@prman10g target /
    Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: egvbfi2 (not mounted)
    connected to recovery catalog database
    RMAN> list incarnation;
    RMAN>
    Please advice?
    Thanks,
    Jairaj

    Hi,
    You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
    Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
    Mount the instance and just restore the datafiles.
    Liron Amitzi
    Senior DBA consultant
    link: [www.dbsnaps.com]
    link: [www.obriumsoftware.com]

  • 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

  • Unregister from rman catalog

    Dear All,
    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?

    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?No ned to confiugre, while connecting to RMAN or in backupjob scripts just do not mention catalog connectivity.
    If any old backups available then register them with controlfile..
    in case of catalog :-
    rman target sys/****@prod catalog rman/rman@catlog
    in case of no-catalog:
    rman target sys/****@prod
    to register old backups:-
    RMAN> catalog start with 'location of backups';

  • RMAN-06429: TARGET database is not compatible with this version of RMAN

    he Hi,
    how can i solve this issue . how i will upgrade the Rman. My production database details are below
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    while i'm configuring rman i'm getting below error . please help me.
    C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    rgds,
    john

    Johnvd wrote:
    Hi Hemant,
    i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
    how its happening is there any where i have to change the path.
    Regards,
    johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
    If you are using windows, run the following commands in command prompt and then copy/paste the output:
    echo 5ORACLE_HOME%
    echo %PATH%
    If you are using unix, run the following commands in terminal and then copy/paste the output:
    echo $ORACLE_HOME
    echo $PATH
    Regards
    Gokhan

  • How to upgrade RMAN catalog from 10.2.0.4 to 11?

    Hi, we are on Oracle 10.2.0.4, Solaris 5.10. Our RMAN catalog is 10.2.0.4 version and we have several 11g databases that need to connect to the catalog and obviously cannot. So we need to upgrade the catalog to 11. Does anyone have any docs on how to do it. Do I need to upgrade RMAN database to 11 via conventional upgrade and then do UPGRADE CATALOG? Really confusing, any help would be very appreciated.
    Thank you!

    You need to:
    1 - upgrade the recovery catalog database
    2 - upgrade the recovery catalog Schema
    Please check the details on note *452529.1 Recovery catalog for RMAN backup*.
    Normally newer databases (target) can be cataloged on previous version catalog database, but with 11g there is the bug 6756872 (RMAN REGISTER OF 11G TARGET INTO 10G CATALOG FAILS WITH ORA-04028) which force you to upgrade the catalog.
    You can also review RMAN Compatibility Matrix (Note 73431.1) which has all valid version combinations.
    If your scenario is simple enough, another option could be create a new 11g RMAN catalog and register there your databases, without importing data from the 10.2 catalog.
    Regards.

  • Can't register a database in RMAN catalog (PL/SQL package not current)

    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    Regards

    user13064912 wrote:
    Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
    $ rman catalog rman/rman target sys@MPOWER
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: MPOWER (DBID=**********)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    RMAN-00571: ===============
    RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: =================
    RMAN-03008: error while performing automatic resync of recovery catalog
    ORA-00904: : invalid identifier
    Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
    I cannot register the target database into the RMAN catalog.
    I highly appretiate if you give me an advice on this.
    RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
    Your rman client is higher than your target server. That could be the problem.
    Best Regards,
    Gokhan
    If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

  • Schedule a crontab in rman catalog

    Hi,
    I am trying to schedule a crontab in rman catalog side but it wasn't work.
    I prepared a scripts and I dont know why it was not worked.
    Please can anyone tell me how can I schedule my crontab in rman.
    The scripts is this,
    00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
    vi ora_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
    run {
    backup incremental level 0 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
    vi ora01_rman.sh
    ORACLE_SID=p001
    ORACLE_BASE=/orahome/p001
    ORACLE_HOME=$ORACLE_BASE/10.0.2
    PATH=$ORACLE_HOME/bin:$PATH
    $ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
    run {
    backup incremental level 1 as compressed backupset database plus archivelog;
    delete noprompt archivelog all completed before 'sysdate-7';
    waiting for your replies,
    Thanks & Regards

    Here's my working stuff:
    I use an .env file. Here's the crontab entry, script and env file.
    00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
    #!/bin/bash
    # Name: db_rman_full.sh
    # Purpose: Database rman backup
    # Usage : db_rman_full <DBNAME>
    . /u01/app/oracle/dba_tool/env/PRIMARY.env
    echo "Starting RMAN..."
    $ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
    run { allocate channel d1 type disk;
    backup full as compressed backupset
    database plus archivelog;}
    crosscheck backup;
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
    DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
    exit
    EOF
    echo `date`
    echo
    echo 'RMAN Full on PRIMARY Complete'
    env
    ORACLE_BASE=/u01/app/oracle
    ULIMIT=unlimited
    ORACLE_SID=PRIMARY
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0
    ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
    LIBPATH=$LD_LIBRARY_PATH:/usr/lib
    TNS_ADMIN=$ORACLE_HOME/network/admin
    PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
    export TERM=vt100
    export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
    export ORACLE_HOME
    export LIBPATH LD_LIBRARY_PATH ORA_NLS33
    export TNS_ADMIN
    export PATH
    ----If you find this helpful please mark it so----

  • Howto: RMAN catalog backupset in different location

    Hi,
    How can I tell RMAN catalog that the location of backup set has changed.
    For example: after my RMAN backup all my backup pieces went to C:\first_location\
    directory. I am using a catalog while running backup.
    Now I moved the backup pieces to D:\new_location\ directory. Say C:\first_location\ directory is no longer for some reason. How do I tell my catalog that the backup pieces about the new location D:\new_location\
    Catalog, Rman, database all in 10.2 version.
    thank you in advance

    Thank you for your response to my question.
    Can someone help me with syntax and usage of new location of backup pieces in a backup set to be reflected in my catalog. Catalog, target and rman all 10g version.
    thanks in advance

  • RMAN catalog Downgrade from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4)

    I am in the process of downgrading rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4). Using expdp/impdp we migrated the rman schema from 11g to 10g. I am able to connect to 10g catalog now. but if i run any command it gives following error.
    ./rman target sys
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Feb 16 11:21:11 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    target database Password:
    connected to target database:
    RMAN> connect catalog rman/*******@rman
    connected to recovery catalog database
    RMAN> show all ;
    RMAN configuration parameters for database with db_unique_name NACC are:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of show command at 02/16/2010 11:21:34
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog
    RMAN> exit
    Have i missed anything which has to be done .
    Thanks
    Ajeet

    Hi Tycho ,
    Thanks for your help and suggestions . What i did is i migrated the rman catalog from 11gR1 (11.1.0.6.0) to 10gR2 (10.2.0.4) then connected rman catalog from 11gR2 Client which is the highest version available and then did the following.
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 11.02.00.01
    DBMS_RCVMAN package upgraded to version 11.02.00.01
    DBMS_RCVCAT package upgraded to version 11.02.00.01
    RMAN>
    Now i am able to connect directly and take backup's from 11gR2 , 11gR1 and 10gR2 clients respectively. I also tested the backup's from grid control which are working fine.
    Currently my rman catalog database is 10.2.0.4 and my rman catalog schema is 11.02.00.01.
    Thanks for everyone's help.
    Ajeet
    Edited by: user12169940 on Feb 17, 2010 4:02 AM

  • How to recover the rman catalog

    all,
    I have created a recovery catalog and back it up using the control file and the nocatalog option - see below
    rman nocatclog target=rman
    run{
    backup database;
    backup (archivelog all delete input);
    How do I recover the catalog if it dies?
    rgds
    alan

    hi,
    thanks for the response. I will give it a try, but at a cistomer site doing this and they have no test server to try it on. Production only so need to be sure of what is going to happen.
    rgds
    alan

  • One 8i instance and two rman catalogs 8i and 8

    Can I have a single 8i instance for RMAN only with two catalogs, one for 8i and one for 8.0?

    Robert,
    Yes you can use a single database for 2 recovery catalogs. You can create 2 different schemas for each RMAN catalog version and each of those schemas can hold a different version of the RMAN catalog.
    The only reason I can think that you would need 2 different catalogs is because you have an 8.1.X target and a 8.0.5 target? If so, make sure to have the RMAN catalog be the latest 8.1.x release.
    In general, the rules of RMAN compatibility are as follows:
    o The RMAN catalog schema version should be greater than or equal to the catalog database version. See "Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases".
    o The RMAN catalog is backwards compatible with target databases from earlier releases. See "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases".
    o The versions of the RMAN executable and the target database should be the same.
    Note 1: 8.1 or Later Catalog Schemas in 8.0 Catalog Databases
    RMAN cannot create release 8.1 or later catalog schemas in 8.0 catalog databases.
    Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases
    Restore operations for an 8.0.4 or 8.0.5 target with an 8.1 or later catalog schema do not work when both these conditions are met:
    The target database is mounted or open
    You are connected to a recovery catalog
    If any of these conditions is not met, then you can use an 8.1 or later catalog schema with an 8.0.4 or 8.0.5 target database.
    Note 3: 8.1.6 Catalog Schema and Pre-8.1.6 RMAN Executable
    Using a pre-8.1.6 release of the RMAN executable with recovery catalog schema of release 8.1.6.0 or 8.1.6.1 (newly created by 8.1.6 RMAN executable using the CREATE
    CATALOG command) requires the following update at the catalog database:
    SQL> UPDATE CONFIG SET VALUE='080004' WHERE NAME='COMPATIBLE';
    null

  • Set RMAN catalog default setting for all databases

    Hi,
    I am running a 11gR1 RMAN catalog.
    I am wondering if is it possible to change a default configuration setting in the RMAN catalog  so that all the new databases will inherit it.
    For example, I would like all the new databases registered to the catalog to have:
    BACKUP OPTIMIZATION ON
    RETENTION POLICY TO REDUNDANCY 7
    Thanks,
    massi

    No, the catalog cannot "dictate" configurations for databases.  Each database retains configuration in the controlfile and this can be updated only by an rman connection (i.e. rman connecting to the database as a target). The CONFIGURE command in rman is used to set a "permanent" configuration parameter for a database but must be issued for each database individually.
    Hemant K Chitale

Maybe you are looking for

  • Can not enable SandBox on mi Webcenter application

    Greetings i have developed a webcenter application ...and i have tried to enable sandbox in order to show a save button on my composer panel in edit mode...and a pop-up message to save changes if i close before clicking the save button. In the adf-co

  • RSCRM_BAPI - Extract Table

    Hi All, I am using  RSCRM_BAPI  to fetch data from query into extract table. The table name will be automatically assign pre-fix "/BIC/0C" in front of the customize table name. Thus, it is not allow to transport the table, may I know how to transport

  • Get error in AJRW - Fiscal Year change for Assets

    Dear Expert! I am facing with the following problem when run AJRW in Test Run mode. Company Code: 1000 Fiscal year: 2010 Fiscal year change statistics - Test Version Status    Company code    Read.....   Already changed.... To change.... Incorrect...

  • Cannot open the Time Machine Preferences

    I'm running into this new problem after upgrading a client MBP to 10.6.2. I get an error message when trying to open the Time Machine Preferences: The document "TimeMachine.prefPane" could not be opened. System Preferences cannot open files in the "M

  • Issues with VoLTE on SIM-Free iPhone 6 on AT&T

    I have noticed that AT&T does not appear to support VoLTE calls on the new SIM-free iPhone 6 (A1586).  I have a Verizon iPhone 6 (A1549) and just bought the new SIM-free iPhone 6. I can insert my Verizon SIM card into either phone and make calls over