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.

Similar Messages

  • 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

  • Create a clone database form rman catalog !

    Dear Friend ,
    I have a rman catalog database . I am using this rman catalog for against a database name 'testdb' . Everyday I take rman full backup of the testdb using the catalog database .
    Now I create a another database which will be the clone of the testdb . I want to create it using that rman catalog database . Can I create a new database using the catalog database ?
    If yes, then plz help me to give some directions .....

    Check here:
    [http://www.shutdownabort.com/quickguides/clone_rman.php]
    [Duplicating a Database with Recovery Manager|http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmdupdb.htm#441628]
    Oracle documentation Link added.

  • RMAN: To Register 8i Database in 9i Catalog

    Dear friends,
    I am working with Oracle 9.0.1.1 under W2K. Recently I configured Recovery Catalog database in our 9i server. Now I wanted to register two target databases that are running in another server Oracle 8i (same network).
    When I tried to register, I encounter the error like "RMAN version not combatible with Oracle 9.0.1.1 ... Target database version is too old"
    Is it possible to register the target database 8i into 9i catalog??? If not, what could be the alternative?
    Thanks in advance,
    M M Sheriff

    Hey Sheriff,
    have a look at the link below. It shows you all the compatibilities of RMAN catalog and target databases
    and executables. I'm sure that you can use the 8i catalog and executable for oracle9i targets.
    Hope this was a little helpful...
    Cheers,
    Ralf
    http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=73431.1

  • V10.2.0.5 and Database Target Recovery Catalog Assignments

    We recently upgraded to version from version 10.2.0.4 to 10.2.0.5. After, I started to continue where I left off with assigning recovery catalogs to our database targets. What was a simple process previously, is now becoming a headache. First, when adding an already registered recovery catalog I received this message "The specified username does not match the recovery catalog username configured for this database.". I was then told by support to update the back-end repository tables to make the recovery catalog username lowercase. This didn't work so I removed the registered catalog and attempted to add it back. Then I received this message which is rather frightening:
    "In this version of Enterprise Manager, recovery catalog settings are now specific to each Enterprise Manager user. Existing recovery catalog settings made prior to upgrading Enterprise Manager have been preserved in order to allow existing backup jobs to continue to work. However, if you change the recovery catalog setting for this database, all non-user-specific settings will be removed, and each Enterprise Manager user that manages this database will have to individually reset their recovery catalog settings for this database. Do you want to continue?"
    I can't find any mention of this change in any updated documentation, support page, or other. Essentially, this tells me that as of GC version 10.2.0.5, assignment of a recovery catalog to a given database target is no longer centralized but de-centralized. Each user with OEM GC now has to assign a recovery catalog to each database instance irregardless if their profile is setup as a Super Admin. Or, if you expect to run a manaul backup for a given database you have to log in under a shared account which has all the catalogs assigned which defeats the purpose of any SAS 70 auditing.
    I have a ticket in with Oracle support at this time. If anyone has any insight to this I would love to know the reasoning behind it. Thanks.

    Well, product development responded with this:
    "The catalog management model has been changed in 10.2.0.5GC to
    accommodate new database catalog features and enhance security.
    Each team member would have to register the catalog separately for the
    targets they manage, through their own EM account. This is a one-time
    activity. Once that is done, the functionality is the same as before."
    What a huge faux pas.

  • Backup and restore to the other database with Recovery Catalog

    Dear All,
    i need your help about recovery catalog.
    I have 3 databases, 2 databases version are 8.1.7.3 (HostA and HostB) and other database is 9.2.0.6 (as Catalog Database)
    I want to backup files from HostA with Catalog Database into tape, then restore the backup files into HostB.
    Please suggest me how to do this.
    Best Regards,
    abip

    you can achieve this with the rman duplicate command.
    if you have the same directory structure then it is a relatively simple task, if the directory structure is different then you need to use the
    'set newname' syntax.
    regards
    Alan

  • Error while Registering the Database with Catalog..

    I m creating recovery catalog in same database, and getting the errors.
    1. I have created TOOLS tablespace
    2.CREATE USER RMAN2
    SQL> CREATE USER rman IDENTIFIED BY cat
    2 TEMPORARY TABLESPACE temp
    3 DEFAULT TABLESPACE tools
    4 QUOTA UNLIMITED ON tools;
    CREATE USER rman IDENTIFIED BY cat
    ERROR at line 1:
    ORA-01920: user name 'RMAN' conflicts with another user or role name
    SQL> ed
    Wrote file afiedt.buf
    1 CREATE USER rman2 IDENTIFIED BY cat
    2 TEMPORARY TABLESPACE temp
    3 DEFAULT TABLESPACE tools
    4* QUOTA UNLIMITED ON tools
    SQL> /
    User created.
    3. GRANT RECOVERY_CATALOG_OWNER
    SQL> GRANT RECOVERY_CATALOG_OWNER TO rman2;
    Grant succeeded.
    4. To create the recovery catalog:
    1. Connect to the database that will contain the catalog as the catalog owner.
    H:\>rman catalog rman2/cat@rock
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 10:45:52 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to recovery catalog database
    2. Run the CREATE CATALOG command to create the catalog.
    RMAN> CREATE CATALOG;
    recovery catalog created
    3. Optionally, start SQL*Plus and query the recovery catalog to see which tables were created:
    H:\>sqlplus
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 5 11:53:36 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Enter user-name: rman2/cat
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> select count(*) from cat;
    COUNT(*)
    91
    SQL> ed
    Wrote file afiedt.buf
    1 select owner, table_name, tablespace_name
    2 from dba_tables
    3* where table_name='DB'
    SQL> /
    OWNER TABLE_NAME
    TABLESPACE_NAME
    RMAN2 DB
    TOOLS
    RMAN DB
    ABAMCO_TEST
    Next step is to registering the Database in the Recovery Catalog.
    Registering a Database in the Recovery Catalog
    H:\>rman TARGET / CATALOG rman2/cat@rock
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 11:56:09 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-01031: insufficient privileges
    I m getting above error while registering the Database with Catalog,
    Can anybody help me how can I register the Database with Catalog.????
    Waiting for Reply!!!!!!!

    Dear Manoj I can log in at TARGET Database.
    H:\>rman
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Sep 5 12:41:59 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN> connect target sys/rock
    connected to target database: ROCK (DBID=3255117147)
    RMAN>
    ============================================================
    USING CONNECT STRING as you said.
    H:\>rman target "sys/rock@rock as sysdba" catalog rman2/cat@rock
    Argument Value Description
    target quoted-string connect-string for target database
    catalog quoted-string connect-string for recovery catalog
    nocatalog none if specified, then no recovery catalog
    cmdfile quoted-string name of input command file
    log quoted-string name of output message log file
    trace quoted-string name of output debugging message log file
    append none if specified, log is opened in append mode
    debug optional-args activate debugging
    msgno none show RMAN-nnnn prefix for all messages
    send quoted-string send a command to the media manager
    pipe string building block for pipe names
    timeout integer number of seconds to wait for pipe input
    checksyntax none check the command file for syntax errors
    Both single and double quotes (' or ") are accepted for a quoted-string.
    Quotes are not required unless the string contains embedded white-space.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00552: syntax error in command line arguments
    RMAN-01009: syntax error: found "as": expecting one of: "append, at, auxiliary, catalog, cmdfile, clone, checksyntax, debug, log, msglog, mask, msgno, nocatalog, pipe, rcvcat, script, slaxdebug, send, target, timeout, trace"
    RMAN-01007: at line 0 column 16 file: command line arguments
    H:\>rman
    It didnt work either.
    I have only one database rock, and created recovery catalog in it. I want to register rock database with recovery catalog.

  • Registering recovery catalog in Enterprise Manager

    Hi,
    I created recovery catalog database successfully using RMAN of 10g R2 on command prompt. Every thing seems working fine on RMAN but when I connect to target database using EM and click the recovery catalog link, it does not show me the configured recovery catalog. When I try to configure the catalog, it gives me the error message "Bad Packet". I dont what the problem is. Can any one help me with this?

    Hi,
    I am using winXP and using EM DB of Oracle 10g. I used RMAN on command prompt and created recovery catalog by creating a recovery catalog user and assigning a catalog user to it. I have also registered target database with recovery catalog. Now all this is working on command prompt using RMAN utility. Both target and recovery are on one computer. Now when I try to see recovery catalog in EM DB, its says no recovery catalog has been configured and when I try to configure recovery catalog, following error message keeps coming
    Validation Error
    Examine and correct the following errors, then retry the operation:
    Error - java.sql.SQLException: Io exception: Bad packet type
    *Host--------- shahnawaz 
    * Port---------5500
    * SID-----------qasimdb
    * Recovery Catalog Username-----zee
    * Recovery Catalog Password------zee
    I hope my question is quite clear. If you need more info. just let me know please. I will appreciate.
    regards,
    Qasim

  • Config recovery catalog database

    dear all.
    i had read several documents about "create recovery catalog", but all of that start with statement
    CREATE TABLESPACE
    ...and continue with CREATE USER, etc.
    I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
    thanks
    The version is ORacle 10gr2

    hi,
    the recovery catalog is just a normal database with a schema called rman or whatever you choose.
    it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
    schema creation assumming windows O/S
    -- Create tablepsace to hold repository
    CREATE TABLESPACE "RMAN"
    DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
    AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    -- Create rman schema owner
    CREATE USER rman IDENTIFIED BY rman
    TEMPORARY TABLESPACE temp
    DEFAULT TABLESPACE rman
    QUOTA UNLIMITED ON rman;
    GRANT connect, resource, recovery_catalog_owner TO rman;
    then create the recovery catalog
    C:>rman catalog=rman/rman@w2k1
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN> create catalog tablespace "RMAN";
    recovery catalog created
    RMAN> exit
    Recovery Manager complete.
    C:>
    then register your database
    C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: W2K2 (DBID=1371963417)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    let us know how you get on.
    rgds
    alan

  • Recovery catalog, target database.

    Hello all,
    I have a question concerning recovery catalog.
    Can i use the same database as recovery catalog and target database?
    Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?
    Regards,

    NB wrote:
    Hello all,
    I have a question concerning recovery catalog.
    Can i use the same database as recovery catalog and target database?
    Let us say that i have a database orcl, can this database be the target and the recovery catalog at the same time ? is there any disadvantages?Yes you can use the same database as the recovery catalog but that's going to be a wrong decision. Think about this, you have lost your target database and since you had your recovery catalog also stored in it, now that's also gone! So a good thing or bad thing it would be ?
    Edit:
    Please read the same from the docs,
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmcatdb.htm#CHDECBEH
    Do not use the target database to be backed up as the database for the recovery catalog. The recovery catalog must be protected in the event of the loss of the target database.Aman....
    Edited by: Aman.... on Aug 7, 2011 4:26 PM

  • Resync recovery catalog with controlfile

    Oracle :10.2.0.2
    os : solaris 5.10
    When doing stage refresh with production using RMAN a small pitfall happen.
    By mistake i have connected to the stage database and production recovery catalog. This was done after changing the db name for stage database. Recovery catalog has taken this as new incarnation. The stage database opened with resetlogs after refresh. The db id's of both the incarnations are same.
    DB_KEY DBID DBINC_KEY NAME CUR
    1 3582966461 2 PRD NO
    1 3582966461 578463 STG YES
    Could anyone help me to resync the recovery catalog with old incarnation with production database.
    Help needed ASAP.
    Thanks

    Hi,
    We are following the rename datafile and then switching and opening the db with resetlogs. In this scenario we are only changing the db name not the dbid.
    If it is not for a restore test the duplicate command previously mentioned does everything for you. If you want to proceed manually change the DBID manually after the restore.
    Any further suggetions to resolve my issue.
    The suggested unregister/register failed ? Catalog is just an optional help, losing data from the catalog does not compromise the possibilities of restorations.
    Best regards
    Phil

  • To calculate the size of backup for a particular database in RMAN catalog

    Hi ALL,
    Could you please guide me how I can calculate the size of backup data for a particular database in Recovery Catalog, if I am using Tapes as my backup media for recovery catalog.
    Regards
    Harpreet Singh

    Hi,
    I am not Up to the mark of your question ..
    If you see the V$log you can get it.. Size of the redo logs can be determined either by examining the file system size or by reading the BYTES column on the V$LOG view. Then Check the number of redo Logs avaialble checked whether they are mirrored or etc., Combining the two figures we have a total redo log data at peak in one day. This is the amount of data that any backup facility or storage of Archive Redo Logs would have to take into account. This figure should be mitigated against the fact that manual switching of redo logs means that not all archived redo logs will be the full size.
    - Pavan Kumar N

  • Report from recovery catalog

    Hello
    How can I see the backup interval, database versions of the databases in recovery catalog ?

    adam wrote:
    Hello
    How can I see the backup interval, database versions of the databases in recovery catalog ?Which database interval, versions you want to check? Check for the views starting from rc_ and you would get to know all about recovery catalog.
    Aman....

  • How to find databases registered in recovery catalog!

    I want to know how many databases registered in recovery catalog
    How can i find it?
    Thank you!

    Log in as your catalog owner and execute select distinct db_name from dbinc; with this you will see all registered databases , In 11G onwards as virtual catalog owner you will only see the databases on which you have been granted access.
    Regards
    Karan

  • Clone from recovery catalog

    Hi,
    Every month i am doing duplicate from prod to test database,from coming month i have to change my strategy to do clone from standby instead of production.so i have created recovery catalog and registered my standby.my queston ,is it possible to do duplicate from recovery catalog to test database.if possible,this is my connection
    rman catalog rman/rman123@catdb auxiliary /;,and i should do any modification in Recovery catalog. pls suggest me to do the cloning from RC.if possible
    my database 10.2.aix server.
    Regards
    Faruk

    You can use a recovery catalog when doing a cloning / DUPLICATE.
    Note, however, the 10.2 restrictions on the DUPLICATE Command : http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta028.htm#RCMRF126
    You must be connected to both the target database and auxiliary instance. The auxiliary instance must be started with the NOMOUNT option, and the target database must be mounted or open. The target database cannot be a standby database.
    Hemant K Chitale

Maybe you are looking for