RMAN Message

Hi,
I am using a Backup Application "Omniback" from HP.
This Application uses RMAN internally to manage the Backup.
Here are some messages that I get and I am not sure what it means.
Can someone help with this ?
RMAN-08013: channel dev_0: piece 1 created
RMAN-08503: piece
handle=LTO_PRODAH_DB_ALL_DELARC<ORCL_21313:519096986:1>.dbf comment=API
Version 1.0,MMS Version 1.0.0.0
RMAN-08525: backup set complete, elapsed time: 00:00:15
RMAN-08071: channel dev_0: deleting archivelog(s)
RMAN-08514: archivelog
filename=R:\ORACLE\ORADATA\PRODAH\ARCHIVE\ORCLT001S16873.ARC
recid=16780
stamp=519022856
RMAN-08013: channel dev_1: piece 1 created
RMAN-08503: piece handle=LTO_PRODAH_DB_ALL_DELARC<ORCL_21314:519096986:1>.dbf comment=API
Version 1.0,MMS Version 1.0.0.0
RMAN-08525: backup set complete, elapsed time: 00:00:15
RMAN-08071: channel dev_1: deleting archivelog(s)
RMAN-08514: archivelog filename=R:\ORACLE\ORADATA\PRODAH\ARCHIVE\ORCLT001S16874.ARC recid=16781 stamp=519022858
RMAN-08009: channel dev_0: starting archivelog backupset
RMAN-08502: set_count=21315 set_stamp=519097001 creation_time=02/26/2004 [01:36:41]
RMAN-08014: channel dev_0: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=16875 recid=16782 stamp=519022860
RMAN-08009: channel dev_1: starting archivelog backupset
RMAN-08502: set_count=21316 set_stamp=519097002 creation_time=02/26/2004 [01:36:42]
RMAN-08014: channel dev_1: specifying archivelog(s) in backup set
RMAN-08504: input archivelog thread=1 sequence=16876 recid=16783 stamp=519022862
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel dev_0
RMAN-10006: error running sql statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
[Major] From: http://us.f201.mail.yahoo.com/ym/[email protected]&YY=6774&order=down&sort=date&pos=0&view=a&head=b "" Time: 2/26/04
1:36:50 AM Oracle8 RMAN command failed with exit status: 3.
Couls someone help with this?
Thanks
Jaffery

I recommend you to open an iTAR.
Joel Pérez

Similar Messages

Show RMAN message in log file and screen at same time

Is there any way I can save all RMAN message in a log file and also show on standar out (screen).
Thanks

Hi,
You can try a shell script like this if you are using linux:
#!/bin/sh
# Name: test_backup
# Author: Tad_cs
# Description: Executes backup using the RMAN
export ORACLE_HOME=$1
export ORACLE_SID=$2
export LOG_DIR=$3
# Variables:
SCRIPT="test_backup"
data_log=`date '+%y-%m-%d_%H:%M:%S'`
logfile=${LOG_DIR}/${SCRIPT}-${data_log}.log
# Execution of script backup of rman:
$ORACLE_HOME/bin/rman <<EOF > $logfile
connect target rman/rman
connect catalog rman/rman
run { execute script test_backup; }
EOF
exitSo, While the script is performing, you can open other screen, search for
the log that is generating, and see the contents using:
tail -f log_file_name.logIs this you need?
[]´s

RMAN Message Log

While running RMAN 9.2.0.6 on AIX, I get various messages such as:
Starting backup at 19-JUN-05.
Finished backup at 19-JUN-05.
These messages do little to help me to time the individual steps of a RMAN process. Is there any way to get the date & time printed in these messages.

RMAN, as any other Oracle utility , uses the defined (explicitly or implicitly) NLS_DATE_FORMAT. So you have to change this to a format, which includes both: date and time.

RMAN error messages appear in Dutch

Dear all,
RMAN messages appear in Dutch language which is rather difficult to understand. Can anyone suggest how can I make the language to english.
from sql prompt alter session set nls_language and nls_territory has been given.
from enterprise manager the settings has been changes from dutch to english.
I am using Oracle 10g under Windows 2000. My windows 2000 is installed in dutch but oracle 10g was installed in english.
Thanks in advance
salim

You should set that in the DOS command line using the SET command.
Take as reference this other post:
Re: What time is scn...
Bye, Aron

RMAN 9i and 10g

Hi
In 10g the I just renamed the database(its not using ASM) and with recovery catalog I got :
Why I cannot see the list of incarnation in 9i? Should I run NID on both the envirionments to refeister them with the catalog?
Thanks in Advance
Regards
C:\Documents and Settings\XXX>rman target sys/pwd@tns catalog user/pwd@tns
Recovery Manager: Release 10.1.0.4.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ABC1 (DBID=307316191)
connected to recovery catalog database
RMAN> register database ;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 08/30/2007 16:37:58
RMAN-20002: target database already registered in recovery catalog
RMAN> list incarnation of database;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
468 475 EFG 307316191 PARENT 1 25-FEB-05
468 469 EFG 307316191 PARENT 303040 30-AUG-07
468 4052 ABC 307316191 CURRENT 350434 30-AUG-07
This is the output from 9i:
C:\Documents and Settings\XXX>rman target sys/pwd@tns catalog user/pwd@rcat
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ABC (DBID=2556242117)
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 08/30/2007 16:38:3
8
RMAN-20002: target database already registered in recovery catalog
RMAN> list incarnation of database;
RMAN>
Message was edited by:
Singh

Thanks for your time and reply and showing concern Daljit
Here is what I did on 10g. Can you please tell me the other method to rename the database other than using create controlfile?
Her is what I did on 10g environment and it worked but it didn't work on 9i:
RMAN> UNREGISTER DATABASE;
database name is "ABC1" and DBID is 307316191
Do you really want to unregister the database (enter YES or NO)? yes
database unregistered from the recovery catalog
RMAN> REGISTER DATABASE;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
on 9i I get:
RMAN> unregister database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "allocate, alter
, backup, beginline, blockrecover, catalog, change, connect, copy, create, cross
check, configure, duplicate, debug, delete, drop, exit, endinline, host, {, libr
ary, list, mount, open, print, quit, recover, register, release, replace, report
, renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, s
pool, startup, shutdown, send, show, test, upgrade, validate"
RMAN-01008: the bad identifier was: unregister
RMAN-01007: at line 1 column 1 file: standard input
On Recovery catalog database for 9i environment I get:
SQL> select * from user_catalog;
TABLE_NAME TABLE_TYPE
DB TABLE
RMAN_SEQ SEQUENCE
NODE TABLE
CONF TABLE
DBINC TABLE
CKP TABLE
TS TABLE
TSATT TABLE
DF TABLE
DFATT TABLE
OFFR TABLE
TABLE_NAME TABLE_TYPE
RR TABLE
RT TABLE
ORL TABLE
RLH TABLE
AL TABLE
BS TABLE
BP TABLE
BCF TABLE
CCF TABLE
XCF TABLE
BSF TABLE
TABLE_NAME TABLE_TYPE
BDF TABLE
CDF TABLE
XDF TABLE
BRL TABLE
BCB TABLE
CCB TABLE
SCR TABLE
SCRL TABLE
CONFIG TABLE
XAL TABLE
RSR TABLE
TABLE_NAME TABLE_TYPE
FB TABLE
RC_DATABASE VIEW
RC_DATABASE_INCARNATION VIEW
RC_RESYNC VIEW
RC_CHECKPOINT VIEW
RC_TABLESPACE VIEW
RC_DATAFILE VIEW
RC_REDO_THREAD VIEW
RC_REDO_LOG VIEW
RC_LOG_HISTORY VIEW
RC_ARCHIVED_LOG VIEW
TABLE_NAME TABLE_TYPE
RC_BACKUP_SET VIEW
RC_BACKUP_PIECE VIEW
RC_BACKUP_DATAFILE VIEW
RC_BACKUP_CONTROLFILE VIEW
RC_BACKUP_SPFILE VIEW
RC_DATAFILE_COPY VIEW
RC_CONTROLFILE_COPY VIEW
RC_BACKUP_REDOLOG VIEW
RC_BACKUP_CORRUPTION VIEW
RC_COPY_CORRUPTION VIEW
RC_OFFLINE_RANGE VIEW
TABLE_NAME TABLE_TYPE
RC_STORED_SCRIPT VIEW
RC_STORED_SCRIPT_LINE VIEW
RC_PROXY_DATAFILE VIEW
RC_PROXY_CONTROLFILE VIEW
RC_RMAN_CONFIGURATION VIEW
RC_DATABASE_BLOCK_CORRUPTION VIEW
RC_PROXY_ARCHIVEDLOG VIEW
RC_RMAN_STATUS VIEW
RCVER TABLE
RC_BACKUP_FILES VIEW
65 rows selected.
SQL>
Should I need to delete the entries from:
RC_DATABASE and
RC_DATABASE_INCARNATION
and try to register again?
Best Regards

RMAN backup multiple database on multiple hosts using recovery catalog

I would like to know if I create one schema called "rman" is enough for repository for backing up multiple database on multiple machines using recovery catalog.
Or is there any better way to handle for reporting peposes.
Quick response is appreciated.
OS Solairs9.
Oracle 9i.
Thanks.
Srini

This worked perfectly fine except for putting sbt in single quotes.
See the reults below.
You are just great Daljith.
Thanks and I do appreciate your help.
Still you did not answe my question.
How come I see backups from June and May even though they are from
diffierent catalog database?
RMAN> allocate channel for maintenance device type 'sbt';
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=9 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: VERITAS NetBackup for Oracle - Release 5.0GA (200)
RMAN> crosscheck backup;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_22_1_628264333 recid=17 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_21_1_628264333 recid=18 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_23_1_628265249 recid=19 stamp=628265249
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-00 recid=20 stamp=628266151
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_26_1_628266195 recid=21 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_25_1_628266195 recid=22 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-01 recid=23 stamp=628266233
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_29_1_628267004 recid=24 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_28_1_628267004 recid=25 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_30_1_628267919 recid=26 stamp=628267920
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-02 recid=27 stamp=628268832
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_32_1_628268875 recid=28 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_33_1_628268875 recid=29 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-03 recid=30 stamp=628268913
Crosschecked 30 objects
RMAN> delete expired backup;
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
11820 11804 1 1 EXPIRED SBT_TAPE bk_2_1_624018818
11821 11805 1 1 EXPIRED SBT_TAPE bk_1_1_624018817
11822 11806 1 1 EXPIRED SBT_TAPE bk_3_1_624019733
11823 11807 1 1 EXPIRED SBT_TAPE al_5_1_624020641
11824 11808 1 1 EXPIRED SBT_TAPE al_4_1_624020641
11825 11809 1 1 EXPIRED SBT_TAPE al_6_1_624020677
11826 11810 1 1 EXPIRED SBT_TAPE bk_8_1_624115253
11827 11811 1 1 EXPIRED SBT_TAPE bk_7_1_624115252
11828 11812 1 1 EXPIRED SBT_TAPE bk_9_1_624116161
11829 11813 1 1 EXPIRED SBT_TAPE al_11_1_624117067
11830 11814 1 1 EXPIRED SBT_TAPE al_10_1_624117067
11831 11815 1 1 EXPIRED SBT_TAPE bk_13_1_624365687
11832 11816 1 1 EXPIRED SBT_TAPE bk_12_1_624365686
11833 11817 1 1 EXPIRED SBT_TAPE bk_14_1_624366605
11834 11818 1 1 EXPIRED SBT_TAPE al_16_1_624367501
11835 11819 1 1 EXPIRED SBT_TAPE al_15_1_624367501
Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
deleted backup piece
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
deleted backup piece
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
deleted backup piece
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
deleted backup piece
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
deleted backup piece
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
deleted backup piece
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
deleted backup piece
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
deleted backup piece
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
deleted backup piece
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
deleted backup piece
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
deleted backup piece
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
deleted backup piece
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
deleted backup piece
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
deleted backup piece
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
deleted backup piece
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
Deleted 16 EXPIRED objects
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
11895 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11896 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11897 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11916 B F A SBT_TAPE 18-JUL-07 1 1
11926 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11927 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11935 B F A SBT_TAPE 18-JUL-07 1 1
11939 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11940 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11941 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11960 B F A SBT_TAPE 18-JUL-07 1 1
11970 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11971 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11977 B F A SBT_TAPE 18-JUL-07 1 1
RMAN>
Message was edited by:
user539835

ALL OPTIONS IN RMAN

제품 : ORACLE SERVER
작성날짜 : 1999-12-09
*** All options in RMAN ***
여기서는 rman에서 사용하는 모든 option의 list들을 보여준다.
target <connect-string>
rcvcat <connect-string>
cmdfile <filename>
msglog <filename>
debug
nocatalog
append
Option Description
1. target
Target은 target database의 connect string을 지정한다. 만약
"connect internal"과 같은 기능을 하고자 하려면 다음과 같이 type한다.
"target /"
2. rcvcat
rcvcat은 recovery catalog의 connect string을 지정한다.
3. cmdfile
Cmdfile은 RMAN이 input을 받을 화일 이름을 지정한다. 만약 이것이 지정되지
않으면 STDIN에서 input을 받는다.
4. msglog
msglog는 rman이 message를 내보낼 화일을 지정한다. 만약 이것이 지정되지
않으면 STDOUT으로 나간다.
5. debug
이것은 RMAN의 debug mode를 시작한다.
6. nocatalog
만약 recovery catalog를 가지고 있지 않으면 이 옵션을 사용해야 한다.
7. append
만약 "msglog"를 지정한다면 이 option은 그 화일에 overwrite하지 않고 append
할 것임.
NOTES:
대문자를 가지고 있지 않으면 인용부호를 이용할 필요는 없다. 유닉스에서는
back-slash를 가지고 인용부호를 사용해야 합니다. 예를 들어
cmdfile \'FOO\'
command line에서 target과 rcvcat을 반드시 지정할 필요는 없다. 왜냐하면
일단 RMAN이 시작되면 CONNECT 명령을 통해서 접속할 수 있기 때문이다.
좀더 자세한 사항은 Oracle8 backup and Recovery Guide를 참고하기 바란다.
trace option은 debug output이 지정된 화일로 전송되도록 한다.
만약 RMAN input file을 만들기 위해 shell script를 사용하고자 한다면
bourne-shell in-line file specification인 "<<"을 사용하기 보다 cmdfile
option을 사용해야 합니다.
그러므로, 다음과 같이 shell script를 짜는 대신에
rman target / nocatalog << EOF
rman-commands-here
EOF
다음과 같이 작성해 줍니다.
cat << EOF > /tmp/rmancmds.txt
rman-commands-here
EOF
rman target / nocatalog cmdfile /tmp/rmancmds.txt
'rman junk' 라고 입력하면 rman option의 full list를 볼 수 있을 것이다.

The only thing that I have heard other people try that has worked more times than on chance alone is to delete the iWeb application and then reinstall iWeb 1.0 from your iLife or recovery disks. Then update to 1.1.1 via Software Update.

OSB / RMAN configuration for recovery area backup

Hi
I am having trouble performing a recovery area backup to tape.
Current config
Media server - attached tape library (OSB installed as media server, admin and client - Contains RMAN Repository) - configured as per guide. I can see the library tapes and have tested an OSB filesystem backup to tape which was fine, this was done from the OSB GUI.
Server 1 - databaseA, DatabaseB (OSB client installed) .
ZFS device - Shared storage where the FRA for DatabaseA belongs. All databaseA backups go here (currently databaseA is running in nonarchivelog mode).
I have set the tape details for databaseA, done a backup to the FRA but the backup recovery area to tape backup just hangs, no real errors and the job list through the obtool and list the job it always has state as 'retryable', I am wondering if I have missed some configuration somewhere? I am using Grid control for this.
I did have a couple of RMAN messages tried to resolve this as per some metalink notes to no avail, I am assuming this is causing the problem? Or am I missing something else?
specification does not match any archived log in the repository
specification does not match any datafile copy in the repository
Can anyone help?

Rest the times on the servers and now get the following errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 10/28/2011 16:22:55
ORA-19506: failed to create sequential file, name="16mq8bjj_1_2", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
shmcheck: obscheduled reports that job 'oracle/16.1' has terminated with status 'failed'.
The action at time of failure was 'wait_for_resource'.
The error message was 'unknown'.
exit;

RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE

제품 : RMAN
작성날짜 : 2002-12-09
RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
==========================================================
PURPOSE
이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
설명할 것이다.
How to restore archive logs with limited disk space
Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
file이 restore될 disk의 space를 control할 수 있게 해 준다.
만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
마지막 archive log가 적용될 때마다 발생한다.
MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
실수를 하지 않게 해 준다.
아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
STEP 1: Add data to the database to enforce log switches
STEP 2: Backup the database and archive logs and delete the logs
STEP 3: Add additional data to enforce new log switches
STEP 4: Remove the data file and simulate a database crash
STEP 5: Restore the data file from the backup
STEP 6: Recover the database using MAXSIZE
위 예제는 Unix와 Windows 모두에 적용될 수 있다.
STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
1) MAXSIZE가 archive log size보다 작은 경우:
이 경우 RMAN-6558 Error message를 만나게 된다.
그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
2) MAXSIZE가 archive log size보다 큰 경우:
예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
restore/recovery는 user에게 transparent하게 수행되어진다.
즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
아무런 Message도 발생시키지 않는다.
# Step 1: INSERT enough new data to generate log switches
create table rman_tst (col1 varchar2 (10));
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 2: BACKUP the database and the archive logs automatically
# and then delete the input
run {
backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
delete input;
# Step 3: INSERT enough new data to generate new log switches
begin
for i in 1..30000 loop
insert into rman_tst values(i,'test');
commit;
end loop;
end;
# Step 4: REMOVE users01.dbf file and crash the database
mv users01.dbf users01.org
shutdown abort
# Restore is now needed as the data file is deleted. The backup was
# taken before the new data was added to it, thus archive logs are
# needed to bring the database up to date
# Step 5: RESTORE the data file from the full backup
run {
restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
# Step 6: RECOVER
run {
recover database delete archivelog maxsize 10 K;
# This will fail with RMAN-6558 as the archived log has a size of 16 KB,
# which is bigger than MAXSIZE limit of 10 KB. So the error is expected
# and MAXSIZE works as designed.
# Now rerunning STEP 6: but with MAXSIZE 50 K
run {
recover database delete archivelog maxsize 50 K;
RELATED DOCUMENTS
Recovery Manager Reference, Release 2 (9.2)

cold backup means offline backup, you shut database normally and copy datafiles to another location.
i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
backing up archivelogs whith rman script which is:
run {
allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
change archivelog all validate;
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
release channel c1;
so here is the details.
1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
So
first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
and then restore them and then apply them.
we need rman commands to register these backups and restore them.
Regards,
Kamil

Error Message from RMAN after backup

Hello,
I get this message when i try to backup a imported database:
RMAN-00571: ==================================================
=========
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ==================================================
=========
RMAN-03007: retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel tut
RMAN-10035: exception raised in RPC: ORA-19502: write error on file "/ora_db/backup/SKR/test.bak", blockno 238593 (blocksize=512)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
Additional information: 238593
Additional information: 1024
Additional information: 239121
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
The RMAN ist configured correctly because i can backup the database before importing the dumpfile.
I tryed to set the Parameter SETSIZE but then i get a different error message.
Discspace free: 50 GB
I hope someone can help me.
Thorsten

OK,
its already done, you have to set "setsize" (Thanks to th e helper).
But why?

RMAN ALert Log Message: ALTER SYSTEM ARCHIVE LOG

Created a new Database on Oracle 10.2.0.4 and now seeing "ALTER SYSTEM ARCHIVE LOG" in the Alert Log only when the online RMAN backup runs:
Wed Aug 26 21:52:03 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:52:03 2009
Thread 1 advanced to log sequence 35 (LGWR switch)
Current log# 2 seq# 35 mem# 0: /u01/app/oracle/oradata/aatest/redo02.log
Current log# 2 seq# 35 mem# 1: /u03/oradata/aatest/redo02a.log
Wed Aug 26 21:53:37 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:53:37 2009
Thread 1 advanced to log sequence 36 (LGWR switch)
Current log# 3 seq# 36 mem# 0: /u01/app/oracle/oradata/aatest/redo03.log
Current log# 3 seq# 36 mem# 1: /u03/oradata/aatest/redo03a.log
Wed Aug 26 21:53:40 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/u03/exports/backups/aatest/c-2538018370-20090826-00'
I am not issuing a log swiitch command. The RMAN commands I am running are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/exports/backups/aatest/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u03/exports/backups/aatest/%d_%U';
BACKUP DATABASE PLUS ARCHIVELOG;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-2';
I do not see this message on any other 10.2.0.4 instances. Has anyone seen this and if so why is this showing in the log?
Thank you,
Curt Swartzlander

There's no problem with log switch. Please refer to documentation for more information on syntax "PLUS ARCHIVELOG"
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref377
Adding BACKUP ... PLUS ARCHIVELOG causes RMAN to do the following:
*1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*2. Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.*
*3. Backs up the rest of the files specified in BACKUP command.*
*4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*5. Backs up any remaining archived logs generated during the backup.*
This guarantees that datafile backups taken during the command are recoverable to a consistent state.

RMan Error message Please Help

Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valide

Hi,
First of all I would not use RMAN as a tablespace name. It may be confusing oracle and besides it maybe a reserved term not available for use and a cause for some of those errors listed.
But here is what is in my notes that work.
After the database is created named RCAT you must create the user RMAN. It is then after he is created the program will run.
Create user RMAN
SQL> CREATE TABLESPACE CATTBS
'D/ORACLE/ORADATA/RECAT' SIZE 5M
AUTOEXTEND ON;
CREATE USER RMAN IDENTIFIED BY RMANTEMPORARY TABLESPACE TEMP
DEFAULT TABLESPACE CATTBS
QUOTA UNLIMITED ON CATTBS;
After the user has been created you need to grant some permissions for him to use.
GRANT RECOVERY_CATALOG_OWNER TO RMAN;
COMMIT;
GRANT CONNECT,RESOURCE TO RMAN;Now you need to create the RECOVERY CATALOG
Go to the host operating system oracle/ora81/bin/RMAN.EXE and execute this script the following prompt shows up.
RMAN>
You now need to create the CATALOG in tablespace CATTBS.
RMAN>CREATE CATALOG TABLESPACE CATTBS;
responds with
RMAN>RECOVERY CATALOG CREATED
Now you need to run these two scripts CATALOG.SQL AND CATPROC.SQL
RMAN>@D:\ORACLE\ORA81\RDBMS\ADMIN\CATALOG.SQL
\CATPROC.SQL
Running these two scripts now allows you to view the recovery catalog views.
This completes the setup of the recovery catalog database.
Now connect to your target
RMAN> connect target internal/oracle@ora
RMAN> connect RCVCAT rman/rman@rcat
Give the command to register database:
RMAN>register database
it responds with
RMAN>database registered in recovery catalog
You need to connect to the RCAT database with the following command:
RMAN>CONNECT CATALOG RMAN/RMAN@RCAT;
Hope this format helps.
Al

Defer log shipping and RMAN-08137 message when doing archivelog backup

Hello,
in a Primary & Dataguard scenario in which we set to DEFER the log shipping to the Dataguard during a high impact process done in the Primary, we receive the message "RMAN-08137: WARNING: archive log not deleted as it is still needed" when doing archive log backup with rman.
Is it the expected behaviour due to the DEFER status with the Dataguard? or even in this scenario we might we able to delete the logs and therefore we have to look more in deep to find our problem?
Thanks in advance for your help.

Hello,
Had a look on v$archived_log and found the archivelogs that are not deleted and the state for them is
DEST_ID=1
STANDBY_DEST=NO
ARCHIVED=YES
APPLIED=NO
as http://docs.oracle.com/cd/B12037_01/server.101/b10755/dynviews_1015.htm says , they are all Local, were archived and there is no apply needed for them as they are not defined to go to the StandBy Database.
Therefore, why can not still archive them? How can we check if they had been processed by a Streams process?
Regards

How rman backup messages printed in alert file?

surprised how the messages of rman getting printed in alert file?
i am using 10.2.0.4 on AIX and using veritas net backups.....from rman.....
ORA-19624: operation failed, retry possible
ORA-19506: failed to create sequential file, name="c-1650503797-20091118-0c", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:

Raman wrote:
Well. i agree. we have logs to capture media backups....so wanted to cut only these media backups failure out of alert file...else what is happening here is our monitoring reports these as alerts as already we know from media backup logs...So why not modify your monitoring of the alert log to exclude that particular error?
Personally, I'd allow both systems to continue to report the error from their perspective.
>
in nutshell...just exploring any options to turn off the media backup failures like any rman parameters or can anything to do with veritas parameters?
Anyway thanks to all for your valuable opinions.
Thanks,
Raman.

Alert log message and RMAN

Hi ,
following is the message from Alert log file and trace files.
This error encountered during RMAN backup but the backup was fine.
Didn't get any errors in RMAN log file.
Can anybody tell me what's the problem and solution?
----------- alert log file --------------------
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
----------- trace files -------------------
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 24
Unix process pid: 950328, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.053
*** SESSION ID:(77.60408) 2006-03-09 02:14:13.040
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
~
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 1769540, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.311
*** SESSION ID:(53.5721) 2006-03-09 02:14:13.310
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 1392642, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.549
*** SESSION ID:(59.52476) 2006-03-09 02:14:13.548
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4

Hello looks like when backing up database using RMAN it did not find the archivelogs hence you got the errors. Try doing "Crosscheck archivelog all" and see.
-Sri
<< Symptoms >>
Archivelog backup using RMAN failed with error :
RMAN-03002: failure of backup command at 08/18/2005 14:51:16
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /arch/arch2/1_266_563489673.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: A file or directory in the path name does not exist.
Additional information: 3
<<Cause>>
RMAN get the information about what archivelog files are required to back up from the v$archived_log view.
RMAN cannot find the file archivelog in the archivelog destination. So itscannot continue taking the backup because this file does not exist.
<<Solution>>
Check if the archivelog exist in the log archive destination. If the is moved to some other location then restore the file back to its original location and then do RMAN back.
else
RMAN> crosscheck archivelog all;
After the crosscheck all take the rman backup.

RMAN Message

Similar Messages

Maybe you are looking for