Databases Reference
In-Depth Information
4.
Follow a recipe in this topic that helps resolve the issue.
5.
Use your favorite search engine to search the Web for information from other DBAs who
have encountered similar situations.
6.
Ask other DBAs for help.
7.
Search Oracle's RMAN backup and recovery documentation at
http://otn.oracle.com .
8.
Search Oracle's My Oracle Support (MOS) web site at
http://support.oracle.com .
9.
Search for an answer or post a question on Oracle's RMAN forum at
http://forums.oracle.com .
10.
Open a service request (SR) with Oracle Support.
11.
Enable more output logging and debugging (see Recipes 17-7, 17-8, and 17-9).
Note
before you can use the Mos web site to open an sr, you must first purchase a valid oracle support license.
How It Works
With RMAN troubleshooting, usually you start with the error message displayed on your terminal or recorded in a log
file. This section discusses a typical RMAN error stack. To begin with, you'll almost always see the following text as the
first part of the output when there's an RMAN error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN error messages can sometimes be frustrating to interpret. Even for something as simple as an incorrectly
typed RMAN command, you'll be presented with a lengthy output describing the error. For example, you might
receive the following message stack:
RMAN-01009: syntax error: found "identifier": expecting one of: "advise,
allocate, alter, analyze, associate statistics, audit, backup, begin, @, call,
catalog, change, comment, commit, configure, connect, convert, copy, create,
create catalog, create global, create script, create virtual, crosscheck, declare
...
When presented with an RMAN error message stack, follow the steps outlined in the Solution section of this
recipe. You'll have to vary the steps depending on your scenario. For example, if you have a priority-one (P1)
production problem, you may want to open an SR with Oracle Support as your first step. For most other situations,
you'll use a subset of the solution steps and resolve the problem on your own.
 
 
Search WWH ::




Custom Search