RMAN Catalog - Identify session for a specific SID

Dear all,
is it possible to identify the rman session on the recovery-catalog database that is currently backing up a specific SID?
Or in other words: Is the SID of the target database visible somewhere in the V$-Views on the catalog database when a backup is running?
Kind regards
Carsten

The recovery catalog stores metadata about RMAN operations,but it does not record ongoing processes. There's a catalog view,which holds HISTORICAL data:
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcviews050.htm#i84920
Werner

Similar Messages

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

Setting default unconditional mode(s) for a specific SID in TMS

I am working in ECC 5.0, and I'm trying to configure one of the systems in our TMS landscape to use a specific unconditional mode (u2) by default. Does anyone know a method by which I can set this in the TMS configuration? I was looking at parameter R3TRANSOPTIONS for this, but after multiple searches on help.sap.com (and other sites), I cannot verify (1) that this will even work (2) if it will work, what the syntax for the call is.
Thanks in advance for your help!

Hi Katherine
This is not possible with a normal import all job for TMS or other settings as far as I know. It is also not recommended that you would use an unconditional mode by default.
The unconditional mode is specified by the tp process, so an R3trans parameter is not going to help. Their are a number of TP parameters as well, but no parameter is available for the unconditional mode in SAP.
If you would absolutely need this, I think the simplest solution would be to create a custom program to do this, you can then program a report which uses the tp command with U02. You would have to be careful with authorisation of this report as it could be dangerous for end users to perform this.
Reward points if useful.
Kind regards
Tom

Configuration of sessions for deployed servlet, jsp, wdp

Hello,
I wonder how to configure session for a specific servlet. As there are several locations where to deal with session management.
I have found the Security Provider->SessionExpirationPeriod property which is fixed to ~27 hours, this is a general parameter for all security providers.
I need to do it per application, I have then tried to set the session in the servlet descriptor it is not taken into account.
 <session-config>
 <session-timeout>10000</session-timeout>
 </session-config>
The security provider of the servlet is set to SAML authentication.
Thanks for your input on this topic,
Tanguy Mezzano

Finally, it was that parameter.

Identify session number for background job

Hi,
We have AQ and couple of jobs inside the db that does the processing for us.
Once while we get to a stage where they seem to lock each other and don’t do much work. I’m thinking maybe I should start tkprof for some of those session as starting point.
How can I identify session relevant to those jobs?
V11.2 we also suing virtual private database.
Thanks

user9198889, to tie a foreground process to an Oracle session background process the following article may be of interest along with another article on how to trace an already running process:
Is there a way to trace a UNIX process id to a SID and SERIAL# ?
http://www.jlcomp.demon.co.uk/faq/sid_from_proc.html
How do I switch on sql trace in another session that is already running?
http://www.jlcomp.demon.co.uk/faq/alien_trace.html
Now when your session executes a dbms_scheduler or dbms_jobs call you add another independent session to the process. Depending on your Oracle version you need to add more views to you process for hunting down what is wrong but if you have lock waits you should be able to find waiting and blocking sessions using v$session, v$lock, and other lock associated views like dba_blockers, dba_waiters, etc ....
HTH -- Mark D Powell --

Session maintenance at server side for webservice developed in CXF.

Hi.
Can anybody explain how to maintain session for a Webservice which is developed with the help of CXF? As earlier we were using AXIS, but recently we migrated to CXF. I tried to find out code samples, many places it’s given the session handling from client side which is not suitable for webservices. As client can work on different technologies.
So i cannot request client to put code for session handling.
Help is appreciated.
Thanks in advance.
Regards
Sreedhar

Hi.
Can anybody explain how to maintain session for a Webservice which is developed with the help of CXF? As earlier we were using AXIS, but recently we migrated to CXF. I tried to find out code samples, many places it’s given the session handling from client side which is not suitable for webservices. As client can work on different technologies.
So i cannot request client to put code for session handling.
Help is appreciated.
Thanks in advance.
Regards
Sreedhar

License for RMAN catalog standby database ?

Hi
I am planning to to setup a RMAN catalog for a large business that they have many databases.
I know that RMAN catalog does not need a separate license.
Does anybody know that if I setup a standby database for the catalog then do I need a separate license or it can be implemented without any license requirement ?
Thanks
Kamran

Is it "yes" that you know the answer to the question ?
Is it "yes" that he needs a separate licence ?
Is it "yes" that it can be implemented without any licence requirement ?
Do you really think that your answer is helpful ? Or are you trying to be an irritant ?
Hemant K Chitale

How to identify the right Install Disc Version for a specific mac model???

Hello
i hope someone here can help me here...
I have 12 mac mini's and about 20 Packs of the original OSX 10.4.x CD'/DVD's (the grey ones).
How can i find out witch CD (and AHT) is the right one for witch mac mini model? They all have the line 'mac mini' but the are different Versions of OS and AHT and every time when i try this i get the wrong one for a specific model.
I have been looking for more detailed informations but can't find anything!?
Any Idea?
Why Apple does not provide a table with all Model Numbers and e.g. the fitting AHT Versions?
Heeeelp pleeeeease - i am going crazy here...
Thank's !

Hello iKing
Apple keeps that info close to its chest, because the whole idea of the grey disks is to limit their currency as potential upgrade disks in the secondhand market.
So rather than post here in this user's forum, instead contact Apple and explain your problem and provide the serial numbers of your Mac minis and Apple should be able to tell you the corresponding version numbers of the relevant disks.
And after, I'd suggest use a texta/soft marker pen on the CD/DVD's to pair them with their hardware.
A spelling error was edited.

RMAN 11gR2 DUPLICATE TARGET FOR STANDBY FROM ACTIVE DATABASE - Issue -HELP

First question.
Can primary and standby database have the same SID name?
As I recall it is yes.
I believe they must have different GLOBAL or DB_UNIQUE_NAME?
Anyway, RMAN I believe is telling me it is having problems copying control file on first and dies.
Permissions Issue on STANDBY machine?
RMAN> connect target backup_admin/backup_admin
connected to target database: LABDG (DBID=1973403623)
RMAN> connect auxiliary sys/oracle@STANDBY;
connected to auxiliary database: LABDG (not mounted)
RMAN> DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE;
Starting Duplicate Db at 18-JUL-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=10 device type=DISK
contents of Memory Script:
backup as copy reuse
targetfile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' auxiliar
'/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwLABDG' ;
executing Memory Script
Starting backup at 18-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=151 device type=DISK
Finished backup at 18-JUL-11
contents of Memory Script:
backup as copy current controlfile for standby auxiliary format '/u01/oradat
restore clone controlfile to '/u01/app/oracle/flash_recovery_area/LABDG/cont
'/u01/oradata/LABDG/control01.ctl';
executing Memory Script
Starting backup at 18-JUL-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
copying standby control file
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/18/2011 11:20:54
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2011 11:20:
ORA-17628: Oracle error 19505 returned by remote Oracle server

Hi,
Permissions Issue on STANDBY machine?First problem I see is the sysdba password must be the same on both sides (target and auxiliary dbs).
From the documentation.
The source database and auxiliary instances must use the same SYSDBA password, which means that both instances must have password files. You can
create the password file with a single password so you can start the auxiliary instance and enable the source database to connect to it.Check all prereqs for the standby db duplicate here.
http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724
Rgds,
Tycho

Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

I will explain my scenario below:
We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
Please suggest me the best way forward...
Many Thanks
Nukesh

Hi Asif,
I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
RMAN> list incarnation;
using target database control file instead of recovery catalog
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
RMAN> exit
TEST1DB-> rman target sys@MYTEST1
Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
target database Password:
connected to target database: MYTEST (DBID=2433328848, not open)
RMAN> reset database to incarnation 2;
using target database control file instead of recovery catalog
database reset to incarnation 2
RMAN> run {
2> restore database until scn 10000;
3> recover database until scn 10000;
4> alter database open resetlogs;
5> };
Starting restore at 07-NOV-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/07/2010 11:45:18
RMAN-20208: UNTIL CHANGE is before RESETLOGS change
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
RMAN-01007: at line 0 column 2 file: standard input
RMAN>
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
RMAN> exit
SQL> select name from v$database;
NAME
MYTEST
SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
NAME TYPE VALUE
control_file_record_keep_time integer 7
SQL>

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

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

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

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 - Identify session for a specific SID

Similar Messages

Maybe you are looking for