How to un-register target database in Catalog DB?

I am using 8.0.5. I create a Catalog database and register a target database with it for online backup. How do I un-register a target database from the Catalog DB if I do not want to continue taking backup? Is there any 'unregister' command?
Thanks in advance
- Sanchayan RoyChoudhury
Bangalore, India
null

Let me try...
If u know your dbid (which can be found out by just logging into rman with the target databasse)
login ot the catalog database throught sqlpplus as the catalog schema owner...
run the following query..
SELECT db_key, db_id FROM db WHERE db_id ="dbid just found";
then run
execute dbms_rcvcat.unregisterdatabase(db_key, db_id);
This will unregister your database from the catalog. however keep in mind that you will lose all records of your old backups..
HTH
null

Similar Messages

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 primary database to catalog database.

Hi all,
Here we have a dataguard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. Also we configured one schema on a third machine as catalog database using following steps.
The steps executed in catalog database(appsdb):
SQL> create tablespace rmancatlog_tbs datafile '/u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend off extent management local segment space management auto;
SQL> create user rman identified by oracle
2 default tablespace rmancatlog_tbs
3 quota unlimited on rmancatlog_tbs
4 ;
SQL> GRANT connect, resource, recovery_catalog_owner TO rman;
RMAN> create catalog;
recovery catalog created
Added tns entries of catalog database in primary and standby. Then from primary database we tried to register to catalog database. It is showing that it is registering. But every query afterwards in rman is throwing the error. Below are the steps and error:
[oracle@db1 ~]$ rman target sys/oracle catalog rman/oracle@appsdb
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: NIOS (DBID=1589015669)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 10/08/2012 06:16:06
RMAN-00600: internal error, arguments [8201] [] [] [] []
Can anyone help regarding this error?

on resync catalog it is throwing no output or error.
but it shows same error afterwards.
RMAN> resync catalog;
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of report command at 10/09/2012 03:55:53
RMAN-00600: internal error, arguments [8201] [] [] [] []

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

10204 catalog database 112 target database and OEM

catalog database is 10.2.0.4 on server CSERV
OEM server is 10.2.0.4 OSERV
target database is 11.2 on server TSERV
I ran the RMAN command from RSERV (v10204) and registered target database (v112) without error
I went into OEM->TARGET page ->Maintenance->Recovery Catalog Settings->
     selected Use recovery catalog
     (the correct catalog was listed in the drop down (CSERV:1521:RMANUSER-rman_schema1
     added the OS username/password for TSERV
     pressed 'OK'
The error that was returned was:
"Recovery catalog scheme version 10.02 is not compatible with this version of RMAN."
I'm sure i'm doing something stupid, but would really appreciate any help.....
Regards,
Susan

Hi Susan,
Probably you used a 10g rman client on the command line to connect to both the target (11.2) and the catalog (10.2.0.4) during registration.
(according to the compatibilty matrix this works).
Be aware:
When using an older version of the RMAN client with a newer version of the database, you do not get the features of the newer version.According to your own information Grid uses the 11gr2 software.
added the OS username/password for TSERVWhich is incompatible with the 10.2 catalog.
Unfortunately, we can't upgrade the catalog at this time.You can upgrade the catalog schema without upgrading the catalog rdbms (but probably you do not want to execute any change during xmas and new year).
Please check:
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsynta052.htm
Regards,
Tycho

How to remove a RAC database

Hi Guys,
We have some issues with ASM diskgroups and due to this the diskgroups holding a 2 node RAC DB are not mounted . We want to remove this database cleanly so that we can drop the troubled diskgroups and create new one.Unfortunately we dont have a backup of this database as it is not production.So how can we clean it from asm/crs - dbca needs the database to be up before it can be removed but becuase of asm issue and non-availability of backups,it can not be brought up!
Any suggestions would be appreciated.
Thanks.

Hi,
as database is mounted by RAC
1. shutdown node2 (database and ASM instance)
2. login to node1 , rman- drop database, which will drop all datafile, controlfile etc.
3. srvclt remove datase -d <db_name> : to remove from CRS reposioty
4. delete all parameter file or password file etc from $ORALCE_HOME/dbs
5. remove detail from /etc/oratab
5. drop ASM diskgroup
For more detail following metalink notes.
Note 239998.1: 10g RAC: How to Clean Up After a Failed CRS Install
Note:311350.1 :How to cleanup ASM installation (RAC and Non-RAC)
Note:251412.1 :How to Drop the Target Database Using RMAN
Regards
[email protected]

Registering DB in Recovery Catalog

how i can register DBs in Recovery Catalog, send commands plz

I'm very slow... Last time I was, remember, I am trying to pick up :)
Daljit Singh

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

Connecting to Catalog & Target Database

I am trying to register a target database with a recovery catalog. RMAN database and the catalog table space were created. When trying to connect to target with the SID set to the instance name and simply connecting as username/password, I am getting connected to the target. If I try to connect using the connect string, I get the following error
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-12154: TNS:could not resolve service name
But the TNS names have been properly configured and I am able to connect from sql*plus using the connect string.
Similarly I set the SID to RMAN database and try to connect catalog with username/password I am able to connect to Catalog and if I use connect string for the target, I am getting the same error as mentioned above.
I really do not know, How to resolve this and to connect to Target and RMAN databases simultaneously.

I suggest you do the following to see if the connect strings are really working, either:
1) Change ORACLE_SID to be of the catalog database, now do:
% sqlplus "<user>/<pwd>@<target string> as sysdba"
Does that work? If as I suspect it does not work or connects you to the catalog database (not the target), then it is a missconfiguration of the network files.
2) Do the same for connection to the catalog, set ORACLE_SID to be the one of the target database and do:
% sqlplus "<user>/<pwd>"
Does that connects you to the catalog?

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

Views to check the catalog database name from target database.

Hi,
Please help me to find view to check the catalog database name which is connected to my target database because I am new to the current environment where I am working now and the previous DBA have done the set up having 2 catalog database. I want view to check from target database, which can show the catalog database name to which it is connected to.
We can check the catalog database name from the following ways but I want views to check it from target database.
1.TNSnames.ora
2.Any backup script connecting to catalog database.
3.From catalog database we can use rc_database view to check the databases registered with the catalog database.

Please help me to find view to check the catalog database name which is connected to my target databaseYou can check for any RMAN backup jobs that been scheduled on the server.
In the scheduled script check rman command.
You can then identify the database alias (of the catalog db) that is used in the rman backup script.
Once you have found the database alias, check for the database alias entry in tnsnames.ora file present in your target database server.
Once the entry is found, you can find the IP address and catalog db name from the tns entry.
Edited by: st. osh on Nov 22, 2012 11:38 PM

Unable to register database in catalog into emrep

Hello guys,
I have a RMAN catalog in one server that works fine, now I tried to move this catalog to the emrep database (In this database I have the Grid Control), as I can´t use export / import because the original database is 10.1.0.5 and the emrep database is 10.1.0.4, I have created a new catalog into the emrep database.
The problem appear when I try to register one database on it:
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/15/2009 12:10:43
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
So, my first question is: Is possible create a RMAN catalog in the same database of Grid Control?
If this is possible, any suggestions that can help me to resolve this errors?
Thanks.

Hello Damorgan, thanks for your answer.
I follow the steps in a remote database ( BEEVODES ) which I want register into catalog ( tstsuse11-emrep ):
oracle@srvdb01 ~]$ echo $ORACLE_BASE
*/u01/app/oracle*
oracle@srvdb01 ~]$ echo $ORACLE_HOME
*/u01/app/oracle/product/10.1.0/db_1*
oracle@srvdb01 ~]$ export ORACLE_SID=BEEVODES
oracle@srvdb01 ~]$ rman target / catalog rman@tstsuse11-emrep
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: BEEVODES (DBID=822996874)
recovery catalog database Password:
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/16/2009 12:12:49
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
But I continue with the same error.
I supose the instalation of emrep is ok, because the Grid Control ( installed there ) works fine.
Thanks again.

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

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

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]

How to un-register target database in Catalog DB?

Similar Messages

Maybe you are looking for