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

Similar Messages

Starting Rman getting error PL/SQL package not current

I come across a problem. My server is windows 2003 and Oracle is 10g Release 2.
My previous DBA install Oracle 10g R1, 10gR2 and Oracle Data Warehouse Builder 10g on the same server at different Oracle_Home. When I came to this work. I tried to use Rman for backup. When i went to server command line, type Rman, Rman target /. the error message was:
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.02 in TARGET database is not current and PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.02 in TARGET database is not current.
I found the solution from oracle_metalink ( Note:429499.1). I followed note to use Oracle Universal Installer to move the 10.2.0.2 home. Then I can start Rman. Then I fixed some other small errors. I came back to loginto Rman. The system told me the same errors. I used Oracle Installer to check the Oracle_Home. Only two home exist. One is 10gR2 10.2.0.2. Another one is data warehouse builder with version 10.2.0.3. So it seems that 10gR2 Home is not current. How can I remove this Oracle_Home? If I remove it off, database will be dead. So if I remove oracle data warehouse builder, will it make two PL/SQL package for Rman current? or I have to remove DW builder first, then patch 10gR2 Home to 10.2.0.3? Please help. Thanks.

damorgan:
No. it is not related to oracle_home and oracle_sid. It is related to PATH setting. I have solved the problem. Thanks for your comment.

Can I use Other database as the repository, Sybase/SQL Server? Urgent!!!

Hi all,
Can I use Other database as the repository, Sybase/SQL Server? Urgent!!!
And Can I use other database store business data and sync with lite?
Thanks ahead!!!

Jonathan,
No, it is not possible to use any other database than Oracle (8.1.7) or later .
Oracle Lite will only work with Oracle.
Regards

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

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!
,

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.

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.

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

Reader 10.1.7 Windows xp, can't access at all just get message the patch package not recognised

Reader 10.1.7 with windows xp, can't access at all, or remove , just get message that patch package not recognised. Or else Runtime error Help please

Uninstall the corrupted Reader installation using http://labs.adobe.com/downloads/acrobatcleaner.html
then reinstall the latest version from http://get.adobe.com/reader/enterprise/

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.

One instance registered in two rman catalogs is possible?

Customer wants that one instance be registered in two different rman catalogs.
and perform two different backups.
There is a sincronism between control file and Catalog, what could mess it up having two catalogs. On the other hand there is the DBID who identify the database on each catalog.
Can anyone clarify if this is possible or not?
TX

Lalbuque,
RMAN performs a backup using a "Media Manager Layer" or "MML". There can only be one MML installed at once on a particular ORACLE_HOME and it seems that yours is TSM; you cannot run an RMAN backup to tape without an MML. This is true even if you backup WITHOUT a catalog so adding a second will not help.
There are a number of solutions to this problem. Here are a couple.
Firstly, you could backup your database to the non-TSM tapes without RMAN. You can do this either by shutting the database down first or you could put the database into backup mode for the duration of the backup. The former is simpler but a) requires an outage and b) requires you to be absolutely sure that your shutdown was clean. The latter requires some detailed knowledge of oracle backup concepts but avoids the other problems.
The second solution is to backup your database to disk with RMAN and then to copy the resultant files to tape.
Whatever solution you choose please bear three things in mind:
1) The purpose of backup is to recover. Make sure you have a documented recovery process and test it.
2) The use of a second catalog is not required.
3) Test your ability to recover. Have I said that already :-)
--Tony Hasler

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 ( CATALOG CREATION ) STEP BY STEP by Joel Pérez

Hi everybody
I am a person that answer questions for some forums here. I have seen that a lot of people get trouble to begin to work with RMAN and my purpose with this topic is to guide rookies and everybody that wants to learn a little bit more about usage of RMAN. I go to add the steps day by day. Enjoy it!
Please do not replay in this topic!!!
When I finish this article I am going to give you opportunity to give your opinions about this.
For complete reference for this theme go here:
Recovery Manager Quick Reference Contents / Search / / PDF
Recovery Manager Reference Contents / Search / Index / PDF
Recovery Manager User's Guide Contents / Search / Index / PDF
http://otn.oracle.com/pls/db92/db92.docindex?remark=homepage
Joel Pérez
http://otn.oracle.com/experts

Now, We have to get connection with the target database.
steps:
- Ensure the target database is started. In this case the database that will be the target database is : "LQACNS1"
- Get connect to the target database.
- Get connection to the database where the catalog is.
- Register the database in the catalog
This one of several methods to realize whether the target database is started.
[oracle@ozawa oracle]$ ps -ax|grep ora
16336 ? S 0:26 /opt/ora9/product/9.2/bin/tnslsnr LISTENER -inherit
16342 ? S 0:03 ora_pmon_LQACNS1
16344 ? S 0:39 ora_dbw0_LQACNS1
16346 ? S 2:36 ora_lgwr_LQACNS1
16348 ? S 0:17 ora_ckpt_LQACNS1
16350 ? S 2:21 ora_smon_LQACNS1
16352 ? S 0:00 ora_reco_LQACNS1
16354 ? S 0:04 ora_cjq0_LQACNS1
16356 ? S 8:55 ora_qmn0_LQACNS1
16358 ? S 8:58 ora_qmn1_LQACNS1
16360 ? S 8:53 ora_qmn2_LQACNS1
16362 ? S 9:00 ora_qmn3_LQACNS1
[oracle@ozawa oracle]$ export ORACLE_SID=LQACNS1
[oracle@ozawa oracle]$
[oracle@ozawa oracle]$
[oracle@ozawa oracle]$ sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Mon Mar 1 13:37:59 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> conn / as sysdba
Connected.
SQL>
SQL> select * from dual;
D
X
SQL>
- Working with the target database and the catalog to register the database.
[oracle@ozawa oracle]$ rman target sys@lqacns1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
target database Password:
connected to target database: LQACNS1 (DBID=1237456636)
RMAN>
RMAN> connect catalog rman/rman@ldevcard
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
- to start of this moment you can use RMAN to perform beckups of the target database.
Joel Pérez
http://otn.oracle.com/experts

Rman catalog error

Hi all,
when i'm trying to register a database in recovery catalog i'm getting the following error.
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-02291: integrity constraint (RMAN.RLH_F1) violated - parent key not found

Have a look at the thread and see if it would help you unregister it properly. It has works for various related errors
Grid Control and Rman Catalog

Can we put RAC database in Archivelog mode without shutting down

All,
Can we put RAC database in Archivelog mode without shutting down.
Currently our new production database (2 node RAC) is in no archive log mode, Need to enable archive log in the database...
I believe we need to set the cluster_database=false and then put the DB in archive log mode then we need to bounce the database to take effect...
Just curious to know in 11gR2 ...Can we put the RAC database in archive log mode without any downtime ...?

Even RAC or non-RAC, database should bounced and enable/disable archive log mode from mount status.

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

Similar Messages

Maybe you are looking for