Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
16Activity
0 of .
Results for:
No results containing your search query
P. 1
rmantroublrshooting

rmantroublrshooting

Ratings: (0)|Views: 810 |Likes:
Published by api-3730388
TRouble shooting through RMAN
TRouble shooting through RMAN

More info:

Published by: api-3730388 on Oct 15, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as TXT, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

recovery manager troubleshooting

this chapter describes how to troubleshoot and debug recovery manager. it includes
the following topics:
interpreting message output
testing the media management api
monitoring rman jobs
terminating an rman session
troubleshooting scenarios

interpreting message output

recovery manager provides detailed error messages that can aid in troubleshooting problems. also, the oracle database server and third-party media vendors generate useful debugging output of their own. this section addresses the following topics:

identifying types of message output
identifying error codes
interpreting rman error stacks
interpreting debugging output

identifying types of message output
output that is useful for troubleshooting failed rman jobs is located in several
different places, as explained in the following table:
type of output
produced by
location
description

rman messages
rman
direct this output to:
standard output (typically the terminal)
a log file specified by the log option on the command line
a log file created by re-directing standard output using operators at the command
line
describes actions relevant to the rman job as well as error messages generated by
rman, the server, and the media vendor.

rman trace file
rman's debug command
the file specified using the trace parameter at the command line.
contains exhaustive output on the creation and execution of pl/sql program units.

alert.log
oracle database server
the directory specified in the user_dump_dest initialization parameter.
contains a chronological log of errors, init.ora settings, and administration
operations. records values for overwritten control file records (see "monitoring
the overwriting of control file records").

oracle trace file
oracle database server
the directory specified in the user_dump_dest initialization parameter.
contains detailed output generated by oracle server processes. this file is
created when an ora-600 or ora-3113 error message occurs.

sbtio.log
third-party media management software
the directory specified in the user_dump_dest initialization parameter.
contains information on the functioning of the media management device.

media manager log file
third-party media management software
the filenames for any media manager logs other than sbtio.log are determined by
the media management software.
contains information on the functioning of the media management device.

identifying error codes

typically, you find the following types of error codes in rman message stacks:
errors prefixed with rman-
errors prefixed with ora-
errors preceded by the line additional information:

explanations for rman and ora error codes are in oracle8i error messages.
rman error message numbers
table 9-1 indicates the error ranges for common rman error messages, all of which

are described in oracle8i error messages:
table 9-1 rman error message ranges (page 1 of 2)
error range

cause
0550-0999
command line interpreter
1000-1999
keyword analyzer
2000-2999
syntax analyzer
3000-3999
main layer
4000-4999
services layer
5000-5499
compilation of restore or recover command
5500-5999
compilation of duplicate command
6000-6999
general compilation
7000-7999
general execution
8000-8999
pl/sql programs
9000-9999
low-level keyword analyzer
10000-10999
server-side execution
11000-11999
interphase errors between pl/sql and rman
20000-20999
recovery catalog packages
media manager error numbers

when errors occur through the media management api, rman returns an error message
number prefixed as follows:
additional information:

below is the list of message numbers and their corresponding error text. in the
error codes, o/s stands for operating system. the errors prefixed with an asterisk
are internal and should never be seen during normal operation.

table 9-2 media manager error message ranges
cause
no.
message

sbtopen
7000
7001
7002*
7003
7004
7005
7006
7007
7008
7009
7010
7011
7012*
backup file not found (only returned for read)
file exists (only returned for write)
bad mode specified
bad block size specified
no tape device found
device found, but busy; try again later
tape volume not found
tape volume is in-use
i/o error
can't connect with media manager
permission denied
o/s error for example malloc, fork error

Activity (16)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
sunny_dba liked this
sunny_dba liked this
kss2906 liked this
sharmakaushal liked this
rony_jsr liked this
gangadhar.kreddy liked this
anuragmishra50 liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->