Monitoring RMAN Session
I am using RMAN Duplicate command to clone production database to auxiliary database. My environment is Oracle 9.2.0.8 64 bit AIX 5.3
I have following scenario:
Duplicate database from server A to server B (Non ASM)
Primary Database SID: jldr
Duplicate Database SID: odsarch
RMAN Catalog SID: CATALOG
oracle@fincl4.dc.albilad.com:/home/oracle/dba/scripts>rman target sys/passwd@JLDR catalog rman/passwd@CATALOG auxiliary /
Recovery Manager: Release 9.2.0.8.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: JLDR (DBID=628146835)
connected to recovery catalog database
connected to auxiliary database: odsarch (not mounted)
RMAN> run {
set until time "to_date('Jun 01 2010 00:00:00','Mon DD YYYY HH24:MI:SS')";
ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/TDPO.dw3_tdp)';
duplicate target database to orsarch NOFILENAMECHECK;
}2> 3> 4> 5>
.........
.........
channel c1: starting datafile backupset restore
channel c1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oradata/jldr_sys/data/system01.dbf
restoring datafile 00004 to /u01/oradata/jldr_sys/data/drsys01.dbf
restoring datafile 00048 to /u01/oradata/jldr_ods/index/ods_idx09.dbf
restoring datafile 00081 to /u02/oradata/jldr_ods/index/ods_idx21.dbf
restoring datafile 00084 to /u01/oradata/jldr_ods/data/ods37.dbf
restoring datafile 00085 to /u01/oradata/jldr_jbl/index/jbloader_idx04.dbf
restoring datafile 00090 to /u02/oradata/jldr_ods/data/ods40.dbf
restoring datafile 00091 to /u02/oradata/jldr_ods/index/ods_idx24.dbf
restoring datafile 00094 to /u02/oradata/jldr_ods/data/ods42.dbf
restoring datafile 00096 to /u02/oradata/jldr_ods/index/ods_idx26.dbf
restoring datafile 00097 to /u01/oradata/jldr_ods/data/ods44.dbf
restoring datafile 00099 to /u02/oradata/jldr_ods/data/ods46.dbf
restoring datafile 00102 to /u02/oradata/jldr_ods/data/ods48.dbf
restoring datafile 00104 to /u02/oradata/jldr_ods/data/ods50.dbf
restoring datafile 00105 to /u02/oradata/jldr_ods/data/ods51.dbf
restoring datafile 00107 to /u02/oradata/jldr_ods/data/ods53.dbf
restoring datafile 00109 to /u02/oradata/jldr_ods/data/ods55.dbf
restoring datafile 00111 to /u02/oradata/jldr_ods/data/ods57.dbf
restoring datafile 00112 to /u02/oradata/jldr_ods/index/ods_idx28.dbf
restoring datafile 00123 to /u01/oradata/jldr_eai/index/jbloader03.dbf
restoring datafile 00135 to /u01/oradata/jldr_eai/index/ods61.dbf
restoring datafile 00136 to /u01/oradata/jldr_ssr/index/ssr_idx02.dbf
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/23/2010 23:48:52
RMAN-03015: error occurred in stored script Memory Script
ORA-19501: read error on file "kelf146d_1_1", blockno 530547201 (blocksize=512)
ORA-27190: skgfrd: sbtread2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1017E (RC-50) Session rejected: TCP/IP connection failure
RMAN> run {
set until time "to_date('Jun 01 2010 00:00:00','Mon DD YYYY HH24:MI:SS')";
ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_ods.opt)';
ALLOCATE AUXILIARY CHANNEL c2 DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo_ods.opt)';
duplicate target database to orsarch NOFILENAMECHECK;
}
skipping datafile 11; already restored to file /u01/oradata/jldr_jbl/data/jbloader01.dbf
skipping datafile 12; already restored to file /u01/oradata/jldr_ods/data/ods01.dbf
.........
.........
skipping datafile 90; already restored to file /u02/oradata/jldr_ods/data/ods40.dbf
skipping datafile 94; already restored to file /u02/oradata/jldr_ods/data/ods42.dbf
skipping datafile 97; already restored to file /u01/oradata/jldr_ods/data/ods44.dbf
skipping datafile 99; already restored to file /u02/oradata/jldr_ods/data/ods46.dbf
skipping datafile 102; already restored to file /u02/oradata/jldr_ods/data/ods48.dbf
skipping datafile 104; already restored to file /u02/oradata/jldr_ods/data/ods50.dbf
skipping datafile 105; already restored to file /u02/oradata/jldr_ods/data/ods51.dbf
skipping datafile 107; already restored to file /u02/oradata/jldr_ods/data/ods53.dbf
skipping datafile 109; already restored to file /u02/oradata/jldr_ods/data/ods55.dbf
skipping datafile 111; already restored to file /u02/oradata/jldr_ods/data/ods57.dbf
skipping datafile 119; already restored to file /u01/oradata/jldr_eai/index/scratch02.dbf
skipping datafile 123; already restored to file /u01/oradata/jldr_eai/index/jbloader03.dbf
skipping datafile 135; already restored to file /u01/oradata/jldr_eai/index/ods61.dbf
skipping datafile 136; already restored to file /u01/oradata/jldr_ssr/index/ssr_idx02.dbf
skipping datafile 108; already restored to file /u02/oradata/jldr_ods/data/ods54.dbf
skipping datafile 110; already restored to file /u02/oradata/jldr_ods/data/ods56.dbf
skipping datafile 118; already restored to file /u01/oradata/jldr_eai/index/scratch01.dbf
skipping datafile 131; already restored to file /u02/oradata/jldr_ods/data/ods58.dbf
skipping datafile 133; already restored to file /u02/oradata/jldr_ods/data/ods59.dbf
skipping datafile 134; already restored to file /u01/oradata/jldr_ods/data/ods60.dbf
skipping datafile 128; already restored to file /u01/oradata/jldr_ods/index_16k/ods_idx01_16K.dbf
channel c1: starting datafile backupset restore
channel c1: specifying datafile(s) to restore from backup set
restoring datafile 00003 to /u01/oradata/jldr_sys/data/cwmlite01.dbf
restoring datafile 00005 to /u01/oradata/jldr_sys/data/example01.dbf
restoring datafile 00006 to /u01/oradata/jldr_eai/index/eai_idx01.dbf
restoring datafile 00008 to /u01/oradata/jldr_sys/data/tools01.dbf
restoring datafile 00010 to /u01/oradata/jldr_sys/data/xdb01.dbf
restoring datafile 00014 to /u01/oradata/jldr_jbl/index/jbloader_idx01.dbf
restoring datafile 00015 to /u01/oradata/jldr_ods/data/business_objs01.dbf
restoring datafile 00016 to /u01/oradata/jldr_ods/data/tivoliorts.dbf
restoring datafile 00018 to /u01/oradata/jldr_ods/data/ACCTMIS.dbf
restoring datafile 00021 to /u01/oradata/jldr_mstmt/data/mis_stmt01.dbf
restoring datafile 00042 to /u01/oradata/jldr_jbl/index/jbloader_idx03.dbf
restoring datafile 00044 to /u01/oradata/jldr_ods/index/ods_idx08.dbf
restoring datafile 00051 to /u01/oradata/jldr_ods/index/ods_idx10.dbf
restoring datafile 00057 to /u01/oradata/jldr_ods/index/ods_idx12.dbf
restoring datafile 00062 to /u01/oradata/jldr_ods/index/ods_idx14.dbf
restoring datafile 00065 to /u01/oradata/jldr_ssr/data/ssr01.dbf
restoring datafile 00066 to /u01/oradata/jldr_ssr/index/ssr_idx01.dbf
restoring datafile 00072 to /u02/oradata/jldr_ods/index/ods_idx18.dbf
restoring datafile 00074 to /u01/oradata/jldr_enjaz/index/enjazfawri_idx01.dbf
restoring datafile 00078 to /u02/oradata/jldr_ods/index/ods_idx20.dbf
restoring datafile 00083 to /u02/oradata/jldr_ods/index/ods_idx22.dbf
restoring datafile 00086 to /u01/oradata/jldr_ods/data/ods38.dbf
restoring datafile 00087 to /u02/oradata/jldr_ods/index/ods_idx23.dbf
restoring datafile 00089 to /u01/oradata/jldr_eai/index/jbloader02.dbf
restoring datafile 00093 to /u02/oradata/jldr_ods/index/ods_idx25.dbf
restoring datafile 00100 to /u02/oradata/jldr_ods/index/ods_idx27.dbf
restoring datafile 00113 to /u02/oradata/jldr_ods/index/ods_idx29.dbf
restoring datafile 00115 to /u02/oradata/jldr_ods/index/ods_idx31.dbf
restoring datafile 00120 to /u01/oradata/jldr_sys/undo/undotbs02.dbf
channel c2: starting datafile backupset restore
channel c2: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /u01/oradata/jldr_sys/data/system01.dbf
restoring datafile 00004 to /u01/oradata/jldr_sys/data/drsys01.dbf
restoring datafile 00007 to /u01/oradata/jldr_sys/data/odm01.dbf
restoring datafile 00009 to /u01/oradata/jldr_sys/data/users01.dbf
restoring datafile 00013 to /u01/oradata/jldr_eai/index/eai_idx02.dbf
restoring datafile 00019 to /u01/oradata/jldr_ods/data/ACCOUNT.dbf
restoring datafile 00022 to /u01/oradata/jldr_mstmt/index/mis_stmt_idx01.dbf
restoring datafile 00075 to /u02/oradata/jldr_ods/index/ods_idx19.dbf
restoring datafile 00081 to /u02/oradata/jldr_ods/index/ods_idx21.dbf
restoring datafile 00085 to /u01/oradata/jldr_jbl/index/jbloader_idx04.dbf
restoring datafile 00091 to /u02/oradata/jldr_ods/index/ods_idx24.dbf
restoring datafile 00096 to /u02/oradata/jldr_ods/index/ods_idx26.dbf
restoring datafile 00112 to /u02/oradata/jldr_ods/index/ods_idx28.dbf
restoring datafile 00114 to /u02/oradata/jldr_ods/index/ods_idx30.dbf
restoring datafile 00116 to /u02/oradata/jldr_ods/index/ods_idx32.dbf
restoring datafile 00121 to /u01/oradata/jldr_sys/data/audit.dbf
Now, when I connect to database and try to see rman jobs:
sqlplus>select SID, START_TIME,TOTALWORK, sofar, (sofar/totalwork) * 100 done, sysdate + TIME_REMAINING/3600/24 end_at from v$session_longops where totalwork > sofar AND opname NOT LIKE '%aggregate%' AND opname like RMAN%' ;
SQL> @longops_rman.sql
SID START_TIME TOTALWORK SOFAR DONE END_AT
---------- ----------------- ---------- ---------- ---------- -----------------
10 27/06/10 10:24:12 4654592 0 0
12 27/06/10 10:24:36 15918960 0 0
However, when we see from IBM TSM, it shows data is being moved from the tape storage to the machine by rman session. However, I cannot see anything in rman job inside database. Remember db is in 'startup nomount' state.
Br,
--
Anjum