A possible bug in RMAN CATALOG command in 10g on Linux (SLES9 SP3)

Hi,
I ran into this issue while using RMAN command "CATALOG DATAFILECOPY <filename> TAG <tagname>". In this instance, RMAN is actually trying to write 8K data at block 1. Since a copy is being cataloged, it doen't make any sense to modify it. Please note that this modification doesn't happen without TAG option. This behavious doesn't seem to be present on Oracle 9 on Solaris 8. For more details, please check the following thread:
help with RMAN CATALOG command
Thanks,
Raghu.

Hi Steve,
Unfortunately this is a bug, bug 3612370 in fact. I've published the bug so that it can be tracked via metalink if you have a support contract.
The bug is as you suspected with JDev's parse of the modules. We don't have a workaround at the moment but I'll post here again if we make any progress.
Thanks for reporting this,
Geoff
JDev Test Team

Similar Messages

Possible bug when using Key Command

Greetings,
Can someone confirm this behavior in Logic 9? When I'm editing a plugin and hit my key command to go to a location, enter the measure # and hit enter - all **** breaks loose. It's as though I'm scrolling through a bunch of screensets and the enter location window still stays on top.
Am I the only experiencing this? Misery sure does love company.
Cheers

fyi, it looks like this issue has been resolved with jdev 11.1.1.0.2 (Update 2)

RMAN - Cataloging a backupset

Hi all,
On 9i how i can include a backupset on RMAN catalog ?
On 10g I know that using this command bellow run ok.
catalog start with 'D:\backup\' noprompt;
can anybody help me?
Wander(Brazil)

You cannot catalog a backup set with Oracle 9i according to the documentation.

Need a create db script to manually create a 10g rman catalog db on unix

Hi, Gurus:
I would like to manually create a rman catalog database (Oracle 10g) on a HP-UX environment. Could anyone share a sql script to do that?
It is going to be used to backup about 15 databases directly to tape and the retention policy is going to be 35 days. How big the database should be?
Thanks in advance.

I can't find any documentation supporting Oracle support's theory.And who writes the Oracle documentation? People in this forum?
You got the "Best Practice" advise.
If you have rman catalog on the same server or on the same database, it is like storing your backup on the same server you took it from.
So, the idea od RMAN catalog is to have your catalog available for any recovery. If you cannot recover your recovery catalog, then you are better off using the controlfile as the repository.

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

Set RMAN catalog default setting for all databases

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

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

How to upgrade RMAN catalog from 10.2.0.4 to 11?

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

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

To Find the instance name in RMAN catalog

Hi ,
I have rman catalog which got registered 150 databases. Am able to get the dbname,id for the 150 databases but not able to get the server name (host name) of the correspoding databases in catalog views as well as in db views.
Kindly revert us if you know any other analyisis or way to find the server names.
Regards
Krishnan

What does RMAN care if RAC is involved or not?
Oracle provides RMAN for backing up and restoring the database. RMAN enables you to back up, copy, restore, and recover datafiles, control files, SPFILEs, and archived redo logs. RMAN is included with the Oracle server and it is installed by default. You can run RMAN from the command line or you can use it from the Backup Manager in Oracle Enterprise Manager. The procedures for using RMAN in RAC environments do not differ substantially from those for Oracle single-instance environments. Refer to the Oracle Backup and Recovery documentation set for more information about single-instance RMAN backup procedures.

Unregistering of a database from RMAN Catalog

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

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

How to get RMAN catalog information from Target database?

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

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

Can someone confirm a possible bug with Universal Access?

Can someone confirm a possible bug with Universal Access?
I have a Mac Pro 3,1, 10.7.1 but if you could confirm or not this possible bug with any model.
In Energy Saver preference pane:
Set Mac to never sleep.
Set Display Sleep to ~2 minutes.
In Desktop & Screen Saver:
Set screen saver to start at ~1 minutes.
In Universal Access:
Check Enable access for assistive devices.
Check radio button Zoom to On.
Zoom in window not checked.
Confirm that Zoom works by pressing:
⌥⌘= (option, command, =).
Set screen back to normal by pressing ⌥⌘-.
Let screen sleep after screen saver starts.
Wake screen and see if ⌥⌘= still works.
Thanks … Ken

Other than the time intervals (smallest Screen Saver kick-in is 3 minutes), it works fine for me - at least I can still zoom in/out after waking the display.
Tested on two different MacBook Pro models in 10.7.1

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

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

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

Our RMAN Catalog Problem

Hello
We have 7 major oracle instances on 2 servers and we have created a RMAN catalog on another server
Our principal databases are Standard Oracle 10g (10.2.0.2.0) under linux , and the catalog is Enterprise Oracle 10g (10.2.0.2.0) in Windows all the databases are registered in catalog when I query RC_DATABSE view it shows all
instances informations , in all RMAN login commands the "CATALOG" clause has been written
Now my problem is that just two of databases backups are recorded in catalog for example when I query "RC_BACKUP_SET" view it only contains backups of two databases while are backups have been performed completely without any error
Do you know what is problem ?
thank you

select dbid,name from rman_user.rc_database;
DBID        NAME
<h4>----------------  ----------------</h4>
1498968931       SCSDB
4293064263        SSTDB
861276728         SUBDB
2404423160        SAM
3976246282        SFIDB
1760672514    SCEDB
817528985        S900NS1
select t.name,t1.db_id,bs_key
from rman_user.RC_BACKUP_SET t1,rman_user.rc_database t
where t1.db_id=t.dbid;
NAME        DB_ID        BS_KEY
<h4>----------------  ----------------  ----------------</h4>
SUBDB        861276728        14366
SUBDB        861276728        14365
SUBDB        861276728        14364
SAM        2404423160        14491
SAM        2404423160        14490
SAM        2404423160       14489
select name, max(START_TIME)
from rman_user.rc_database d,
rman_user.rc_backup_set s
where db_id(+) = dbid
group by name
order by 2 desc;
NAME        MAX(START_TIME)
<h4>----------------  ----------------</h4>
SCEDB
S900NS1
SCSDB
SFIDB
SSTDB
SAM        6/14/2008 1:06:15 AM
SUBDB        6/13/2008 9:02:43 PM
This date (6/14/2008) is old because I haven't used the catalog for a long time, due to the problem I've mentioned above.
Edited by: TakhteJamshid on Jan 10, 2010 2:49 AM
Edited by: TakhteJamshid on Jan 10, 2010 3:00 AM

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

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

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

Creating RMAN catalog. Are these steps correct?

Are these steps to set up the RMAN catalog correct?
I.
The following two databases are the target databases which needs to be backed up.
1. a 11.1.0.7.0 database
2. a 10.2.0.1.0 databaseII.
Catalog schema in a 10.2.0.4.0 database called catdb.
III.
I am going to use the RMAN client(10.2.0.1.0) in my laptop (Windows Server 2003).
CATALOG schema creation
=======================
To create the Catalog Database (10.2.0.4.0), this what i am going to do in catdb
     a. create tablespace CAT_TBS
     b.     CREATE USER rman_cat_schema
          IDENTIFIED BY rman_cat_schema
          DEFAULT TABLESPACE cat_tbs
          TEMPORARY TABLESPACE temp
          QUOTA UNLIMITED ON cat_tbs;
     c.      GRANT create session TO rman_cat_schema;
     d.      GRANT recovery_catalog_owner TO rman_cat_schema;
     e.      GRANT execute ON dbms_stats TO rman_cat_schema;
   f. Invoke the <font color="red"><b>RMAN binary from my laptop</b></font> :
              C:\>set ORACLE_SID=catdb
           C:\>rman catalog rman_cat_schema/rman_cat_schema@catdb log=catalog.log
                           Hopefully Catalog will get the created at catdb .
Registering the database
=========================
To register the database,this is what i am going to do.
     a. Add the Tns Entry about the catdb in tnsnames.ora file of the target database
     b. Log in to target database's machine and invoke the<font color="red"><b> RMAN executable in the target database. </b></font>
        $ export ORACLE_SID=oraprod314
        $ rman TARGET / CATALOG rman_cat_schema/rman_cat_schema@catdb
             c. Then i can give the REGISTER DATABASE command. like
             $rman > register database;
        Edited by: Citizen_2 on 14-Sep-2009 11:46

Yes, You can connect to RMAN catalog using a lower version client. see this.
SQL> conn rman/rman@mycatdb
Connected.
SQL> select * from rcver;
VERSION
11.01.00.06
SQL>
rman
Recovery Manager: Release 9.2.0.7.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
RMAN> connect target /
connected to target database: STSTDB (DBID=2045697105)
RMAN> connect catalog rman/rman@abcd.
connected to recovery catalog database
RMAN>
You can take the backups and do recoveries. But, if you want to achieve certain features of the recovery catalog of higher versions to backup / recover your database, you better use the right RMAN client which allows the features to use.
It is always advisable to use the RMAN Client same as the database version you want to backup to avoid any confusions.
Hope it is helpul.
Regards
Edited by: vasu77 on Sep 15, 2009 10:01 AM
Edited by: vasu77 on Sep 15, 2009 2:11 PM

A possible bug in RMAN CATALOG command in 10g on Linux (SLES9 SP3)

Similar Messages

Maybe you are looking for