RMAN session

Hi ,
The DB version is 10.2.0.4. Whenever the archive log destination is full, the users were not able to login in to the database which means no new sessions are created. Using RMAN i used to delete the old archives older than n days. How does rman make a connection , creates a session to the database for this delete process??
baskar.l

baskar.l wrote:
Hi ,
The DB version is 10.2.0.4. Whenever the archive log destination is full, the users were not able to login in to the database which means no new sessions are created. Using RMAN i used to delete the old archives older than n days. How does rman make a connection , creates a session to the database for this delete process??
baskar.lRMAN uses the Sys connection . If you check the alert log , it says, connect as Internal user . Since the internal was desupported since 9i and Sys has got the same functionality, RMAN can work using it.
Aman....

Similar Messages

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
[email protected]:/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

Hi,
Just a thought that having the TIMED_STATISTICS parameter set to FALSE or failing to gather the statistics for the objects using DBMS_STATS are two possible reasons for no data through the v$session_longops.
regards

RMAN Session in Hung Status

Hi ,
We have observed few issue while backing up the archive logs through tapes ( Symantec Backup). Backup team told us that they are not able to see the jobs at their end running , while we are triggering the backup . Later on we find lot of rman session active in the database ( 27 RMAN Session in v$session)
I have few question :
> If there are already rman session which are in hung state , Even if we trigger the new backup , Will that complete trigger or they will also went into the hug state. ( I think new session will also goes into the hung state) . Symantec backup team said they don't have any issue at their end.
>Generally we kill the all the backup processes at OS level ( ps -ef | grep rman & ps -ef | grep backup ) , Is that possible still few RMAN session doesn't get killed from v$session. ( I am not sure about this , As per my understanding , if we kill any rman session at the OS level , it should be killed from the v$session)
Database Version : 11gR2
OS : AIX 6.1
BACKUP : Symantec backup
REgards
Sourabh GUpta

Hi ,
We are just trying to find the RCA for this , I have few doubts based on that I will troubleshoot this :
> If there are already rman session which are in hung state , Even if we fire the new backup , Will that complete or they will also went into the hug state. ( I think new session will also goes into the hung state) . Symantec backup team said they don't have any issue at their end.
>Generally we kill the all the backup processes at OS level ( ps -ef | grep rman & ps -ef | grep backup ) , Is that possible still few RMAN session doesn't get killed from v$session. ( I am not sure about this , As per my understanding , if we kill any rman session at the OS level , it should be killed from the v$session)
Regards
Sourabh Gupta

What to do if there is abrupt termination of RMAN during a backup session

Hi All,
I am trying to automate the Level 0 and Level 1 backups which we ought to take. Following the is the RMAN related part of it for L1 backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;"
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '${BKP_LOCATION}/${LType}_%F';"
run {"
allocate channel c1 type disk;"
backup"
incremental level 1 cumulative tag = $BTAG"
format '${BKP_LOCATION}/${LType}_%d_set%s_piece%p_%T_%U.bkp'"
(database include current controlfile tag $CTAG) ;"
sql 'alter system archive log current';"
sql 'alter system archive log current';"
backup archivelog from sequence ${CSEQ} tag $ATAG"
format '${BKP_LOCATION}/${LType}_Arch_%d_set%s_piece%p_%T_%U.bkp';"
release channel c1;"
exit;"
In the above snippet, the variables are substituted for within a shell script and then put into a command file for RMAN. I am a novice in the backup and recovery. I got above piece of code from someone working on RMAN and built my automation logic around it.
The script works fine and I am trying to build to script level recovery feature around it. My question is:
-- What happens if I invoke the script, the backup session starts and then there is abrupt termination of the RMAN session either because of losing the db connection or receiving an interrupt signal or a kill signal or some other weird reason.
-- What if I re-invoke my script? Will it start from the point where it was stopped earlier or would it start from the point where we had last successful Level 1 backup completed?
Thanks in Advance.

Hi user781131,
What happens if I invoke the script, the backup session starts and then there is abrupt termination of the RMAN session either because of losing the db
connection or receiving an interrupt signal or a kill signal or some other weird reason?The backup set which rman was creating is not commited due to the abnormal termination but all succesfull backup sets can be used.
What if I re-invoke my script? Will it start from the point where it was stopped earlier or would it start from the point where we had last successful Level 1 backup
completed?In your backup script you do not use the < NOT BACKED UP SINCE TIME > clause so it will again do a level 1 backup off all datafiles.
See:
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1017236
This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up. If AS BACKUPSET is set, then this feature is only useful if RMAN generates multiple backup sets during the backup.
Regards,
Tycho
Edited by: tychos on 28-jan-2010 15:21

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

Regarding rman user session

hi all,
i need to create a trigger for tracing a particular user session or rman session so that only one trace file is used throughout, regardless of there number of logins or logoff
thanks

Create a logon trigger, that checks for a certain login-name
We do the same for checking applications that log on.
Remember that if you're calling a procedure from the logon trigger, you have to disable the trigger every time you work/develop on the procedure.
Otherwise the trigger gets Invalid and all logons are denied
I can't show you the code we use now, because our storage-network has failed
Edit: Back online
The code
CREATE OR REPLACE TRIGGER check_logon_logging
after logon on database
begin
illegal_appl_prc;
end;

Oracle 3113 creating a standby with rman

Hello,
environment is 11gR2 on Linux.
Tested on CentOS 5.5 as OS and local LAN as interconnect and the duplicate command terminates successfully in some minutes.
Same script but using oel 5.5 and a wan (3Mbit/s) and I keep getting 3113 errors after about 2h or 3h.
I suspect some timeout on wan (that is over vpn) but I would also like to trace something at my side.
I run a shell script with nohup and send it to background and this is the log, from which you can see the rman script:
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 14:50:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: TESDB1 (DBID=11492743)
RMAN>
connected to auxiliary database: DUMMY (not mounted)
RMAN>
RMAN> run{
2> allocate channel prmy1 type disk;
3> allocate auxiliary channel stby1 type disk;
4> duplicate target database for standby from active database
5> spfile
6> parameter_value_convert 'TESDB1','TESDB1DR'
7> set db_file_name_convert='/TESDB1/','/TESDB1DR/'
8> set log_file_name_convert='/TESDB1/','/TESDB1DR/'
9> set 'db_unique_name'='TESDB1DR'
10> set control_files='/app/oradata/TESDB1DR/control01.ctl','/app/oradata/flash_recovery_area/TESDB1DR/control02.ctl'
11> set db_recovery_file_dest='/app/oradata/flash_recovery_area'
12> set DB_RECOVERY_FILE_DEST_SIZE='4977M'
13> nofilenamecheck;
14> }
using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=12 device type=DISK
allocated channel: stby1
channel stby1: SID=135 device type=DISK
Starting Duplicate Db at 07-SEP-10
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /app/oradata/TESDB1DR/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting backup at 07-SEP-10
channel prmy1: starting datafile copy
input datafile file number=00003 name=/app/oradata/TESDB1/undotbs01.dbf
.. after about three hours (and 3.2Gb transferred) it continues with:
RMAN-03009: failure of backup command on prmy1 channel at 09/07/2010 17:53:49
RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
Process ID: 3187
Session ID: 192 Serial number: 3
continuing other job steps, job failed will not be re-run
.. after 15 minutes:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2010 18:09:35
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on clone_default channel at 09/07/2010 18:09:34
RMAN-10038: database session for channel clone_default terminated unexpectedly
RMAN> **end-of-file**
RMAN>
Recovery Manager complete.
the undo tbs is 3.2 Gb so I'm not sure if the 3113 happens at the end of copy... but the tablespace doesn't succeed
and the other jobs don't start even if it says "continuing other job steps"..
rman started at 14:50 and in listener at dr site I have:
Tue Sep 07 14:50:55 2010
07-SEP-2010 14:50:55 * service_update * TESDB1DR * 0
07-SEP-2010 14:50:55 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=oracle)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35240)) * establish * TESDB1DR * 0
Tue Sep 07 15:00:58 2010
07-SEP-2010 15:00:58 * service_update * TESDB1DR * 0
Tue Sep 07 16:35:04 2010
07-SEP-2010 16:35:04 * service_update * TESDB1DR * 0
Tue Sep 07 17:02:04 2010
07-SEP-2010 17:02:04 * service_update * TESDB1DR * 0
07-SEP-2010 17:02:10 * service_update * TESDB1DR * 0
Tue Sep 07 17:53:17 2010
07-SEP-2010 17:53:17 * service_update * TESDB1DR * 0
Tue Sep 07 18:09:00 2010
07-SEP-2010 18:09:00 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=rman)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=32610)) * establish * TESDB1DR * 0
In alert.log at dr site I have at 17:02 (about 50 minutes before error):
Tue Sep 07 15:05:01 2010
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Sep 07 17:02:03 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:02:03
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35226))
some times (always at 17:02) and nothing more
In alert.log at primary site:
Tue Sep 07 14:50:36 2010
Clearing standby activation ID 11529351 (0xafec87)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
Tue Sep 07 16:00:40 2010
Thread 1 advanced to log sequence 759 (LGWR switch)
Current log# 3 seq# 759 mem# 0: /app/oradata/TESDB1/redo03.log
Tue Sep 07 16:00:41 2010
Archived Log entry 528 added for thread 1 sequence 758 ID 0xafec87 dest 1:
In sqlnet.log of primary site:
Tue Sep 07 17:53:49 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:53:49
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.12.41)(PORT=1521))
and the same at 18:09
No other errors.
Any hints?
BTW: what is the minimum size of undo tbs? Can I have compression enabled also during duplication if transport service is configured with COMPRESSION=ENABLED, or does it count only when copying redo files?
Thanks in advance,
Gianluca

Thanks for your reply.
I will try your suggestion as it could come useful some time.
So with this alternate method at the end I would have standby aligned as of backup time, correct?
And after running something like this on standby:
SQL> alter database recover managed standby database disconnect from session;
It will begin to receive, archive and apply redo logs, correct?
Some answers regarding the original question. It was confirmed that there was a 2hours cut-off time at firewall level.
The first datafile that the rman session began to copy was 3.2Gb in size, taking more than 2 hours completing.
Monitoring with netstat on source and target I saw this at source during the duplicate process:
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
tcp 0 369240 10.49.1.93:50371 192.168.12.41:1521 ESTABLISHED
and the session bound to port 50371 was the only one pushing data (send queue not empty).
The other 3 ones I presume are for control of rman session. I get 3 sessions even if I open only one channel on primary side.
After the first datafile completes copy, a new session (with port 14871) is established substituting the other one.
The three initial ones instead remain for all the duplicate process.
tcp 0 487872 10.49.1.93:14871 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
So after the copy of the first file, the session come back to one or more of the initial 3 ones, and they probably make a push-ack, got a 3113 as the firewall has silently cut them after 2 hours.... and the datafile, even if completed, is not marked as completed. A new run would copy again it...
Now the time has been put to 8hours, with 24hours being the maximum value set (no disable possible as far as the network guy said...).
And the duplicate completed correctly.
Would I have to fear any problems with this cut-off due to "normal" dataguard operations or not, in your opinion?
Thanks
Gianluca

To see the rman process running on UNIX

Hi
What is command on AIX / UNIX to see if we have any rman processes still running?
Thanks.
I tried ps -ef | grep oraprod (user) but see no rman processes.
Many thanks

There are 2 things what should be checked:
1. from unix side as already pavan mentioned
ps -ef | grep rman
2. from oracle side to look for rman sessions:
select * from v$session where program like 'rman%';
If both requests return nothing - rman had finished his job and already from logfiles or with help of rman commands (list, report) You can understand īs the job done or not.

RMAN-03002: failure of recover command

Hi all,
I am testing a new backup and restore mechanism of a 11.2 system in Linux. A third mirror of the disks from the database server has been split and mounted in a media server. An RMAN backup was taken then, on tape, using HP Data Protector. Then, in the media server again, I mounted all the disk groups and removed all the files from ASM via asmcmd. With everything cleared, I proceeded in doing the following:
1. Started up nomount using an old PFILE.
2. Initiated an RMAN session and SET DBID, connected to the target and the catalog. Restore the SPFILE in a PFILE.
3. Shutdow and started up nomount with PFILE the newly created file (edited it first to comment out CLUSTER_DATABASE parameter, as the media server is not configured for this).
4. Restored the contorl file. This was done successfully.
5. Restored the database. This was done successfully.
6. Mounted the database and attempted to recover it. I received the following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/12/2013 09:42:24
RMAN-06094: datafile 1 must be restored
7. I attempted a recover from SQL*Plus; the error message was a little more helpful:
SQL> recover database using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
8. I checked my source database and the file name is as it appears above. But in the restored system, the file has a different name:
ASMCMD> pwd
+BT1_A_SYSTEM/BT1_A/DATAFILE
ASMCMD> ls -l SYSTEM*
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE JUL 11 16:00:00 Y SYSTEM.257.820514399
9. OK. I presume that this happened because we are using OMF. But, I was expecting RMAN to specify the full file names and thus restore them with their original names. The problem is now that the control file has the original file names, which cannot be found in the media server, where the restore took place. I am wondering if I should MOUNT the database after the control file restore and before I start the database restore, so RMAN might have the opportunity of renaming the file names in the control file.
Has anyone encountered this problem? I would appreciate some help.
Regards,
Takis.

That is correct Hemant. I latter realised my mistake.
When I mounted the database, the control file was opened. Then I repeated the restore. RMAN, this time was able to access the control file and rename dynamically the files, as they were restored and getting their new names.
So, I think, the correct sequence of events may be:
1, Check in ASM if the disk groups are mounted (lsdg). If not, mount the disk groups (alter diskgroup <dg_name> mount;).
2. Startup nomount (if no PFILE available, create a simple one with only db_name in it).
3. From RMAN, set DBID and then connect to target and catalog.
4. restore spfile to pfile from autobackup
5. restore control file(s) from autobackup
6. alter database mount
7. restore database
8. restore archivelog all
9. recover database
10. alter database open resetlogs
In my case, this worked, by enslarge. RMAN stopped when it run out of archived redo logs.
I then attempted, via SQL*Plus:
recover database using backup controlfile until cancel
When prompted, I typed: CANCEL
That was fine, but then, when I attempted:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 525336576 bytes disk space from 2147483648 limit
So, I needed to increase the parameter db_recovery_file_dest_size which I did (in the pfile; luckily I had available space in the disk group). I shut down and started up (mount). Then:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-00392: log 24 of thread 2 is being cleared, operation not allowed
ORA-00312: online log 24 thread 2: '+BT1_A_RECO'
So:
SQL> alter database clear unarchived logfile group 24;
Database altered.
SQL> alter database open resetlogs;
Database altered.
SQL> select * from dual;
D
X
Happy days!
Regards,
Takis.

RMAN in DataGuard Technology

Hi,
our Business requirement is:
1-having Full backup on Sat on produciton side and incremental backup every day.
2- Having Full backup on Sun on Standby database and incremental backup every day.
to fulfill these requirement i did the following:
1- inremental backup 0 on prod on Sat and Differential incremental backup 1 every day and store in directory called /prod/
2- Incrementally Updated Backups starting On Sun on the standby side and run every day, and store in directory called /standby/
I read the documentiaiton and it says the best practice is doing the following:
having Catalog database==> done.
having unique database name on prod and each standby DB==> done.
do Incrementally Updated Backups on standby side to minimze the performance in the prod side ==> done.
take control backup and spfile on the prod db==> done
i followed those essential best practice from Oracle documentation and i just add one thing which is taking the backup alos in the prod side.
now when i run list backup command from RMAN session and i can see the backup in both servers prod and standby, and if i lunched from prod server, i can see the backup that taking in both servers registered in catalog, however for standby db the status is expired which is makes sence because those backup files phyisical not excite in the prod server and the same thing happen if i lunched the rman from standby server, i found the backup of prod is expired.
Now My questions:
1-How can i force catalog to distingusih between those 2 backup and doesnt give me expired status?
2- i set up the retention policy for 7 windows day, it works fine for the stanby database and delete those files that > 7 but in prod doesnt work, looks like couldnot solvo the retention policy and i guess because i am taking full backup 0 on Sat and this against the Incrementally Updated Backups that takes on Sun, How can i solve this one?
3- i did restore senario for the backups i am taking on test server and the result was for the Incrementally Updated Backups that took on standby, i was able to restore and recover to the point i want and it works like the way it should be, but when i did another restore senario with the backup from prod server, didnt work, it restore the full backup 0 and then didnt apply the incremetail backup i have from the following day, however it asks for applying archives log instead of using the incremental backup, i though RMAN smart enough to choose between restore from incremental or from archives. How can i restore with DB with the backup i have from prod? btw, when i did the restore senario on test, i didnt connect to catalog though, i only connect to targer in both senarios
rman targe /
RMAN >.......
4- Should i stop taking backup on prod side and stay enough with the Oracle recommendation by taking only Incrementally Updated Backups on standby DB?
THE PARAMETER SETTING IS
on the prod side:
oracle:XXX:/export/home/oracle # rman target / catalog rman/rman@catalog
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: XXX (DBID=1665948166)
connected to recovery catalog database
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/10.1.0/dbs/napcf_XXX.f'; # default
RMAN> exit
Recovery Manager complete.
Finally MY OS is linux
DB is 10.1.5
I am sorry for long thread but i want to be clear as possible and I can and Thanks for the help and suggestion.

Firstable, thanks God that some1 finally answer the question.
All your points are correct and that is what i followed exactly, and if you read my thread you will notice that i did follow the practice correctly, however, as i mentions it is business requirement that ask to have 2 back up on prod as well as on standby ( and the backup on prod is extra step as i said in my thread , i know it is not part of the best practice ), for me as DBA i agree with only one backup in standby DBs, but again this is business requirement not my decision.
The key concept is there is 1 database, and only 1 backup is required, either primary or standby, not both.
this is not really true,
check this pdf file from Oracle on Appendix A, http://www.oracle.com/technology/deploy/availability/pdf/RMAN_DataGuard_10g_wp.pdf
you will find it is possible to have backup on primary as well as standby, but my only problem is with the Catalog how can i enforce them to recoginze those backups especially when i lunched the delete commands, i need to delete file that not satisfy my retention policy, due to the fact that there are 2 full backup happen in different time on Sat in prod server and on Sun standby , looks like the catalog couldnt solve this issue, therefore when crosscheck and delete command issue couldnot delete the backup that more than 7 days.

RMAN failure for "archive-log ... not found in controlfile"

Recovery Manager: Release 8.1.6.0.0 - Production
RMAN> connect target sys/XXXX@cldb;
2> connect catalog rman/XXXX@rmandb1;
3>
4> resync catalog;
5>
6> # Backup the database
7> run {
8> allocate channel ch1 type disk;
9> backup incremental level 0 format
10> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_%t_%s_%p' database;
11> sql 'alter system archive log current';
12> }
13>
14> # Backup the archived redo logs
15> run {
16> allocate channel ch1 type disk;
17>
18> backup incremental level 0 format
19> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_%t_%s_%p' archivelog all;
20> sql 'alter system archive log current';
21> }
22>
23> # Backup the control file
24> run {
25> allocate channel ch1 type disk;
26> sql 'alter database backup controlfile to trace';
27> copy current controlfile to
28> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/controlfile.bak';
29> }
30>
31>
RMAN-06005: connected to target database: CLDB (DBID=1292102281)
RMAN-06008: connected to recovery catalog database
RMAN-03022: compiling command: resync
RMAN-03023: executing command: resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel ch1: starting incremental level 0 datafile backupset
RMAN-08502: set_count=816 set_stamp=422358010 creation_time=22-FEB-01
RMAN-08010: channel ch1: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00001 name=/opt/orabase/oradata/cldb/system01.dbf
---snip----
more like this
---snip----
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_422358010_816_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:01:46
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03022: compiling command: sql
RMAN-06162: sql statement: alter system archive log current
RMAN-03023: executing command: sql
RMAN-08031: released channel: ch1
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=17 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: backup
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=817 set_stamp=422358179 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=85 recid=2610 stamp=422352397
RMAN-08504: input archivelog thread=1 sequence=86 recid=2611 stamp=422352397
----snip----
more similar stuff here
----snip----
RMAN-08504: input archivelog thread=1 sequence=140 recid=2732 stamp=422358121
RMAN-08013: channel ch1: piece 1 created
RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_422358179_817_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:00:17
RMAN-08009: channel ch1: starting archivelog backupset
RMAN-08502: set_count=818 set_stamp=422358197 creation_time=22-FEB-01
RMAN-08014: channel ch1: specifying archivelog(s) in backup set
----snip----
more like this
----snip----
RMAN-08504: input archivelog thread=1 sequence=164 recid=2756 stamp=422358123
RMAN-08504: input archivelog thread=1 sequence=165 recid=2757 stamp=422358123
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAG E STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel ch1
RMAN-10035: exception raised in RPC: ORA-19571: archived-log recid 2011 stamp 419161314 not found in controlfile
RMAN-10031: ORA-19571 occurred during call to DBMS_BACKUP_RESTORE.BACKUPARCHIVEDLOG
I added the resync catalog command to the backup. But I am still getting this error. What is happening? I have the control_file_record_keep_time = 14 in the paramater file. Do I need to change this to something greater?
null

The error message is pointing to an inconsistency between what RMAN "thinks"
should be there and what is in control files.
There are a few things you can try to do
1. Compare V$LOG, V$LOGFILE, etc. Some of these views are based on control files
2. Shutdown and restart the instance.
This may help in synchronizing control files
with internal structures.
3. Trace RMAN session using oradebug and even 10046 to find out what it is doing
4. Dump entire controlfile to trace using
alter session set events 'immediate trace name controlf level 10';
Or dump loghist only
alter session set events 'immediate trace name loghist level 4';
This will dump 2**level entries.
5. Re-create controlfiles with CREATE CONTROLFILE
Regards,
Sev

Can rman backups be used to restore to a different server

We are using R12 with 10gr2 database
If i take Rman backups, can they be used to restore on some other test server for cloning and bringing that test server upto date like the production.
I am confues and dont know and This is the only reason i dont use rman for backups, instead take cold backups manually every night as they are used every week to clone some other server for testing purpose
Please advice
Thanks

Hi..
1. Copy the pfile to the new server.
2. startup nomount the database using the pfile.
3. Open a new RMAN session and connect to this database
4. Restore the controlfile, this will bring the database in mount stage
5. Once step 4 is completed, restore and recover the database.
NOTE:-- These are the steps for restoring the database when the RMAN backup pieces are copied to the same location as they are on the main server.If you copy the rman backup to some different location, then you will have to use the CATALOG BACKUPPIECE 'location' command before restoring the database.
Go through [http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmdupdb.htm]
HTH
Anand
Edited by: Anand... on Dec 23, 2008 8:13 PM Added link

How to stop RMAN backup in solaris platform.

Dear All;
How to stop RMAN backup in solaris platform.
Ranjan

788442 wrote:
How to stop RMAN backup from oracle end.
To stop Rman backup you have to identify rman session as below
select * from v$session
where MODULE like 'rman%'or you can use v$rman_status identify sid and serial then kill this session as
alter system kill session '<sid>,<serial>' immediate;

Rman backup command hangs for datafile ,works with archivelogs backup.

Issue is archivelogs backup is going fine ,But when we go for datafile backup its hanging there from oracle side as not able to give file handle.
RMAN session started with debug it gives only
DBGRPC: ENTERED krmqgns [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: looking for work for channel default (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: commands remaining to be executed: (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: CMD type=backup cmdid=1 status=STARTED [expect.cpp/673]
16:00:40.19 DBGRPC: 1 STEPstepid=1 cmdid=1 status=STARTED [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: no work found for channel default (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: EXITED krmqgns with status 1 [expect.cpp/673]
16:00:40.19 DBGRPC: krmxpoq - returning rpc_number: 17 with status: STARTED16 for channel sqlbt_ch1 [expect.cpp/673]
16:00:40.19 DBGRPC: krmxr - sleeping for 10 seconds [expect.cpp/673]
Is any body seen this type of message from rman.
Thanks
Shirish

OK. Did you miss the second Oracle document?
RMAN Debug For Backup Shows "krmxr: sleeping for x seconds" [ID 458259.1]
Also a ton of information here :
RMAN backup database as copy from file system to ASM diskgroup very slow
and here :
RMAN Error > Please assist!
and here :
RMAN and Amazon Web Services
http://oravdba.blogspot.com/2011_01_01_archive.html
Best Regards
mseberg

How to view RMAN errors using v$views?

Hi,
From v$rman_status, i got the following output. But how to know what kind of errors throu v$views.
SID RECID STAMP PARENT_RECID PARENT_STAMP SESSION_RECID
SESSION_STAMP ROW_LEVEL ROW_TYPE COMMAND_ID
OPERATION STATUS MBYTES_PROCESSED
START_TIM END_TIME INPUT_BYTES OUTPUT_BYTES OPT OBJECT_TYPE OUTPUT_DEVICE_TYP
0 6540 734738844 6540
734738844 0 SESSION 2010-11-10 22:07:21
RMAN COMPLETED WITH ERRORS_ 0
10/NOV/10 10/NOV/10 0 0 NO
-thanks
Sakthi.

Hi Sakthivel
From v$rman_status, i got the following output. But how to know what kind of errors throu v$views. You need to query v$rman_output for the info.
first determine the session_stamp (or use the one from v$rman_status):
select distinct session_stamp
from v$rman_output order by session_stamp desc;Than use
select output from v$rman_output
where session_stamp like '&session_stamp%'
/to get the output of the rman session.
Rgds,
Tycho

RMAN session

Similar Messages

Maybe you are looking for