/ Recovery Manager Error Message File
/
/    MODIFIED (MM/DD/YY)
/    swerthei  09/13/99 - add renormalize keyword
/    gpongrac  08/16/99 - add DOT                                              
/    gpongrac  08/13/99 - ad 6455 and 6546                                     
/    gpongracz 08/10/99 - change 20215
/    gpongrac  08/05/99 - add configure and compatible
/    fsanchez  08/06/99 - bug_935058
/    gpongrac  07/27/99 - chamge 8511 to include tag                           
/    swerthei  07/14/99 - dont translate 600, 601
/    swerthei  06/08/99 - add resetlogs keyword
/    dbeusee   02/12/99 - bug-728666                                           
/    gpongrac  02/26/99 - autolocate
/    swerthei  12/30/98 - add 6454 for duplex factoring
/    dbeusee   11/13/98 - misc_815: add LIST .. RECOVERABLE.. COMPLETED..
/    gpongrac  07/28/98 - add timeout                                          
/    gpongrac  07/09/98 - add pipe messages                                    
/    gpongrac  07/06/98 - add pipe                                             
/    dbeusee   11/17/98 - mesg_815_4: Added 6453.
/    swerthei  10/29/98 - change proxy message explanation
/    fsanchez  11/01/98 - bug-757372
/    fsanchez  10/13/98 - bug-615050                                         
/    swerthei  10/03/98 - add more startup failure messages
/    fsanchez  10/26/98 - bug-729947                                           
/    fsanchez  10/26/98 - last_msgs
/    swerthei  10/29/98 - change proxy backup description
/    swerthei  10/24/98 - add proxy support to REPORT OBSOLETE
/    dbeusee   10/22/98 - misc_815/mesg_815_3: added 20211 & chg'd 20207/8.
/    dbeusee   10/21/98 - mesg_815_2: fix cause for msg 6143.
/    fsanchez  10/20/98 - new messages for duplicate and tspitr
/    swerthei  10/19/98 - add new messages for restore validate
/    dbeusee   09/11/98 - misc_815/mesg_815: fixed 6235-7 & 6143 & removed 6104
/    swerthei  10/29/98 - add LOGICAL
/    fsanchez  10/15/98 - Readibility changes
/    swerthei  09/30/98 - add message for connection after NOCATALOG declared
/    gpongrac  06/29/98 - add nocatalog option to rman help
/    fsanchez  07/29/98 - clone_db
/    gpongrac  06/12/98 - add back slash
/    fsanchez  06/30/98 - clean_msgs
/    swerthei  06/23/98 - add messages for CREATE, UPGRADE, DROP
/    dbeusee   05/13/98 - misc_81_fixes_1: added DBID to connected msg and 6412
/    swerthei  05/28/98 - add SEND command
/    swerthei  05/19/98 - add messages for proxy copy enhancement
/    dbeusee   04/21/98 - rpt_redundancy_enh
/    gpongrac  05/04/98 - add catalog upgrade message
/    gpongrac  04/29/98 - add catalog upgrade required msg
/    gpongrac  05/01/98 - add deleted log msg for krmk
/    gpongrac  04/23/98 - change 8014
/    gpongrac  04/28/98 - add diskratio
/    gpongrac  01/29/98 - add debug keywords
/    gpongrac  04/22/98 - change 3012
/    gpongrac  04/14/98 - add nomount
/    gpongrac  04/08/98 - add force, abort, normal, immediate
/    gpongrac  03/26/98 - shutdown cmd
/    gpongrac  03/02/98 - add alter database keywords
/    gpongrac  03/02/98 - add sga size messages
/    gpongrac  02/26/98 - startup cmd
/    gpongrac  03/19/98 - add noredo option
/    dbeusee   04/04/98 - xcheck enh.
/    dbeusee   03/30/98 - Fix msg 6230 to read: List of Backup Sets.
/    mzhou     03/04/98 - add 5004
/    fsanchez  03/03/98 - Duplexed backup sets
/    dbeusee   02/27/98 - Fix msg 2000 to give clue why wrong msg file.
/    dbeusee   02/06/98 - crosscheck/list enh.
/    fsanchez  12/30/97 - Add dbid, correct 6186, add new SET DBID errors
/    gpongrac  01/23/98 - add package upgrade warning messages
/    gpongrac  01/15/98 - change %d to %s for 6085
/    gpongrac  12/23/97 - add 6088 but for controlfilecopies
/    gpongrac  12/17/97 - change 6186
/    gpongrac  10/20/97 - fix 6185
/    gpongrac  09/29/97 - add version error messages
/    gpongrac  09/17/97 - add duplicate backup object error
/    gpongrac  09/04/97 - setsize operand
/    swerthei  09/16/97 - add CHECK
/    swerthei  09/11/97 - change 6176, add 6177, 6178, 6179
/    swerthei  09/05/97 - add 6176
/    gpongrac  09/11/97 - add product factoring messages
/    tpystyne  09/08/97 - update 6052 cause and action
/    mzhou     08/28/97 - add second cause to error 5000
/    gpongrac  04/29/97 - add print script message
/    mzhou     07/31/97 - add 5003 -- system/rbs ts not allowed in tspitr
/    mzhou     07/24/97 - add 0302 -- plsql
/    mzhou     07/28/97 - add no clone connection when allocate clone channel
/    gpongrac  06/04/97 - add channel session terminated
/    gpongrac  05/27/97 - change 1007 to include filename
/    gpongrac  05/23/97 - add EOF message
/    gpongrac  04/17/97 - add limit keywrod
/    swerthei  04/23/97 - change message 6134
/    gpongrac  04/14/97 - add not connected messages
/    gpongrac  04/10/97 - add no controlfilecopy with offline range found error
/    gpongrac  04/09/97 - change 6095 a bit
/    gpongrac  04/04/97 - add backup piece tag not found error
/    mzhou     04/07/97 - add no-set-newname when restore clone error
/    gpongrac  04/01/97 - add already connected error
/    swerthei  03/28/97 - add message 7007
/    gpongrac  03/26/97 - add newline token
/    gpongrac  03/25/97 - add OCI warning messages
/    gpongrac  04/03/97 - add offline range apply messages
/    tpystyne  03/20/97 - add 8040 and 8041
/    swerthei  03/10/97 - add commandid
/    gpongrac  03/14/97 - change 8039
/    gpongrac  03/13/97 - change 8502 and 8010
/    gpongrac  02/28/97 - add computeRecoveryActions errors
/    gpongrac  02/24/97 - add 3023
/    gpongrac  02/24/97 - change 559 to 561
/    gpongrac  02/24/97 - add error stack banner messg
/    gpongrac  02/24/97 - add compile and execute messages
/    gpongrac  02/24/97 - add executing script message
/    gpongrac  01/31/97 - change 3017
/    gpongrac  01/31/97 - RPC test
/    gpongrac  02/13/97 - add 568 and 3099
/    swerthei  02/10/97 - add messages for RESTORE VALIDATE
/    swerthei  02/06/97 - change description for 6028
/    swerthei  01/21/97 - add messages for CHANGE BACKUPSET
/    gpongrac  01/21/97 - add get clone name failure
/    swerthei  01/17/97 - implement CHANGE VALIDATE
/    swerthei  01/15/97 - report deletable -> report obsolete
/    swerthei  01/14/97 - implement SET CLONENAME
/    gpongrac  01/14/97 - add getCloneName error
/    swerthei  01/08/97 - add orphan keyword
/    gpongrac  01/06/97 - change 6054
/    swerthei  01/03/97 - more messages for REPORT DELETABLE
/    swerthei  12/31/96 - add messages for REPORT DELETABLE
/    swerthei  12/20/96 - add messages for REPORT SCHEMA
/    swerthei  12/19/96 - add AT, SCHEMA keywords
/    gpongrac  12/17/96 - add clone db sqlerror message
/    gpongrac  12/17/96 - correct 3006
/    swerthei  12/13/96 - add 6134, 6135
/    gpongrac  12/05/96 - add clone_cf keyword
/    gpongrac  11/25/96 - add krmr messages
/    gpongrac  11/22/96 - add error in script message
/    swerthei  12/04/96 - change explanation for message 6056
/    gpongrac  12/02/96 - change 6068
/    gpongrac  11/27/96 - add obsolete rcvcat or too new cf message
/    jnewman   12/04/96 - edit Cause and Action statements
/    swerthei  11/19/96 - 6281->6132
/    swerthei  11/15/96 - add snapshot keyword
/    swerthei  11/13/96 - add 6129, 6130
/    tpystyne  11/18/96 - remove obsolete messages 20211-20213
/    gpongrac  11/11/96 - add 6281
/    swerthei  11/08/96 - add 6124, 6125
/    swerthei  11/06/96 - resolve merge conflict: 6103->6122, 6104->6123
/    swerthei  11/06/96 - document LIST/REPORT output
/    tpystyne  11/03/96 - move change from recover.bsq to krmk.pc
/    swerthei  11/01/96 - change message 6103
/    swerthei  10/31/96 - add DEVICE keyword
/    gpongrac  10/29/96 - add implicit resync failure
/    tpystyne  10/28/96 - implement change uncatalog
/    swerthei  10/28/96 - add messages for LIST INCARNATION
/    swerthei  10/23/96 - add messages for LIST command
/    swerthei  10/21/96 - add 6098
/    gpongrac  10/23/96 - change 6079
/    gpongrac  10/17/96 - add ocipi failure msg
/    tpystyne  10/21/96 - add backup not available messages
/    gpongrac  10/15/96 - add mesg to print failing sql statement in krmk
/    gpongrac  10/14/96 - fix merge errors
/    tpystyne  10/13/96 - improve rdbms_rcvcat error messages
/    gpongrac  10/10/96 - add fatal compilation error msg
/    gpongrac  10/09/96 - add stored script messages
/    gpongrac  10/04/96 - add 6089
/    gpongrac  10/03/96 - add 6087
/    tpystyne  10/03/96 - add new translate messages
/    swerthei  09/30/96 - 8073->6036
/    swerthei  09/27/96 - 8038->6088, 8040->6089
/    swerthei  09/27/96 - remove CORRUPT keyword
/    gpongrac  09/25/96 - add datafile name not found or ambiguous error
/    swerthei  09/25/96 - add 6086, 6087
/    swerthei  09/24/96 - add keywords OFFLINE, READONLY, INACCESSIBLE, CORRUPT
/    swerthei  09/23/96 - 6036->8073
/    swerthei  09/16/96 - add 6085
/    tpystyne  09/15/96 - cleanup recovery catalog resync
/    swerthei  09/10/96 - add 567
/    swerthei  09/06/96 - fix spelling error in message RMAN-10031
/    gpongrac  08/31/96 - media recovery messages
/    gpongrac  08/29/96 - add help messages
/    swerthei  08/28/96 - add 8058, 6083
/    swerthei  08/27/96 - add REPLICATE command
/    gpongrac  08/22/96 - add datafilecopy tag not unique error
/    gpongrac  08/23/96 - execute script errors
/    tpystyne  08/27/96 - add catalog controlfile messages
/    gpongrac  08/16/96 - add stored script errors
/    gpongrac  08/15/96 - add FOREVER token
/    gpongrac  08/13/96 - add 8056
/    swerthei  07/24/96 - 8038 -> 8038/8040
/    gpongrac  07/26/96 - add recover errors
/    tpystyne  07/15/96 - change and catalog commands
/    gpongrac  07/15/96 - add incremental backup set restore message
/    tpystyne  07/05/96 - new dbms_rcvman messages
/    gpongrac  07/10/96 - add SQL token
/    gpongrac  07/01/96 - add 8512
/    gpongrac  07/08/96 - delete input not implemented yet
/    swerthei  06/27/96 - add 6050
/    swerthei  06/25/96 - add 8036-8038
/    gpongrac  06/20/96 - add cause/action for copy and backup messages
/    tpystyne  06/19/96 - improve message descriptions
/    gpongrac  06/18/96 - add trace file error messages
/    swerthei  06/19/96 - add commentary for restore messages
/    gpongrac  06/17/96 - add 6049
/    swerthei  06/17/96 - add 8034, 8035
/    tpystyne  06/14/96 - add message 20207
/    gpongrac  06/11/96 - pass set_count to genPieceName
/
/ Keywords: 0001-0549
/
/ Note that the keywords are NOT in strict alphabetic order.
/ A 20 number range is reserved for each letter of the alphabet.  New keyword
/ should be added to the appropriate error number range.
/
// NLS_DO_NOT_TRANSLATE [0001,0549]
/
/ A: 0-19
0001, 2, "all"
0002, 2, "allocate"
0003, 2, "archivelog"
0004, 2, "available"
0005, 2, "archivelog key (brl)"
0006, 2, "archivelog backup specification"
0007, 2, "append"
0008, 2, "at"
0009, 2, "affinity"
0010, 2, "alter"
0011, 2, "abort"
0012, 2, "auxiliary"
0013, 2, "auxname"
0014, 2, "and"
0015, 2, "after"
0016, 2, "autolocate"
/ B: 20-39
0020, 2, "backup"
0021, 2, "backuppiece"
0022, 2, "backupset"
0023, 2, "backup controlfile"
0024, 2, "backup specification list"
0025, 2, "backup specification"
0026, 2, "backup command operand list"
0031, 2, "between"
0032, 2, "before"
/ C: 40-59
0040, 2, "cancel"
0041, 2, "catalog"
0042, 2, "change"
0043, 2, "channel"
0044, 2, "cmdfile"
0045, 2, "connect"
0046, 2, "copy"
0047, 2, "controlfile"
0048, 2, "create"
0049, 2, "cumulative"
0050, 2, "current"
0051, 2, "configure"
0052, 2, "controlfilecopy"
0053, 2, "clone_cf"
0054, 2, "clone"
0055, 2, "clonename"
0056, 2, "command"
0057, 2, "check"
0058, 2, "crosscheck"
0059, 2, "completed"
/ D: 60-79
0060, 2, "database"
0061, 2, "datafile"
0062, 2, "datafilecopy"
0063, 2, "UNUSED"
0064, 2, "delete"
0065, 2, "disk"
0066, 2, "dump"
0068, 2, "define"
0069, 2, "depends on"
0070, 2, "debug"
0071, 2, "days"
0073, 2, "destination"
0074, 2, "device"
0075, 2, "dbid"
0076, 2, "dba"
0077, 2, "diskratio"
0078, 2, "duplex"
0079, 2, "drop"
/ E: 80-99
0080, 2, "execute"
0081, 2, "exit"
0082, 2, "expired"
0083, 2, "echo"
0084, 2, "duplicate"
/ F: 100-119
0100, 2, "filesperset"
0101, 2, "for"
0102, 2, "for delete"
0103, 2, "format"
0104, 2, "from"
0105, 2, "from backupset"
0106, 2, "from datafilecopy"
0107, 2, "full"
0108, 2, "forever"
0109, 2, "force"
/ G: 120-139
0120, 2, "group"
/ H: 140-159
0140, 2, "high"
0141, 2, "host"
/ I: 160-179
0160, 2, "identifier"
0161, 2, "incarnation"
0162, 2, "incarnation key"
0163, 2, "include"
0164, 2, "include current controlfile"
0165, 2, "incremental"
0166, 2, "input"
0167, 2, "inaccessible"
0168, 2, "id"
0169, 2, "immediate"
/ J: 180-199
0180, 2, "job"
0181, 2, "job command list"
/ K: 200-219
0200, 2, "kbytes"
0201, 2, "k"
/ L: 220-239
0220, 2, "level"
0221, 2, "like"
0224, 2, "logseq"
0225, 2, "logscn"
0226, 2, "library"
0227, 2, "libname"
0228, 2, "libparm"
0229, 2, "libtext"
0230, 2, "low"
0231, 2, "list"
0232, 2, "limit"
0233, 2, "logfile"
0234, 2, "log"
0235, 2, "logical"
/ M: 240-259
0240, 2, "maxopenfiles"
0241, 2, "maxcorrupt"
0242, 2, "msglog"
0243, 2, "mask"
0244, 2, "msgno"
0245, 2, "maintenance"
0246, 2, "mount"
0247, 2, "m"
/ N: 260-279
0260, 2, "name"
0261, 2, "need"
0262, 2, "need backup"
0263, 2, "nochecksum"
0264, 2, "nocatalog"
0265, 2, "newname"
0266, 2, "new-line"
0267, 2, "noredo"
0268, 2, "normal"
0269, 2, "nomount"
0270, 2, "nofilenamecheck"
0271, 2, "null"
/ O: 280-299
0280, 2, "of"
0281, 2, "offline"
0282, 2, "orphan"
0283, 2, "obsolete"
0284, 2, "off"
0285, 2, "on"
0286, 2, "open"
0287, 2, "only"
/ P: 300-319
0300, 2, "parms"
0301, 2, "print"
0302, 2, "plsql"
0303, 2, "pfile"
0304, 2, "proxy"
0305, 2, "pool"
0306, 2, "pipe"
/ Q: 320-339
0320, 2, "quoted string"
/ R: 340-359
0340, 2, "rcvcat"
0341, 2, "readrate"
0342, 2, "recover"
0343, 2, "register"
0344, 2, "register database"
0345, 2, "release"
0346, 2, "reload"
0347, 2, "replace"
0348, 2, "report"
0349, 2, "reset"
0350, 2, "reset database"
0351, 2, "restart"
0352, 2, "restore"
0353, 2, "resync"
0354, 2, "resync catalog"
0355, 2, "rpctest"
0356, 2, "run"
0357, 2, "redundancy"
0358, 2, "replicate"
0359, 2, "readonly"
/ S: 360-379
0360, 2, "script"
0361, 2, "setlimit"
0362, 2, "skip"
0363, 2, "step"
0364, 2, "switch"
0365, 2, "scn"
0366, 2, "slaxdebug"
0367, 2, "set"
0368, 2, "sql"
0369, 2, "snapshot"
0370, 2, "schema"
0371, 2, "setsize"
0372, 2, "startup"
0373, 2, "shutdown"
0374, 2, "send"
0375, 2, "size"
/ T: 380-399
0380, 2, "tablespace"
0381, 2, "tag"
0382, 2, "target"
/ msg 383 is for the token TEXTLINE_
0383, 2, ""
0384, 2, "thread"
0385, 2, "time"
0386, 2, "to"
0387, 2, "to (reuse)"
0388, 2, "txt"
0389, 2, "type"
0390, 2, "type disk"
0391, 2, "test"
0392, 2, "trace"
0393, 2, "transactional"
0394, 3, "timeout"
/ U: 400-419
0400, 2, "unavailable"
0401, 2, "unrecoverable"
0402, 2, "until"
0403, 2, "unknown node type"
0404, 2, "uncatalog"
0405, 2, "upgrade"
/ V: 420-439
0420, 2, "validate"
/ W: 470-479
/ X: 480-489
/ Y: 490-499
/ Z: 500-519
/ A-Z overflow: 440-469
0440, 2, "reuse"
0441, 2, "recoverable"
0442, 2, "resetlogs"
0443, 2, "compatible"
0444, 2, "renormalize"
/
/ Punctuation: 520-549
/
/ NLS Translators:
/
/ The punctuation characters here are critical parts of the rman command
/ language, and are used in the documentation and sample rman scripts.
/ We strongly recommend that you do not change any of these characters.
/ If you must change one or more of these characters, you must follow the
/ following rules, and must also document for your customers the effects
/ that your change will have on the RMAN command language.
/
/ Message 522 (HASH_ token) 526 (QUOTE_ token) 532 (ATSIGN) and 533 (_)
/ must be single characters.  The other punctuation tokens may be changed,
/ but all characters in a punctuation token MUST be punctuation characters!
/ If you change message 532 to some other character, you must choose a
/ character that is NOT used by PLSQL.  For example, "%" should not be used
/ because PLSQL uses that character as part of the "%NOTFOUND" keyword.
/ 533 (_) is a special case of a punctuation character that is NOT
/ considered to be punctuation.  Thus, it may appear in an identifier or
/ a tag.
/
/ Porters and NLS Translators:
/
/ Message 520 must be the name of the program as seen by krmmmai in
/ argv[0].
/
0520, 2, "rman"
0521, 2, ","
0522, 2, "#"
0523, 2, "("
0524, 2, ")"
0525, 2, "end-of-file"
0526, 2, "\""
0527, 2, "{"
0528, 2, "}"
0529, 2, "<<<"
0530, 2, ">>>"
0531, 2, ";"
0532, 2, "&"
0533, 2, "_"
0534, 2, "'"
0535, 2, "="
0536, 2, "^"
0537, 2, "@"
0538, 2, "."

/ Errors
/
/ KRMM errors: 0550-0999
/
0550, 1, "parser package failed to load"
// *Cause:  lpmloadpkg() return an error indication.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
0551, 1, "initialization of parser package failed"
// *Cause:  The parser package initialization routine returned an error.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
0552, 1, "syntax error in command line arguments"
// *Cause:  The arguments supplied to RMAN could not be parsed, or no
//          arguments were supplied at all.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
0553, 1, "internal recovery manager package failed to load"
// *Cause:  lpmloadpkg() return an error indication.
// *Action: This message should be accompanied by other error message(s)
//         indicating the cause of the error.
0554, 1, "initialization of internal recovery manager package failed"
// *Cause:  The internal package initialization routine returned an error.
// *Action: This message should be accompanied by other error message(s)
//         indicating the cause of the error.
0555, 1, "target database connect string must be specified"
// *Cause:  The TARGET parameter was not specified.
// *Action: Supply the necessary parameter.
0556, 1, "could not open CMDFILE \"%s\""
// *Cause:  An error occurred when trying to open the file.
// *Action: Check that the filename was specified correctly and that the
//          file exists and that the user running RMAN has read permission
//          for the file.
0557, 1, "could not open MSGLOG \"%s\""
// *Cause:  An error occurred when trying to open the file.
// *Action: Check that the filename was specified correctly and that the
//          file exists and that the user running RMAN has write permission
//          for the file.
0558, 1, "error encountered while parsing input commands"
// *Cause:  The parser detected a syntax error.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
/
/ Message 559 is the prompt.  Message 560 is the termination message.
/
// UI [559]
/
0559, 1, "RMAN> "
0560, 1, "Recovery Manager complete."
/
/ Message 561 is the continuation prompt
/
// UI [561]
/
0561, 1, "%u> "
0562, 1, "username too long"
// *Cause:  The specified user name exceeds the maximum allowable username
//          length.
// *Action: Correct the username.
0563, 1, "password too long"
// *Cause:  The specified password exceeds the maximum allowable password
//          length.
// *Action: Correct the password.
0564, 1, "host data too long"
// *Cause:  The SQL*NET host connect string exceeds the max allowable length.
// *Action: Correct the host string.
0565, 1, "unable to read input file"
// *Cause:  An error occurred while trying to read from STDIN or from the
//          CMDFILE.
// *Action: Ensure that the cmdfile is readable.  The cmdfile must be
//          a text file with 1 line per record.
0566, 1, "could not open TRACE \"%s\""
// *Cause:  An error occurred when trying to open the file.
// *Action: Check that the filename was specified correctly and that the
//          user running RMAN has write permission for the file.
0567, 1, "Recovery Manager could not print some error messages"
// *Cause: An error occurred while trying to print the error message stack.
// *Action: If the associated error message indicates a condition that
//          can be corrected, do so, otherwise contact Oracle.
0568, 1, "user interrupt received"
// *Cause:  The user typed ^C or ATTN.
// *Action: none
0569, 1, "=============== ERROR MESSAGE STACK FOLLOWS ==============="
// *Cause:  This message preceeds an error message stack.
// *Action: The errors are printed in last-in first-out order.  So to interpret
//          them correctly, read from the bottom to the top.
0570, 1, "**end-of-file**"
// *Cause:  The end of an inline cmdfile was reached.  This is just
//          an informational message.
0571, 1, "==========================================================="
0572, 1, "waiting for dbms_pipe input"
// *Cause:  This message is used only when the PIPE option was specified.
// *Action: enqueue some RMAN input into the pipe
0573, 1, "dbms_pipe.next_item_time returned unknown type code: %d"
// *Cause:  This is an internal error
// *Action: contact Oracle Support.
0574, 1, "rman aborting due to errors read/writing dbms_pipe"
// *Cause:  RMAN was run with input/output being sent to dbms_pipe.  An
//          error was encountered while reading from or writing to the pipe.
//          This error should be preceeded by information describing the error.
// *Action: RMAN terminates.  Refere to the cause/action for the preceeding
//          errors.
0575, 1, "timeout while trying to write to dbms_pipe"
// *Cause:  RMAN was running in dbms_pipe mode.  A timeout occurred while 
//          calling dbms_pipe.send_message.  This occurs when the pipe is full
//          and no process has dequeued any of the messages.  This is usually
//          caused by death of the process that was talking to rman.
// *Action: RMAN will abort.
/
/ Help messages
/
0580, 1, "Argument     Value          Description"
0581, 1, "-----------------------------------------------------------------------------"
0582, 1, "target       quoted-string  connect-string for target database"
0583, 1, "rcvcat       quoted-string  connect-string for recovery catalog"
0584, 1, "debug        none           if specified, activate debugging mode"
0585, 1, "cmdfile      quoted-string  name of input command file"
0586, 1, "msglog       quoted-string  name of output message log file"
0587, 1, "trace        quoted-string  name of output debugging message log file"
0588, 1, "append       none           if specified, msglog opened in append mode"
0589, 1, "nocatalog    none           if specified, then no recovery catalog"
0597, 1, "-----------------------------------------------------------------------------"
0598, 1, "Both single and double quotes (' or \") are accepted for a quoted-string."
0599, 1, "Quotes are not required unless the string contains embedded white-space."
/
/ Internal Errors
/
// NLS_DO_NOT_TRANSLATE [600,601]
600,  4, "internal error, arguments [%s] [%s] [%s] [%s] [%s]"
// *Cause:  An internal error in recovery manager occurred.
// *Action: Contact Oracle Support.
601,  4, "fatal error in recovery manager"
// *Cause:  A fatal error has occurred.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
/
/ KRMP errors: 1000-1999
/
/ 1000 is used to separate multiple errors when formatting the errors
/ for printing
1000, 1, ", "
/ 1005 is used to format an error message from the parser.  Do NOT change
/ this!
1005, 1, "%s"
1006, 1, "error signalled during parse"
// *Cause:  An error was signalled during parsing.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
1007, 1, "at line %d column %d file: %s"
// *Cause:  This is an informational message indicating the line
//          and column where a syntax error was detected.
1008, 1, "the bad identifier was: %s"
// *Cause:  This is an informational message indicating the identifier token
//          that caused a syntax error.
/
/ KRML errors: 2000-2999
/
2000, 1, "wrong message file version (msg %d not found)"
// *Cause:  The rmanxx.msb file is not the correct version.
// *Action: Check that the installation was done correctly.  The RMAN
//          binary (executable, load module, whatever it is called on your O/S)
//          and the rmanxx.msb file must be from the same version, release, and
//          patch level.
2001, 1, "unrecognized punctuation symbol \"%s\""
// *Cause:  An illegal punctuation character was encountered.
// *Action: Remove the illegal character.
2002, 1, "unexpected end of input file reached"
// *Cause:  This is probably caused by failure to supply the closing quote
//          for a quoted string.
// *Action: Correct the input.
2003, 1, "unrecognized character: %s"
// *Cause:  An input character that is neither an alpha, digit, or punctuation
//          was encountered.
// *Action: Remove the character.
2004, 1, "quoted string too big"
// *Cause:  A quoted string longer than 2000 bytes was encountered.
// *Action: This may be caused by a missing close quote.  If so, add the
//          missing quote, otherwise shorten the string.
2005, 1, "token too big"
// *Cause:  A token longer than 1000 bytes was encountered
// *Action: Tokens must be separated by whitespace or punctuation.  
//          Either add the missing whitespace or punctuation, or shorten
//          the token.
2006, 1, "script line too long"
// *Cause: a line longer thatn 500 bytes was encountered
// *Action: break the line up into shorter lines
/
/ KRMI errors: 3000-3999
/
3000, 1, "recovery manager compiler component initialization failed"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: Check the accompanying errors.
3001, 1, "recovery manager command sequencer component initialization failed"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
3002, 1, "failure during compilation of command"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
3003, 1, "command not implemented yet: %s"
// *Cause:  The command is not implemented in the current release.
// *Action: Avoid using the command.
3004, 1, "fatal error during execution of command"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
3005, 1, "RMAN-%05.5d: %s"
// *Cause: This is just an informational message
3006, 1, "non-retryable error occurred during execution of command: %s"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
3007, 1, "retryable error occurred during execution of command: %s"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.  If the error can be fixed, the
//          the RETRY command can be used to retry the failed operation.
3008, 1, "error while performing automatic resync of recovery catalog"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
3010, 1, "fatal error during library cache pre-loading"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
/
/ 3011 is the banner message
/
3011, 1, "Recovery Manager: Release %s %s"
/
3012, 1, "fatal error during compilation of command"
// *Cause: A fatal error occurred during compilation of a command.
// *Action:  This message should be accompanied by other errors explaining
//           the cause of the failure.
3013, 1, "command type: %s"
// *Cause: Informational message to accompany 3012
3014, 1, "implicit resync of recovery catalog failed"
// *Cause: This message is accompanied by other errors explaining the
//         cause of the failure.
3015, 1, "error occurred in stored script %s"
// *Cause: Informational message only
/
3017, 1, "recursion detected in stored script %s"
// *Cause: A stored script is calling itself or another script which calls
//         itself.
// *Action: Remove the recusion.
3018, 1, "async RPCs are working correctly"
// *Cause: This is an informational message.
3019, 1, "async RPCs are NOT working"
// *Cause: The RPCTEST command has determined that RPCs are not executing
//         asynchronously.  Instead, they are blocking.  This is caused
//         by using a SQL*NET driver that does not support non-blocking UPI.
// *Action: Try using a different SQL*NET driver.
3020, 1, "async RPC test will take 1 minute"
// *Cause: Informational message
3021, 1, "executing script: %s"
// *Cause: Informational message only.
3022, 1, "compiling command: %s"
// *Cause: Informational message only.
3023, 1, "executing command: %s"
// *Cause: Informational message only.
3024, 1, "performing implicit full resync of recovery catalog"
// *Cause: Informational message only.
3025, 1, "performing implicit partial resync of recovery catalog"
// *Cause: Informational message only.
3026, 1, "error recovery releasing channel resources"
// *Cause: An error was caught, and RMAN is cleaning up the channels"
// *Action: None, informational message only.
3027, 1, "printing stored script: %s"
// *Cause: Informational message.
3028, 1, "fatal error code: %d"
// *Cause: Informational message.  This preceeds error 3012.
3029, 1, "echo set on"
// *Cause: a SET ECHO ON command was issued
3030, 1, "echo set off"
// *Cause: a SET ECHO OFF command was issued
/
3099, 1, "job cancelled at user request"
// *Cause: The user interrupted the current job.
// *Action:  None.
/
3999, 1, "Oracle error occurred while while converting a date: ORA-%-05d: %s"
// *Cause: Internal error converting a date.
// *Action: Contact Oracle Support.
/
/ KRMS/General Errors: 4000-4999
/
4000, 1, "memory allocation failure"
// *Cause:  A memory allocation request could not be satisified.
// *Action: Increase the amount of memory available to RMAN.
4001, 1, "heap initialization failure"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
4002, 1, "ocipi failed, ORA-%s"
// *Cause:  OCI process level initialization failed.
// *Action: This error should not normally occur.
4003, 1, "ociinit failed"
// *Cause:  The call to OCIEnvInit failed.
// *Action: This error should not normally happen.  Contact Oracle 
//          Customer Support.
4004, 1, "error from recovery catalog database: %s"
4005, 1, "error from target database: %s"
4006, 1, "error from auxiliary database: %s"
4007, 1, "warning from recovery catalog database: %s"
4008, 1, "warning from target database: %s"
4009, 1, "warning from auxiliary database: %s"
4010, 1, "target database Password: "
4011, 1, "recovery catalog database Password: "
4012, 1, "auxiliary database Password: "
4013, 1, "must connect before startup"
4014, 1, "startup failed: %s"
// *Cause:  The database failed to startup.
// *Action: The cause of the failure is included in the error message.
//          Correct the cause of the failure and retry the startup command.
4015, 1, "error setting target database character set to %s"
// *Cause:  An error was received while setting the session character set
//          in the target database.
// *Action: This error should not normally happen.  Contact Oracle 
//          Customer Support.
4016, 1, "could not get OCI error handle"
// *Cause:  An error was received while initializing the OCI layer.
// *Action: This error should not normally happen.  Contact Oracle 
//          Customer Support.
/
/ KRMR Errors: 5000-5999
/
5000, 1, "SET AUXNAME required for datafile %s"
// *Cause: Either:
//         -) The controlfile mounted by the auxiliary database does not have
//         an entry for this datafile, therefore filename conversion is
//         not possible.  
//
//         -) A COPY DATAFILE TO AUXNAME command was issued,
//         but no auxname was set for this datafile.
// *Action:  Use the SET AUXNAME command to specify a filename that the
//           auxiliary database can use as a restore destination.
5001, 1, "auxiliary filename %s conflicts with a file used by the target database"
// *Cause: RMAN is attempting to use the specified filename as a restore
//         destination in the auxiliary database, but this name is already
//         in use by the target database.
// *Action: Use the SET AUXNAME command to specify a name for the datafile
//          that does not conflict with a filename in use by the target db.
5002, 1, "aborting point-in-time tablespace recovery"
// *Cause: Previously encountered error(s) were issued which require
//         corrective action.
// *Action: Resolve the error conditions, and then re-issue the RECOVER
//          command.
5003, 1, "point-in-time recovery is not allowed for tablespace %s"
// *Cause: The SYSTEM tablespace or a tablespace containing rollback
//         segments is not allowed in point-in-time recovery.
// *Action: Remove the indicated tablespace from the recovery set and
//          retry the operation.
5004, 1, "target database log mode is NOARCHIVELOG" 
// *Cause: An attempt was made to apply TSPITR to a database that is
//         in NOARCHIVELOG mode. 
// *Action: If all required archive log files are available to TSPITR, 
//          alter the target database log mode to ARCHIVELOG and  
//          retry the TSPITR operation. Otherwise, TSPITR cannot be 
//          applied to this database.
5005, 1, "point-in-time recovery is not allowed for re-created tablespace %s"
// *Cause: The requested tablespace has been re-created and 
//         is not allowed in point-in-time recovery.
// *Action: Remove the indicated tablespace from the recovery set and
//          retry the operation.
/
/ KRMC Errors: 5500-5999
/
5500, 1, "the auxiliary database must be not mounted when issuing a DUPLICATE command"
// *Cause: A DUPLICATE command was issued, but the auxiliary database is 
//         mounted.
// *Action: Dismount the auxiliary database.
5501, 1, "aborting duplication of target database"
// *Cause: Previously encountered errors require corrective action.
// *Action: Resolve the error conditions, and reissue the DUPLICATE TARGET
//          DATABASE command.
5502, 1, "the target database must be mounted when issuing a DUPLICATE command"
// *Cause: A DUPLICATE command was issued, but the target database control file
//         is not mounted.
// *Action: Mount the target database control file by issuing
//          ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
5503, 1, "at least one auxiliary channel must be allocated to execute this command"
// *Cause:  No auxiliary channels are allocated.
// *Action: Allocate an auxiliary channel.
5504, 1, "at least two redo log files or groups must be specified for this command"
// *Cause:  Only one redo log file or group was specified
// *Action: Specify at least one more redo log file or group
5505, 1, "auxiliary filename conversion of '%s' exceeds maximum length of %s"
// *Cause:  When the given filename is converted to the name used for the
//          auxiliary database, the converted name is larger than the maximum
//          allowed filename.
// *Action: Change initialization parameter DB_FILE_NAME_CONVERT
//          to convert to a valid filename.
5506, 1, "error during recursive execution"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
/
/ KRMK Errors: 6000-6999
/
6000, 1, "could not open recovery manager library file: %s"
// *Cause:  The "recover.bsq" file could not be opened.
// *Action: Check that the file was installed correctly and that the user
//          running RMAN has authority to read the file.
6001, 1, "error parsing job step library"
// *Cause:  A syntax error was encountered while parsing "recover.bsq".
// *Action: Ensure that the correct version of the file is installed and
//          that it has not been modified in any way.
6002, 1, "command not allowed when not connected to a recovery catalog"
// *Cause:  A command that is allowed only when a recovery catalog connect
//          string was supplied was attempted.
// *Action: Avoid using the command, or restart RMAN and supply a recovery
//          catalog connect string via the CATALOG parameter.
6003, 1, "ORACLE error from target database: %s"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
6004, 1, "ORACLE error from recovery catalog database: %s"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
6005, 1, "connected to target database: %s (DBID=%s)"
// *Cause:  Informational message.
6006, 1, "connected to target database: %s (not mounted)"
// *Cause:  Informational message.
6007, 1, "target database not mounted and db_name not set in init.ora"
// *Cause:  The target database has not mounted the controlfile, and
//          its "init.ora" file does not specify the DB_NAME parameter.
// *Action: MOUNT the target database, or add the DB_NAME parameter to
//          its "init.ora" and restart the instance.
6008, 1, "connected to recovery catalog database"
// *Cause:  Informational message.
6009, 1, "using target database controlfile instead of recovery catalog"
// *Cause:  Informational message.
6010, 1, "error while looking up datafile: %s"
// *Cause:  An error occurred while looking up the specified datafile in
//          the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the filename is entered correctly.
//          If the datafile was added recently, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6011, 1, "invalid level specified: %d"
// *Cause:  An invalid incremental backup level was specified.
// *Action: Incremental backup level must be between 0 and 8.
6012, 1, "channel: %s not allocated"
// *Cause:  A RELEASE or SETLIMIT command was found for a channel identifier
//          that was not yet allocated.
// *Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command.
6013, 1, "duplicate channel identifier found: %s"
// *Cause:  A channel identifier was reused without first releasing the
//          channel.
// *Action: Add a RELEASE CHANNEL command.
6014, 1, "command not implemented yet: %s"
// *Cause:  Not all commands are implemented for the beta release.
// *Action: Avoid using the command.
6015, 1, "error while looking up datafilecopy name: %s"
// *Cause:  An error occurred while looking up the specified datafilecopy name
//          in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the filename is entered correctly.
//          If the datafilevopy was created when the recovery catalog was not
//          available, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6016, 1, "duplicate backup operand specified: %s"
// *Cause:  The specified operand appears more than once in the same
//          backup specifier or backup command.
// *Action: Delete the duplicate operand.
6017, 1, "initialization of parser failed"
// *Cause:  The parser package initialization routine returned an error.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
6018, 1, "duplicate operand specified in backup specification: %s"
// *Cause:  A backup spec operand appears more than once in a backup
//          specification.
// *Action: Delete the duplicate operand.
6019, 1, "could not translate tablespace name \"%s\""
// *Cause:  An error occurred while looking up the specified tablespace name
//          in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the tablespace is entered correctly.
//          If the tablespace was added recently, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6020, 1, "connected to auxiliary database"
// *Cause:  Informational message.
6021, 1, "FROM DATAFILECCOPY/BACKUPSET may not be specified with archivelogs"
// *Cause:  The FROM DATAFILECCOPY/BACKUPSET option applies only to
//          datafile and controlfile restores.
// *Action: Use this option only for datafile and controlfile restores.
6022, 1, "FROM TAG option may not be specified with archivelogs"
// *Cause:  The FROM TAG option applies only to datafile and controlfile
//          restores.
// *Action: Use this option only for datafile and controlfile restores.
6023, 1, "no backup or copy of datafile %d found to restore"
// *Cause:  A datafile, tablespace, or database restore could not proceed
//          because no backup or copy of the indicated file was found.
//          It may be the case that a backup or copy of this file exists but
//          does not satisfy the criteria specified in the user's restore
//          operands.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6024, 1, "no backup or copy of the controlfile found to restore"
// *Cause:  A controlfile restore could not proceed
//          because no backup or copy of the controlfile was found.
//          It may be the case that a backup or copy of this file exists but
//          does not satisfy the criteria specified in the user's restore
//          operands.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6025, 1, "no backup of log thread %d seq %d scn %s found to restore"
// *Cause:  An archivelog restore restore could not proceed
//          because no backup of the indicated archived log was found.
//          It may be the case that a backup of this file exists but
//          does not satisfy the criteria specified in the user's restore
//          operands.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6026, 1, "some targets not found - aborting restore"
// *Cause:  Some of the files specified for restore could not be found.
//          Message 6023, 6024, or 6025 is also issued to indicate which
//          files could not be found.  Some common reasons why a file
//          can not be restored are that there is no backup
//          or copy of the file that is known to recovery manager, or
//          there are no backups or copies that fall within the criteria
//          specified on the RESTORE command, or some datafile copies have
//          been made but not cataloged.
// *Action: The Recovery Manager LIST command can be used to display the
//          backups and copies that Recovery Manager
//          knows about.  Select the files to be restored from that list.
// *Action:
6027, 1, "no archivelogs found that match specification"
// *Cause:  An archivelog record specifier did not match any archivelogs
//          in the recovery catalog.
// *Action: Resubmit the command with a different archivelog record
//          specifier.  The rman LIST command can be used to display all
//          archivelogs that Recovery Manager knows about.
6028, 1, "duplicate operand specified in restore specification: %s"
// *Cause:  The CHANNEL, TAG, FROM, PARMS, VALIDATE,
//          or CHECK READONLY option was specified
//          more than once in the restore command or in one of the restore
//          specifications.
// *Action: Correct and resubmit the comand.
6029, 1, "the controlfile may be included only in a datafile backup set"
// *Cause:  The "include current controlfile" option was specified for
//          an archivelog backup set.
// *Action: Use this option only for datafile backup sets.
6030, 1, "the DELETE INPUT option may not be used with a datafile backup set"
// *Cause:  The DELETE INPUT option was specified for a backup that contains
//          the current controlfile or datafiles.
// *Action: Remove the option and resubmit the command.
6031, 1, "could not translate database keyword"
// *Cause:  An error was received when calling dbms_rcvman
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
6032, 1, "at least 1 channel of TYPE DISK must be allocated to execute a COPY command"
// *Cause:  No channel of TYPE DISK was allocated.
// *Action: Allocate a channel of TYPE DISK and re-issue the command.
6033, 1, "channel %s not allocated"
// *Cause:  An rman command requests a specific channel, but
//          the requested channel has not been allocated.
// *Action: ALLOCATE the channel, or correct the channel identifier.
6034, 1, "at least 1 channel must be allocated to execute this command"
// *Cause:  No channels are allocated.
// *Action: ALLOCATE a channel.
6035, 1, "wrong version of recover.bsq, expecting %s, found %s"
// *Cause:  The "recover.bsq" file is incompatible with the RMAN executable.
// *Action: Install the correct version of recover.bsq.
6036, 1, "datafile %d is already restored to file %s"
// *Cause:  A SET NEWNAME command was issued to restore a datafile to a
//          location other than the original datafile, and Recovery Manager
//          determined that the best candidate for restoring the file is the
//          datafile copy with the same name, therefore the file is already
//          restored and no action need be taken.
// *Action: None - this is an informational message.
6037, 1, "incremental backups feature not implemented"
6038, 1, "recovery catalog package detected an error"
// *Cause:  A call to dbms_rcvman returned an error.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
6039, 1, "no set newname command has been issued for datafile %d"
// *Cause:  A SWITCH command was specified for a datafile, but no destination
//          was specified and no SET NEWNAME command has been previously issued
//          for that file.  An explicit file to switch to must be specified if
//          no SET NEWNAME command has been issued.
// *Action: Correct and resubmit the SWITCH command.
6040, 1, "controlfile is already restored to file %s"
// *Cause:  The best candidate controlfile for restoration is the one that
//          is named in the RESTORE (controlfile) command, hence no action
//          need be taken.
// *Action: None - this is an informational message.
6041, 1, "cannot switch file %d to copy of file %d"
// *Cause:  An attempt was made to switch a datafile to a copy of a different
//          datafile.
// *Action: Correct and resubmit the SWITCH command.
6042, 1, "TAG option not supported for archivelog backup sets"
// *Cause: The tag option was supplied but does not apply to this type
//         of backup.
// *Action: Remove the TAG operand and re-enter the command
6043, 1, "TAG option not supported for archivelog or current controlfile copies"
// *Cause: The tag option was supplied but does not apply to this type
//         of copy.
// *Action: Remove the TAG operand and re-enter the command
6044, 1, "duplicate operand specified in copy specification: %s"
6045, 1, "LEVEL option not supported for archivelog or current controlfile copies"
// *Cause:  The LEVEL option was supplied but does not apply to this type
//          of copy.
// *Action: Remove the LEVEL operand and re-enter the command.
6046, 1, "archivelog name: %s"
// *Cause:  An error occurred while translating an archivelog name to its
//          recovery catalog recid/timestamp.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: Check the accompanying errors.
6047, 1, "duplicate datafile %d specified for restoration from copy"
// *Cause:  The indicated datafile was specified more than once in the
//          same restore command.
// *Action: Correct and resubmit the RESTORE command.
6048, 1, "duplicate controlfile specified for restoration from copy"
// *Cause:  The controlfile was specified more than once in the same
//          RESTORE command.
// *Action: Correct and resubmit the RESTORE command.
6049, 1, "backup (backup set...) not implemented yet"
// *Cause: The command 'backup backupset' was entered.  This command is not
//         yet implemented
// *Action: Enter a different command.
6050, 1, "archivelog thread %d sequence %d is already on disk as file %s"
// *Cause:  An archivelog which was requested to be restored (either
//          explicitely or via a range specification) does not need to
//          be restored because it already exists on disk.
// *Action: None - this is an informational message
6051, 1, "DELETE INPUT option not implemented yet"
// *Cause: This option was specified in a backup specification.
// *Action: Remove the DELETE INPUT option.
6052, 1, "no parent backup or copy of datafile %d found"
// *Cause:  An incremental backup at level 1 or higher could not find
//          any parent backup or copy of the indicated datafile.
//          A level 0 backup of the datafile will be taken automatically.
// *Action: This is an informational message only
6053, 1, "unable to perform media recovery because of missing log"
// *Cause: This message is accompanied with another message identifying
//         the missing log.  The log would be needed to perform the media
//         recovery, but the log is not on disk and no backup set containing
//         the log is available.
// *Action: Determine if a backup set containing the log can be made available.
//          If so, then use the CHANGE command to make the backup set
//          available and retry the command.  If not, then a point in time
//          recovery up to the missing log is the only alternative.
6054, 1, "media recovery requesting unknown log: thread %s scn %s"
// *Cause: Media recovery is requesting a log whose existance is not
//         recorded in the recovery catalog or controlfile.
// *Action: If a copy of the log is available, then add it to the recovery
//          catalog and/or controlfile via a CATALOG command and then
//          retry the RECOVER command.  If not, then a point in time recovery
//          up to the missing log is the only alternative.
6055, 1, "could not find log sequence %s thread %s"
// *Cause: A log which was on disk at the start of media recovery or which
//         should have been restored from a backup set could not be found.
// *Action: Check the Recovery Manager message log to see if the log was
//          restored by a previous job step.  If so, then check the
//          V$ARCHIVED_LOG view to see if the log is listed in the controlfile.
//          If so, then validate that the log exists on disk and is
//          readable.  If the log was not restored, or was restored but
//          no record of the log exists in V$ARCHIVED_LOG, then contact
//          Oracle support.
6056, 1, "could not access datafile %d"
// *Cause:  A backup could not proceed
//          because the datafile header could not be read or the header
//          was not valid.
// *Action: Make the datafile accessible or skip it.
6066, 1, "the target database must be mounted when issuing a RECOVER command"
// *Cause: A RECOVER command was issued, but the target database controlfile
//         is not mounted.
// *Action: Mount the target database controlfile by issuing
//          ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
6067, 1, "RECOVER DATABASE required with a backup or created controlfile"
// *Cause: The controlfile has been restored from a backup or was created
//         via ALTER DATABASE CREATE CONTROLFILE.
// *Action: Use the RECOVER DATABASE command to perform the recovery.
6068, 1, "recovery aborted because of missing datafiles"
// *Cause: This error should be accompanied by one or more instances of
//         message ORA-06094.
// *Action: Refer to message ORA-06094.
6069, 1, "controlfile is missing the filename for datafile %s"
// *Cause: Media recovery of a backup controlfile added this datafile to
//         the controlfile, but it does not set the filename because that
//         is unsafe.
// *Action: If the datafile is on disk, then issue ALTER DATABASE RENAME
//          to correct the controlfile.  Otherwise, RESTORE the datafile,
//          and then use SWITCH to make it known to the controlfile.
//          If the tablespace containing this datafile will be dropped,
//          then reissue the RECOVER command with a SKIP clause to skip
//          recovery of this tablespace.
6070, 1, "DBWR could not identify datafile %s"
// *Cause: DBWR could not find the specified datafile.
6071, 1, "could not open datafile %s"
// *Cause: An error was encountered when trying to open the specified
//         datafile.
// *Action: Ensure that the datafile exists and is accessible.
6072, 1, "I/O error occurred when reading file header for datafile %s"
// *Cause: An I/O error occurred.
// *Action: RESTORE the datafile to a new location, then do a SWITCH,
//          and then retry the RECOVER command.
6073, 1, "file header is corrupt for datafile %s"
// *Cause: ORACLE detected a corruption in the file header.  A media failure
//         has probably occurred.
// *Action: RESTORE the datafile to a new location, then do a SWITCH,
//          and then retry the RECOVER command.
6074, 1, "file %s is not an ORACLE datafile"
// *Cause: The file header indicates that this file is not a datafile.
//         The file may have been overlaid or corrupted.
// *Action: RESTORE the datafile to a new location, then do a SWITCH,
//          and then retry the RECOVER command.
6075, 1, "datafile %s does not belong to this database"
// *Cause: The file header indicates that this file belongs to some
//         other ORACLE database.
// *Action: RESTORE the datafile to a new location, then do a SWITCH,
//          and then retry the RECOVER command.
6076, 1, "datafile %s contains wrong datafile"
// *Cause: The datafile header indicates the file contains a different
//         datafile number.
// *Action: RESTORE the datafile, and then retry the RECOVER command.
6077, 1, "datafile %s is a different version than contained in the controlfile"
// *Cause: The controlfile entry for this datafile specifies a different
//         version of this datafile.  Different versions of a datafile can
//         exist when a tablespace is dropped, and a new tablespace is 
//         created which reuses the same datafile numbers.
// *Action: If the datafile is correct, the fix the controlfile by using
//          the SWITCH command.  Otherwise, RESTORE the correct version of
//          this datafile and retry the RECOVER command.
6078, 1, "the controlfile is older than datafile %s"
// *Cause: The controlfile appears to be older than the specified datafile,
//         but it is not marked as a backup controlfile.  This indicates that
//         the controlfile has been replaced with an older version.  This error
//         does not occur when a backup controlfile which was created via
//         Recovyer Manager or the ALTER DATABASE BACKUP CONTROLFILE command
//         is restored because such controlfiles are marked as backups.
// *Action: RESTORE a controlfile and perform RECOVER DATABASE.
6079, 1, "database must be mounted to perform recovery"
// *Cause: A RECOVER command was issued, but the target database is
//         not mounted.
// *Action: Issue ALTER DATABASE MOUNT.
// *Cause: The datafile is off-line but not off-line for drop, and
//         RECOVER DATABASE is being done.  Database-level media recovery
//         skips off-line files.
// *Action: If this file should not be skipped, then kill Recovery Manager,
//          alter the datafile on-line, and re-issue the RECOVER command.
6080, 1, "SWITCH required for datafile %s"
// *Cause: The controlfile record for this datafile is for an older incarnation
//         of the datafile.  A SWITCH command must be issued to update
//         the controlfile before doing RECOVER.
6081, 1, "error reading datafile header for datafile %s, code %s"
// *Cause: X$KCVFH returned the specified code in the hxerr column when
//         it was queried for the specified datafile.
// *Action: Ensure the datafile exists and is readable.  Using a newer
//          release of Recovery Manager may return a more meaningful error
//          message.  If you have no newer version of Recovery Manager,
//          contact Oracle support.
6082, 1, "datafilecopy tag %s is ambiguous"
// *Cause: The specified tag refers to multiple datafile copies belonging
//         to different datafiles.
// *Action: Specify the datafilecopy by filename rather than by tag.
6083, 1, "error when loading stored script %s"
// *Cause: The recovery catalog database returned an error.  This error
//         explains the cause of the problem.
// *Action: Correct the problem and retry.
6084, 1, "the target database may not be mounted when issuing REPLICATE"
// *Cause: A REPLICATE command was issued, but the target database
//         is already mounted.
// *Action: dismount the target database controlfile by issuing
//          ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT
//          via Enterprise Manager or Server Manager.
6085, 1, "must use SET NEWNAME command to restore datafile %s"
// *Cause: A RESTORE command for the specified datafile could not find a
//         destination name for the specified datafile.
// *Action: Add a SET NEWNAME command prior to the RESTORE command to specify
//          the restore destination for this file.
6086, 1, "offline files may only be skipped in a datafile backup set"
// *Cause:  The "skip offline" option was specified for an archivelog
//          backup set.
// *Action: Use this option only for datafile backup sets.
6087, 1, "read-only files may only be skipped in a datafile backup set"
// *Cause:  The "skip readonly" option was specified for an archivelog
//          backup set.
// *Action: Use this option only for datafile backup sets.
6088, 1, "datafile copy %s not found or out of sync with catalog"
// *Cause:  The indicated file is not found, or is found but is not the same
//          file that the recovery catalog
//          thinks it is.  It is likely that some operation outside of Recovery
//          Manager has altered the file, or that Recovery Manager has not
//          resynced with the target database.
// *Action: Re-catalog the file and retry the operation.
6089, 1, "archived log %s not found or out of sync with catalog"
// *Cause:  The indicated file is not found, or is found but is not the same
//          file that the recovery catalog
//          thinks it is.  It is likely that some operation outside of Recovery
//          Manager has altered the file, or that Recovery Manager has not
//          resynced with the target database.
// *Action: Re-catalog the file and retry the operation.
6090, 1, "error while looking up controlfile copy: %s"
// *Cause:  An error occurred while looking up the specified controlfile copy
//          in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the filename is entered correctly.
//          If the controlfile copy was created when the recovery catalog 
//          was not available, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6091, 1, "no channel allocated for maintenance"
// *Cause:  A command was entered that requires a maintenance channel, and no
//          maintenance channel is allocated.
// *Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup
//          pieces, or using the CROSSCHECK or DELETE EXPIRED commands.
6092, 1, "error while looking up backup piece"
// *Cause:  An error occurred while looking up the specified backup 
//          piece in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the name or key is entered correctly.
//          If the backup piece was created when the recovery catalog 
//          was not available, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6093, 1, "recovery catalog contains obsolete version of datafile %s"
// *Cause: The specified datafile number was dropped and then reused.
//         The controlfile mounted by the target database contains the
//         newer version of the datafile, but the recovery catalog contains
//         information about only the older version.
// *Action: Issue a RESYNC command to update the recovery catalog, then
//          reissue the failing command.  If the error persists, contact
//          Oracle support.
6094, 1, "datafile %s must be restored"
// *Cause: A RECOVER command was issued, and the recovery catalog indicates
//         the specified datafile should be part of the recovery, but
//         this datafile is not listed in the controlfile, and cannot be found
//         on disk.
// *Action: Issue a RESTORE command for this datafile, using the same
//          UNTIL clause specified to the RECOVER command (if any), then
//          reissue the RECOVER.
6095, 1, "a backup controlfile must be restored to recover datafile %s"
// *Cause: The controfile currently mounted by the target database contains
//         a newer incarnation of the datafile than the recovery catalog
//         indicates is appropriate for the point-in-time being recovered to.
// *Action: Restore the controlfile, using the same UNTIL clause specified
//          on the failing RECOVER command, then reissue the
//          command.  If no controlfile can be restored, then you should
//          issue a CREATE CONTROLFILE command.
6096, 1, "SWITCH required for newname of datafile %s to take effect"
// *Cause: A SET NEWNAME was issued for this datafile, but no SWITCH
//         command was issued before the RECOVER command.
// *Action: Issue a SWITCH command to make the newname take effect before
//          doing RECOVER.
6097, 1, "text of failing SQL statement: %s"
// *Cause:
// *Action: This is an informational message to accompany message 6003 or 6004.
6098, 1, "the target database must be mounted when issuing a BACKUP command"
// *Cause: A BACKUP command was issued, but the target database controlfile
//         is not mounted.
// *Action: Mount the target database controlfile by issuing
//          ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
6099, 1, "error occurred in source file: %s, line: %d"
// *Cause: See accompanying error
// *Action: See accompanying error
6100, 1, "no channel to restore a backup or copy of datafile %d"
// *Cause:  A datafile, tablespace, or database restore could not proceed
//          because the backup of the indicated file exists on a device type
//          that was not allocated for restore.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6101, 1, "no channel to restore a backup or copy of the controlfile"
// *Cause:  A controlfile restore could not proceed
//          because the backup of the indicated file exists on a device type
//          that was not allocated for restore.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6102, 1, "no channel to restore a backup or copy of log thread %d seq %d scn %s"
// *Cause:  An archivelog restore restore could not proceed
//          because the backup of the indicated file exists on a device type
//          that was not allocated for restore.
// *Action: None - this is an informational message.  See message 6026 for
//          further details.
6103, 1, "duplicate qualifier found in REPORT command: %s"
// *Cause: The indicated qualifier appears more than once in a REPORT qualifier
//         list.
// *Action: delete the duplicate qualifier
6104, 1, "clone name for datafile %d unset"
// *Cause: This message is issued in response to a SET CLONENAME FOR 
//         <datafile> TO NULL command.
// *Action: None - this is an informational message.
6105, 1, "duplicate qualifier found in LIST command: %s"
// *Cause: The indicated qualifier appears more than once in a LIST qualifier
//         list.
// *Action: delete the duplicate qualifier
6106, 1, "this command requires that target database be mounted"
// *Cause: A command was issued that requires the target database to be
//         mounted, but the target database is not mounted.
// *Action: Mount the target database controlfile by issuing
//          ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
6107, 1, "warning - controlfile is not current for REPORT NEED BACKUP DAYS"
// *Cause: The REPORT NEED BACKUP DAYS command may report some files as
//         requiring backups when they really do not, because the most current
//         online status of the file is not known unless a current controlfile
//         is mounted.
// *Action: No action required, however, a current controlfile should be
//          mounted, if possible, to get the most accurate REPORT output.
6108, 1, "changed datafile copy unvailable"
// *Cause: This is an informational message.
// *Action: No Action Required.
6109, 1, "changed archivelog unavailable"
// *Cause: This is an informational message.
// *Action: No Action Required.
6110, 1, "changed controlfile copy unavailable"
// *Cause: This is an informational message.
// *Action: No Action Required.
6111, 1, "changed backup piece unavailable"
// *Cause: This is an informational message.
// *Action: No Action Required.
6112, 1, "changed datafile copy available"
// *Cause: This is an informational message.
// *Action: No Action Required.
6113, 1, "changed archivelog available"
// *Cause: This is an informational message.
// *Action: No Action Required.
6114, 1, "changed controlfile copy available"
// *Cause: This is an informational message.
// *Action: No Action Required.
6115, 1, "changed backup piece available"
// *Cause: This is an informational message.
// *Action: No Action Required.
6116, 1, "datafile copy cannot be found on disk, return code %s"
// *Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the
//         datafilecopy cannot be found on disk.
// *Action: If the storage containing the datafilecopy has been removed from
//          the host, restore it and retry the command.  If the datafilecopy
//          is permanently gone, then issue the CHANGE DATAFILECOPY DELETE
//          command for this datafile.
6117, 1, "archivelog cannot be found on disk, return code %s"
// *Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the
//         archivelog cannot be found on disk.
// *Action: If the storage containing the archivelog has been removed from
//          the host, restore it and retry the command.  If the archivelog
//          is permanently gone, then issue the CHANGE ARCHIVELOG DELETE
//          command for this archivelog.
6118, 1, "control file copy cannot be found on disk, return code %s"
// *Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the
//         control file copy cannot be found on disk.
// *Action: If the storage containing the control file copy has been removed
//          from the host, restore it and retry the command.  If the
//          control file copy is permanently gone, then issue the CHANGE
//          CONTROLFILECOPY DELETE command for this datafile.
6119, 1, "uncataloged datafile copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
6120, 1, "uncataloged archivelog"
// *Cause: This is an informational message.
// *Action: No Action Required.
6121, 1, "uncataloged controlfile copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
6122, 1, "CHANGE .. UNCATALOG not supported for BACKUPSET/BACKUPPIECE"
// *Cause: The CHANGE BACKUPPIECE/BACKUPSET .. UNCATALOG command was entered.
//         The UNCATALOG operation is not supported with backup pieces.
// *Action: Use CHANGE BACKUPPIECE/BACKUPSET .. DELETE instead.
6123, 1, "operation not supported without the recovery catalog"
// *Cause: A command was used which requires a connection to a recovery
//         catalog database.  The command cannot be used when your backup
//         repository is the target database controlfile.
// *Action: If a recovery catalog database is available, then connect to the
//          recovery catalog and retry the command, otherwise enter a different
//          command.
6124, 1, "error while looking up datafilecopy key: %d"
// *Cause:  An error occurred while looking up the specified datafilecopy key
//          in the recovery catalog.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.
6125, 1, "error while looking up archivelog key: %d"
// *Cause:  An error occurred while looking up the specified archivelog key
//          in the recovery catalog.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.
6126, 1, "skipping offline file %s"
// *Cause:  The indicated file will not be included in the backup set because
//          it is offline and the SKIP OFFLINE option was specified.
// *Action: None
6127, 1, "skipping read only file %s"
// *Cause:  The indicated file will not be included in the backup set because
//          it is read only and the SKIP READONLY option was specified.
// *Action: None
6128, 1, "skipping inaccessible file %s"
// *Cause:  The indicated file will not be included in the backup set because
//          it could not be read, and the SKIP INACCESSIBLE option was
//          specified.
// *Action: None
6129, 1, "invalid reserved channel ID: %s"
// *Cause:  The specified channel id is invalid.  DELETE and DEFAULT are
//          reserved channel names and may not be specified by users.
// *Action: Specify a different channel ID.
6130, 1, "snapshot controlfile name set to: %s"
6131, 1, "skip offline/readonly only allowed with current controlfile"
// *Cause:  The SKIP OFFLINE and SKIP READONLY options are only permitted
//          when the target database controlfile is current.  When the
//          target controlfile is not current, it is not possible to obtain
//          a datafile's offline/readonly status.
// *Action: Remove the skip option or mount a current controlfile on the
//          target database.
6132, 1, "cannot backup datafile %s because it is not in the controlfile"
// *Cause: A backup command was issued that includes the specified datafile,
//         but the datafile is not listed in the controlfile.  The controlfile
//         is not current (it is a backup or a created controlfile).
// *Action: Recover the controlfile to make it current, then retry the 
//          backup command.
6133, 1, "recovery catalog may have obsolete data for datafile %s"
// *Cause: A RESTORE UNTIL was issued, and the recovery catalog choose
//         an older incarnation of the datafile than is listed in the
//         controlfile.
// *Action: If the recovery catalog has correct data for the datafile,
//          then restore a backup controlfile using the same UNTIL clause,
//          then retry the datafile restore.  Otherwise, restore a backup
//          of the incarnation of the datafile listed in the controlfile.
6134, 1, "host command complete"
// *Cause: An operating system command has completed.
// *Action: None - this is an informational message.
6135, 1, "error executing host command: %s"
// *Cause: A host command returned a non-zero return code.
// *Action: Correct the offending command.
6136, 1, "ORACLE error from auxiliary database: %s"
// *Cause:  This message should be accompanied by other error message(s)
//          indicating the cause of the error.
// *Action: Check the accompanying errors.
6137, 1, "must have recovery catalog for REPORT SCHEMA AT TIME"
// *Cause: A 'REPORT SCHEMA at_clause' command was issued, but there is no
//         recovery catalog database.
// *Action: If you are not using a recovery catalog, then you may only issue
//          the 'REPORT SCHEMA' command with no at_clause.
6138, 1, "controlfile not mounted - must specify AT clause with REPORT command"
// *Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no
//         recovery catalog, and there is also no controlfile mounted at the
//         target database, so there is no place to get the information about
//         the current list of files comprising the database.
// *Action: Use a recovery catalog or mount a controlfile at the target
//          database.
6139, 1, "warning - controlfile is not current for REPORT SCHEMA"
// *Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no
//         recovery catalog, and the controlfile mounted by the target
//         instance is not current, so the information about the current list
//         of datafiles may not be current.
// *Action: Use a recovery catalog or mount a current controlfile.
6140, 1, "cannot specify TAG option with LIST INCARNATION"
// *Cause: The TAG option was specified with LIST INCARNATION.  This is not
//         permitted because there is no TAG associated with a database
//         incarnation.
// *Action: Remove the TAG option and re-run the LIST command.
6141, 1, "cannot specify TAG option with ARCHIVELOG list"
// *Cause: The TAG option was specified with an ARCHIVELOG list.  This is not
//         permitted because there is no TAG associated with archivelog copies
//         or backup sets.
// *Action: Remove the TAG option and re-run the LIST command.
6142, 1, "DEVICE TYPE may only be specified with LIST BACKUP"
// *Cause: The DEVICE TYPE option was specified with a LIST COPY, LIST
//         INCARNATION, CROSSCHECK, or DELETE EXPIRED command.  This is not
//         permitted because only backup sets may reside on different types
//         of devices and CROSSCHECK and DELETE EXPIRED commands must use
//         the same device type as was specified in the ALLOCATE CHANNEL FOR
//         MAINTENANCE/DELETE command.
// *Action: Remove the DEVICE TYPE option and re-run the command.
6143, 1, "LIKE may only be specified with LIST COPY"
// *Cause: The LIKE option was specified with a list BACKUP or INCARNATION
//         command.  This is not permitted because only copies of datafiles or
//         archive logs have file names that may be tested with a LIKE operand.
// *Action: Remove the LIKE option and re-run the LIST command.
6144, 1, "FROM or UNTIL may not be specified with LIST INCARNATION"
// *Cause: The FROM or UNTIL option was specified with LIST INCARNATION.
//         This is not
//         permitted because there is no time associated with
//         a database incarnation.
// *Action: Remove the FROM or UNTIL option and re-run the LIST command.
6145, 1, "controlfile is not current - obsolete file list may be incomplete"
// *Cause: A CHANGE or REPORT command needs to compute the list of backups that
//         are redundant and may be deleted.  If the mounted controlfile is not
//         current, it may not be possible to determine if a satisfactory
//         backup exists for files which have been offline since the last
//         OPEN RESETLOGS.
// *Action: No action need be taken - this is an informational message only.
//          To ensure a complete report of obsolete backups, mount a current
//          controlfile.
6146, 1, "changes found for file %d beyond offline SCN"
// *Cause: A CHANGE or REPORT command needs to compute the list of backups that
//         are redundant and may be deleted.  A backup was found for a file
//         which is shown as offline in the target database controlfile, but
//         the backup contains changes beyond the SCN when the file went
//         offline.  This is most likely because the target database
//         controlfile is not really current, but is a restored copy of an
//         older controlfile.
// *Action: Mount a current controlfile or a backup controlfile.
6147, 1, "no obsolete backups found"
// *Cause: A CHANGE or REPORT command could find no files that meet the
//         specified criteria for obsoleteness.
// *Action: None - this is an informational message.
6148, 1, "redundancy count must be greater than zero"
// *Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE
//         command was zero.
// *Action: Specify a REDUNDANCY operand of 1 or greater.
6149, 1, "must have recovery catalog for SET AUXNAME"
// *Cause: A 'SET AUXNAME' command was issued, but there is no
//         recovery catalog database.
// *Action: If a recovery catalog exists, then specify the
//          RCVCAT option when starting Recovery Manager, otherwise the
//          'SET AUXNAME' command may not be used.
6150, 1, "auxiliary name for datafile %d set to: %s"
// *Cause: This message is issued in response to a SET AUXNAME command.
// *Action: None - this is an informational message.
6151, 1, "datafile %s creation scn %s"
// *Cause: This is an informational message.  It should be accompanied
//         by other messages.
// *Action:  none
6152, 1, "CHANGE VALIDATE not supported for backup pieces or backup sets."
// *Cause: The CHANGE VALIDATE command may not be performed on a backup piece.
// *Action: The CHANGE VALIDATE command may only be performed on datafile
//          copies and archived logs.
//          To verify the contents of a backup set, use the VALIDATE BACKUPSET
//          command, which must be use inside of an RMAN RUN command.
6153, 1, "validation failed for datafile copy"
// *Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile
//         copy could not be found or no longer contains the same data, so its
//         record was deleted from the recovery catalog.
// *Action: None - this is an informational message.
6154, 1, "validation succeeded for datafile copy"
// *Cause: The CHANGE DATAFILE COPY VALIDATE command found that the datafile
//         copy still matches its data in the recovery catalog.
// *Action: None - this is an informational message.
6155, 1, "validation failed for controlfile copy"
// *Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the
//         controlfile copy could not be found or no longer contains the same
//         data, so its record was deleted from the recovery catalog.
// *Action: None - this is an informational message.
6156, 1, "validation succeeded for controlfile copy"
// *Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the
//          controlfile copy still matches its data in the recovery catalog.
// *Action: None - this is an informational message.
6157, 1, "validation failed for archived log"
// *Cause: The CHANGE ARCHIVELOG VALIDATE command found that the archived log
//         could not be found or no longer contains the same data, so its
//         record was deleted from the recovery catalog.
// *Action: None - this is an informational message.
6158, 1, "validation succeeded for archived log"
// *Cause: The CHANGE ARCHIVED LOG VALIDATE command found that the archived log
//         still matches its data in the recovery catalog.
// *Action: None - this is an informational message.
6159, 1, "error while looking up backup set"
// *Cause:  An error occurred while looking up the specified backup set
//          in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the key is entered correctly.
//          If the backup set was created when the recovery catalog 
//          was not available, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6160, 1, "no backup pieces found for backup set key: %d"
// *Cause:  No backup pieces for the requested backup set were found in the
//          recovery catalog, or the target database controlfile.
// *Action: Specify an existing backup set.
6161, 1, "error when inspecting auxiliary filename: %s"
// *Cause: This error is accompanied by other errors explaining the cause.
// *Action: Correct the auxiliary filename if it is wrong via the 
//          SET AUXNAME command.
6162, 1, "sql statement: %s"
// *Cause:  This is the sql statement about to be executed for a SQL command.
// *Action: None, informational message only.
6163, 1, "some datafiles cannot be recovered, aborting the RECOVER command"
// *Cause: This message should be followed by one or more 6162 or
//         6164 messages.
6164, 1, "no channel of required type allocated to recover datafile %d"
// *Cause: A RECOVER command could not proceed because incremental backup sets
//         or archive log backup sets exist on a device type that has not
//         been allocated.
// *Action: Use the LIST command to determine which device type is needed, then
//         allocate a channel of that type.
6165, 1, "datafile %s is too old to recover, restore a more recent copy"
// *Cause: The archived logs and/or incremental backup sets required to
//         recover the datafile do not exist, but a more recent backup
//         of the datafile exists which can be recovered.
// *Action: Issue a RESTORE for the datafile, then reissue the RECOVER
//          command.
6166, 1, "datafile %s cannot be recovered"
// *Cause: Incremental backups or archived redo logs needed to recover the
//         datafile cannot be found, and no recoverable full backup or
//         datafile copy exists.
// *Action: Use the LIST command to see if there is a backup set or datafile
//          copy that can be made AVAILABLE.  If not, then the datafile
//          is unrecoverable.  If a full or datafile copy exists, then
//          a point-in-time recovery may be possible.
6167, 1, "already connected"
// *Cause: a CONNECT command was issued, but RMAN is already connected
//         to the specified database.
// *Action: RMAN has no DISCONNECT command, so to connect to a different
//          instance, exit RMAN and start it again.
6168, 1, "no backup pieces with this tag found: %s"
// *Cause: A tag was used to specify a list of backup pieces, but no
//         backup pieces with this tag could be found.
// *Action: Make sure the tag is specified correctly.
6169, 1, "could not read file header for datafile %s error reason %s"
// *Cause: The specified datafile could not be accessed.  The reason
//         codes are:
//         1  - filename is MISSINGxx in the controlfile
//         2  - file is offline
//         3  - file is not verified
//         4  - DBWR could not find the file
//         5  - unable to open file
//         6  - I/O error during read
//         7  - file header is corrupt
//         8  - file is not a datafile
//         9  - file does not belong to this database
//         10 - file number is incorrect
//         12 - wrong file version
//         15 - controlfile is not current
// *Action: If the error can be corrected, do so and retry the operation.
//          The SKIP option can be used to ignore this error during a backup.
6170, 1, "no controlfile copy found with offline range recid %s stamp %s datafile %s"
// *Cause: This offline range is needed for recovering the specified datafile,
//         but the offline range record has aged out of the current
//         controlfile and no controlfile copy with the record could be
//         accessed.  At least 1 controlfile copy containing the offline range
//         was found in the recovery catalog and was in AVAILABLE status.
// *Action: Query the rc_controlfile_copy view for the names of all
//          controlfile copies, then issue a 
//          CHANGE CONTROLFILECOPY ... VALIDATE; command for them.
//          Then reissue the RECOVER command.
6171, 1, "not connected to target database"
// *Cause: A command was issued but no connection to the target database
//         has been established.
// *Action: Issue a CONNECT TARGET command to connect to the target database.
6172, 1, "not connected to recovery catalog database"
// *Cause: A command was issued but no connection to the recovery catalog
//         database has been established.
// *Action: Issue a CONNECT RCVCAT command to connect to the recovery catalog
//          database.  If you are not have a recovery catalog, then you
//          must use the NOCATALOG option when starting RMAN.
6173, 1, "no set newname command has been issued for datafile %s when restore auxiliary"
// *Cause:  Auxiliary type was specified for the controlfile, but no 
//          SET NEWNAME command has been previously issued for a datafile.
// *Action: Issue SET NEWNAME command for every datafile in the recovery set.
6174, 1, "not connected to auxiliary database"
// *Cause: An auxiliary command was issued but no connection to a 
//         auxiliary database has been established.
// *Action: Issue a CONNECT AUXILIARY command to
//          connect to the auxiliary database.
6175, 1, "deleted script: %s"
// *Cause: A DELETE SCRIPT command was executed.
6176, 1, "no recovery required; all files are readonly or offline"
// *Cause: A RECOVER DATABASE command does not need to
//         recover any files because all of the files to be recovered are
//         offline or read only.  This can only occur when the SKIP clause
//         includes the system tablespace.
// *Action: None, informational message only
6177, 1, "restore not done; all files readonly, offline, or already restored"
// *Cause: A RESTORE command does not need to restore any files,
//         because all of the files to be restored are offline, read-only, or
//         are already restored to their correct destinations.
// *Action: None, informational message only
6178, 1, "datafile %d not processed because file is offline"
// *Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing
//         the indicated datafile because it is offline clean at the desired
//         point in time.
// *Action: None, informational message only
6179, 1, "datafile %d not processed because file is read only"
// *Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing
//         the indicated datafile because it is part of a read only tablespace
//         at the desired point in time.
// *Action: None, informational message only
//         
6180, 1, "incremental backups require Oracle8 Enterprise Edition"
// *Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified.
// *Action: Use FULL, or INCREMENTAL LEVEL 0.
6181, 1, "multiple channels require Oracle8 Enterprise Edition"
// *Cause: Attempt to allocate more than 1 channel in a job.
// *Action: Remove all except one ALLOCATE CHANNEL command.
6182, 1, "archivelog larger than SETSIZE: thread %s seq %s %s"
// *Cause: A BACKUP ARCHIVELOG command specified the SETSIZE operand too low.
//         The specified archivelog is larger than SETSIZE will allow.
// *Action: Increase SETSIZE limit.
6183, 1, "datafile or datafilecopy larger than SETSIZE: file# %s %s"
// *Cause: A BACKUP DATAFILE(copy) command specified the SETSIZE operand too 
//         low.  The specified datafile is larger than SETSIZE will allow.
// *Action: Increase SETSIZE limit.
6184, 1, "duplicate object in backup specifier: %s %s"
// *Cause: A backup command specifies the same datafile or copy of a datafile
//         multiple times.
// *Action: Eliminate the duplicates.
6185, 1, "Recovery Manager incompatible with %s database: RMAN %d.%d.%d to %d.%d.%d required"
// *Cause: This version of recovery manager is incompatible with the
//         indicated database or the dbms_backup_restore package
//         installed in the indicated database.
// *Action: If the database has been upgraded from an earlier version, ensure
//          that the catxxxx.sql script has been run successfully.
//          Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.
//          Otherwise, use a version of RMAN within the range specified
//          in the error message.
6186, 1, "PL/SQL package %s.%s version %s in %s database is too old"
// *Cause: The specified PL/SQL package is a version that is too old to work
//         with this version of the Recovery Manager (RMAN).
// *Action: If the database indicated is RCVCAT, then you can use the
//          UPGRADE CATALOG command to upgrade the recovery catalog to the
//          most current version.  If the database is TARGET or AUXILIARY,
//          then you must either upgrade the specified database or use
//          an older version of RMAN.
6187, 1, "controlfile copy %s not found or out of sync with catalog"
// *Cause:  The indicated file is not found, or is found but is not the same
//          file that the recovery catalog
//          thinks it is.  It is likely that some operation outside of Recovery
//          Manager has altered the file, or that Recovery Manager has not
//          resynced with the target database.
// *Action: Re-catalog the file and retry the operation.
6188, 1, "cannot use command when connected to target database"  
// *Cause:  An attempt was made to issue a command that can be used only when  
//          there is no connection to the target database.  
// *Action: Avoid using the command, or restart RMAN and use the command  
//          before connecting to the target database. 
6189, 1, "current DBID %u does not match target mounted database (%u)"  
// *Cause: SET DBID was used to set a DBID that does not match the DBID  
//         of the database to which RMAN is connected. 
// *Action: If the current operation is a restore to copy the database,  
//          do not mount the database. Otherwise, avoid using the SET DBID 
//          command, or restart RMAN. 
6190, 1, "PL/SQL package %s.%s version %s in %s database is not current"
// *Cause:  RMAN detected an old version of the specified package.
//          RMAN will execute in backwards-compatible mode.
// *Action: No action is required, but certain features and bug-fixes may not
//          be available when RMAN runs in backwards-compatible mode.
//          If the database is RCVCAT, then you can use the
//          UPGRADE CATALOG command to upgrade the recovery catalog to the
//          most current version.
//          If the database is TARGET or AUXILIARY, then you must
//          either upgrade the specified database or use an older version of
//          RMAN.  The files that must be run to upgrade the target
//          or auxiliary database are dbmsrman.sql and prvtrman.plb.
6191, 1, "PL/SQL package %s.%s version %s in %s database is too new"
// *Cause:  RMAN detected an incompatible version of the specified package.
// *Action: Use a newer version of recovery manager.  Message 6439 indicates
//          the minimum required version of recovery manager.
6193, 1, "connected to target database (not started)"
// *Cause:  This is an informational message.
// *Action: The database must be started before any other RMAN commands
//          are issued.
6194, 1, "target database instance not started"
// *Cause:  A command was issued that requires the target database instance
//          be started.
// *Action: Issue a STARTUP command to start the instance.
6195, 1, "auxiliary database not started"
// *Cause: A command was issued that requires the auxiliary database instance 
//         be started.
// *Action: Issue a STARTUP AUXILIARY command.
6196, 1, "Oracle instance started"
// *Cause: A STARTUP command completed successfully.
// *Action: none, this is an informational message.
6197, 1, "Total System Global Area %13lu bytes"
6198, 1, "%-24s %13lu bytes"
6199, 1, "database mounted"
/
/ LIST/REPORT command messages occupy a sub-range of the krmk
/ messages, to keep them contiguous.
/ Their range is 6200-6399.  Within this range, 10 contiguous message numbers
/ are reserved for each type of report.
/
6200, 1, "List of Archived Log Copies"
6201, 1, "Key     Thrd Seq     S Completion time Name"
6202, 1, "------- ---- ------- - --------------- ------------------------------------"
6203, 1, "%-7s %-4s %-7s %1s %-15s %s"
// *Cause: This message is issued in response to a LIST COPY OF ARCHIVELOG
//         command.  If a recovery catalog is in use, then the information
//         comes from the recovery catalog, otherwise it comes from the
//         target database controlfile.  The following fields are shown for
//         each archived log:
//           Key: This is the unique key which identifies this archived log in
//             the recovery catalog.  This value can be used in a CHANGE
//             command to change the status of the log.  If the target
//             database controlfile is being used as the recovery catalog,
//             then this field is zero.
//           Thrd: This is the thread number of the log.
//           Seq: This is the sequence number, within the thread, of the log.
//           S: This is the status of the file.  Possible values are:
//                A - Available
//                U - Unavailable
//                D - Deleted
//             Status 'U' will not be used if the target database controlfile
//             is being used as the recovery catalog.
//           Completion time: This is the date and time when the log was
//             archived or copied.
//             This column will be printed in the default ORACLE
//             date format, unless overridden with a NLS_DATE_FORMAT
//             environment variable.
//           Name: This is the filename of the log.
// *Action: None
/
6205, 1, "List of Controlfile Copies"
6206, 1, "Key     S Completion time Ckp SCN    Ckp time        Name"
6207, 1, "------- - --------------- ---------- --------------- ------"
6208, 1, "%-7s %1s %-15s %-10s %-15s %s"
// *Cause: This message is issued in response to a LIST COPY OF
// *Action: None
/
6210, 1, "List of Datafile Copies"
6211, 1, "Key     File S Completion time Ckp SCN    Ckp time        Name"
6212, 1, "------- ---- - --------------- ---------- --------------- ------"
6213, 1, "%-7s %-4s %1s %-15s %-10s %-15s %s"
// *Cause: This message is issued in response to a LIST COPY OF
//         DATABASE/TABLESPACE/DATAFILE command.  If a recovery catalog is in
//         use, then the information comes from the recovery catalog, otherwise
//         it comes from the target database controlfile.  The following fields
//         are shown for each datafile copy:
//           Key: This is the unique key which identifies this datafile copy in
//             the recovery catalog.  This value can be used in a CHANGE
//             command to change the status of the copy.  If the target
//             database controlfile is being used as the recovery catalog,
//             then this field uniquely identifies this copy in the
//             controlfile.
//           File: The file number that this file was copied from.
//           S: This is the status of the file.  Possible values are:
//                A - Available
//                U - Unavailable
//                D - Deleted
//             Status 'U' will not be used if the target database controlfile
//             is being used as the recovery catalog.
//           Completion time: This is the date and time when the datafile
//             copy was created.
//             This column will be printed in the default ORACLE
//             date format, unless overridden with a NLS_DATE_FORMAT
//             environment variable.
//           Ckp SCN: This is the checkpoint SCN of the datafile copy.  The
//             file contains all changes made at or before this SCN.
//           Ckp time: This is the time that the file was last checkpointed.
//           Name: This is the filename of the datafile copy.
//           
// *Action: None
/
6220, 1, "    List of Archived Logs Included"
6221, 1, "    Thrd Seq     Low SCN    Next SCN   Low Time        Next Time"
6222, 1, "    ---- ------- ---------- ---------- --------------- ---------------"
6223, 1, "    %-4s %-7s %-10s %-10s %-15s %s"
// *Cause: This message is issued in response to a LIST BACKUP OF ARCHIVELOG
//         command.  If a recovery catalog is in
//         use, then the information comes from the recovery catalog, otherwise
//         it comes from the target database controlfile.
//         To be included in the report, at least one complete copy of the
//         backup set must exist.  If the DEVICE TYPE option is specified
//         on the report command, then the list includes only those backup
//         sets which reside on the specified devices, otherwise all available
//         backup sets are listed.
//         The following fields
//         are shown for each archivelog which is included in a backup set:
//           Key: This is the unique key which identifies this backup set in
//             the recovery catalog.  If the target database controlfile is
//             being used as the recovery catalog, then this field is a unique
//             identifier which identifies this backup set in the target
//             database controlfile.
//           Thrd: This is the thread number of the log.
//           Seq: This is the sequence number, within the thread, of the log.
//           Completion time: This is the date and time when the backup set
//             was created.
//             This column will be printed in the default ORACLE
//             date format, unless overridden with a NLS_DATE_FORMAT
//             environment variable.
// *Action: None
/
6230, 1, "List of Backup Sets"
6231, 1, "Key     Recid      Stamp      LV Set Stamp  Set Count  Completion Time"
6232, 1, "------- ---------- ---------- -- ---------- ---------- ----------------------"
6233, 1, "%-7s %-10s %-10s %-2s %-10s %-10s %s"
// *Cause: This message is issued in response to a LIST BACKUP OF
//         DATABASE/TABLESPACE/DATAFILE command.  If a recovery catalog is in
//         use, then the information comes from the recovery catalog, otherwise
//         it comes from the target database controlfile.
//         To be included in the report, at least one complete copy of the
//         backup set must exist.  If the DEVICE TYPE option is specified
//         on the report command, then the list includes only those backup
//         sets which reside on the specified devices, otherwise all available
//         backup sets are listed.
//         The following fields
//         are shown for each datafile which is included in a backup set:
//           Key: This is the unique key which identifies this backup set in
//             the recovery catalog.  If the target database controlfile is
//             being used as the recovery catalog, then this field is a unique
//             identifier which identifies this backup set in the target
//             database controlfile.
//           File: The file number of the file that was backed up.
//           Type: The type of backup.  Possible values are:
//             Full: full (or an incremental level 0) backup.
//             Incremental: incremental backup
//             Cumulative: cumulative incremental backup
//           LV: This is the incremental backup level.
//           Completion time: This is the date and time when the backup set
//             was created.
//             This column will be printed in the default ORACLE
//             date format, unless overridden with a NLS_DATE_FORMAT
//             environment variable.
/
6234, 1, "    List of Backup Pieces"
6235, 1, "    Key     Pc# Cp# Status      Completion Time        Piece Name"
6236, 1, "    ------- --- --- ----------- ---------------------- ------------------------"
6237, 1, "    %-7s %-3s %-3s %-11s %-22s %s"
/
6238, 1, "    List of Datafiles Included"
6239, 1, "    File Name                                  LV Type Ckp SCN    Ckp Time"
6240, 1, "    ---- ------------------------------------- -- ---- ---------- -------------"
6241, 1, "    %-4s %-37s %-2s %-4s %-10s %s"
/
6242, 1, "    Controlfile Included"
6243, 1, "    Ckp SCN    Ckp time"
6244, 1, "    ---------- ---------------"
6245, 1, "    %-10s %s"
/
6246, 1, "List of Database Incarnations"
6247, 1, "DB Key  Inc Key DB Name  DB ID            CUR Reset SCN  Reset Time"
6248, 1, "------- ------- -------- ---------------- --- ---------- ----------"
6249, 1, "%-7s %-7s %-8s %-16s %-3s %-10s %s"
// *Cause: This message is issued in response to a LIST INCARNATION OF DATABASE
//         command.  The following fields are shown for each database that is
//         registered with the recovery catalog:
//         DB Key: This is the unique key which identifies this database in
//           the recovery catalog.
//         Inc Key: This is the unique key which identifies this incarnation of
//           the database in the recovery catalog.
//         DB Name: The name of the database.
//         DB ID: The database ID.  This is a number which remains the same for
//           the life of the database, even if the database name is changed.
//         CUR: 'YES' if this is the current incarnation of this database,
//           otherwise 'NO'.
//         Reset SCN: SCN of the most recent resetlogs operation.
//         Reset Time: Time of the most recent resetlogs operation.
/
6250, 1, "Report of files that need backup due to unrecoverable operations"
6251, 1, "File Type of Backup Required Name"
6252, 1, "---- ----------------------- -----------------------------------"
6253, 1, "%-4s %-23s %s"
// *Cause: An unlogged change (such as 'create table unrecoverable') has been
//         made to this file, and the most recent backup of the file does not
//         contain those changes.
// *Action: Take a backup of this file.  If this file is lost before a backup
//          is taken, then the unlogged modifications will be lost.  The
//          message indicates whether a full backup is required or whether a
//          incremental backup will suffice.
/
6260, 1, "Report of files that need more than %d incrementals during recovery"
6261, 1, "File Incrementals Name"
6262, 1, "---- ------------ ----------------------------------------------"
6263, 1, "%-4s %-12s %s"
// *Cause: This message is issued in response to the REPORT NEED BACKUP
//         INCREMENTAL command, for those files which would use more than
//         the specified number of incrementals during recovery.
// *Action: To reduce the number of incremental backups which would be used
//          during recovery of this datafile, take a new full backup of this
//          file now.
6270, 1, "Report of files whose recovery needs more than %d days of archived logs"
6271, 1, "File Days  Name"
6272, 1, "---- ----- -----------------------------------------------------"
6273, 1, "%-4s %-5s %s"
// *Cause: This message is issued in response to the REPORT NEED BACKUP DAYS
//         command for those files which need more than the specified number
//         of days' archived logs for recovery.
// *Action: To reduce the number of logfiles needed for recovery of this
//          datafile, take a new full or incremental backup now.
/
6280, 1, "Report of obsolete backups and copies"
6281, 1, "Type                 Key    Completion Time    Filename/Handle"
6282, 1, "-------------------- ------ ------------------ --------------------"
6283, 1, "Datafile Copy        %-6s %-18s %s"
6284, 1, "Backup Set           %-6s %-18s"
6285, 1, "Backup Piece         %-6s %-18s %s"
6286, 1, "Proxy Copy           %-6s %-18s %s"
// *Cause: This message is issued in response to the REPORT OBSOLETE
//         command.  Each of the files listed is obsolete because it
//         is more redundant than the level of redundancy specified in the
//         REPORT command.
6290, 1, "Report of database schema"
6291, 1, "File K-bytes    Tablespace           RB segs Name"
6292, 1, "---- ---------- -------------------- ------- -------------------"
6293, 1, "%-4s %10s %-20s %-7s %s"
// *Cause: This message is issued in response to the REPORT SCHEMA command.
//         The report shows the physical schema of the database at the
//         indicated time.  The following fields are shown for each datafile:
//           File: The file number.
//           K-bytes: The size of the file.
//           Tablespace: The name of the tablespace which contains this file.
//           RB segs: YES if this file is part of a tablespace containing
//             rollback segments, otherwise NO.
//           Name: The file name.
/
6300, 1, "Report of files with less than %d redundant backups"
6301, 1, "File #bkps Name"
6302, 1, "---- ----- -----------------------------------------------------"
6303, 1, "%-4s %-5s %s"
// *Cause: This message is issued when the REPORT NEED BACKUP REDUNDANCY
//         command is used for those files which have less than the specified
//         number of backups which can be used for recovery.
// *Action: Take another backup of the datafiles listed.
6310, 1, "List of Proxy Copies"
6311, 1, "Key     File S Completion time Ckp SCN    Ckp time        Handle"
6312, 1, "------- ---- - --------------- ---------- --------------- ------"
6313, 1, "%-7s %-4s %1s %-15s %-10s %-15s %s"
// *Cause: This message is issued in response to a LIST BACKUP
//         DATABASE/TABLESPACE/DATAFILE command when some backups were taken
//         with the PROXY option.  If a recovery catalog is in
//         use, then the information comes from the recovery catalog, otherwise
//         it comes from the target database control file.  The following
//         fields are shown for each proxy datafile backup.
//           Key: This is the unique key which identifies this proxy backup in
//             the recovery catalog.  This value can be used in a CHANGE
//             command to change its status.  If the target
//             database control file is being used as the recovery catalog,
//             then this field uniquely identifies this copy in the
//             controlfile.
//           File: The file number that this file was copied from.
//           S: This is the status of the file.  Possible values are:
//                A - Available
//                U - Unavailable
//                D - Deleted
//                X - Expired
//             Status 'U' will not be used if the target database controlfile
//             is being used as the recovery catalog.
//           Completion time: This is the date and time when the backup
//             was created.
//             This column will be printed in the default Oracle
//             date format, unless overridden with a NLS_DATE_FORMAT
//             environment variable.
//           Ckp SCN: This is the checkpoint SCN of the backup.  The
//             file contains all changes made at or before this SCN.
//           Ckp time: This is the time that the file was last checkpointed.
//           Handle: This is the media manager handle of the proxy backup.
//           
// *Action: No action required
/
/
/ End of LIST message section.
/
/ Continuation of KRMK messages: 6400-6999
/
6400, 1, "database opened"
// *Cause: This is an informational message.
6401, 1, "database is already started"
// *Cause: A STARTUP command without the FORCE option was issued, but the
//         target database is already started.
// *Action: Use the FORCE option if you want to restart the database.
6402, 1, "Oracle instance shut down"
// *Cause: This is an informational message.
6403, 1, "could not obtain a fully authorized session"
// *Cause: The most likely cause of this error is that one of the databases
//         to which RMAN had previously connected is not started or has
//         has been shutdown.  Other error messages should identify 
//         exactly which database is the problem.
// *Action: Startup the database causing the problem.
6404, 1, "database dismounted"
// *Cause: This is an informational message.
6405, 1, "database closed"
// *Cause: This is an informational message.
6406, 1, "deleted archivelog"
// *Cause: This is an informational message.
6408, 1, "recovery catalog upgraded to version %s"
// *Cause:  This is an informational message issued by the UPGRADE CATALOG
//          command.  It indicates the version of the recovery catalog schema
//          to which the recovery catalog was just upgraded.  Note that this
//          version number may not reflect the version number of your rman
//          executable or target database, because the recovery catalog
//          schema is not changed with each Oracle release.
// *Action: No action required. 
6409, 1, "LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported"
// *Cause:  LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
// *Action: Remove LIKE clause from command.
6410, 1, "cannot use command when channels are allocated"  
// *Cause:  An attempt was made to issue a command that can be used only  
//          when there are no allocated channels. 
// *Action: Do not use the command, or de-allocate channels and use the  
//          command when no channels are allocated. 
6411, 1, "duplex setting out of range (1-4): %d"  
// *Cause:  An attempt was made to set duplexing to an invalid value.  
// *Action: Use a value in the specified range.  
6412, 1, "no proxy copy channel found"
// *Cause:  A proxy copy was started, but no allocated channel supports
//          proxy copy.  This could be because the media management software
//          used by the target database does not support proxy copy, or because
//          all of the allocated channels are of type DISK, which never
//          support proxy copy.
// *Action: If this is a backup, then either allocate a non-disk channel, or
//          do not use the PROXY option.  If this is a restore, then a channel
//          of the same type which created the proxy backup was allocated, but
//          now does not support proxy copy.  If proxy copy is no longer
//          supported by the media management software at the target database,
//          the CROSSCHECK or CHANGE commands should be used so that those
//          backups will not be considered for further restores.
6413, 1, "channel %s does not support proxy copy"
// *Cause:  The channel which was specified for this backup or restore does not
//          support proxy copy.  This could be because the media management
//          software used by the target database does not support proxy copy,
//          or because the channel is of type DISK, which never supports proxy
//          copy.
// *Action: If this is a backup, then either allocate a non-disk channel, or
//          do not use the PROXY option.  If this is a restore, then a channel
//          of the same type which created the proxy backup was allocated, but
//          now does not support proxy copy.  If proxy copy is no longer
//          supported by the media management software at the target database,
//          the CROSSCHECK command should be used so that those
//          backups will not be considered for further restores.
6414, 1, "target database COMPATIBLE option does not support proxy copy"
// *Cause:  PROXY was specified, and the target database uses a media manager
//          that supports proxy copy, but the COMPATIBLE initialization
//          parameter of the target database must be 8.1.0 or greater to create
//          proxy backups.  If the database is downgraded to the earlier
//          release that is specified in the COMPATIBLE parameter, then it will
//          no longer be able to restore proxy backups.
// *Action: Either take a non-proxy backup or change the target database
//          COMPATIBLE parameter.
6415, 1, "file %s cannot be proxy backed up"
// *Cause:  The PROXY option was specified, but the media management software
//          used by the target database cannot back up the specified file
//          using proxy copy.  If PROXY ONLY was specified, then the backup
//          is terminated.  If PROXY was specified, then this file will be
//          placed into a non-proxy backup set.
// *Action: Remove the ONLY option to place the files into
//          a regular backup set, or contact the media management vendor if
//          you believe that the media management software should support
//          proxy copy of this file.
6416, 1, "PROXY ONLY was specified and some files could not be proxy copied"
// *Cause:  PROXY ONLY was specified, and some of the files to be backed up
//          could not be backed up by the media management software used by the
//          target database.  Message 6415 is issued for each file that cannot
//          be proxy copied.
// *Action: Remove the ONLY option to place the files into
//          a regular backup set, or contact the media management vendor if
//          you believe that the media management software should support
//          proxy copy of these files.
6417, 1, "proxy backup of archive logs not supported"
// *Cause:  The BACKUP PROXY ARCHIVELOG command was entered.  Proxy backup
//          of archivelogs is not yet supported.
// *Action: Enter a different command.
6418, 1, "proxy incremental backups with level > 0 not supported"
// *Cause:  PROXY was specified for a non-level-zero incremental backup.
//          Proxy backups may only be full or level 0 backups.
// *Action: Remove one of the conflicting options.
6419, 1, "file %s cannot be proxy restored from handle %s"
// *Cause:  The media management software used by the target database indicated
//          that it cannot restore the specified file from the specified backup
//          handle.
// *Action: Consult the media management software documentation to find out
//          why this restriction exists or contact the media management vendor.
6420, 1, "some files could not be proxy restored - aborting restore"
// *Cause:  Some of the files to be restored could not be restored by the
//          media management software used by the target database.  Message
//          6419 is issued for each file that cannot be restored.
// *Action: Contact the media management vendor if you believe that the
//          media management software should support proxy copy of these files.
//          The CROSSCHECK or CHANGE commands can be used to remove these
//          proxy copies from the catalog to prevent the RESTORE command from
//          trying to restore from these proxy backups.
6421, 1, "sent command to channel: %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
6422, 1, "no channels found for SEND command"
// *Cause:  No channels with the specified names or device types were found.
//          If no channel qualifiers were specified, then no channels were
//          allocated.
// *Action: Specify a different channel type or allocate a channel of the
//          desired type.
6423, 1, "requested limit of %d exceeds vendor limit of %d"
// *Cause:  A SETLIMIT CHANNEL command was used to set the backup piece size
//          limit, but the media management software used by the target
//          database cannot create backup pieces that large.
// *Action: Specify a smaller backup piece limit.
6424, 1, "error while looking up proxy copy"
// *Cause:  An error occurred while looking up the specified proxy
//          copy in the recovery catalog or target database controlfile.
// *Action: This error is accompanied by other errors describing the reason
//          for the failure.  Ensure that the name or key is entered correctly.
//          If the proxy copy was created when the recovery catalog 
//          was not available, then a RESYNC CATALOG must
//          be done to update the recovery catalog.
6425, 1, "<datafile pathname not available>"
// *Cause:  This is an informational message.
6426, 1, "RECOVERY_CATALOG_OWNER role must be granted to user %s"
// *Cause:  The CREATE CATALOG or UPGRADE CATALOG command was used, but the
//          userid that was supplied in the RCVCAT connect string does not
//          have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role.
// *Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog
//          owner.
6427, 1, "recovery catalog already exists"
// *Cause:  The CREATE CATALOG command cannot be used when the recovery catalog
//          already exists.
// *Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog
//          to the most current release without losing any existing backup
//          data.  Use the DROP CATALOG command to remove an existing recovery
//          catalog.
6428, 1, "recovery catalog is not installed"
// *Cause:  A recovery catalog database connection has been made, but the
//          recovery catalog tables and views have not been installed.
// *Action: If you mis-typed the recovery catalog owner userid, then correct
//          the userid and reconnect to the recovery catalog.
//          If this is the first time that you have signed on to Recovery
//          Manager with this recovery catalog owner userid, then use the
//          CREATE CATALOG command to create the recovery catalog schema.
6429, 1, "%s database is not compatible with this version of RMAN"
// *Cause:  The indicated database is not compatible with this version of
//          the Recovery Manager (RMAN).  Other messages have also
//          been issued which detail the cause of the error.
// *Action: See the other messages.  If the database is RCVCAT, then you may
//          be able to use the CREATE CATALOG or UPGRADE CATALOG commands
//          to correct the problem.  If the database is TARGET or AUXILIARY, 
//          then you must either upgrade the target database or use a 
//          newer version of the RMAN executable.
6430, 1, "recovery catalog userid cannot be SYS"
// *Cause:  A recovery catalog connection was made to userid SYS.  The recovery
//          catalog must be created in a userid other than SYS.
// *Action: Specify a different userid in the RCVCAT connect string.
6431, 1, "recovery catalog created"
// *Cause:  This is an informational message issued by the CREATE CATALOG
//          command.
// *Action: No action required.
6432, 1, "recovery catalog dropped"
// *Cause:  This is an informational message issued by the DROP CATALOG
//          command.
// *Action: No action required.
6433, 1, "error installing recovery catalog"
// *Cause:  An error was received from the recovery catalog database while
//          it was being installed.  Another error message shows the error
//          message from the server.
// *Action: The most common reasons for failure to install the recovery
//          catalog are:
//          - Lack of space in the recovery catalog database: allocate more
//          space, use the DROP CATALOG command to remove any partially
//          installed recovery catalog, and retry the command.
//          - Object already exists: This is caused by a partial recovery
//          catalog installation.  Use the DROP CATALOG command to remove the
//          partially installed recovery catalog and retry the command.
6434, 1, "some errors occurred while removing recovery catalog"
// *Cause:  Some errors were received from the recovery catalog database while
//          removing the recovery catalog.
// *Action: Correct the error(s) and retry the command.  Note that the Recovery
//          Manager intercepts and ignores common errors, such as 'object not
//          found', which can happen while removing a partially installed
//          recovery catalog.  Only serious errors will be displayed while
//          removing the recovery catalog.
6435, 1, "recovery catalog owner is %s"
// *Cause:  This is an informational message issued by the UPGRADE CATALOG
//          and DROP CATALOG commands.
// *Action: No action required.
6436, 1, "enter DROP CATALOG command again to confirm catalog removal"
// *Cause:  The DROP CATALOG command deletes the recovery catalog, rendering
//          all database backups unusable, and should be used with care.
//          The command must be entered twice to ensure that this is really
//          what you want to do.
// *Action: If you really want to remove the recovery catalog, then enter
//          the DROP CATALOG command again.
6437, 1, "cannot drop catalog - catalog is newer than this RMAN"
// *Cause:  The DROP CATALOG command was entered, but the recovery catalog was
//          created by a newer version of the Recovery Manager (RMAN).  This
//          version of RMAN  may not be able to drop the entire recovery
//          catalog.
// *Action: Use the version of RMAN which most recently created or upgraded
//          the recovery catalog.
6438, 1, "error executing package DBMS_RCVMAN in %s database"
// *Cause:  Recovery Manager requires the DBMS_RCVMAN package in the SYS
//          schema of the indicated database.  Normally this package is
//          installed during database creation.  To re-create the package,
//          run the files dbmsrman.sql and prvtrmns.plb.
6439, 1, "RMAN must be upgraded to version %s to work with this package"
// *Cause:  This message indicates the minimum version of recovery manager
//          required to use the package which was specified in message 6191.
// *Action: A newer version of RMAN must be used with this package.
6441, 1, "cannot upgrade catalog - catalog is already newer than this RMAN"
// *Cause:  The recovery catalog is already at a version level that is greater
//          than this version of the Recovery Manager.  The UPGRADE CATALOG
//          command is not needed.
// *Action: Either upgrade to a more recent Recovery Manager, or continue to
//          use the current version.  Message 6191 will be issued if the
//          recovery catalog is too new to work with this version of Recovery
//          Manager.
6442, 1, "enter UPGRADE CATALOG command again to confirm catalog upgrade"
// *Cause:  The UPGRADE CATALOG command alters the recovery catalog schema.
//          Although the recovery catalog is designed to be compatible with
//          older versions of the Recovery Manager (RMAN), it is possible that
//          an upgrade will remove support for older versions of RMAN.
// *Action: If you really want to upgrade the recovery catalog, then enter
//          the UPGRADE CATALOG command again.
//          If you are not going to use an older version of RMAN with this
//          recovery catalog, then compatibility is not an issue.
//          If you plan to also continue using an older
//          version of RMAN with this recovery catalog then, before upgrading,
//          consult the Migration Guide for the current Oracle release to
//          determine if upgrading to the current version of the recovery
//          catalog will remove support for older versions of RMAN.
6443, 1, "error upgrading recovery catalog"
// *Cause:  An error was received from the recovery catalog database while
//          upgrading the recovery catalog.
// *Action: Correct the error and retry the command.  Note that the Recovery
//          Manager intercepts and ignores common errors, such as 'column
//          already exists,' which can happen if the recovery catalog has
//          already been partially upgraded.
//          Only serious errors will be displayed while
//          upgrading the recovery catalog.
6444, 1, "%s created with compilation errors"
// *Cause:  During the CREATE CATALOG or UPGRADE CATALOG command, the indicated
//          PL/SQL package specification or body could not be created because
//          of PL/SQL compilation errors.
// *Action: The PL/SQL packages used by the recovery catalog are located in the
//          RECOVER.BSQ library file, and should never be modified.  Make
//          sure that the RECOVER.BSQ file has not been modified or damaged,
//          and then if this error persists, contact Oracle support.
//          Connect to the recovery catalog owner and query the USER_ERRORS
//          view to find out the details of the compilation errors.
6445, 1, "cannot connect to recovery catalog after NOCATALOG has been used"
// *Cause:  The CONNECT CATALOG command was used after the user had already
//          specified the NOCATALOG option.
// *Action: Re-start rman if you wish to use a recovery catalog.
6446, 1, "changed proxy copy unavailable"
// *Cause: This is an informational message.
// *Action: No Action Required.
6447, 1, "changed proxy copy available"
// *Cause: This is an informational message.
// *Action: No Action Required.
6448, 1, "uncataloged proxy copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
6449, 1, "deleted proxy copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
6450, 1, "crosschecked proxy copy: found to be '%s'"
// *Cause: This is an informational message.
// *Action: No Action Required.
6451, 1, "proxy copy handle=%s recid=%s stamp=%s"
// *Cause: This is an informational message.
// *Action: No Action Required.
6452, 1, "%s package upgraded to version %s"
// *Cause:  This is an informational message issued by the UPGRADE CATALOG
//          command.  It indicates the version to which the indicated package
//          was just upgraded.  Note that this
//          version number may not reflect the version number of your rman
//          executable or target database, because the recovery catalog
//          packages are not changed with each Oracle release.
// *Action: No action required. 
6453, 1, "RECOVERABLE may only be used with datafile objects"
// *Cause:  An attempt was made to use LIST ... RECOVERABLE .. with
//          OF CONTROLFILE or OF ARCHIVELOG.
// *Action: Remove the RECOVERABLE keyword and try again.
6454, 1, "duplexed backups require Oracle8 Enterprise Edition"
// *Cause: The SET DUPLEX command was specified.
// *Action: Remove the SET DUPLEX command.
6455, 1, "illegal compatible value %s.%s.%s:  must be between %s and %s"
// *Cause: Compatibility cannot be set to the value specified.
// *Action: specify a value within the required range.
6456, 1, "compatibility set to: %s.%s.%s"
// *Cause: This is an informational message only
6457, 1, "UNTIL scn (%s) is ahead of last scn in archived logs (%s)"
// *Cause: UNTIL scn cannot be more than the last scn of the last archived log
// *Action: Check the UNTIL scn. 
//
/
/ KRMQ Errors: 7000-7999
/
7000, 1, "execution layer initialization failed"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7001, 1, "could not open channel %s"
// *Cause:  An ALLOCATE CHANNEL command could not be processed.
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7003, 1, "unrecoverable error during command execution"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7004, 1, "unhandled exception during command execution on channel %s"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7005, 1, "error during channel cleanup"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7006, 1, "unhandled exception during cleanup on channel %s"
// *Action: This message should be accompanied by other error message(s)
//          indicating the cause of the error.
7007, 1, "cannot allocate more than %d channels"
// *Cause:  The maximum number of RMAN channels has been exceeded.  Note that
//          one channel is reserved for RMAN.
// *Action: Allocate fewer channels.  Contact Oracle if you have a need for
//          more channels in a single job.
7008, 1, "could not locate backup piece %s"
// *Cause:  AUTOLOCATE has been turned on, and there was at least 1 backup
//          set that could not be accessed by any of the allocated channels.
// *Action: Allocate additional channels on other nodes of the cluster
7009, 1, "restore aborted because some backup piece(s) could not be located"
// *Cause:  Same as 7008.
// *Action: Refer to 7008.
/
/ recover.bsq Errors: 8000-8999
/
8000, 1, "channel %s: copied datafile %s"
8001, 1, "restore not complete"
// *Cause:  All of the backup pieces have been successfully applied, but
//          x$dbms_backup_restore indicates that the restore conversation
//          is not complete.  This usually means that the backup set
//          contained corrupt data.
// *Action: Restore the files from a different backup set, if possible.  The
//          Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to
//          prevent Recovery Manager from attempting to restore from the
//          corrupt backup piece(s).
8002, 1, "starting full resync of recovery catalog"
8003, 1, "starting partial resync of recovery catalog"
8004, 1, "full resync complete"
8005, 1, "partial resync complete"
8006, 1, "database registered in recovery catalog"
8007, 1, "channel %s: copied datafilecopy of datafile %s"
8008, 1, "channel %s: starting %s datafile backupset"
8009, 1, "channel %s: starting archivelog backupset"
8010, 1, "channel %s: specifying datafile(s) in backupset"
8011, 1, "including current controlfile in backupset"
/ 8012 is currently unused
8012, 1, "including controlfile copy in backup set"
8013, 1, "channel %s: piece %s created"
8014, 1, "channel %s: specifying archivelog(s) in backup set"
8015, 1, "datafile %s switched to datafile copy"
8016, 1, "channel %s: starting datafile backupset restore"
8017, 1, "channel %s: starting archivelog restore to default destination"
8018, 1, "channel %s: starting archivelog restore to user-specified destination"
8019, 1, "channel %s: restoring datafile %s"
8021, 1, "channel %s: restoring controlfile"
8022, 1, "channel %s: restoring archivelog"
8023, 1, "channel %s: restored backup piece %s"
8024, 1, "channel %s: restore complete"
8025, 1, "channel %s: copied controlfile copy"
8026, 1, "channel %s: copied archivelog"
8027, 1, "channel %s: copied current controlfile"
8028, 1, "channel %s: copy current controlfile failed"
8029, 1, "snapshot controlfile name set to default value: %s"
8030, 1, "allocated channel: %s"
8031, 1, "released channel: %s"
8032, 1, "channel %s: recid %s stamp %s does not match recovery catalog"
// *Cause:  The record that identifies the source file for a copy or backup
//          database does not contain the same data as is stored in the
//          recovery catalog.
// *Action: Perform a full resync and retry the operation.  If the problem
//          persists, then contact Oracle.
8033, 1, "channel %s: including datafilecopy of datafile %s in backupset"
// *Cause: This is an informational message.
// *Action: No Action Required.
8034, 1, "full resync skipped, target database not mounted"
// *Cause: This is an informational message.
// *Action: No Action Required.
8035, 1, "partial resync skipped, target database not mounted"
// *Cause: This is an informational message.
// *Action: No Action Required.
8036, 1, "channel %s: could not create controlfile record for %s %s"
// *Cause:  The record identifying the named file was no longer present in the
//          target database controlfile, and repeated attempts to inspect the
//          file were unsuccessful in creating the record.  This could be
//          because the circular-reuse section of the controlfile which
//          holds information about the specified type of file is too small and
//          there is other database activity which is causing the record to
//          be overwritten before it can be used.
// *Action: Try increasing either the size of the controlfile circular-reuse
//          section for this file type (datafile copy or archived log, as
//          indicated in the error message, or the
//          control_file_record_keep_time initialization parameter.  If neither
//          of those remedies works then contact Oracle.
8037, 1, "channel %s: unexpected validation return code %s"
// *Cause:  This is an internal error that should never be issued.
// *Action: Contact Oracle Support.
8039, 1, "channel %s: starting incremental datafile backupset restore"
8040, 1, "full resync skipped, controlfile is not current or backup"
8041, 1, "partial resync skipped, controlfile is not current or backup"
/
8050, 1, "cataloged datafile copy"
8051, 1, "cataloged archivelog"
8052, 1, "cataloged controlfile copy"
8054, 1, "starting media recovery"
8055, 1, "media recovery complete"
8056, 1, "skipping datafile %s because it has not changed"
// *Cause: The specified datafile has not had its checkpoint advanced since
//         the previous backup, therefore it does not need a new incremental
//         backup.
// *Action: This message is informational only.
8057, 1, "channel %s: backup cancelled because all files were skipped"
// *Cause: All datafiles for this incremental backup set were skipped,
//         therefore no backup set is created.
// *Action: This message is informational only.
8058, 1, "replicating controlfile"
// *Cause: This is an informational message.
// *Action: No Action Required.
8059, 1, "media recovery failed"
8060, 1, "unable to find archivelog"
8066, 1, "database reset to incarnation %s in recovery catalog"
// *Cause: This is an informational message.
// *Action: No Action Required.
8070, 1, "deleted datafile copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
8071, 1, "channel %s: deleting archivelog(s)"
// *Cause: This is an informational message.
// *Action: No Action Required.
8072, 1, "deleted controlfile copy"
// *Cause: This is an informational message.
// *Action: No Action Required.
8073, 1, "deleted backup piece"
// *Cause: This is an informational message.
// *Action: No Action Required.
8074, 1, "crosschecked backup piece: found to be '%s'"
// *Cause: This is an informational message.
// *Action: No Action Required.
8085, 1, "created script %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
8086, 1, "replaced script %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
8087, 1, "channel %s: started backup set validation"
// *Cause: This is an informational message.
// *Action: No Action Required.
8088, 1, "applied offline range to datafile %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
8089, 1, "channel %s: specifying datafile(s) to restore from backup set"
// *Cause: This is an informational message.
// *Action: No Action Required.
8090, 1, "channel %s: starting proxy datafile restore"
// *Cause: This is an informational message.
// *Action: No Action Required.
8091, 1, "channel %s: specifying datafile(s) for proxy backup"
// *Cause: This is an informational message.
// *Action: No Action Required.
8092, 1, "channel %s: specifying datafilecopy of datafile %s for proxy backup"
// *Cause: This is an informational message.
// *Action: No Action Required.
8093, 1, "specifying current controlfile for proxy backup"
// *Cause: This is an informational message.
// *Action: No Action Required.
8094, 1, "channel %s: specifying datafile(s) for proxy restore"
// *Cause: This is an informational message.
// *Action: No Action Required.
8095, 1, "channel %s: piece %s created with %s copies"
// *Cause: This is an informational message.
// *Action: No Action Required.
8096, 1, "channel %s: starting validation of datafile backupset"
// *Cause: This is an informational message.
// *Action: No Action Required.
8097, 1, "channel %s: starting validation of archivelog backupset"
// *Cause: This is an informational message.
// *Action: No Action Required.
8098, 1, "channel %s: validation complete"
// *Cause: This is an informational message.
// *Action: No Action Required.
8100, 1, "channel %s: starting proxy validation"
// *Cause: This is an informational message.
// *Action: No Action Required.
8101, 1, "channel %s: proxy validation complete"
// *Cause: This is an informational message.
// *Action: No Action Required.
8102, 1, "channel %s: located backup piece: %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
8103, 1, "channel %s: could not locate backup piece: %s"
// *Cause: This is an informational message.
// *Action: No Action Required.
/
/ MASKable Information messages: 8500
/
8500, 1, "channel %s: sid=%s devtype=%s"
8501, 1, "output filename=%s recid=%s stamp=%s"
8502, 1, "set_count=%s set_stamp=%s creation_time=%s"
8503, 1, "piece handle=%s comment=%s"
8504, 1, "input archivelog thread=%s sequence=%s recid=%s stamp=%s"
8505, 1, "output filename=%s"
8506, 1, "input filename=%s"
8507, 1, "input datafilecopy recid=%s stamp=%s filename=%s"
8508, 1, "archivelog destination=%s"
8509, 1, "destination for restore of datafile %s: %s"
8510, 1, "archivelog thread=%s sequence=%s"
8511, 1, "piece handle=%s tag=%s params=%s"
8512, 1, "waiting for snapshot controlfile enqueue"
8513, 1, "datafile copy filename=%s recid=%s stamp=%s"
8514, 1, "archivelog filename=%s recid=%s stamp=%s"
8515, 1, "archivelog filename=%s thread=%s sequence=%s"
8516, 1, "controlfile copy filename=%s recid=%s stamp=%s"
8517, 1, "backup piece handle=%s recid=%s stamp=%s"
8518, 1, "channel %s: scanning controlfile copy %s"
8519, 1, "channel %s: scanning datafilecopy %s"
8520, 1, "channel %s: scanning archivelog %s"
8521, 1, "offline range recid=%s stamp=%s"
8522, 1, "input datafile fno=%s name=%s"
8523, 1, "restoring datafile %s to %s"
8524, 1, "input controlfilecopy name=%s"
8525, 1, "backup set complete, elapsed time: %s"
8526, 1, "channel %s: %s"
8527, 1, "channel %s: starting %s proxy datafile backup at %s"
8528, 1, "channel %s: proxy copy complete, elapsed time: %s"
8529, 1, "proxy file handle=%s"
8531, 1, "channel %s: proxy copy %s is %s in media management catalog"
/
// NLS_DO_NOT_TRANSLATE [9000,9999]
/ KRMPP Errors: 9000-9999
/
/   GENERATED BY TOPAZ 1.0.6.0.0
/   Grammar file: krmg.y, Version:8.1.3 Production
/
/
# CHARACTER_SET_NAME = American_America.US7ASCII
/
/
/
/ 
9000,0,	"debug: REDUCE \"%s\", enter state \"%d\""
/
/ 
9001,0,	"debug: SHIFT token \"%s\", enter state \"%d\""
/
/ 
9002,0,	"debug: ACCEPT."
/
/ 
9003,0,	"debug: ERROR: parser detects possible syntax error."
/
/ 
9004,0,	"debug: FATAL: topaz detects fatal error."
/
/ 
9005,0,	"debug: LOOKAHEAD token is \"%s\"."
/
/ 
9006,0,	"debug: keyword found, restore machine: state now \"%d\"."
/
/ 
9007,0,	"debug: NEW TOKEN is \"%s\"."
/
/ 
9008,0,	"debug: Grammar switch: Pushing token \"%s\"."
/
/ 
9009,0,	"debug: Restoring machine: state now \"%d\"."
/
/ 
9010,0,	"debug: Entering error recovery."
/
/ 
9011,0,	"debug: Success. Inserted token \"%s\"."
/
/ 
9012,0,	"debug: Failed. Insert token attempt."
/
/ 
9013,0,	"debug: Trying insert state."
/
/ 
9014,0,	"debug: Success."
/
/ 
9015,0,	"debug: Failed. Insert state attempt."
/
/ 
9016,0,	"debug: Trying delete token."
/
/ 
9017,0,	"debug: Failed. Delete token attempt."
/
/ 
9018,0,	"debug: Trying replace token."
/
/ 
9019,0,	"debug: Success. Replaced with \"%s\"."
/
/ 
9020,0,	"debug: Failed. Replace token attempt."
/
/ 
9021,0,	"debug: Trying delete state, insert token."
/
/ 
9022,0,	"debug: Failed. Delete/insert attempt."
/
/ 
9023,0,	"debug: Error recovery failed."
/
/ 
9026,0,	"debug: Trying insert token."
/
/ The user should tune this message to his/her needs
9101,2,	"syntax error: found \"%s\": expecting one of: \"%s\""
/
/ 
9102,0,	"attempt recovery: symbol \"%s\" inserted before \"%s\"."
/
/ 
9103,0,	"attempt recovery: symbol \"%s\" ignored."
/
/ 
9104,0,	"attempt recovery: symbol \"%s\" substituted for \"%s\"."
/
/ 
9105,4,	"error: got NULL for lexer callback."
/
/ 
9106,0,	"file \"%s\", line \"%s\"."
/
/ 
9107,1,	"error: got NULL for debug callback when debug flag is set."
/
/ 
9108,4,	"fatal: internal error"
/
/ 
9109,4,	"error: too many errors at token: %s"
/
/ 
9110,4,	"error: got NULL for one of memory callbacks and not others"
/
/ Terminals
/
9111,0,	"end-of-file"
9112,0,	"error"
9113,0,	"all"
9114,0,	"allocate"
9115,0,	"append"
9116,0,	"archivelog"
9117,0,	"atsign"
9118,0,	"at"
9119,0,	"available"
9120,0,	"alter"
9121,0,	"abort"
9122,0,	"affinity"
9123,0,	"auxiliary"
9124,0,	"auxname"
9125,0,	"and"
9126,0,	"after"
9127,0,	"autolocate"
9128,0,	"backup"
9129,0,	"backuppiece"
9130,0,	"backupset"
9131,0,	"beginline"
9132,0,	"backslash"
9133,0,	"between"
9134,0,	"before"
9135,0,	"cancel"
9136,0,	"catalog"
9137,0,	"change"
9138,0,	"channel"
9139,0,	"completed"
9140,0,	"channel_id"
9141,0,	"check"
9142,0,	"cmdfile"
9143,0,	"comma"
9144,0,	"command"
9145,0,	"connect"
9146,0,	"copy"
9147,0,	"create"
9148,0,	"controlfile"
9149,0,	"controlfilecopy"
9150,0,	"clone_cf"
9151,0,	"clone"
9152,0,	"clonename"
9153,0,	"cumulative"
9154,0,	"current"
9155,0,	"crosscheck"
9156,0,	"configure"
9157,0,	"compatible"
9158,0,	"database"
9159,0,	"datafile"
9160,0,	"datafilecopy"
9161,0,	"days"
9162,0,	"duplicate"
9163,0,	"debug"
9164,0,	"define"
9165,0,	"delete"
9166,0,	"destination"
9167,0,	"device"
9168,0,	"diskratio"
9169,0,	"dquote"
9170,0,	"dba"
9171,0,	"dot"
9172,0,	"double-quoted-string"
9173,0,	"disk"
9174,0,	"dump"
9175,0,	"dbid"
9176,0,	"duplex"
9177,0,	"drop"
9178,0,	"eof"
9179,0,	"execute"
9180,0,	"exit"
9181,0,	"equal"
9182,0,	"endinline"
9183,0,	"expired"
9184,0,	"echo"
9185,0,	"filesperset"
9186,0,	"for"
9187,0,	"forever"
9188,0,	"format"
9189,0,	"from"
9190,0,	"full"
9191,0,	"force"
9192,0,	"group"
9193,0,	"hash"
9194,0,	"high"
9195,0,	"host"
9196,0,	"identifier"
9197,0,	"id"
9198,0,	"incarnation"
9199,0,	"include"
9200,0,	"incremental"
9201,0,	"input"
9202,0,	"inaccessible"
9203,0,	"integer"
9204,0,	"immediate"
9205,0,	"job"
9206,0,	"kbytes"
9207,0,	"k"
9208,0,	"{"
9209,0,	"("
9210,0,	"<<<"
9211,0,	"level"
9212,0,	"libparm"
9213,0,	"library"
9214,0,	"like"
9215,0,	"list"
9216,0,	"limit"
9217,0,	"logseq"
9218,0,	"low"
9219,0,	"logfile"
9220,0,	"log"
9221,0,	"logical"
9222,0,	"maxopenfiles"
9223,0,	"maxcorrupt"
9224,0,	"msglog"
9225,0,	"mask"
9226,0,	"msgno"
9227,0,	"maintenance"
9228,0,	"mount"
9229,0,	"m"
9230,0,	"name"
9231,0,	"need"
9232,0,	"newname"
9233,0,	"nochecksum"
9234,0,	"nocatalog"
9235,0,	"newline"
9236,0,	"noredo"
9237,0,	"normal"
9238,0,	"nomount"
9239,0,	"nofilenamecheck"
9240,0,	"null"
9241,0,	"of"
9242,0,	"offline"
9243,0,	"orphan"
9244,0,	"obsolete"
9245,0,	"open"
9246,0,	"on"
9247,0,	"off"
9248,0,	"only"
9249,0,	"parms"
9250,0,	"plsql"
9251,0,	"print"
9252,0,	"pfile"
9253,0,	"proxy"
9254,0,	"pool"
9255,0,	"pipe"
9256,0,	"quote"
9257,0,	"rcvcat"
9258,0,	"readonly"
9259,0,	"readrate"
9260,0,	"recover"
9261,0,	"redundancy"
9262,0,	"register"
9263,0,	"reuse"
9264,0,	"release"
9265,0,	"reload"
9266,0,	"replace"
9267,0,	"replicate"
9268,0,	"report"
9269,0,	"recoverable"
9270,0,	"renormalize"
9271,0,	"reset"
9272,0,	"restart"
9273,0,	"restore"
9274,0,	"resync"
9275,0,	"resetlogs"
9276,0,	"rman"
9277,0,	"}"
9278,0,	")"
9279,0,	">>>"
9280,0,	"rpctest"
9281,0,	"run"
9282,0,	"scn"
9283,0,	"script"
9284,0,	";"
9285,0,	"set"
9286,0,	"setlimit"
9287,0,	"skip"
9288,0,	"slaxdebug"
9289,0,	"sql"
9290,0,	"step"
9291,0,	"switch"
9292,0,	"single-quoted-string"
9293,0,	"snapshot"
9294,0,	"schema"
9295,0,	"setsize"
9296,0,	"startup"
9297,0,	"shutdown"
9298,0,	"send"
9299,0,	"size"
9300,0,	"tablespace"
9301,0,	"tag"
9302,0,	"target"
9303,0,	"test"
9304,0,	"timeout"
9305,0,	"textline"
9306,0,	"thread"
9307,0,	"time"
9308,0,	"to"
9309,0,	"trace"
9310,0,	"type"
9311,0,	"transactional"
9312,0,	"unavailable"
9313,0,	"uncatalog"
9314,0,	"underscore"
9315,0,	"unrecoverable"
9316,0,	"until"
9317,0,	"upgrade"
9318,0,	"validate"
/
/ Nonterminals
/
9319,0,	"accept grammar"
9320,0,	"qstring"
9321,0,	"quoted_filename"
9322,0,	"quoted_logfile_name"
9323,0,	"textVal"
9324,0,	"quoted_channel_parms"
9325,0,	"quoted_string_pattern"
9326,0,	"quoted_datafile_name"
9327,0,	"quoted_archivelog_name"
9328,0,	"quoted_media_device"
9329,0,	"quoted_channel_name"
9330,0,	"quoted_controlfile_name"
9331,0,	"quoted_archlog_dest"
9332,0,	"quoted_command_id"
9333,0,	"quoted_host_command"
9334,0,	"quoted_format_spec"
9335,0,	"quoted_date_spec"
9336,0,	"quoted_sql_command"
9337,0,	"quoted_device_command"
9338,0,	"quoted_backup_piece_name"
9339,0,	"quoted_proxy_name"
9340,0,	"media_handle"
9341,0,	"media_device"
9342,0,	"channel_name"
9343,0,	"command"
9344,0,	"string"
9345,0,	"log_archive_dest"
9346,0,	"string_pattern"
9347,0,	"channel_parms"
9348,0,	"date_string"
9349,0,	"textNode"
9350,0,	"CFile_Node"
9351,0,	"Sql_Node"
9352,0,	"AFile_Node"
9353,0,	"DFile_Node"
9354,0,	"BPiece_Node"
9355,0,	"Proxy_Node"
9356,0,	"cTextNodeList"
9357,0,	"cAFile_NodeList"
9358,0,	"cBPiece_NodeList"
9359,0,	"cCFile_NodeList"
9360,0,	"cDFile_NodeList"
9361,0,	"cProxy_NodeList"
9362,0,	"string_or_identifier"
9363,0,	"connect_string"
9364,0,	"filename"
9365,0,	"database_name"
9366,0,	"channel_id"
9367,0,	"tablespace_name"
9368,0,	"script_name"
9369,0,	"tag_name"
9370,0,	"userid"
9371,0,	"password"
9372,0,	"net_service_name"
9373,0,	"usr_pwd_alias"
9374,0,	"tagVal"
9375,0,	"tagValList"
9376,0,	"tag"
9377,0,	"tagList"
9378,0,	"keyVal"
9379,0,	"keyValList"
9380,0,	"datafileSpec"
9381,0,	"datafileSpecList"
9382,0,	"datafile"
9383,0,	"datafileList"
9384,0,	"datafileCopySpecList"
9385,0,	"datafileCopyOperandList"
9386,0,	"datafileCopySpecSingle"
9387,0,	"datafileCopySingle"
9388,0,	"datafileCopyNameList"
9389,0,	"datafileCopyTagList"
9390,0,	"deviceTypeList"
9391,0,	"deviceSpecifierList"
9392,0,	"deviceSpecifier"
9393,0,	"tablespaceList"
9394,0,	"tsName"
9395,0,	"tsNameList"
9396,0,	"archiveLogName"
9397,0,	"archiveLogNameList"
9398,0,	"archiveLogKeyList"
9399,0,	"controlfileCopySpecList"
9400,0,	"controlfileCopySpecSngl"
9401,0,	"controlfileCopyOperandL"
9402,0,	"controlfileCopyOperandS"
9403,0,	"controlfileCopyName"
9404,0,	"controlfileCopyNameList"
9405,0,	"backupPieceSpec"
9406,0,	"backupPieceOperand"
9407,0,	"proxySpec"
9408,0,	"proxyOperand"
9409,0,	"backupSetKeyList"
9410,0,	"archivelogRecordSpecifier"
9411,0,	"fileNamePattern"
9412,0,	"archlogRange"
9413,0,	"fromTime"
9414,0,	"untilTime"
9415,0,	"atTime"
9416,0,	"fromSCN"
9417,0,	"untilSCN"
9418,0,	"atSCN"
9419,0,	"fromLogSeq"
9420,0,	"untilLogSeq"
9421,0,	"atLogSeq"
9422,0,	"timeIntervalSpec"
9423,0,	"logSeq"
9424,0,	"thread"
9425,0,	"thread_arch"
9426,0,	"parms"
9427,0,	"connect"
9428,0,	"cumulative"
9429,0,	"nochecksum"
9430,0,	"checklogical"
9431,0,	"diskratio"
9432,0,	"filesperset"
9433,0,	"maxcorrupt"
9434,0,	"format"
9435,0,	"channelSpecifier"
9436,0,	"channelSpecifierList"
9437,0,	"channel"
9438,0,	"time"
9439,0,	"timeSpec"
9440,0,	"scn"
9441,0,	"kbytes"
9442,0,	"readrate"
9443,0,	"maxopenfiles"
9444,0,	"job"
9445,0,	"script"
9446,0,	"debugLevel"
9447,0,	"setsize"
9448,0,	"proxy"
9449,0,	"argList"
9450,0,	"arg"
9451,0,	"target"
9452,0,	"rcvcat"
9453,0,	"clone"
9454,0,	"libDef"
9455,0,	"libDefList"
9456,0,	"libTextList"
9457,0,	"libTextLine"
9458,0,	"rmanCmdList"
9459,0,	"rmanCmd"
9460,0,	"register"
9461,0,	"reset"
9462,0,	"resync"
9463,0,	"allocateForMaint"
9464,0,	"releaseForMaint"
9465,0,	"change"
9466,0,	"catalog"
9467,0,	"release"
9468,0,	"report"
9469,0,	"list"
9470,0,	"crosscheck"
9471,0,	"deleteExpired"
9472,0,	"maintOperand"
9473,0,	"changeOperand"
9474,0,	"catalogFileList"
9475,0,	"catalogOption"
9476,0,	"catalogOptionList"
9477,0,	"recordSpec"
9478,0,	"reportOperand"
9479,0,	"reportObsoleteOperandList"
9480,0,	"reportObsoleteOperand"
9481,0,	"reportQualifierList"
9482,0,	"reportQualifier"
9483,0,	"reportObject"
9484,0,	"ofEverything"
9485,0,	"ofDefault"
9486,0,	"listCopySpec"
9487,0,	"listBackupsetSpec"
9488,0,	"listIncanationSpec"
9489,0,	"listCmd"
9490,0,	"listOperand"
9491,0,	"listObject"
9492,0,	"listObjList"
9493,0,	"listQualifiers"
9494,0,	"listQualifierList"
9495,0,	"listQualifier"
9496,0,	"maintQualifiers"
9497,0,	"maintQualifierList"
9498,0,	"maintQualifier"
9499,0,	"maintBackupsetSpec"
9500,0,	"recoverableClause"
9501,0,	"completedTimeSpec"
9502,0,	"completedBetweenSpec"
9503,0,	"completedAfterSpec"
9504,0,	"completedBeforeSpec"
9505,0,	"needBackupOperand"
9506,0,	"redundancy"
9507,0,	"createScript"
9508,0,	"deleteScript"
9509,0,	"printScript"
9510,0,	"replaceScript"
9511,0,	"jobControlCmd"
9512,0,	"text"
9513,0,	"textlines"
9514,0,	"jobCmdList"
9515,0,	"jobCommand"
9516,0,	"allocate_kw"
9517,0,	"allocate"
9518,0,	"channelSpec"
9519,0,	"allocOperandList"
9520,0,	"allocOperand"
9521,0,	"setlimitOperandList"
9522,0,	"setlimitOperand"
9523,0,	"set_run_option"
9524,0,	"setPragmaOperand"
9525,0,	"newname"
9526,0,	"archivedest"
9527,0,	"cmdid"
9528,0,	"duplex"
9529,0,	"set"
9530,0,	"setOperand"
9531,0,	"snapshot"
9532,0,	"auxname"
9533,0,	"echo"
9534,0,	"autolocate"
9535,0,	"backup"
9536,0,	"backupType"
9537,0,	"backupSpecList"
9538,0,	"backupOperandList"
9539,0,	"backupOperand"
9540,0,	"backupSpec"
9541,0,	"backupObject"
9542,0,	"backupSpecOperandList"
9543,0,	"backupSpecOperand"
9544,0,	"copy"
9545,0,	"copy_optionList"
9546,0,	"copy_option"
9547,0,	"copySpecList1"
9548,0,	"copySpecList2"
9549,0,	"copySpec"
9550,0,	"copy_inputfile"
9551,0,	"outputfile"
9552,0,	"switch_kw"
9553,0,	"switch"
9554,0,	"switchOperand"
9555,0,	"restore"
9556,0,	"restoreSpecList"
9557,0,	"restoreOperandList"
9558,0,	"restoreOperand"
9559,0,	"fromType"
9560,0,	"untilClause"
9561,0,	"atClause"
9562,0,	"fromTag"
9563,0,	"restoreSpec"
9564,0,	"restoreObject"
9565,0,	"skip"
9566,0,	"skipForever"
9567,0,	"restoreSpecOperandList"
9568,0,	"restoreSpecOperand"
9569,0,	"recover_kw"
9570,0,	"recover"
9571,0,	"recoverObject"
9572,0,	"recoverOpList"
9573,0,	"recoverOp"
9574,0,	"run"
9575,0,	"replicate"
9576,0,	"host"
9577,0,	"sql_kw"
9578,0,	"sql"
9579,0,	"plsql"
9580,0,	"print"
9581,0,	"printObjList"
9582,0,	"validate"
9583,0,	"debug"
9584,0,	"setDbid"
9585,0,	"createCatalog"
9586,0,	"upgradeCatalog"
9587,0,	"dropCatalog"
9588,0,	"startup"
9589,0,	"startup_kw"
9590,0,	"pfile"
9591,0,	"startupOptionList"
9592,0,	"startupOption"
9593,0,	"mountOption"
9594,0,	"alterDatabase"
9595,0,	"alterDatabase_kw"
9596,0,	"database_kw"
9597,0,	"alterOption"
9598,0,	"shutdown"
9599,0,	"shutdownOption"
9600,0,	"shutdown_kw"
9601,0,	"send"
9602,0,	"channelList"
9603,0,	"deviceCommand"
9604,0,	"duplicate"
9605,0,	"checkSpec"
9606,0,	"logSpecList"
9607,0,	"logfile"
9608,0,	"logGrp"
9609,0,	"logNameList"
9610,0,	"logName"
9611,0,	"logSpec"
9612,0,	"lSizeSpec"
9613,0,	"lReuseSpec"
9614,0,	"skipSpec"
9615,0,	"cmdLine"
9616,0,	"cmdfile"
9617,0,	"msglog"
9618,0,	"configure"
9619,0,	"configureOption"
9620,0,	"rmanInput"
9621,0,	"trace_kw"
9622,0,	"assign"
9623,0,	"target_kw"
9624,0,	"rcvcat_kw"
9625,0,	"clone_kw"
9626,0,	"cmdfile_kw"
9627,0,	"at_kw"
9628,0,	"msglog_kw"
9629,0,	"maint_kw"
9630,0,	"connect_kw"
9631,0,	"connectTarget"
9632,0,	";_nl"
9633,0,	"connectRcvcat"
9634,0,	"connectClone"
9635,0,	"retnl"
9636,0,	"saveText"
9637,0,	"pfile_kw"
9638,0,	"cfCopy_kw"
9639,0,	"connectStringSpec"
9640,0,	"format_string"
/
/ KRMX Errors: 10000-10999
/
10000, 1, "error parsing target database connect string \"%s\""
// *Cause:  An invalid target connect string was supplied.
// *Action: Specify a valid connect string and re-run the job.
10001, 1, "error parsing recovery catalog connect string \"%s\""
// *Cause:  An invalid recovery catalog connect string was supplied.
// *Action: Specify a valid connect string and re-run the job.
10002, 1, "ORACLE error: %s"
// *Cause: The specified Oracle error was received.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: Check the accompanying errors.
10003, 1, "unable to connect to target database using connect string \"%s\""
// *Cause:  Recovery manager was unable to connect to the target database.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: Ensure that that the target database is started, and that the
//          connect string is valid.
10004, 1, "unable to connect to recovery catalog using connect string: %s"
// *Cause: Recovery manager was unable to connect to the recovery catalog
// *Action:  Ensure that that the recovery catalog is started, and that the
//           connect string is valid.
//           This message should be accompanied by other error message(s)
//           indicating the cause of the error. 
10005, 1, "error opening cursor"
// *Cause:  An error was received while trying to open a cursor.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If the associated Oracle error message indicates a condition that
//          can be corrected, do so, otherwise contact Oracle.
10006, 1, "error running sql statement: %s"
// *Cause:  An error message was received while running the SQL statement
//          shown.
// *Action: If the associated Oracle error message indicates a condition that
//          can be corrected, do so, otherwise contact Oracle.
10007, 1, "error closing cursor"
// *Cause:  An error was received while trying to close a cursor.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If the associated Oracle error message indicates a condition that
//          can be corrected, do so, otherwise contact Oracle.
10008, 1, "could not create channel context"
// *Cause:  An error was received while trying create a channel context.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If the associated Oracle error message indicates a condition that
//          can be corrected, do so, otherwise contact Oracle.
10009, 1, "error logging off of Oracle"
// *Cause:  An error was received while disconnecting from Oracle.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: This message is informational only.
10010, 1, "error while checking for RPC completion"
// *Cause:  Recovery Manager's channel context had an error while checking to
//          see if a remote procedure call had completed.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If other error messages indicate a condition that can be corrected,
//          do so, otherwise contact Oracle.
10011, 1, "synchronization error while polling for rpc %d, action=%s"
// *Cause:  Recovery Manager could not synchronize properly with a remote
//          procedure call.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10012, 1, "KGU error: %s"
// *Cause:  An error occurred while initializing the KGU subsystem
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10013, 1, "error initializing PL/SQL"
// *Cause:  An error occurred while initializing the PL/SQL subsystem.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10014, 1, "PL/SQL error %d on line %d column %d: %s"
// *Cause:  PL/SQL error
// *Action: The text of this message will be issued by the PL/SQL subsystem.
//          See the PL/SQL error message manual.
10015, 1, "error compiling PL/SQL program"
// *Cause:  An error occurred while compiling a PL/SQL program.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10016, 1, "error creating PL/SQL runtime context"
// *Cause: 
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10017, 1, "error initializing channel context"
// *Cause:  An error was received while trying initialize a channel context.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If other error messages indicate a condition that can be corrected,
//          do so, otherwise contact Oracle.
10018, 1, "error cleaning up channel context"
// *Cause:  An error was received during inter-step cleanup of a channel
//          context.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10020, 1,  "error initializing Recovery Manager execution layer"
// *Cause:  An error was received while initializing the Recovery Manager
//          execution layer in preparation for running a job.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If other error messages indicate a condition that can be corrected,
//          do so, otherwise contact Oracle.
10022, 1, "error in system-dependant sleep routine"
// *Cause:  An error was received while waiting for a remote RPC to complete.
//          The error occurred in the system-dependant sleep routine.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10023, 1, "RPC attempted to unrecognized package"
// *Cause:  The Recovery Manager internal RPC router received a package name
//          that it could not understand.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10024, 1, "error setting up for rpc polling"
// *Cause:  The Recovery Manager could not create the RPC polling context
//          which is required to test for RPC completion.
//          This message should be accompanied by other error message(s)
//          indicating the cause of the error.  
// *Action: If other error messages indicate a condition that can be corrected,
//          do so, otherwise contact Oracle.
10025, 1, "connection is already registered for events"
// *Cause:  The Recovery Manager could not enable the target database
//          connection to test for RPC completion.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10026, 1, "network error %d-%d occurred registering connection"
// *Cause:  An network error occurred while attempting to register the target
//          database connection to test for RPC completion.
// *Action: This is an internal error that should not be issued.
//          The message numbers are issued by the Sql*Net layer.
//          Contact Oracle Support.
10027, 1, "could not locate network layer context"
// *Cause:  Recovery Manager could not locate a necessary context area while
//          attempting to register the target database connection to test for
//          RPC completion.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10028, 1, "network error %d-%d occurred during remote RPC"
// *Cause:  An network error occurred while waiting for a remote RPC to
//          complete.
// *Action: This is an internal error that should not be issued.
//          The message numbers are issued by the Sql*Net layer.
//          Contact Oracle Support.
10029, 1, "unexpected return code %d from PL/SQL execution"
// *Cause:  PL/SQL returned an unexpected return code while executing one
//          channel program.
// *Action: This is an internal error that should not be issued.
//          Contact Oracle Support.
10030, 1, "RPC call appears to have failed to start on channel %s"
// *Cause:  An RPC to a target database instance was issued, but was not
//          observed to start within 5 timeouts.
// *Action: This error is probably accompanied by other error messages 
//          giving the precise cause of the failure.
10031, 1, "ORA-%d occurred during call to %s.%s"
// *Cause:  An RPC to the target database or recovery catalog database
//          encountered an error.
// *Action: This error is accompanied with the error message from the
//          server where the error occurred.
10032, 1, "unhandled exception during execution of job step %d: %s"
// *Cause:  An unhandled PL/SQL execption occurred during a job step.
// *Action: This error is accompanied by the error messages describing
//          the exception.
10033, 1, "error during compilation of job step %d: %s"
// *Cause:  PL/SQL detected a problem during the compilation of a job step
// *Action: This error message is accompanied by the error messages describing
10034, 1, "unhandled exception during execution of job step %d, error unknown"
// *Cause:  PL/SQL detected an unhandled exception during execution of a job
//          step, but no further information available
// *Action: 
10035, 1, "exception raised in RPC: %s"
// *Cause:  A call to a remote package resulted in an exception.
// *Action: The exception should indicate what went wrong.
10036, 1, "RPC call ok on channel %s"
// *Cause:  This is just an informational message.  It should be preceeded
//          by message 10030.
// *Action: none
10037, 1, "RPC anomaly detected on channel %s, upinblt=%d"
// *Cause:  This is an debugging message and can be ignored.
// *Action: None.
10038, 1, "database session for channel %s terminated unexpectedly"
// *Cause:  The database connection for the specified channel no longer exists.
//          Either the session was terminated by some external means or
//          the channel terminated because of an internal error.
// *Action: Check for an oracle trace file for detailed information on why
//          the session terminated.
10039, 1, "error encountered while polling for RPC completion on channel %s"
// *Cause:  This error should be accompanied by other errors giving
//          the cause of the polling error.
/
/ 11000-11999: KRMZ
/
11000, 1, "message number %d not found in recovery manager message file"
// *Cause:  Recovery manager message file is out of date.
// *Action: Make sure that the recovery manager error message file is current
//         a nd installed in the correct location
11001, 1, "Oracle Error: %s"
11002, 1, "could not open a cursor to the target database"
11003, 1, "failure during parse/execution of SQL statement: %s"
11004, 1, "format requires %%c when duplexing"  
// *Cause:  SET_DUPLEX=ON was specified, but %c was not part of the format. 
// *Action: Include %c in format, or use %U.  
/
/ 20000-20999: DBMS_RCVCAT and DBMS_RCVMAN
/
20000, 1, "abnormal termination of job step"
// *Cause:  A job step encountered an error and could not recover.
//          This error should be followed by other errors indicating
//          the cause of the problem.
//
20001, 1, "target database not found in recovery catalog"
// *Cause: target database is not found in the recovery catalog
// *Action: make sure that the target database is registered in the recovery
//         recovery catalog
//
20002, 1, "target database already registered in recovery catalog"
// *Cause: target database is already registered in the recovery catalog
// *Action: if the target database is really registered, there is no need to
//         register it again. Note that the recovery catalog enforces that 
//         all databases have a unique DBID. If the new database was created 
//         by copying files from an existing database, it will have the 
//         same DBID as the original database and cannot be registered in
//         the same recovery catalog.
//
20003, 1, "target database incarnation not found in recovery catalog"
// *Cause: resetlogs change# and/or time of the target database doesn't match
//         any database incarnation in the recovery catalog. 
// *Action: if target database was opened with resetlogs option then use
//         'reset database' to register the new incarnation. 
//
20004, 1, "target database name does not match name in recovery catalog"
// *Cause: name of the target database doesn't match the one stored in
//        the recovery catalog
// *Action: This is an internal error, call support.
//
20005, 1, "target database name is ambiguous"
// *Cause: two or more databases in the recovery catalog match this name
// *Action:
//
20006, 1, "target database name is missing"
// *Cause: target database instance is not started or 
//        db_name initialization parameter is not set
// *Action: startup the instance and make sure that db_name parameter is set 
//
20007, 1, "target database id is missing"
// *Cause: 
// *Action: this an internal error
//
20008, 1, "database incarnation key is missing"
// *Cause: 
// *Action: specify a valid database incarnation key
//
20009, 1, "database incarnation already registered"
// *Cause: this incarnation is already registered in the recovery catalog
// *Action: None
//
20010, 1, "database incarnation not found"
// *Cause: database incarnation does not match any database incarnation in
//         the recovery catalog
// *Action: specify a valid database incarnation key
//
20011, 1, "target database incarnation is not current in recovery catalog"
// *Cause: the database incarnation that matches the resetlogs change# and time
//         of the mounted target database controlfile is not the current
//         incarnation of the database
// *Action: If 'reset database to incarnation <key>' was used to make an
//          old incarnation current then restore the target database
//          from a backup that matches the incarnation and mount it.
//          You will need to do 'startup nomount' before you can restore
//          the controlfile using RMAN.
//          Otherwise use 'reset database to incarnation <key>' make the
//          intended incarnation current in the recovery catalog.
//
20020, 1, "database incarnation not set"
// *Cause: 
// *Action: this is an internal error
//
20021, 1, "database not set"
// *Cause: 
// *Action: this is an internal error
//
20029, 1, "cannot make a snapshot controlfile"
// *Cause: another operation that needs the snapshot controlfile is in progress
// *Action: try again later if necessary
//
20030, 1, "resync in progress"
// *Cause: this procedure can not be called while a resync is in progress
// *Action: This is an internal error
//
20031, 1, "resync not started"
// *Cause: this procedure can only be called in a resync
// *Action: This is an internal error
//
20032, 1, "checkpoint change# too low"
// *Cause: the checkpoint change# is less than the one of the previous resync or
//        the checkpoint change# is null
// *Action: make sure that the right controlfile is used
//
20033, 1, "controlfile sequence# too low"
// *Cause: the controlfile sequence is less than the one of the previous resync 
// *Action: make sure that the right controlfile is used
//
20034, 1, "resync not needed"
// *Cause: the control file has not changed since the previous resync
// *Action: nothing since the recovery catalog is in sync 
//
20035, 1, "invalid high recid"
// *Cause: 
// *Action: This is an internal error
//
20036, 1, "invalid record order"
// *Cause: 
// *Action: This is an internal error
//
20037, 1, "invalid last recid"
// *Cause: 
// *Action: This is an internal error
//
20040, 1, "tablespace resync not started"
// *Cause: 
// *Action: This is an internal error
//
20041, 1, "tablespace resync not completed"
// *Cause: 
// *Action: This is an internal error
//
20042, 1, "invalid tablespace creation change#"
// *Cause: 
// *Action: This is an internal error
//
20043, 1, "invalid tablespace create time"
// *Cause: 
// *Action: This is an internal error
//
20044, 1, "invalid tablespace name"
// *Cause: 
// *Action: This is an internal error
//
20050, 1, "datafile resync not started"
// *Cause: 
// *Action: This is an internal error
//
20051, 1, "datafile resync not completed"
// *Cause: 
// *Action: This is an internal error
//
20052, 1, "invalid datafile create SCN"
// *Cause: 
// *Action: This is an internal error
//
20053, 1, "invalid datafile create time"
// *Cause: 
// *Action: This is an internal error
//
20054, 1, "invalid datafile ts#"
// *Cause: 
// *Action: This is an internal error
//
20061, 1, "thread resync not started"
// *Cause: 
// *Action: This is an internal error
//
20070, 1, "invalid log history sequence#"
// *Cause: 
// *Action: This is an internal error
//
20071, 1, "invalid log history low SCN"
// *Cause: 
// *Action: This is an internal error
//
20080, 1, "invalid archived log name"
// *Cause: 
// *Action: This is an internal error
//
20085, 1, "invalid offline range file#"
// *Cause: 
// *Action: This is an internal error
//
20086, 1, "invalid offline range offline_scn"
// *Cause: 
// *Action: This is an internal error
//
20087, 1, "invalid offline range online_scn"
// *Cause: 
// *Action: This is an internal error
//
20090, 1, "invalid backup set type"
// *Cause: 
// *Action: This is an internal error
//
20091, 1, "invalid backup set level"
// *Cause: 
// *Action: This is an internal error
//
20092, 1, "invalid backup set completion time"
// *Cause: 
// *Action: This is an internal error
//
20093, 1, "invalid backup piece number"
// *Cause: 
// *Action: This is an internal error
//
20094, 1, "missing backup set"
// *Cause: 
// *Action: This is an internal error
//
20095, 1, "invalid backup/copy controlfile checkpoint scn"
// *Cause: 
// *Action: This is an internal error
//
20096, 1, "invalid backup/copy datafile file#"
// *Cause: 
// *Action: This is an internal error
//
20097, 1, "invalid backup/copy datafile create scn"
// *Cause: 
// *Action: This is an internal error
//
20098, 1, "invalid backup redo log low scn"
// *Cause: 
// *Action: This is an internal error
//
20100, 1, "invalid status"
// *Cause: 
// *Action: This is an internal error
//
20101, 1, "datafile copy missing"
// *Cause: 
// *Action: This is an internal error
//
20102, 1, "archived log missing"
// *Cause: 
//
20103, 1, "controlfile copy missing"
// *Cause: 
// *Action: This is an internal error
//
20104, 1, "backup piece missing"
// *Cause: 
// *Action: This is an internal error
//
20105, 1, "datafile missing"
// *Cause: 
// *Action: This is an internal error
//
20106, 1, "proxy copy missing"
// *Cause: 
// *Action: This is an internal error
//
20200, 1, "invalid restore source"
// *Cause: 
// *Action: This is an internal error
//
20201, 1, "datafile not found in the recovery catalog"
// *Cause:  The specified datafile is not found in the recovery catalog
// *Action: make sure that the datafile name is correct and
//         that the recovery catalog is up-to-date
//
20202, 1, "tablespace not found in the recovery catalog"
// *Cause:  the specified tablespace is not found in the recovery catalog
// *Action: make sure that the tablespace name is correct and
//         that the recovery catalog is up-to-date
//
20203, 1, "translation in progress"
// *Cause: this procedure can not be called when name translation is in progress
// *Action: this is an internal error
//
20204, 1, "translation not started"
// *Cause: getDatafile procedure was called before translateTablespace
// *Action: this is an internal error
//
20205, 1, "incomplete UNTIL clause"
// *Cause: The sequence# was NULL
// *Action: this is an internal error
//
20206, 1, "log sequence not found in the recovery catalog"
// *Cause: The specified log sequence does not exists in log history
//        of the current database incarnation
// *Action: check the thread# and sequence#
//
20207, 1, "UNTIL TIME is before RESETLOGS time"
// *Cause: UNTIL TIME cannot be less than the database creation time or
//         RESETLOGS time.
// *Action: Check the UNTIL TIME. If the database needs to be restored to
//          an old incarnation, use the RESET DATABASE TO INCARNATION command.
//
20208, 1, "UNTIL CHANGE is before RESETLOGS change"
// *Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change.
// *Action: Check the UNTIL CHANGE. If the database needs to be restored to
//          an old incarnation, use the RESET DATABASE TO INCARNATION command.
//
20209, 1, "duplicate datafile name"
// *Cause: Two datafiles have the same name
// *Action: this is an internal error
//
20210, 1, "invalid archived log range, thread number is null"
// *Cause: 
// *Action: this is an internal error
//
20211, 1, "FROM TIME is before RESETLOGS time"
// *Cause: FROM TIME cannot be less than the database creation time or
//         RESETLOGS time.
// *Action: Check the FROM TIME. If the database needs to be restored to
//          an old incarnation, use the RESET DATABASE TO INCARNATION command.
//
20215, 1, "backup set not found"
// *Cause: The specified backup set key was not found in the recovery catalog
// *Action: Specify a different backup set key.
20216, 1, "backup piece is missing"
// *Cause: 
// *Action: this is an internal error
//
20217, 1, "datafile not part of the database"
// *Cause: the datafile does not exists or did not exist at until time/scn
// *Action: check the datafile name or number. This is an internal error
//         for restore database or tablespace.
//
20218, 1, "datafile not found in recovery catalog"
// *Cause: This is an internal error
// *Action: Contact Oracle Support.
//
20220, 1, "controlfile copy not found in the recovery catalog"
// *Cause: the specified controlfile is not in the recovery catalog or
//        it has been marked deleted
// *Action: check the filename
//
20221, 1, "ambiguous controlfile copy name"
// *Cause: more than one controlfile copy in the recovery catalog match the
//        specified name.
// *Action:
//
20222, 1, "datafilename not found in recovery catalog or is ambiguous"
// *Cause:  The specified datafilename is not the name of a datafile that is
//          currently part of the target database, or an UNTIL clause has
//          been specified and the filename was for a different datafile
//          at the time specified by the UNTIL clause than it is now.
// *Action: Use a datafile number to specify the datafile you want to RESTORE
//          or RECOVER.
//
20230, 1, "datafile copy not found in the recovery catalog"
// *Cause: the specified datafile is not in the recovery catalog or
//        it has been marked deleted
// *Action: check the datafile copy name or key
//
20231, 1, "ambiguous datafilecopy name"
// *Cause: more than one controlfile copy in the recovery catalog match the
//        specified name.
// *Action: use the datafile copy key to uniquely specify the datafile copy
//
20232, 1, "tag does not match any datafile copy in the recovery catalog"
// *Cause: 
// *Action: check the tag
//
20240, 1, "archived log not found in the recovery catalog"
// *Cause: the specified archived log was not found in the recovery catalog
//        or it has been marked deleted
// *Action: check the archived log name or key
//
20241, 1, "ambiguous archived log name"
// *Cause: more than one archived log in the recovery catalog match the
//        specified name
// *Action: use the archived log key to uniquely specify the archived log
//
20242, 1, "specification does not match any archivelog in the recovery catalog"
// *Cause: 
// *Action: check the archivelog specifier
//
20250, 1, "offline range not found in the recovery catalog"
// *Cause: the specified offline was not found in the recovery catalog
// *Action: check that recovery catalog is current
//
20260, 1, "backup piece not found in the recovery catalog"
// *Cause: the specified backup piece is not in the recovery catalog or
//        it has been marked deleted
// *Action: check the backup piece handle or key
//
20261, 1, "ambiguous backup piece handle"
// *Cause: more than one backup piece in the recovery catalog match the
//        specified handle
// *Action: use the backup piece key to uniquely specify the backup piece
//
20270, 1, "invalid incremental backup level"
// *Cause: 
// *Action: 
//
20271, 1, "invalid incremental cumulative option"
// *Cause: 
// *Action: 
//
20272, 1, "no parent backup found for the incremental backup"
// *Cause: no available backup or copy that could be used as the parent of
//         the incremental backup was found in the recovery catalog.
// *Action: take a level 0 backup or copy of the datafile first
//
20280, 1, "too many device types"
// *Cause: more than 8 device types were allocated
// *Action: make sure that the job allocates at most 8 different device types
//
20298, 1, "DBMS_RCVCAT package not compatible with the recovery catalog" 
// *Cause:  The version of the recovery catalog tables does not work with this
//          version of the DBMS_RCVCAT package.
// *Action: Check that the recovery catalog packages and schema are installed
//          correctly.  The UPGRADE CATALOG command can be used to upgrade
//          the recovery catalog tables and packages to the most current
//          version.
//
20299, 1, "DBMS_RCVMAN package not compatible with the recovery catalog" 
// *Cause:  The version of the recovery catalog tables does not work with this
//          version of the DBMS_RCVMAN package.
// *Action: Check that the recovery catalog packages and schema are installed
//          correctly.  The UPGRADE CATALOG command can be used to upgrade
//          the recovery catalog tables and packages to the most current
//          version.
//
20300, 1, "operation not supported without the recovery catalog"
// *Cause: 
// *Action: 
//
20310, 1, "proxy copy not found in the recovery catalog"
// *Cause: the specified proxy copy is not in the recovery catalog or
//        it has been marked deleted
// *Action: check the proxy copy handle or key
//
20311, 1, "ambiguous proxy copy handle"
// *Cause: more than one proxy copy in the recovery catalog matches the
//        specified handle
// *Action: use the proxy copy key to uniquely specify the proxy copy
//
20312, 1, "ambiguous proxy copy recid"
// *Cause: this is an internal error
20400, 1, "stored script not found"
20401, 1, "script already exists"
// *Cause: a CREATE SCRIPT was issued, but a script with the specified
//         name already exists.
// *Action: use a different name or use REPLACE SCRIPT.
20500, 1, "media recovery aborted"
20501, 1, "redo logs from parent database incarnation cannot be applied"
// *Cause: A RESTORE or RECOVER of a datafile was requested, but recovery
//         of the datafile would require applying redo logs that were
//         generated before the most recent OPEN RESETLOGS.
// *Action: If a full backup or datafilecopy from the current database
//          incarnation exists, ensure that it is marked AVAILABLE, and
//          that a channel of the correct device type is allocated.  It may
//          also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY
//          or FROM TAG operands if these have been specified.
20999, 1, "internal debugging error"
