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

Similar Messages

  • 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.

  • Backing up the RMAN catalog database

    Version: 10.2.0.1.0
    We have created a database to host our RMAN catalog. This catalog holds backup info plus RMAN stored scripts for 5 production databases . Now, we need to backup this RMAN catalog database.
    I am going to use the control file as the catalog (ie. NOCATALOG) for our RMAN catalog database. This should be fine. Right? Any best practices i should follow regarding this?

    Sometime back I had the same question.
    What I decided was cold backuo and RMAN using the control file. (A Belt-and-suspenders approach)
    I also do an export daily after all the other backups are done.
    In addition I keep an information on it, location and size of all files, a current PFILE (it does not change much), what patches etc.
    Given its tiny footprint it would be easy to rebuild given all this.

  • RMAN restore problems

    Hello,
    I have an 11.2.0.1 database (archive mode) on a windows server 2003 R2 32b. The database does backups via RMAN (catalog on other server for that purpose) with NMO (legato networker) and it work fine. But we can't restore the backups. It may be a problem with the database, but it seems more a Media Manager problem. The fact is that when we try to restore, RMAn hungs waiting for recover (without any error, just stays forever until killed), and a session on our backup server remains browsing. It happens also if we make a restore validate. On the other hand, if you make a crosscheck, it works fine.
    As I said, it's very strange, and I think it's an issue with the configuration of the networker, or even the server, but I post here looking for advice, or maybe someone has seen something like this before.
    Any advice would be apreciate, since the only option we have now, it's to reinstall the whole server (OS and database) from a cold backup (copy of datafile,ctrl,...)
    Thanks
    Edited by: Naerbon on 22-mar-2011 8:11
    By the way, we've made some tests:
    - backup and restore with diferent versions of networker client and NMO (thought they were on latest release). Same result.
    - We've created a new instance on that server, blank, and registered new in the catalog. Same, backups, but cannot restore. With this, we've discarted the database issue...
    Edited by: Naerbon on 22-mar-2011 8:21

    Hi,
    yes, the problem was in the comunication between the Media Manager and the client. On the way to the MM, it was all ok, but in the opposite way, MM looked just for 'server' and couldn't find it. Adding the alias on the /etc/host, MM could find the 'server' as it has then 'server.domain'
    As for the scrip, I'll post here the script used for duplicating the prod database on a new installed desa machine. Solved the comunication issue, it worked more than fine.
    run
    set until time "to_date('Mar 20 2011 23:30:00','Mon DD YYYY HH24:MI:SS')";
    allocate channel ch1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=bckservr.privada,NSR_CLIENT=origsrvr.privada, NSR_DATA_VOLUME_POOL=poolBCK)';
    allocate auxiliary channel ch2 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=bckservr.privada, NSR_CLIENT=origsrvr.privada, NSR_DATA_VOLUME_POOL=poolBCK)';
    DUPLICATE TARGET DATABASE TO DBSIDDES;
    With this script we duplicated de database with SID DBSIDPRO in the server origsrvr, to the server destsrvr with SID DBSIDDES. We used a set until time, so we take the last cold backup make this weekend.

  • SQL Reports Bad Idea Against RMAN Catalog?

    11.2.0.1 SPARC 64
    We use OEM to manage/execute our backups. The MML is NetBackup. One downside to this is that the "job" within OEM executes the backup for 20+ databases. In a serial fashion the backups occur in NetBackup...but most are queued - they throttle through and over time they complete. To this end, we have no way of seeing the true backup duration. We know the rman start and completion times, but they're not "actual."
    I started looking at creating a sql statement/report/[pl/sql] block that would give us the granular informatin on the true timings of the backup "pieces" as they relate to a "set."
    Research out on the wire shows a number of high level solutions, but nothing to which a report shows the data files, etc. Usually when I see this I start to question..."hey, is this even a good approach?"
    I do realize that through the RMAN utility there are a number of reports which are available...this post, however, is focused on the idea of sql reports against the rman catalog.
    Any advice would be welcome.
    Conceptual report:
    -> INCREMENTAL LEVEL 0
    --> BACKUP SET
    ---> BACKUP PIECE
    ----> HANDLE, TAG, DATAFILE, START, COMPLETION
    I'm NOT looking for the sql...I can work that out, I just want to know if this is a smart approach or best to stay out of the catalog.
    -abe
    Boulder, Colorado
    Edited by: user10863631 on Mar 10, 2011 7:43 AM
    Edited by: user10863631 on Mar 10, 2011 7:56 AM

    I think this is the wrong forum for such a question. The Database - General (General Database Discussions might be better suited. Or maybe the RMAN forum (Recovery Manager (RMAN)

  • 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

  • Why use RMAN CATALOG ?

    Hi,
    Anybody tell me why use RMAN CATALOG and what benifits if i have create catalog ?

    No we have to configure it. I see. But did this user understand that when you quoted my reply ? We need to understand that a lot of users who post here need help and may not have the level of knowlege you have. So, a response like that adds more problems to the one they already have.
    So even if you are using nocatalog, if it is not configured to auto backup and it is not backed up, you can still loose your RMAN repository.

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

  • 10G RMAN catalog in 9i

    Hi,
    I can't find this information in any documentation, so this is the best place for it.
    Can we create a 10g RMAN catalog on 9i database? If no why? If yes, then is
    there any known issue/problem with this?
    Thanks....

    Hi,
    You can create !!
    But you might experience the problems, with Backward compatability..
    I suppose.. that..
    Thanks
    Pavan Kumar N

  • Controlfile vs. RMAN Catalog

    Hey, my controlfile is increasing really fast. So I have to recreate the the controlfile on a regular basis. Its growing nearly 150 MB in one month.
    Therefore the backups are getting slow, also a logswitch is impacting my database performance. I am using a physical standby so the db parameter archive_lag_target is set to 600 (sec), so every 10 minutes a logswitch occurs.
    v$controlfile_record_section is showing archivelogs are the most space consuming part.
    Now the question:
    Is it an appriopate way to switch from controlfile to rman catalog ? Will this help me to keep the controlfile tiny ?
    Chris

    Hi Christian,
    Why is the size of the controlfile a problem for you?
    There are other points to keep in mind if you use controlfile or rman catalog.
    For example if you would like to use standby databases so Oracle recommend to use an rman catalog.
    For me it is not a problem of the size it is your decision to make a matrix and look about the pros and cons
    between controlfile and rman catalog.
    But if it is a production environment it is a good idea to use a rman catalog.
    regards
    SPA2

  • 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 Upgrade Understanding.

    Hi,
    We just upgraded our target database from oracle version 9.2.0.7 to 9.2.0.8 and our catalog database is still in 9.2.0.7 . Do we need to upgrade the recovery catalog schema in the catalog database If so then how to do that.
    I tried running upgrade catalog command on the recovery schema of the catalog database and it is upgrading to the 9.2.00 version packages.
    reldb3d:instra /opt/app/oracle/product/9.2.0.8/rdbms/admin> rman catalog instra/[email protected]
    Recovery Manager: Release 9.2.0.8.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    RMAN> upgrade catalog;
    recovery catalog owner is INSTRA
    enter UPGRADE CATALOG command again to confirm catalog upgrade
    RMAN> upgrade catalog;
    recovery catalog upgraded to version 09.02.00
    DBMS_RCVMAN package upgraded to version 09.02.00
    DBMS_RCVCAT package upgraded to version 09.02.00
    Right now I am skeptical is it the correct way of upgrading the catalog schema in the catalog database.
    Any suggestions/advice will be highly appreciated.
    Thanks,
    Raheem

    The schema version (or the objects therein) is different from the version of the database in which the rc schema resides. As long as oracle wouldn't force you to upgrade the database, upgrading the schema is enough. The same applies to the the repository database for grid control. The version of the grid repository schema can be different from the version of the database software.
    Whatever you did is correct.

  • Unregister from rman catalog

    Dear All,
    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?

    Currently our production backup is done by rman with catalog database. But I want to decommission it. I want to use the target database controlfile only for rman backup.
    what is the right approach to configure it?No ned to confiugre, while connecting to RMAN or in backupjob scripts just do not mention catalog connectivity.
    If any old backups available then register them with controlfile..
    in case of catalog :-
    rman target sys/****@prod catalog rman/rman@catlog
    in case of no-catalog:
    rman target sys/****@prod
    to register old backups:-
    RMAN> catalog start with 'location of backups';

  • Centralized RMAN Catalog Database

    Hello,
    I have two 10g R2 databases on two separate servers.
    I am trying to centralize my RMAN backup by creating a RMAN_DATABASE in 11G.
    - I create RMAN_DATABASE
    - I created RMAN user and tablespaces
    - I edited my TNSNAMES.ORA so that I could connect to my two 10G R2 databases
    When I run the command:
    rman catalog=rman/password@rman_database target=sys/password@10g_db1I get the following error:
    Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 req
    uired
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    When I google the error it indicates to change the binary files, but that doesn't work either, unless I don't understand what that entails.
    Any suggestions?

    By saying that you have amended your tnsnames.ora to connect to the 10gR2 databases, I assume you are running the rman command on your 11gR1 server. This means that your RMAN client version is 11gR1, and your target database is 10gR2. This is not permitted, see the [compatibility matrix|http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm#i634479].
    I suggest you try this on each of your 10gR2 servers:
    1. Amend tnsnames.ora to include an entry for the 11gR1 rman_database
    2. Ensure your oracle environment variables are set correctly, especially ORACLE_HOME and ORACLE_SID
    3. rman target=sys/password catalog=rman/password@rman_database
    This means you will be using the 10gR2 RMAN client on the 10gR2 target database which ensures no incompatibility problems. There is no issue with the fact your recovery catalog schema is at 11gR1, this is permitted to be greater than the RMAN client being used.

  • Question: Which is better and why....RMAN catalog or Flashback Recovery

    Hey All,
    Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
    Thanks,
    d.

    Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
    Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
    Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
    On the other hand, RMAN backups are safer, being physically elsewhere.
    See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

Maybe you are looking for

  • SAP PO- emailing vendor and recepient--- urgent

    When trying to email PO to both Vendor as well as the person creating the PO...The PO is emailed only to vendor and not picking the ID in the recpient field(internal ID). What is the procedure for emailing both

  • Bapi for the deletion of Automatic blocking indicator for open vendor

    Hi All, At the time of Downpayment of vendor Automatic block indicator is set in vendor payment . Is there any Bapi is available which can delete the payment block key for the all vendor (open item ) with document type 'KZ'- vendor payment at the tim

  • Unwanted sounds in video clip

    I just recorded a outside interview and there are sounds that I DO NOT want in my clip,(someone had a baby crying in the background, and then a loud truck went by). If anyone knows how I can remove this and just have the vocal part of my interviewee

  • GTS 7.2 and AES 2.1

    Will GTS 7.2 support AES 2.1 which will be implemented by German customs in Q4 2011?

  • Photoshop plugin for Scanner

    Hi! I am using brother 4 in 1 which has function of scanner, printer, photocopy and fax. The problem I am having is on Photoshop is it doesn't allows me to scan the document that I need to print, email or keep in the hard disk. Is there any plugin av