RMAN catalog and Target database

Hi All,
Please clarify my below doubts.
We have one server "server1" with oracle (catalog database) version 10.2.0.1
I have server "server2", and we have four oracle homes with four oracle users.Each oracle home consist of one database. all database are with 10.2.0.3 version.
All these databases registered with the above catalog database.
1 -> Can we register databases with a lower catalog database.
2 -> Now we are upgrading one database to 10.2.0.5 (in server2), in upgrade step we need to action step -: catalog upgrade. If we run this command actually what will be the result?
3 -> We are upgrading only one database in server2. remaining 3 database are in the version 10.2.0.3, upgrade catalog command will upgrade catalog database to 10.2.0.5 version, am I right?
4 -> Here do I need to run upgrade catalog ?
Thanks,
Asim
Edited by: user229955 on Feb 25, 2012 4:18 PM

Please refer this MOS document *RMAN Compatibility Matrix [ID 73431.1]*
You would surely get your answers if you mark your previous questions as answered rather than keeping it open.

Similar Messages

Rman backup to be stored on other machine than catalog and Target database

I have target database on machine A, catalog on machine B. I am executing RMAN from machine B but want to store RMAN backup on machine C. is it possible.

Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: NEFT (DBID=3608824086)
connected to recovery catalog database
RMAN> run{
2> allocate channel c1 device type disk format '\\bobfs\f\RMAN\data\neft\Rman_NEFT_%U';
3> backup full database;
4> backup current controlfile;
5> }
6>
allocated channel: c1
channel c1: sid=16 devtype=DISK
Starting backup at 15-OCT-08
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00011 name=F:\DATABASE\NEFT\DATABASENEFT_DATA1.DBF
input datafile fno=00015 name=F:\DATABASE\NEFT\UNDOTBS.DBF
input datafile fno=00013 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_DATA1.DBF
input datafile fno=00002 name=F:\DATABASE\NEFT\UNDOTBS01.DBF
input datafile fno=00001 name=F:\DATABASE\NEFT\SYSTEM01.DBF
input datafile fno=00014 name=F:\DATABASE\NEFT\DATABASENEFT_ARCH_NDX1.DBF
input datafile fno=00005 name=F:\DATABASE\NEFT\EXAMPLE01.DBF
input datafile fno=00012 name=F:\DATABASE\NEFT\DATABASENEFT_NDX1.DBF
input datafile fno=00010 name=F:\DATABASE\NEFT\XDB01.DBF
input datafile fno=00006 name=F:\DATABASE\NEFT\INDX01.DBF
input datafile fno=00009 name=F:\DATABASE\NEFT\USERS01.DBF
input datafile fno=00003 name=F:\DATABASE\NEFT\CWMLITE01.DBF
input datafile fno=00004 name=F:\DATABASE\NEFT\DRSYS01.DBF
input datafile fno=00007 name=F:\DATABASE\NEFT\ODM01.DBF
input datafile fno=00008 name=F:\DATABASE\NEFT\TOOLS01.DBF
channel c1: starting piece 1 at 15-OCT-08
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 10/15/2008 10:45:38
ORA-19504: failed to create file "\\bobfs\f\RMAN\data\neft\Rman_NEFT_7qjt6tat_1_1"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
Recovery Manager complete.
I am executing rman from catalog machine,
WHen i give path \\bobfs\f\RMAN\data\neft\ in start-> run it is accessible from there.
I cant understand why rman is not abl to create file there.
full rights are given to user. and user on rman catalog and network machine is same having same password

Informatica Repository and Target database

I have a scenario in which the repository database is DB1 and target database is DB2. How is that possible? I mean isnt the target database stored in the repository? Is it still alright?

Hi,
Informatica repository tables generally referred as OPB tables and which has all the data related to your mappings and by using these tables informatica will refer the mappings.
Thanks,
Navin Kumar Bolla

Rman problem with NLS_LANG mismatch b/w catalog and target DB

Hi,
I have target database NLS_LANG set to 'AMERICAN_AMERICA.JA16SJIS' and recovery catalog NLS_LANG set to 'JAPANESE_JAPAN.JA16EUC'. When backup is started the rman fails with the following error.
<----
RMAN-00571:
===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
===============
RMAN-00571:
===========================================================
RMAN-03002: failure of allocate command at 11/26/2007 11:22:41
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel
at
11/26/2007 11:22:41
ORA-06502: PL/SQL: numeric or value error
------>
It works fine if I change the recovery catalog NLS_LANG to 'AMERICAN_AMERICA.JA16SJIS'
Any help could be appreciated.
Thanks,
Prince

Hello Faust,
have already tried that in SQLPlus, SQLWorksheet, MS Access (OffXP). All apps used on the same computer. OS Win XP Prof.
Result in Plus and Worksheet
40 ! â a a î l c ç i Ä . < ( + ! 50 ! & e e e i n k g Ü $ * ) ; ^ 60 ! - / Â A A Î L C Ç I ö , % > ? 70 ! E E E I N K G ` : § ' = " 80 ! a b c d e f g h i [ ] g @ 90 ! ° j k l m n o p q r º ¿ A0 ! µ ß s t u v w x y z G ¿ B0 ! 0 1 2 3 4 5 6 7 8 9 a ß ¿ d e ¿ C0 ! ä A B C D E F G H I � t õ D0 ! ü J K L M N O P Q R · u i s u E0 ! Ö S T U V W X Y Z ² � T Õ F0 ! 0 1 2 3 4 5 6 7 8 9 ³ U I S U
result in Access (via ODBC Con)
40 ! â ą ā î ļ č ç ī Ä . < ( + ! 50 ! & ē ę ė į ņ ķ ģ Ü $ * ) ; ^ 60 ! - / Â Ą Ā Î Ļ Č Ç Ī ö , % > ? 70 ! Ē Ę Ė Į Ņ Ķ Ģ ` : § ' = " 80 ! a b c d e f g h i [ ] ğ @ 90 ! ° j k l m n o p q r º ≙ A0 ! µ ß s t u v w x y z Ğ Δ B0 ! ₀ ₁ ₂ ₃ ₄ ₅ ₆ ₇ ₈ ₉ α β γ δ ε ω C0 ! ä A B C D E F G H I ţ õ D0 ! ü J K L M N O P Q R · ų ı ş ū E0 ! Ö S T U V W X Y Z ² Ţ Õ F0 ! 0 1 2 3 4 5 6 7 8 9 ³ Ų İ Ş Ū

RMAN incompatible with TARGET database

I have two databases:
The database with the catalog, version 8.1.7.
The database to be backed up (target), version 8.0.6.
When I try to connect to the target, I get an error stating: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
I've tried changing the "compatible" parameter to 8.0.4, but then I get an error when I restart the database (regarding locally managed tablespaces, which I am not using).
Any idea what I need to do to connect to the target database?
thanks....

Hi !
I guess you have confused the compatible init.ora parameter with RMAN compatible parameter ,
They are entirely different. The excerpts here, which i have taken from the Oracle online docs should
clear your problem.
The compatible parameter specifies the minimum acceptable release of the RMAN executable that can function with the catalog. For example, if the recovery catalog compatibility is set to 8.1.4, then only an RMAN executable of release 8.1.4 or later can connect to the catalog.
You cannot set the compatible parameter to a version that is not supported by the currently-installed DBMS_RCVMAN or DBMS_RCVCAT packages. If you try to set compatibility to a version that is not supported by one of the packages, then you receive an error message that indicates the lowest and highest value you can set, as in the following example:
RMAN> configure compatible = 8.0.1;
RMAN-03022: compiling command: configure
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06455: illegal compatible value 8.0.1: must be between 08.00.04 and 08.01.06
To view the compatibility level of the recovery catalog:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start a SQL*Plus session and connect to the recovery catalog database as the recovery catalog owner. For example, enter:
SQL> connect rman/rman@rcat
Issue the following query:
SQL> SELECT value FROM config WHERE name='compatible';
VALUE
080106
To create an 8.1.6 recovery catalog that is usable with a pre-8.1.6 RMAN executable:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This procedure assumes that you have the use of both an 8.1.6 and pre-8.1.6 RMAN executable. The method employed it to use a pre-8.1.6 RMAN executable to create the recovery catalog, and a release 8.1.6 RMAN executable to upgrade it. The compatibility level is automatically set to 8.0.4, which has the implications described in Table 3-1.
Use a pre-8.1.6 RMAN executable to connect to the catalog database. For example, enter:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.5.0.0
RMAN-06008: connected to recovery catalog database
Create the recovery catalog and then exit. For example, enter:
RMAN> create catalog;
RMAN> exit
Note:
If you use a release 8.0 RMAN executable to create the catalog, you must use the catrman.sql script to create the recovery catalog.
Use the 8.1.6 RMAN executable to connect to the newly created recovery catalog:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0
RMAN-06008: connected to recovery catalog database
Upgrade the recovery catalog to release 8.1.6:
RMAN> upgrade catalog;
RMAN> exit
The compatibility level of the recovery catalog is now automatically set to 8.0.4.
Regards,
Mohamed Iqbal.
[email protected]

Rman repository and target

Hi,
my RMAN repository is in 10g R2, and target is in 8.1.7.4. I want to know when I backup by RMAN what would be the RMAN version executing the job ? RMAN 8.1.7 or RMAN 10g ? Thanks and regards.

Yo would be using the RMAN executable in the target ORACLE_HOME (ie, RMAN would be 'local' to the database).

Issue in OWB mapping - when changing source and target database

Hi,
I need help for resolution of the issue I am facing when moving mapping from development environment to QA.
Here is situation,
We develop ETL using one source, one staging and one target database.
In development we use one control_center for Source to staging and another control center staging to target.
All works fine in development.
Now I have created new runtime repository and imported all OWB projects (with full dependencies, exact replica of development). Now I need to change source and staging and target as different database.
I have created new database location connections and defined/attached DB connectors with stage and target location.
Now issues are
1.     Two Staging mapping are not able to bound with source table (giving different error
a.     One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b.     Other mapping show error for source table/object not bound to repository
2.     All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
Not sure how to proceed from here.
I have recreated new repository and re-imported all project/mappings and defined all connection but still same issue.
Thanks in advance,
Vipin

1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
The above error were resolved when re-synchronized the table (for few I have to reimport the table) and mapping.
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
The above error still pending. My target mapping are not able to deployed/compiled.
For the above I have defined one Staging location to one target target location and target location have connector to staging (not sure if I have to define connector name same as staging location, as I have created DB connector with different name but reference database is same as staging location).
Mapping are assoicated with desired data locatoin and meta data.
control center is also have that data location.
Mapping are configured for the desired location.

One problem with constraints missing in source and target database....

DB Gurus,
In my database I am going to export and import data using datapump but dont specify CONTENT clause.
so when I start working on my application, I came to know there are some constraints are missing. now how to check what are the constraints are missing from Source database and how to create those missing constraints on Target database?
Suggest me if you have any idea.

Create a database link between source and target schema.
Use all_/dba_/_user_constraints to generate the difference using MINUS operator.
something like this:
select owner,constraint_name,constraint_type from dba_constraints@source
MINUS
select owner,constraint_name,constraint_type from dba_constraints

Remove RMAN information from target database control file

Dear Gurus,
Can any one inform me that how I can remove RMAN related information from Target database control file without recreating the control file.
Regards,
asif

I want to remove all RMAN related infromation from control file including the destination specification where backup sets were being created becuase that destination is no more available,
configuration information also need to be removed from control file without recreating the control file.
kindly help,
regards,
asif

Slow rman backup and slow database

Hello all,
Whenever I run rman backup to sbt_tape, the complete database becomes slow. Also RMAN takes more than 12 hours to complete.
RMAN script is:
run {
allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
sql 'alter system switch logfile';
backup incremental level 2 tag 'db_level2_backup'
format'%d/INC2/%t/%s/%p'
database diskratio=0;
backup
format '%d/LOG_INC2/%t/%s/%p'
archivelog all
delete all input;
release channel t1;
}The AWR shows following "Top 5 timed events"
Event                                      Waits     Time(s)     Avg Wait(ms)     % Total Call Time     Wait Class
db file sequential read                    817,467     17,419         21                         28.6         User I/O
CPU time                                  14,294                              23.5
log file sync                            141,642     8,570         61                         14.1          Commit
enq: TX - row lock contention              3,371     7,171       2,127                          11.8         Application
log file parallel write                     149,486     5,356         36                           8.8           System I/OWhat can be done? Can anyone tell what wrong is happening here?
Database is 10.2.0.4
OS is AIX 5.3
SGA_TARGET is 6G
PGA_AGGREGATE_TARGET is 2G
Total physical RAM is 12G
EBiz application is running in the same server
Regards,
SA

On my server, we needed to adjust the vmm on aix for oracle to run best. Before I did that it was really slow.
http://www.ibm.com/developerworks/aix/library/au-aixoracle/index.html
Specifically these as outlined in the document linked above:
Listing 3. Changing the default setting for the lru_file_repage parameter using vmo
root@lpar21ml16ed_pub[] > vmo -o lru_file_repage=0
Setting lru_file_repage to 0
root@lpar21ml16ed_pub[] >
Setting this to 0 tells the VMM that you want to steal only file pages and not computational pages. As this will change if the numperm < minperm or > maxperm, we will make maxperm high and minperm very low. Years ago, before the lru_file_repage parameter was introduced, we used to make maxperm low. If we did this now, we would stop the application caching programs that are currently running.
Listing 4 shows how we'll set these parameters:
Listing 4. Setting the minperm, maxperm and maxclient parameters
vmo -p -o minperm%=5
vmo -p -o maxperm%=90
vmo -p -o maxclient%=90
We also want to take a look at minfree and maxfree. When the pages on our free list fall below minfree, the VMM will start to steal pages, which we don't want to happen until the free list has beefed up the number in maxfree. The values should be similar to the ones shown in Listing 5.
Listing 5. Setting the minfree and maxfree parameters
vmo -p -o minfree=960
vmo -p -o maxfree=1088
Edited by: user455434 on Oct 12, 2010 1:14 PM

How to hide Segementation Catalogs and Target Levels ...

Hi Team,
we tried to hide the out of box segmentation catalogs as we have designed our own customized Segmentation catalogs. But even after disabling Everyone option it is showing up in the target level.
Similarly we tried to hide the Default Account andn Asset Target Level but in vain.
Kindly provide the insight into this.
Regards,
Mohan

Hi,
The catalog hiding feature can also be done during the repository configuration.
1. if you using 10g OBIEE Admin tool, go to Manage --> Marketing Manager
2. Go to Target level on which you want to hide the catalog
5. Remove the catalog from the list in the pop up window comes out.
Hope this is the answer you intended. :)
- Madasamy

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

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

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

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

RMAN catalog and Target database

Similar Messages

Maybe you are looking for