RMAN catalog resync in Dataguard environment

Hello,
I have a quick question regarding the resync of the recovery Catalog in a 10g Dataguard environment...
I plan to perform the backups from the physical standby side. (Backups of DB and archives).
If I want to restore/recover a datafile on the primary side, do I automatically see the backup information once i am connected to the catalog DB, or do I have to perform a "resync catalog;" statement to resync the control file of the primary side with the actual backup information from the catalog?
Thanks in advance,
Boris...

But what is the effect, if I perform this statement on the primary side? Do I loose backup information if I perform a resync of the catalog because the backups were made from standby side? If I perform all backups from standby side the control file on the primary side does not know about the backups.
I am asking because I want to know if I have to adjust the backupscripts. They perform a resync of catalog per default.
Thx, Boris..

Similar Messages

RMAN catalog resync

Hi to all,
I have a basic doubt.
What is the way to check catalog database is in sync after giving sync catalog?
Regards,
Vijayaraghavan K

Pls, look at here for all catalog related tables and corresponding view: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcviews001.htm#i77529
You will be in unsync, say when you added tablespace, but catalog has no information about it, unless you connected with RMAN.
So, you can join catalog views with target database's views and find out what is missing.
F.e:
RC_DATAFILE - This view lists information about all datafiles registered in the recovery catalog. So if you added new datafile to target database, that new datafile will not be listed unless you resync. It means new datafile will be listed in v$datafile of target database, but will not be listed in RC_DATAFILE.

Configuring rman for dataguard environment.

Hi all,
Here we have a dataguard environment with db1 as primary and db2 as physical standby database. We configured dataguard in 10g environments and we are not using grid control. Can anyone provide the steps for configuring rman for incremental backups in this environment? We want to schedule the backups to be taken in standby db, (that is applicable in case of swithover too). In the case of swithover to db2 what all do we need to do in rman manually to resume backups in db1?
Thanks

Hello;
A Standby database is a copy of the Primary so if you try to register it RMAN will probably tell you its already registered. I would start with this :
Standby based backup
1. Enable auto backup of the control file and server parameter file. CONFIGURE CONTROLFILE AUTOBACKUP ON.
2. Skip backups on datafiles already backup. CONFIGURE BACKUP OPTIMIZATION.
3. Set the archive deletion policy. CONFIGURE DELETION POLICY TO NONE.
You have to decide on the exact RMAN script you want to use, but since the database is registered you can perform backup on either the Primary or the Standby as the need arises.
See "Using RMAN to Back Up and Restore Files" in "Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-05"
http://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm
Example in this post
How to manage primary and standby database backups using rman catalog
How to use standby backup to restore primary db
http://alexzeng.wordpress.com/2008/09/13/how-to-use-standby-backup-to-restore-primary-db/
Best Regards
mseberg

Resync or any other maintenace work on RMAN catalog....

I have inherited RMAN catalog created in Oracle 10g R2 to take the backup of 10g databases.
1.I want to check what are all the databases backed up. What query I should run? Like view names.
2.Is there any command I should run to make sure RMAN catalog is up to date. Like synchronizing. Wants to make sure my backup is recoverable.
Thank you,
Smith

1. Use RC_DATABASES view to get registered databases in recovery catalog and RC_BACKUP_SET view to get registered backup sets.
See http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmreprt.htm#CHDIJDEF
2. see RESYNC CATALOG in http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta052.htm#RCMRF150
which says:
>
RMAN automatically executes a full or partial resynchronization of the recovery catalog as needed when you execute RMAN commands, so long as the control file is mounted and the recovery catalog database is available at command execution.
>
Note however that database control file is always the source repository even if you use a recovery catalog.
Even if you loose recovery catalog you should be be able to retrieve RMAN backups. See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#BRADV156.
Edited by: P. Forstmann on 25 févr. 2010 20:15

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

Flashback in dataguard environment

Hi,
We have dataguard environment with Sun OS & Oracle 10g, 11g. Now we want to enable flashback for the primary database as well as standby database (physical standby). NO RMAN. I did manage to configure the flashback for the primary database but confusion is:
-- Do I need to configure flashback at standby or recreate standby after enabling flashback at primary site?
-- Suppose if I use flashback database to restore point and open database with resetlogs, what would be the situation at standby site? Will it be in sync with primary or after resetlogs I need to make new standby database??
-- Is there any space requirement ratio for flashback recovery partition?
Thanks,
Amit.

If you only enabled flashback on your Primary, your Standby is not affected. If you did actually a flashback database on your Primary, you need to address that on the Standby. See an example here:
http://uhesse.wordpress.com/oracle-database-ha-architecture/2010/08/06/using-flashback-in-a-data-guard-environment/
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

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.

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

RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법

제품 : RMAN
작성날짜 : 2001-05-28
RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법
===============================================
1) UNREGISTER 하고자 하는 Database를 RMAN CATALOG에서 확인한다.
SELECT * FROM RC_DATABASE;
2) UNREGISTER하고자 하는 DATABASE에 속한 BACKUPSET들을 모두 제거한다.
- 제거하고자 하는 BACKUPSET을 알아내는 방법
RMAN> list backupset of database;
- BACKUPSET을 제거하는 방법
RMAN> allocate channel for delete type disk;
RMAN> change backupset XXX delete;
* 위에서는 DISK에대해 CHANNEL을 설정하였지만 TAPE에 대해 CHANNEL설정을
하려면 아래와 같은 COMMAND를 수행한다.
RMAN> allocate channel for delete type 'sbt_tape';
또한 XXX는 'list backupset of database'의 결과 중에서 'LIST OF KEY'의
값을 의미한다.
3) 다음과 같은 PROCEDURE를 RECOVERY CATALOG에서 수행함으로써 DATABASE를 UNREGISTER한다.
execute dbms_rcvcat.unregisterdatabase (db_key, db_id)
* DB_KEY와 DB_ID는 다음과 같은 QUERY문에서 알아낼 수 있다.
SVRMGR> select * from rc_database;
EXAMPLE:
========
Unregistering ORCL database:
1) The following will list the backupset for the database that we want to
uncatlog.
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ---------
RMAN-06233: 858 1 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 2 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 3 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 4 Full 16-SEP-98 253487 16-SEP-98
==================================
2) The following will show allocation of a delte channel, deleting the
backupset, and running the list command to confirm that the backupsets were
removed. The delete command will remove the backupsets from the backup location.
RMAN> allocate channel for delete type disk;
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete
RMAN-08500: channel delete: sid=10 devtype=DISK
RMAN> change backupset 858 delete;
RMAN-03022: compiling command: change
RMAN-03023: executing command: change
RMAN-08073: deleted backup piece
RMAN-08517: backup piece handle=C:\ORANT\DATABASE\RMANORCLBACKUP\DF_344180532_30
_1 recid=27 stamp=344180538
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ----------
================================
3) From the recovery catalog:
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAMERESETLOGS_ RESETLOGS
584 585 868345165 ORCL 192881 18-AUG-98
1 row selected.
SVRMGR> execute dbms_rcvcat.unregisterdatabase(584,868345165);
Statement processed.
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAME RESETLOGS_ RESETLOGS
0 rows selected.

RMAN 에서 CATALOG DB생성후 에러메세지....

rman 실행하고 catalog 디비 연결했는데......
자꾸 이런 메세지가 뜨면서 아무런 명령도 안먹히고 에러만 떠요!!
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/17/2006 13:40:20
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 11/17/2006 13:40:20
ORA-19550: 디스패처를 사용하는 동안 backup/restore 함수를 사용할 수 없습니다

rman catalog 접속시에는 MTS로 접속해서는 안됩니다.
DEDICATED로 접속해야 합니다.
tnsnames.ora 에 catalog DB의 접속자 설정시
SERVER=SHARED 가 아닌
SERVER=DEDICATED 로 변경하시기 바랍니다.
DB가 MTS(=shared server)로 구성되어 있더라도
tnsnames.ora 파일에서 접속자 설정시
SERVER=DEDICATED로 설정할 경우에는 DEDICATED로
접속됩니다.
글 수정:
민천사 (민연홍)

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.

RMAN restore failing in another environment

Hi,
I am facing a problem. I have to restore a database backup from production to Integration
environment. In Production, it is RAC db and RMAN and Veritas Net backup taking the backups.
In Integration Environment also we have the same setup.
So the steps I have done so far is:
1.Have the export of RMAN catalog schema from production and imported in RMAN server in Integration
Environment.#
2. UNIX admins put and mounts the TAPE in tape library.
3. Set the environment for new db in oratab file.
4. connected to target and RMAN.
5. startup nomount from RMAN.
6.executed the following commands
RMAN> run {
2> allocate channel t1 type sbt;
3> validate backupset 2805233;
4> }
released channel: ORA_DISK_1
allocated channel: t1
channel t1: sid=317 devtype=SBT_TAPE
channel t1: VERITAS NetBackup for Oracle - Release 6.0 (2005090703)
channel t1: starting validation of datafile backupset
channel t1: reading from backup piece db_11192_1_651890513
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of validate command on t1 channel at 06/05/2008 12:23:51
ORA-19870: error reading backup piece db_11192_1_651890513
ORA-19507: failed to retrieve sequential file, handle=”db_11192_1_651890513″, parms=”"
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file
RMAN>
I’ve got the backupset key from RMAN catalog, but it is failing to validate the backup set.
And also all the subsequent attempts to restore spfile/controlfile/database are failing.
Now, I have been advised by Oracle that this is the problem with Media Manager and I have to contact
them, unfortunately I dont have support service from Veritas.
Could any of you guys please advise, do we need to do any other configrations in net back to Identify
the tapes from foreigen envirnment/ do we need to pass any more paramters from RMAN to see the newly
mounted TAPS?
Your help will be highly appreciated.
Thanks and Regards,
Zach

Zach,
Can you certain tests for me ?
1)
Lets assume some terms here
a) origclient = your target host
b) altclient = your destination host
c)media manager server = host that contains your netbackup master software
Can you goto altclient and first check if your altclient is able to browse the backups generated by the origclient
$NETBACKUP_HOME/bin/bplist -C <origClient> -t 4 -l -R /
2) Have you configured your ORACLE_HOME on the destination to link one of its libraries to the Media Management software ?
goto $ORACLE_HOME/lib
ls -lrt libobk.sl . This file should be a softlink to $NETBACKUP_HOME/bin/libobk.sl64
3) Please use the SEND command in your RMAN restore scripts. You need so specify the NB_ORA_SERV (your media management master server) and NB_ORA_CLIENT (your origclient host)
SEND 'NB_ORA_SERV=<media manager server>, NB_ORA_CLIENT=<origclient>';
4) Make sure your $NETBACKUP_HOME/bp.conf has the required parameters for client and server. client will be your origclient and server will be your media management server that has the netbackup master software

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)

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.

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

RMAN catalog resync in Dataguard environment

Similar Messages

Maybe you are looking for