Rman catalog files

We have 11g rac one node implemented on windows 2008, i took complete backup using rman from the production database and I copied the files to the test server and when am doing
restore database validate it is still pointing to production backup location :
c:\rman\ (test location)
e:rman (production location)
Am getting the error :
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
Wondering why am getting the above error as I didn't catalog any backup piece on that location and the location is taken from production.
test worklog
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
Starting restore at 26-JAN-12
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL01.CTL
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL02.CTL
Finished restore at 26-JAN-12
RMAN> catalog backuppiece 'C:\rman\DATA_73_1_29N1OG00_1_1.BAK';
released channel: ORA_DISK_1
cataloged backup piece
backup piece handle=C:\RMAN\DATA_73_1_29N1OG00_1_1.BAK RECID=34 STAMP=773622357
RMAN> catalog backuppiece 'C:\rman\'DATA_74_1_2AN1OG00_1_1.BAK';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "comma, ;"
RMAN-01008: the bad identifier was: DATA_74_1_2AN1OG00_1_1
RMAN-01007: at line 1 column 31 file: standard input
RMAN> catalog backuppiece 'C:\rman\DATA_74_1_2AN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_74_1_2AN1OG00_1_1.BAK RECID=35 STAMP=773622388
RMAN> catalog backuppiece 'C:\rman\DATA_75_1_2BN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_75_1_2BN1OG00_1_1.BAK RECID=36 STAMP=773622401
RMAN> catalog backuppiece 'C:\rman\DATA_76_1_2CN1OG01_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK RECID=37 STAMP=773622413
RMAN> catalog backuppiece 'C:\rman\DATA_77_1_2DN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK RECID=38 STAMP=773622427
RMAN> catalog backuppiece 'C:\rman\DATA_78_1_2EN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK RECID=39 STAMP=773622439
RMAN> catalog backuppiece 'C:\rman\DATA_79_1_2FN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK RECID=40 STAMP=773622501
RMAN> catalog backuppiece 'C:\rman\DATA_80_1_2GN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK RECID=41 STAMP=773622513
RMAN> catalog backuppiece 'C:\rman\DATA_81_1_2HN1OG03_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK RECID=42 STAMP=773622525
RMAN> catalog backuppiece 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_82_1_2IN1OG3N_1_1.BAK RECID=43 STAMP=773622546
RMAN> catalog backuppiece 'C:\rman\DATA_83_1_2JN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_83_1_2JN1OG3N_1_1.BAK RECID=44 STAMP=773622560
RMAN> catalog backuppiece 'C:\rman\DATA_84_1_2KN1OG75_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_84_1_2KN1OG75_1_1.BAK RECID=45 STAMP=773622574
RMAN> restore database validate;
Starting restore at 26-JAN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=350 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=407 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=466 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=524 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=582 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=640 device type=DISK
channel ORA_DISK_1: starting validation of datafile backup set
channel ORA_DISK_2: starting validation of datafile backup set
channel ORA_DISK_3: starting validation of datafile backup set
channel ORA_DISK_4: starting validation of datafile backup set
channel ORA_DISK_5: starting validation of datafile backup set
channel ORA_DISK_6: starting validation of datafile backup set
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
channel ORA_DISK_3: reading from backup piece C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK
channel ORA_DISK_4: reading from backup piece C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK
channel ORA_DISK_5: reading from backup piece C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK
channel ORA_DISK_6: reading from backup piece C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:00:46
channel ORA_DISK_2: errors found reading piece handle=E:\RMAN\DATA_81_1_2HN1OG03
_1_1.BAK
channel ORA_DISK_2: failover to piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_2: restored backup piece 1
channel ORA_DISK_2: validation complete, elapsed time: 00:00:56
channel ORA_DISK_6: piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_6: restored backup piece 1
channel ORA_DISK_6: validation complete, elapsed time: 00:01:26
channel ORA_DISK_3: piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_3: restored backup piece 1
channel ORA_DISK_3: validation complete, elapsed time: 00:01:36
channel ORA_DISK_5: piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_5: restored backup piece 1
channel ORA_DISK_5: validation complete, elapsed time: 00:01:36
channel ORA_DISK_4: piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_4: restored backup piece 1
channel ORA_DISK_4: validation complete, elapsed time: 00:02:07
Finished restore at 26-JAN-12Kai

Those "prod" locations are found in the backup controlfile:
>
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
>
>
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
>
You can see how RMAN noticed it couldn't find that piece and then found one that you had previously cataloged. Looks good to me.

Similar Messages

Catalog addiional rman backup files

Im trying to catalog addiional rman backup files, and getting this error:
RMAN-07518: Reason: Foreign database file DBID: 2319619701 Database Name: SASP
Previous activities: Database dictionary was recreated due to charset problems while exporting the database...
Enterprise Manager was reconfigure with create repos due to same problems....
Thanks in advance...
Message was edited by:
elvyscruz

Previous activities: Database dictionary was
recreated due to charset problems while exporting the
database...
Enterprise Manager was reconfigure with create repos
due to same problems....I have not seen the full error messages that follows this one (post it if possible). However, if you recreated the database, then your database will now have a new DBID after it was recreated. You can see the current DBID of the database to see if it matches the one above.
If it is a standby database and it is logical standby, then it will also have a different DBID.
select dbid, name, database_role from v$database;

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)

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.

Schedule a crontab in rman catalog

Hi,
I am trying to schedule a crontab in rman catalog side but it wasn't work.
I prepared a scripts and I dont know why it was not worked.
Please can anyone tell me how can I schedule my crontab in rman.
The scripts is this,
00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
vi ora_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
run {
backup incremental level 0 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
vi ora01_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
run {
backup incremental level 1 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
waiting for your replies,
Thanks & Regards

Here's my working stuff:
I use an .env file. Here's the crontab entry, script and env file.
00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
#!/bin/bash
# Name: db_rman_full.sh
# Purpose: Database rman backup
# Usage : db_rman_full <DBNAME>
. /u01/app/oracle/dba_tool/env/PRIMARY.env
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
run { allocate channel d1 type disk;
backup full as compressed backupset
database plus archivelog;}
crosscheck backup;
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
exit
EOF
echo `date`
echo
echo 'RMAN Full on PRIMARY Complete'
env
ORACLE_BASE=/u01/app/oracle
ULIMIT=unlimited
ORACLE_SID=PRIMARY
ORACLE_HOME=$ORACLE_BASE/product/11.2.0
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
LIBPATH=$LD_LIBRARY_PATH:/usr/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
export TERM=vt100
export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
export ORACLE_HOME
export LIBPATH LD_LIBRARY_PATH ORA_NLS33
export TNS_ADMIN
export PATH
----If you find this helpful please mark it so----

RMAN catalog fails to show target database information when in nomount mode

Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
:->rman catalog cde01_rman4/xxxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: EGVBFI2 (DBID=4238332493, not open)
connected to recovery catalog database
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
RMAN>
However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
:->rman catalog cde01_rman4/xxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: egvbfi2 (not mounted)
connected to recovery catalog database
RMAN> list incarnation;
RMAN>
Please advice?
Thanks,
Jairaj

Hi,
You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
Mount the instance and just restore the datafiles.
Liron Amitzi
Senior DBA consultant
link: [www.dbsnaps.com]
link: [www.obriumsoftware.com]

What is RMAN configure file ?

Hi,
When you create recovery catalog, and start RMAN, where does RMAN get information to decide to get configure from catalog database instead of control file? what is the file name? Thanks.

hi
if you connect ( currently) with target database control file then ur backup information goes in control file instead of recovery catalog..
C:\>rman target=sys/oracle
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
RMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle nocatalog
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
using target database controlfile instead of recovery catalog
RMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
connected to recovery catalog database
RMAN> exit
Recovery Manager complete.
C:\>rman catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to recovery catalog databaseRMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
connected to recovery catalog databasehope this helps
Taj
Message was edited by:
User 52

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 RMAN binary from my laptop :
 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 RMAN executable in the target database. 
 $ 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

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.

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 - CTRL-file - Sync

hi all,
is there a possiblity to transfer the information about backup from the control file to the rman catalog?
I have first created rman-backups without the rman - catalog and created today the rman catalog. If I exeute the command "list backup of database" I only got the information when I am not logged in on the rman-catalog
is there a possiblity to sync the information from the controle file to the rman catalog?
best regards
Stefan

Issue RESYNC CATALOG on the rman prompt being connected to the recovery catalog.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcatdb003.htm
Resynchronization, compares the recovery catalog to either the current control file of the target database/backup control file and updates the recovery catalog with information that is missing or changed.
Adith

Weird RMAN catalog issue

I am on 10.2.0.4, RMAN + RMAN catalog + Data Gurad and I am desporate :)
My db crashed with the following:
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 49: Disc quota exceeded
A look in the FRA showed that it was 100% full. Archived logs take all of the space. I delete archived logs via OS method and then do delete expired archvied log all. If I am connected to recovery catalog while doing this, Oracle DOES NOT delete archieved logs from FRA (I don't see them on diks, but FRA stays full). If I connect to target only and do not connect to the catalog and do the same thing, FRA gets emptied out. WHY???? Thank you for any input!!!
p.s. Here is my delete archvied log script:
#!/bin/ksh -x
# Script to delete archive logs older then 4 days
find /data/archive/PROD/archivelog -mtime +4 -exec rm -r {} \;
. /data/app/oracle/.profile
export ORACLE_SID=PROD
export DATESTAMP="`date +"%y:%m:%d"`"
rman <<EOF
SPOOL MSGLOG TO '/data/app/home/dba/backup_files/archive_logs/PROD_clear_a
rch${DATESTAMP}.log'
@/data/app/home/dba/scripts/connect_nocat.rman
run {
allocate channel d1 device type disk;
crosscheck archivelog all;
delete noprompt expired archivelog all;
release channel d1;
EXIT;
EOF

hi,
you wrote: +"...Oracle DOES NOT delete archieved logs from FRA..."+
If you try to delete needed files (depends on your retention policy:
show RETENTION POLICY;
report need backup;
restore archivelog all preview summary;
) you may have to use "force" option in the statement. Even if they don't exist on disk, RMAN will throw errors.
What is the output of:
crosscheck archivelog all;
delete noprompt expired archivelog all;
P.S. it's better not to delete oracle files in OS if RMAN handles B&R policy ;-)

How to restore the control fie? without having RMAN catalog.

Hi ,
can anyone help me out here.???
How can i restore the control file.if i dont have the RMAN catalog.
Please provide me steps that'll be helpful. I am frsher in oracle DBA
Please mail me: [email protected]
Regards
Vikas Singh

Hi Vikas,
You can restore the control if you have the full backup of your database in some location.
Lets assume you have the full backup piecs in loc "/u02/backup/..bkp"
steps:
shut abort;
startup nomount;
catalog start with "/u02/backup/..bkp"
restore spfile from '/u02/backup/..bkp";
restore controlfile from "/u02/backup/..bkp"
shut immediate;
startup mount;
alter database open;
Once the db is up with controlfile immediately take the full database backup of your database.
Let me know having issue after following this.
-- rohit
http://dbarohit.blogspot.in/

RMAN backup file location

hi gurus,
my database backup file are located in one location and rman is looking for backup files in another location.
backup files are large size so it's long time to move
how can i tell to rman look for rman in perticular location
please let me know
thank you!

899329 wrote:
hi gurus,
my database backup file are located in one location and rman is looking for backup files in another location.
backup files are large size so it's long time to move
how can i tell to rman look for rman in perticular location
please let me know
thank you!Instead of moving if you want to register those backups with your controlfile. (RMAN repository)
then
$rman target /
RMAN> catalog start with 'location';
It will search for backup pieces in that location, and it prompts you for confirmation with YES/NO.
Give yes, so that all the files will be cataloged, Later you can able to view in list backup.
HTH.

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 catalog files

Similar Messages

Maybe you are looking for