^_^小麦苗^_^

小麦苗博客,实用经典,简单易懂,接地气!---技术应用型博客,主打实用性,只讲实用的,不讲没用的,多做实验,多思考!

  • 博客访问: 5982689
  • 博文数量: 949
  • 用 户 组: 普通用户
  • 注册时间: 2012-09-23 17:46
  • 认证徽章:
个人简介

QQ:646634621 网名:小麦苗 blog:http://blog.itpub.net/26736162/abstract/1/ 微信公众号:xiaomaimiaolhr QQ群:618766405 微信群:私聊 DBA宝典号内搜:http://data.newrank.cn/m/s.html?s=OSsuPjE4LDI7 《Oracle笔试面试宝典》作者

ITPUB论坛APP

ITPUB论坛APP



APP发帖 享双倍积分

文章分类

全部博文(949)

文章存档

2017年(395)

2016年(313)

2015年(168)

2014年(73)

微信关注

IT168企业级官微



微信号:IT168qiye



系统架构师大会



微信号:SACC2013

订阅
热词专题

分类: Oracle


【OERR】 oerr ora 错误 11.2.0.3【00000-19999】





# 11.2.0.3 by lhr
/ $Header: rdbms/mesg/error.txt /st_rdbms_11.2.0/1 2010/11/07 22:24:04 kquinn Exp $ error.msg

/ Copyright (c) 1987, 2000 by the Oracle Corporation. All rights reserved.
/
/
/
/ File:     RDBMS:[UTL]error.msg
/ Created:  10/17/86
/
/          -=(  COMPLY WITH STANDARDS WHEN CHANGING MESSAGES  )=-
/
/  Email SDRESKIN your changes and he will verify compliance with standards.
/
/          -=(  COMPLY WITH STANDARDS WHEN CHANGING MESSAGES  )=-
/
/ Message Standards    
/ =================
/ Author  Brian Quigley
/ Written 07/28/92

/ Purpose
/ -------
/   When a message is generated, you are speaking directly to the user.  Often,
/ the quality of your software is judged by the ease with which a user can fix
/ problems.  Your purpose is to make it as easy as possible to use Oracle
/ products. 

/   Note that the "Cause:" and "Action:" sections for a message will also be 
/ seen by the user.  Thus, it is important to keep these sections simple, yet
/ as helpful as possible. 

/   Whenever possible, include all relevant information within the message.

/   Your purpose is to make a message as informative as possible.

/ Size Of Message
/ ---------------
/   Message text should be limited to a maximum of 76 characters. Messages
/ containing embedded % directives should not overrun the 76 character limit
/ unless they signal unusual errors which do not occur as part of user
/ applications.  For example, startup errors and system-dependent errors can
/ probably may have longer message text. 
/

/ Simple Language
/ ---------------
/   Avoid cryptic messages and overly technical language.

/     NOT GOOD: index key does not exist root dba %s, dba %s (%s)
/     BETTER  : index key does not exist for row: %s, %s, %s


/ Lowercase vs. Uppercase
/ -----------------------
/   Use uppercase for commands and keywords.

/     NOT GOOD: alter cluster statement no longer supported
/     BETTER  : ALTER CLUSTER statement no longer supported


/   Use lowercase in the message wording, including the first letter.

/     NOT GOOD: Invalid syntax
/     BETTER  : invalid syntax


/ Commands, Keywords, Parameters Values
/ -------------------------------------
/   Whenever possible, give the command, keyword, and parameter values that the
/ user used. 

/   Use uppercase to indicate commands and keywords.

/     NOT GOOD: missing IDENTIFIED keyword
/     BETTER  : GRANT CONNECT statement requires the IDENTIFIED keyword

/     NOT GOOD: MAXVALUE is less than current value
/     BETTER  : ALTER SEQUENCE MAXVALUE %s is less than current MAXVALUE %s


/ Period
/ ------
/   Do not end a message with a period.


/ Numbers
/ -------
/   Do not enclose numbers with special characters.

/     NOT GOOD: number of control files (%s) does not equal %s
/     BETTER  : specified %s control files while other instances have %s

/   Spell out the word "number" to ensure the message is understood.

/     NOT GOOD: change %s for thread (%s) is in sequence #%s
/     BETTER  : the change number %s for thread %s is in sequence number %s


/ Numbers - User Input
/ --------------------
/   Do not enclose user-input numbers with special characters.

/     NOT GOOD: file size (%s) exceeds maximum of %s blocks
/     BETTER  : a file size of %s would exceed the allowed maximum of %s blocks


/ Quotes
/ ------
/   Do not use single or double quotes to highlight a text variable or command.

/     NOT GOOD: 'row_locking = always' requires transaction processing 
/     BETTER  : ROW_LOCKING = ALWAYS requires transaction processing 


/ Single Quotes
/ -------------
/   Never use single quotes.


/ Double Quotes
/ -------------
/   ALWAYS and ONLY use double quotes to identify database objects.

/     NOT GOOD: file %s: bad block size "% bytes" expecting "%s"
/     BETTER  : expected block size of %s bytes in file "%s" but found %s

/     NOT GOOD: duplicate column %s
/     BETTER  : duplicate column "%s" specified for table "%s", schema "%s"


/ Ellipses
/ --------
/   Never use ellipses.

/     NOT GOOD: datatype {%s} for column %s, table %s.%s is not supported
/     BETTER  : datatype %s not support for column "%s" table "%s" schema "%s"


/ Parentheses
/ -----------
/   ALWAYS and ONLY use parentheses for identifying constraint names.

/     NOT GOOD: unique constraint %s.%s violated
/     BETTER  : unique constraint (%s.%s) violated

/     NOT GOOD: invalid file size (%s)
/     BETTER  : size of %s bytes is invalid for file "%s"


/ Brackets
/ --------
/   ALWAYS and ONLY use brackets for identifying program argument values.

/     NOT GOOD: Internal Error: %s,%s,%s,%s,%s,%s,%s
/     BETTER  : internal error, arguments: [%s],[%s],[%s],[%s],[%s],[%s]


/ Grammar
/ ------
/    Use complete sentences whenever possible (but no period at end of
/ sentence).

/    Use not use multiple sentences in a message, i.e. one sentence only.

/    Use the active voice.

/    Do not use an antagonistic tone.

/    Use correct punctuation whenever possible.


/ Recommended Style
/ ---------------------
/   Try to make positive recommendations or suggestions as part of the message.

/   Explain what is invalid AND what is valid.

/     NOT GOOD: invalid file size (%s)
/     BETTER  : file size of %s is invalid
/     BEST    : file size of %s bytes is outside valid range %s to %s bytes

/     NOT GOOD: duplicate column %s
/     GOOD    : duplicate column "%s" in %s
/     BEST    : duplicate column "%s" in %s "%s"
/                                        ^    ^
/                        this variable ...    ... this variable
/                   indicates the TYPE            indicates the NAME
/                   of database object            of the object


/   Thus, substituting ... 'colin', 'view'

/        in:    duplicate column "%s" in %s
/     gives:    duplicate column "colin" in view


/   And, substituting ... 'ugotit', 'primary, foreign or index key'

/        in:    duplicate column "%s" in %s
/     gives:    duplicate column "ugotit" in primary, foreign or index key

/   And, substituting ... 'pedestal', 'table', 'entablature'

/        in:    duplicate column "%s" in %s "%s"
/     gives:    duplicate column "pedestal" in table "entablature"

/   And substituting ... 'wat', 'dee', 'dikins'

/        in:    illegal constraint (%s.%s) for schema "%s"
/     gives:    illegal constraint (wat.dee) for schema "dikins"


/ Text Variables
/ --------------
/   Do not place text variables at the beginning of messages, as this does not 
/ allow correct alphabetical sorting of the messages.  The alphabetical listing
/ at the back of the Messages Manual is a necessary tool for Customer Support.

/     NOT GOOD: %s not found
/     BETTER  : object %s not found
/     BEST    : object %s not found in schema %s


/ Internal Errors & Routine Names
/ -------------------------------
/   Use ORA-00600 messages for internal messages not to be seen by the user.

/   Do not use routine names in messages.

/     NOT GOOD: ORA-03116, ttcxxx: invalid buffer length
/     BETTER  : ORA-00600, internal error, arguments: [ttcxxx], [], [], [], []


/ Public vs. Non Public Messages 
/ ------------------------------
/   Use ORA-00600 messages for internal messages not to be seen by the user.

/   For messages which are for internal use only, indicate this in ERROR.MSG
/ message listing or at beginning of the range of this type of message in the
/ file. Debug event codes, CORE messages, are examples. 

/   Use "// *Document: NO" as follows:

/   e.g. 
/       10049, 00000, "protect library cache memory heaps"
/       // *Document: NO
/       // *Cause: 
/       // *Action: Use the OS memory protection (if available) to protect
/       //          library cache memory heaps that are pinned.


/ Programmer's Comments
/ ---------------------
/   If you wish to add comments regarding a message that should not be seen by
/ the public, use "// *Comment: " as follows:

/   e.g. 
/       32769, 00000, "incompatible SQL*Net version"
/       // *Cause: An attempt was made to use an older version of SQL*Net that
/       //         is incompatible with current version of ORACLE.
/       // *Action: Use a newer version of SQL*Net.
/       // *Comment: Can only happen if user tried to use an illegal copy of a 
/       //           pre-lease version of SQL*Net.


/ ORACLE vs. Oracle
/ -----------------
/    The word ORACLE in uppercase refers to the ORACLE server. Use the term
/ "ORACLE server" when referring to the server. 

/    The word Oracle in lowercase with capitalized first letter refers to the
/ company. Use "Oracle Corp." when referring to the company.


/------------------------------------------------------------------------------
/
/ MODIFIED
/    kquinn     07/05/10 - 9287616: add event 10253
/    kquinn     11/02/10 - Backport kquinn_bug-9287616 from main
/    wbattist   01/11/10 - bug 9275168 - modify message text for ORA-32701 to
/                          make it clearer
/    kquinn     02/13/09 - 5687266: ensure ora-1722 is documented
/    ccaominh   12/12/08 - Bug 7020906: Add event 10481
/    tbhukya    12/12/08 - 7627130: Add 39250 err msg to e38001.msg 
/    kquinn     09/03/08 - 7359014: add 12999 error message
/    ineall     08/28/08 - 7234592: Add 16439
/    ashrives   04/18/08 - 6820451 Add 27129->27135 to e24280.msg
/    swolicki   12/31/07 - reserved range 62010-62029 for DUMA Kernel-Side
/    mpopeang   11/19/07 - bug5589956: add error 62001
/    arogers    10/26/07 - 6413891 Add 27079 to e24280.msg
/    chliang    04/19/07 - add 30136
/    kquinn     04/17/07 - 5523578: add event 25476
/    chliang    04/11/07 - add 41400 and 41401
/    debanerj   08/09/06 - added 3145 for Vector I/O 
/    jaskwon    05/31/06 - Reserve additional block for resource manager 
/                          errors 
/    chliang    03/29/06 - add new error 3140 and 3141 
/    kshergil   01/23/06 - 4093938: add new error 32029
/    kshergil   10/31/05 - 4658627: added error/event 43806
/    skiyer     09/20/05 - 4581483: edited error14132 to reflect temp table 
/                          usage is wrong 
/    sschodav   08/22/05 - added new error 24854 for bug 4366667 
/    wclin      09/06/05 - add event 30579 for internal Oracle Text tests 
/    kshergil   06/28/05 - 4364202: add event 10621
/    kquinn     06/14/05 - 4421376: Add event 10519 
/    jgalanes   05/17/05 - Add 44401 - 44409 events for Classic export import 
/    amysoren   04/22/05 - add error 13950 
/    kquinn     03/24/05 - 4162293: Add event 22824 
/    chliang    02/03/05 - add error 3135 and 3136
/    aramacha   02/11/05 - Fix 4046467 : Add error 25316.
/    kquinn     10/09/04 - 3830972: Add event 10854 
/    ssubrama   08/11/04 - bug 3814658 add event 10639 
/    porangas   08/03/04 - 3774546: Add error 24817
/    ssubrama   07/26/04 - bug 3747472 add event 14529 
/    chliang    06/20/04 - add error 24450
/    kshergil   04/23/04 - 3566511: add event 10629 
/    desinha    02/18/04 - 3128021: add row dep info for 14132 
/    porangas   01/22/04 - [3385076]: adding an event 10508.
/    kquinn     01/13/04 - 3296775: Added error 25011 
/    ssubrama   12/24/03 - add event 10973 for bug 2619509 
/    akatti     12/01/03 - [2934659]:add OCI event 24910 
/    kquinn     11/30/03 - 3255701: Add 24952 error 
/    chliang    08/01/03 - bug 2940345: add error 24816
/    ssappara   07/02/03 - Bug2909969:Added error 24909
/    desinha    01/10/03 - bug 2588217 add event 10506 to disable fix
/    dtahara    11/06/02 - 2607029: add event 10504 to disable fix
/    ssubrama   11/07/02 - bug 2656881 event 10970 to backout 2133357
/    vakrishn   10/15/02 - added errors 8189-8196 for flashback table project.
/    sbedarka   09/16/02 - #(2479110) handle pin deadlock error
/    kquinn     08/13/02 - 2235386: Amended 10027/10028
/    akatti     08/23/02 - [2436572]:added error 25409
/    cunnitha   05/30/02 - bug 2313473:added error 32583
/    sbedarka   05/16/02 - #(2268284) amend 12842 details
/    sbedarka   05/03/02 - #(2242434) write parse error to alert if 10035 set,
/                            10035 being reused.
/    ssubrama   04/09/02 - bug 2200057 add error 6579
/    phchang    02/11/02 - #1941831: add error 2314
/    ptearle    01/11/02 - 2098120: add event 10502 to disable fix
/    aramacha   02/13/02 - Fix for 2163927 : added error 28595.
/    ssubrama   12/15/01 - bug 1814582 add error message 22283
/    kquinn     10/04/01 - 1662642: Add event 10624
/    phchang    09/10/01 - #1914633: correct max size in error 22973
/    gviswana   05/29/01 - Add event 10513 to disable wrap source compression
/    jarnett    05/08/01 - add event 10501 for periodic heap check.
/    ptearle    03/03/01 - 1577003: add event 10138
/    allee      01/26/01 - bug 971108, new error message 30770, 32576
/    dgprice    01/12/01 - bug 1394096 new error message 1062
/    cunnitha   01/10/01 - #1364334:add error 1690
/    ptearle    12/27/00 - 1344111: add event 10137
/    snutakki   12/04/00 - replace event 13300 with 10337 to avoid conflicts
/    snutakki   11/30/00 - #1183055: Add new event 13300
/    sbedarka   11/15/00 - #(822764) behaviour controlled via event 10945
/    ptearle    11/16/00 - 1089848: add event 10136
/    kquinn     07/19/00 - 532570: Add 10371 event
/    etucker    06/01/00 - add messages for datetime messages
/    sbedarka   05/23/00 - #(966634) add new error 30626
/    sparrokk   02/17/00 - Add message 30563
/    wnorcott   01/18/00 - Add ORA- msgs 31401-31599 for CDC
/    prao       01/16/00 - 987371: change trigger debug event from 10250 to 10309
/    kquinn     01/14/00 - 1065010: Add event 10129, document 10122
/    kquinn     01/18/00 - 762114: Add event 10191
/    phchang    11/10/99 - Added (missing) message 27157
/    tguenssl   09/30/99 - 887509: add message 27092
/    kquinn     11/18/98 - 710922: Add error 1948
/    kquinn     01/07/99 - Add message 28604
/    kquinn     11/24/98 - 769412: Event 10119 used for QKA only
/    sbedarka   05/08/99 - #(743019) controlled by event 10154
/    sbedarka   12/03/98 - Changed 10152 to 10153 owing to conflict
/    sbedarka   11/19/98 - 737725: Add event 10152
/    kquinn     07/21/98 - 692355: Add event 10151
/    kquinn     03/18/98 - add message 7345
/    phchang    01/20/98 - Add message 25196
/    eyho       08/25/97 - add DLM debug trace event
/    jdraaije   12/19/96 - name change from callout to external proc.(again)
/    pravelin   12/12/96 - Repair damage from merge error in version 312
/    swerthei   12/09/96 - add 19659
/    cxcheng    12/05/96 - add message 22308
/    cchu       11/27/96 - Fix merge problem
/    wchang     11/22/96 - add repapi error codes and messages
/    mluong     11/21/96 - fix compilation error
/    bmichon    11/21/96 - Adding Error 29400, data cartridge error
/    fputzolu   11/20/96 - allow pkey update within same partition (14402)
/    pravelin   11/20/96 - Add 2 messages for heterogeneous (HO) connection err
/    sdange     11/20/96 - add more error messages.
/    sgollapu   11/19/96 - Add 24344
/    moshen     11/19/96 - add event 10403
/    lchidamb   11/18/96 - add display type error messages
/    jnewman    11/16/96 - Re-editing messages 02300-02350
/    jnewman    11/15/96 - Edit cause and action for 22800-22810
/    slari      11/15/96 - change wording of OER(2031)
/    jnewman    11/14/96 - Editing error messages 02300 -02350
/    jdraaije   11/13/96 - reapply name change from callouts to external proc's
/    rtaranto   11/10/96 - Add trace event 10278 (used for testing)
/    bhirano    11/10/96 - modify 4031 error message
/    rjenkins   11/08/96 - 10149: year 2000 check constraint event
/    amganesh   11/08/96 - correct action message
/    jwijaya    11/08/96 - more revision of object errors
/    vkrishna   11/07/96 - modify object error messages
/    skrishna   11/07/96 - add 21301 error
/    rgmani     11/07/96 - Add HO error message #28556
/    jbellemo   11/07/96 - DistSecDoms: add errors
/    dchatter   11/07/96 - add back 24351,24352 which somehow disappeared
/    dchatter   11/07/96 - fix error msgs for OCI to conform to standards
/    swerthei   11/07/96 - change explanation for message 19584
/    ramkrish   11/06/96 - Reserve 29400-29499 for Oracle8 Cartridges
/    ramkrish   11/06/96 - 21560: chg Cause, Action; 22285: chg Mesg
/    jsriniva   11/05/96 - iot: add alter table messages
/    slari      11/05/96 - add OER(24343)
/    aroy       11/04/96 -  add error to catch NULL LOBS
/    rherwadk   11/04/96 - add error message #96
/    bwadding   11/04/96 - Add event 12837
/    opeschan   11/04/96 - add ORA-6505
/    tanguyen   11/04/96 - add 22869, remove {2344,22862}
/    pshah      11/03/96 - Removing error #23600
/    skrishna   11/03/96 - add error 21525
/    skrishna   11/03/96 - add 22065 error
/    jwlee      11/02/96 - duplex archive log destinations
/    rmurthy    11/02/96 - add error 22992 for remote lobs
/    sjain      11/01/96 - Add new messages
/    vkrishna   11/01/96 - fixup 22812 and 22915
/    celsbern   11/01/96 - Updated #24271
/    tanguyen   11/01/96 - change text of 22867
/    vkrishna   11/01/96 - fixup 22812 and 22915
/    celsbern   10/31/96 - Fixed text for 23419
/    sgollapu   10/31/96 - Add error for invalid stmt hndl
/    rherwadk   10/31/96 - fix for error message #68
/    jnewman    10/31/96 - Change purpose of range 8500-8599
/    pshah      10/31/96 - Making #25228 and #25229 more informative
/    pshah      10/31/96 - Adding errors #6525 and #6526 back
/    jwlee      10/31/96 - remove duplicate rbr posting error
/    jwijaya    10/30/96 - review and revise object errors
/    jwlee      10/31/96 - remove duplicate rbr posting error
/    asriniva   10/30/96 - OSSTK messages
/    ranantha   10/30/96 - Change comment for event 10938
/    ranantha   10/29/96 - Add event 10938 for PL/SQL trace.
/    azhao      10/29/96 - re-add lob errors 22990 and 22991
/    swerthei   10/25/96 - add 19657
/    wuling     10/28/96 - add 29300-29321, fix 21000
/    arhee      10/28/96 - add event for IPC tracing
/    jwlee      10/25/96 - error 10199
/    tpystyne   10/25/96 - change 27001 and add 27020
/    aroy       10/25/96 - Add error no 24336
/    bhimatsi   10/24/96 - 22868-9 : lobs and drop tablespace errors
/    mluong     10/24/96 - fix compilation error
/    mluong     10/24/96 - get fix from bhirano
/    vkrishna   10/24/96 - modify 22807, nested table errors
/    twang      10/23/96 - new error for pdml global deadlock
/    mcoyle     10/23/96 - Add 12835 for OPS_ADMIN_GROUP
/    tcheng     10/22/96 - add 25008
/    jnewman    10/22/96 - cosmetic changes start 280 10/22
/    slari      10/21/96 - add OER(24337)
/    sgollapu   10/21/96 - Add Readonly Error for SvcCtx
/    mluong     10/21/96 - fix merge problem.
/    mluong     10/21/96 - fix compile error
/    jnewman    10/21/96 - cosmetic changes to errors 10/21
/    skrishna   10/21/96 - add 21602
/    slari      10/21/96 - add OER(24337)
/    jsriniva   10/19/96 - iot: alter error messages
/    bhirano    10/18/96 - add new ksm errors for large pool init.ora parameter
/    lchidamb   10/18/96 - add date, display type related errors
/    bwadding   10/18/96 - add events for kxib
/    hasun      10/17/96 - Add 12038 for snapshots
/    mluong     10/17/96 - fix compile error
/    jdraaije   10/16/96 - callouts have been renamed to external procedures
/    rhari      10/16/96 - More external procedure error messages
/    hasun      10/16/96 - Add error 12037 for snapshots
/    ramkrish   10/16/96 - Reserve 22280-22299 for LOB/FILE; Free 24280-24299
/    rpark      10/14/96 - fix error 1794 to say 32 instead of 16 max num of co
/    aroy       10/12/96 - add error messages for npilfrd/wr
/    wuling     10/11/96 - reserve 29300-29399 for dbms_pitr, change 21001
/    tcheng     10/10/96 - change message 22979
/    slari      10/09/96 - add OER(24336)
/    slari      10/09/96 - add OER(24336)
/    slari      10/09/96 - add OER(24336)
/    tsaulys    10/09/96 - add 1061
/    sgollapu   10/08/96 - Remove "in <function>" occurrences in err msgs
/    pshah      10/07/96 - Add event #10931
/    rwessman   10/07/96 - added messages for the Oracle Security Service
/    pshah      10/07/96 - Add event #10931
/    fge        10/03/96 - update message 25112
/    ldoo       10/03/96 - Add 23419
/    tanguyen   10/03/96 - incomplete and mutually referring types (err 22867)
/    jnewman    10/03/96 - cosmetic change to cause/action
/    ato        10/02/96 - relocate AQ export check errors
/    ademers    10/02/96 - add 23384-88, 26531
/    ramkrish   10/02/96 - Fix mrgerr during add_ro_bfile(09/19) xref v184/v185
/    rherwadk   10/02/96 - enhance error message ORA-4017
/    rjenkins   10/01/96 - 2k char 4k varchar2
/    ldoo       10/01/96 - Add 23418
/    jsriniva   09/30/96 - iot: add alter-related error msgs
/    ldoo       09/26/96 - Add 26563
/    arhee      09/26/96 - bug 403081
/    swerthei   09/25/96 - add 19657, 19658
/    rmurthy    09/25/96 - errors for Alter Lob
/    kosinski   09/24/96 - Merge Win32 changes into base development
/    tlee       09/24/96 - update mesg 1211 and 1592
/    fge        09/24/96 -  add 25122 for partitioned bitmap index
/    fge        09/20/96 -  25111: change message text
/    rgmani     09/20/96 - Add new HO error messages #28524 to #28530
/    varora     09/20/96 - add no map/order method error
/    jcohen     09/18/96 -  update 25113: GLOBAL not allowed for bitmap index
/    jcohen     09/18/96 -  update 25113: GLOBAL not allowed for bitmap index
/    ldoo       09/18/96 - Change mesg of 23326 and obsolete 23311
/    ramkrish   09/18/96 - reserve 22285-99 for KOLF - Generic BFILE manager
/    celsbern   09/18/96 - add messages for DBMS_HO package
/    adowning   09/17/96 -  v8 import of snapshots
/    schandra   09/16/96 - 2075: concurrent attempts to heuristically end trans
/    masubram   09/13/96 - Add 12036 for updatable snapshot log not empty
/    jarnett    09/12/96 - bug 336488 merge: errors 160-163
/    dchatter   09/12/96 - delete merge symbols
/    hasun      09/11/96 - Modify 12004 to be more specific
/    esoyleme   09/11/96 -  update 25425 and 25408
/    adowning   09/10/96 - snapshot log validation messages
/    jboonleu   09/10/96 - add koh error code
/    jnath      09/10/96 -  bug 346936: repcat error 23356
/    wbridge    09/09/96 - tablespace point in time recovery
/    aroy       09/09/96 - add messages for NCHAR support
/    jstamos    09/09/96 - fix 23346 for bug 398867
/    rmurthy    09/09/96 - modify message for error 22894
/    tcheng     09/06/96 - reuse 25007
/    asgoel     09/06/96 - Added errors for and validating replication code
/    tlee       09/04/96 - update conversion mesgs
/    khnguyen   09/04/96 - add msg 12704 for character set mismatch
/    whuang     09/03/96 - adding the event for array index insertion
/    nmichael   08/30/96 - More error messages for bulk SQL
/    rhari      08/30/96 - Add error #6524 for unsupported callout options
/    tcheng     08/28/96 - fix mesg 25007
/    surman     08/28/96 - Merge 367403 to 8.0.2: Fix 1002 mesg
/    jsriniva   08/28/96 - allow last index column in include clause for iots
/    sthakur    08/28/96 - add missing descriptor message
/    anori      08/27/96 - remove OIDGENERATORS error message
/    edarnell   08/27/96 - add collections messages
/    ato        08/27/96 - add AQ error for datatype mismatach
/    pshah      08/26/96 - Adding error messages for AQ admin interface (create
/    tcheng     08/26/96 - add 25007
/    rmurthy    08/23/96 - add error 22893-94 for scoped REFs
/    jklein     08/23/96 - bug 284399 - error codes without leading zeroes
/    jklein     08/23/96 - bug 332114 - 10200, 10203 events switched
/    jklein     08/23/96 - bug 342658 - improve cause for error 701
/    tpystyne   08/23/96 - add 238
/    ssamu      08/22/96 - add exchange error msg
/    jsriniva   08/22/96 - add 'column name expected' error msg for iots
/    swerthei   08/22/96 - add 19656
/    dchatter   08/22/96 - remove merge comments
/    rbodamer   08/21/96 - Add HO error messages
/    nmichael   08/21/96 - New error messages for dbms_sql
/    ldoo       08/21/96 - Add 23393 and 23394
/    ato        08/21/96 - add more dbms_aqadm error messages
/    akruglik   08/20/96 - add msg 14118
/    asurpur    08/19/96 - Adding new message for expiration of external accoun
/    aroy       08/19/96 - oci nchar support messages
/    heri       08/19/96 -  Add 10148 : use old random generator
/    tcheng     08/18/96 - add 25006
/    dchatter   08/16/96 - add error message - handle already initialized
/    tcheng     08/16/96 - 22906: disallow DML on THE expression
/    rxgovind   08/15/96 - add error 22930
/    sgollapu   08/14/96 - Add 24327
/    tanguyen   08/13/96 - add 22862-3
/    rjenkins   08/13/96 - add error for changing constraint
/    swerthei   08/12/96 - remove 19591
/    ssamu      08/12/96 - get rid of 14502, 14077, use 2149
/    jwijaya    08/11/96 - add objects option not installed
/    jwijaya    08/11/96 - add objects option not installed
/    swerthei   08/08/96 - add 19653
/    vkrishna   08/07/96 - add Nested Table related messages
/    akruglik   08/07/96 - add msg 14117
/    smuralid   08/06/96 - add 22802, 22803
/    rherwadk   08/06/96 -  fix message text for error# 2096
/    swerthei   08/05/96 - add 19649, 19650, 19651, 19652
/    jarnett    08/02/96 -  bug 371279 - limit maximum call depth
/    rxgovind   08/02/96 - add error 22928
/    tcheng     08/01/96 - add OBJECT keyword to WITH OID clause
/    schandra   07/30/96 - change 2020 error message
/    aborr      07/30/96 - kccmus gets error if created control mounted
/    tanguyen   07/29/96 - enhance 2344 to include create type
/    bnainani   07/29/96 - Change cause for 02226, add 10515, 23600
/    rmurthy    07/28/96 - add errors 22886 - 22892 for REFs
/    ato        07/26/96 - add 24277
/    rhari      07/25/96 - Error 6523 for max callout arguments
/    fge        07/24/96 - merge bitmap from 7.3.3 to 8 beta1
/    varora     07/24/96 - add 22885 error message
/    atsukerm   07/23/96 - add new DBMS_SPACE messages.
/    swerthei   07/23/96 - change text for 19625
/    adowning   07/19/96 - add 23392
/    vkrishna   07/19/96 - add 22909
/    akruglik   07/19/96 - error 14074 will be used only for ADD PARTITION
/    asgoel     07/17/96 - Adding two error numbers for debugging and tracing r
/    mcoyle     07/16/96 - Add 12832 for GV$ hard affinity
/    gpongrac   07/16/96 - add 295
/    tcheng     07/16/96 - add 22977,22978,22979
/    kmuthukk   07/15/96 - add v7 compat event for pl/sql fixed-char binds
/    vkrishna   07/12/96 - add error for null nested table instabce
/    tcheng     07/12/96 - add 22975, 22976
/    tcheng     07/12/96 - fix 22970
/    adowning   07/10/96 - 23389: obsolete switch_snapshot_master
/    tlahiri    07/09/96 - add 00377: too many relog ops during a direct load
/    mchien     07/09/96 - fix error msg
/    anori      07/07/96 - add alter table restriction messages for ADT columns
/    swerthei   07/01/96 - add 19638
/    slari      06/28/96 - OCI error for exec if iter = 0 and non-select
/    swerthei   06/27/96 - add 19560
/    tanguyen   06/26/96 - reuse 2344 for replacing type with OID clause
/    smuralid   06/26/96 - add 2348-2350
/    tanguyen   06/25/96 - remove 2344
/    akruglik   06/25/96 - add mesages complaining about length of partition bo
/    fputzolu   06/25/96 - add event 10124 to force creation of segmented array
/    ksriniva   06/24/96 - add error messages for sls.c
/    rwessman   06/24/96 - Updated Oracle Security Service errors.
/    jdraaije   06/20/96 - add callout agent connection errors
/    slari      06/20/96 - add oci error messages
/    ssamu      06/20/96 - add message for object in PTI
/    jboonleu   06/20/96 - update messages for KOC
/    dchatter   06/19/96 - 24325: a converted svc cannot beused in V8 calls
/    arhee      06/19/96 - change IPC error messages
/    varora     06/19/96 - add method errors
/    sthakur    06/18/96 - clean up kod and koka error messages
/    asurpur    06/18/96 - change password expired message
/    sdas       06/18/96 - iot: add iot direct-load error message
/    schandra   06/17/96 - Convert XA to use new OCI
/    tarora     06/17/96 - eliminated some unnecessary skgfr msgs, changed
/                          27053
/    aroy       06/14/96 - add error 24801
/    jsriniva   06/13/96 - add iot overflow in tablespace but not iot top index
/    akruglik   06/12/96 - fix for bugs 373151 and 373181
/    rwrivera   06/11/96 - update IPC messages
/    rherwadk   06/10/96 - OER 111: don't allow mts_servers > mts_max_servers
/    gngai      06/06/96 - Added 8178 for SET TRANSACTION
/    swerthei   06/03/96 - 294 - invalid archive format specifier
/    schandra   06/02/96 - session migration password
/    ramkrish   06/02/96 - dbms_lob: rephrase mesg with format char changes
/    skrishna   06/02/96 - add 22166 and 22167
/    rxgovind   06/02/96 - add errors for trusted 3gl cbks
/    tpystyne   06/01/96 - add events 10326 and 10327
/    tcheng     05/31/96 - add 22974, 2345
/    jwlee      05/30/96 - minimum support of Lamport SCNs
/    tcheng     05/30/96 - add 25005
/    tanguyen   05/30/96 - add 2346
/    cxcheng    05/29/96 - cleanup before beta 1 - remove 19400-19449
/    rwessman   05/29/96 - Need to add number space for Oracle Security Service
/    tarora     05/29/96 - change 27014
/    swerthei   05/28/96 - remove 19577, 19578, change 19571, 19588
/    twang      05/25/96 - error messages for lock manager process termination
/    hasun      05/24/96 - Add snapshot error message 12030
/    ldoo       05/23/96 - New repl security model
/    akruglik   05/23/96 - add message 14110
/    akruglik   05/23/96 - define event 14087; add message 14108
/    tarora     05/23/96 - improve/add SKGFQ msgs
/    skotsovo   05/23/96 - add more lob errors
/    akruglik   05/22/96 - rephrase msg 14041
/    cxcheng    05/21/96 - change error message 22314 to be more general
/    swerthei   05/21/96 - add 19637
/    tarora     05/21/96 - add message for skgfq
/    akruglik   05/21/96 - partition bound syntax changes: 
/                            reuse T_HIGH and T_VALUE messages for 
/     T_LESS and T_THAN
/    akruglik   05/21/96 - mark messages mentioning TABLE$OR$INDEX$PART$NUM not
/                          to be documented
/    bhimatsi   05/21/96 - add errors for LOB clause parsing
/    esoyleme   05/21/96 - Fill in failover errors
/    ldoo       05/20/96 - Add 26500 again
/    jgautam    05/17/96 - PDML: Add messages for PDML restrictions
/    jgautam    05/17/96 - PDML: Add messages for PDML restrictions
/    hasun      05/16/96 - Add snapshot error message for LOB filter columns
/    swerthei   05/16/96 - remove 19603
/    bhimatsi   05/15/96 - add lob segment space errors
/    rjenkins   05/15/96 - deferred unique constraints
/    dchatter   05/14/96 - adding/modifying OCI 8 messages
/    ddas       05/13/96 - enhance cost info for rowsources
/    jwijaya    05/09/96 - fix the message of 22165
/    tanguyen   05/08/96 - remove USAGE from 2305, add 2344
/    nmacnaug   05/08/96 - update gc error messages
/    abrumm     05/07/96 - error codes for index maint options
/    ramkrish   05/07/96 - Update dbms_lob errors in new range
/    jcohen     05/07/96 - QKA Disable Bitmap And-EQuals
/    hasun      05/06/96 - replmerge
/    skrishna   05/06/96 - add 22164 and 22165
/    ssamu      05/02/96 - split 2266 into drop & truncate messages
/    tarora     05/02/96 - add msgs for skgfrofl
/    ssamu      05/02/96 - split 2266 into drop & truncate messages
/    tcheng     05/01/96 - add 25004
/    cxcheng    05/01/96 - add error message 22319
/    cxcheng    04/29/96 - add message 22321
/    cxcheng    04/26/96 - add message 19491 for delete
/    tanguyen   04/23/96 - fix 2343 - add "in other schemas"
/    schandra   04/21/96 - loosely-coupled branches
/    swerthei   04/20/96 - change text for 19576
/    nlewis     04/18/96 - DistSecDoms: add msgs 28020-28024
/    wbridge    04/18/96 - keep tablespace info in controlfile
/    akruglik   04/18/96 - redefine 14084 since it is no longer meaningful
/    skrishna   04/17/96 - add error messages for collection (KOLC)
/    jwlee      04/16/96 - add events for testing tablespace-relative DBAs
/    atsukerm   04/12/96 - new error messages for DBMS_SPACE.
/    abrumm     04/11/96 - OER(2365) Direct Load State --> Index Unusable
/    tarora     04/11/96 - add to some kcc msgs
/    tarora     04/10/96 - add 27073
/    rwrivera   04/09/96 - getting IPC error messages
/    tanguyen   04/09/96 - add 2342-2343
/    wuling     04/09/96 - add message 19706, 19707
/    pravelin   04/04/96 - add Heterogeneous Option (HO) error messages
/    aborr      04/04/96 - error if use snapshot routines with backup cfile
/    swerthei   04/02/96 - change text for 19586
/    asurpur    04/02/96 - Dictionary Protection Implementation
/    aborr      03/29/96 - eliminate #01214: maxloghistory limit exceeded
/    jmuller    03/29/96 - Fix bug 343966: flag uses of types before their 
/      "        03/29/96   declarations; but allow this to be turned off for 
/      "        03/29/96   backward compatibility 
/    chong      03/26/96 - DBMS_LOB moved from 23385-23399 to 24280-24299
/    ldoo       03/25/96 - Reserve a range for replication PL/SQL packages
/    swerthei   03/25/96 - add message for recovery catalog record mismatch
/    rbodamer   03/18/96 - Create Error range for Heterogeneous Option
/    rbodamer   03/18/96 - Correct Error range for Heterogeneous Option
/    swerthei   03/14/96 - add message 19708, remove 19620
/    ldoo       03/13/96 - Reserve 26500 - 26999 for Replication
/    ldoo       03/12/96 - Add 26500
/    ldoo       03/12/96 - Reserve a range for replication
/    ato        03/11/96 - allocate sub-range for oltp features
/    swerthei   03/11/96 - more SMR messages
/    aborr      03/08/96 - dup name check on snapshot controlfile name
/    asurpur    03/08/96 - Reserving error range for security related errors
/    tanguyen   03/08/96 - fix 2305 to disallow {ALTER, DELETE}
/    aborr      03/07/96 - bug257523: warn if resetlogs will fail after inc rcv
/    rxgovind   03/06/96 - add error 22929
/    cxcheng    03/06/96 - add message for ortbeg()
/    slari      03/05/96 - add kpu error 243xxx
/    tarora     03/02/96 - add message for SKGFR
/    swerthei   03/01/96 - change message 19625
/    bhimatsi   02/29/96 - Minimum Extent clause for tablespace (25120-21)
/    aborr      02/23/96 - KCC fixed table inconsistent due to concurrent updat
/    tanguyen   02/23/96 - add 2305 for granting priv on type
/    swerthei   02/20/96 - add retryable-error semantics
/    swerthei   02/20/96 - add errors for SwitchToCopy
/    tarora     02/19/96 - add slnrm msgs
/    aborr      02/16/96 - correct controlfile resize error message (224)
/    emendez    02/15/96 - merging all branches
/    tpystyne   02/14/96 - add event 10325
/    tarora     02/14/96 - removed 213, 1586. corrected func name in skgfr msgs
/    ltan       02/08/96 - PDML:add 1687,25119 for tablespace LOGGING attribute
/    aborr      02/06/96 - reword some controlfile-related messages
/    swerthei   02/02/96 - Restore messages for SMR
/    tarora     01/31/96 - rename so->sksa. added ksfq msgs
/    swerthei   01/31/96 - more SMR messages, for milestone 4
/    aborr      01/31/96 - add error messages for V8 controlfile
/    swerthei   01/29/96 - enhance SMR messages
/    tanguyen   01/30/96 - add 2304 for OID clause in CREATE TYPE
/    ramkrish   01/25/96 - reserve 23385-23399 for dbms_lob (& file) package
/    swerthei   01/22/96 - more SMR messages
/    wuling     01/15/96 - add messages for krbi (19700-19705)
/    swerthei   01/15/96 - change SMR string length messages
/    smuralid   01/15/96 - add ORA-2341 => "non-queryable types in sql"
/    jweisz     01/05/96 - change second MODIFiED to MOD HISTORY
/    tarora     01/03/96 - added message for skgfr (27060)
/    usundara   01/02/96 - (rtaranto) merge from /main/712: Update message 4062
/    aho        12/28/95 - deferred unique constraints - index trace
/    tarora     12/27/95 - added more information for some OSD errors
/    gswart     12/26/95 - New snapshot too old error message
/    nmacnaug   12/20/95 - correct parameter name
/    sthakur    12/20/95 - add KOKA errors
/    ldoo       12/19/95 - Add trace events for internal triggers
/    jwijaya    12/19/95 - add ranges for object SQL
/    abrumm     12/15/95 - add direct load error msg
/    tcheng     12/13/95 - add mesg for constraints on row-type table
/    nmacnaug   12/12/95 - kcl parsing error
/    tarora     12/01/95 - added message for ksfq
/    tarora     11/30/95 - add messages for skgfq, skgfr osds, shrink
/                          OSD error range (27000-27299)
/    tanguyen   11/28/95 - reassign message numbers and fix msgs for TYPE DDL
/    tanguyen   11/28/95 - fix merge problem
/    tanguyen   11/28/95 - reassign message numbers and fix messages for 
/                          TYPE DDL
/    cxcheng    11/28/95 - fix merge problems
/    qtran      11/22/95 - recover modification history
/    jhyde      11/21/95 - add events 10711-10716
/    atsukerm   11/21/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm
/    tcheng     11/17/95 - add error mesg for extent view
/    rherwadk   11/17/95 - add error messages for skgm
/    bhirano    11/17/95 - add init.ora parameter errors
/    swerthei   11/16/95 - reserve 27000-27499 for V8 Unix OSDs
/    aho        11/16/95 - iot : parse errors
/    swerthei   11/15/95 - change text for 1507 and add more explanation
/    lwillis    11/14/95 - 10118 CBO enable hash costing
/    lwillis    11/09/95 - 10117 parallel cost model
/    lthieme    11/07/95 - add message text for simulated error ORA-07347
/    swerthei   11/02/95 - reserve 19500-19998 for SMR
/    msimon     11/02/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm
/    jweisz     11/01/95 - Add pls error msgs 6515,16,17 for rhari
/    akruglik   10/31/95 - add messages for index partition maintenance operati
/    wbridge    10/30/95 - flush buffer cache on redo corruption
/    qtran      10/30/95 - reserve trace events range for bitmap row sources
/    akruglik   10/30/95 - rephrase mesg 14070 to indicate that options are 
/                   allowed for partitioned indices OR with REBUILD
/    ssamu      10/27/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm
/    rjenkins   10/27/95 - deferred constraints
/    hjakobss   10/27/95 - events 10107-10116
/    rtaranto   10/26/95 - Update message 4062
/    abrumm     10/24/95 - add generic Rejected message
/    jklein     10/20/95 - bitmap dml
/    achaudhr   10/19/95 - improve diction of some error msgs
/    ssamu      10/18/95 - new error message for split/move partition
/    ssamu      10/17/95 - new analyze messages
/    fputzolu   10/17/95 - PTI: add error 14403 for partition locking
/    arhee      10/17/95 - add event 10374
/    bhimatsi   10/16/95 - bug 313376, 1557 should take argument
/    achaudhr   10/16/95 - UJV: new errors for updatable join views
/    rmirchan   10/15/95 - 12827 parallel min percent message
/    lfeng      10/14/95 - Add Spatial Data Option messages
/    aho        10/11/95 - alter index allocate extent
/    jcohen     10/10/95 - bitmap index checkin
/    abrumm     10/08/95 - direct path loader partition support
/    jbellemo   10/05/95 - add event 10145
/    wbridge    10/04/95 - do not automatically use a file name from the log
/    rhari      10/02/95 - add event 10928
/    cxcheng    09/29/95 - modify collection type messages
/    akruglik   09/28/95 - add a message to be issued if a user tries to trunca
/    msimon     09/26/95 - Add in preliminary version of kdl subsystem
/    pshah      09/25/95 - add error message #00124 for MTS 
/    smuralid   09/22/95 - add ORA-2335 through ORA-2337
/    smuralid   09/21/95 - change ORA-953 (was "invalid index name")
/    slari      09/21/95 - b301008, add OER(24307) for osetpi
/    jtellez    09/21/95 - Add multi instance index create event 10709
/    gngai      09/21/95 - Added cause and action to several msg
/    smuralid   09/20/95 - add ORA-2327 through ORA-2334
/    jboonleu   09/20/95 - update error message file with ORI errors
/    hbergh     09/18/95 - bug 274084: error when system rollback seg specifie
/    tanguyen   09/15/95 - add 21602: dropping type with dependency
/    boki       09/13/95 - fix error messages 23430 - 23434
/    scorcora   09/12/95 - Bug #197210, OER(100) to 123, 100 for ansi not found
/    pshah      09/12/95 - add error range for Advanced Queueing (25200-25699)
/    hasun      09/12/95 - Modify message #23375
/    hasun      09/08/95 - Modify Cause and Action of 23309
/    akruglik   09/07/95 - messages for CREATE INDEX processing
/    lwillis    09/01/95 - Add 10076 enable cp join costing
/    jbellemo   08/31/95 - merge changes from branch 1.564.720.43
/    gdoherty   08/31/95 - mergetrans fix_pti_merge_bugs
/    schandra   08/30/95 - modify error message for ORA-03296
/    akruglik   08/29/95 - add msg 14071
/    akruglik   08/29/95 - add msg 14070
/    lthieme    08/23/95 - resolve standby database inspection issues
/    aborr      08/23/95 - bug 298769: stop kcvirv loop when kcvucp gets IO er
/    ssamu      08/22/95 - add new analyze errors
/    ksriniva   08/17/95 - add UNIX message 7444 for oradbx
/    ssamu      08/14/95 - change text for message
/    dsdaniel   08/11/95 - merge PTI with Objects
/    dsdaniel   08/11/95 - reserve range 14000 to 14999 for PTI
/    ksriniva   08/04/95 - add errors for invalid heap dumps
/    schatter   08/03/95 - add event 10375
/    hasun      08/03/95 - Modify replication error 23381
/    jbellemo   08/02/95 - fix up Cause phrasing
/    mramache   08/01/95 - clarify error 4097
/    jbellemo   08/01/95 - TRUSTSP: add 12436 and replace 991, 12432
/                          (support for psdswc, PL/SQL switches).  Add events
/                          10925, 10926, 10927 for pl/sql switches to control
/                          behavior-change bugfixes 237911, 190119 and 235190.
/    akruglik   08/01/95 - merge changes from ak_BIG_PTI 1.0 NDE view
/    ssamu      07/28/95 - add new message
/    akruglik   07/27/95 - define msgs 13011-13013, 13016
/    hjakobss   07/26/95 - event 10106
/    ssamu      07/24/95 - new messages for analyze
/    ssamu      07/24/95 - add messages for partitioned table analyze
/    emendez    07/23/95 - cheking RCS rev to stabilize 7-7
/    hjakobss   07/20/95 - event 10105
/    skaluska   07/18/95 - PTI: add error message for no such partition
/    mramache   07/18/95 - modify meaning of error 4097
/    boki       07/13/95 - fix message for 23377
/    bhimatsi   07/11/95 - merge changes from branch 1.564.720.42
/    jleo       07/07/95 - add event 10104 to dump statistics for hash join
/    arhee      07/05/95 - new events for ksim testing
/    rhari      07/03/95 - Reserve 13000 - 13199 for Oracle7 MultiDimension
/    tcheng     06/30/95 - merge with k7030101
/    boki       06/28/95 - modify for offline instantiation
/    ajasuja    06/28/95 - change message 6575
/    akruglik   06/26/95 - merge changes to support CREATE/DROP/ALTER partition
/    amozes     06/22/95 - add event for table queue statistics
/    akruglik   06/21/95 - remove definitions of messages used for reporting in
/    tcheng     06/16/95 - merge o8 changes; add to SCCS
/    usundara   05/31/95 - [merge changes from revision 1.564.720.44] 
/                          reserve event space 10925 through 10974 for PL/SQL
/    hasun      05/30/95 - Add error for invalid connection qualifier
/    jbellemo   05/12/95 - #221259: remove 1415
/                          add event 10069
/    aho        05/12/95 - even more errors for recreate index
/    hjakobss   05/11/95 - event 10103
/    fputzolu   05/10/95 - PTI: reserve range 13400-13500, add 13400,1,2, chang
/    lthieme    05/09/95 - fix #278985 do not allow mnt with no lock mgr.
/    rxgovind   05/05/95 - change error 6514
/    nmichael   05/04/95 - Event 10277 - New event for sharing cursors
/    svenkate   05/03/95 - events for direct read
/    slari      05/03/95 - change ORA-02391
/    boki       05/03/95 - bug 279979 -- add new error msg
/    akruglik   05/03/95 - ALTER TABLE errors
/    thayes     05/02/95 - Add event to allow PERSISTENT DLM ops
/    lthieme    05/02/95 - fix #151892 check control file size on open
/    kosinski   05/02/95 - Merge from 0.1 BIG snapshot
/    aho        05/02/95 - more errors for recreate index
/    dchatter   05/01/95 - reword message 3127 and add new message 3131
/    rxgovind   04/17/95 - add error 6514
/    jwlee      04/17/95 - rewrite 1241 slightly
/    thayes     04/14/95 - Add releasable lock DLM error
/    hbergh     04/14/95 - add new cause/action to 1545
/    jwlee      04/10/95 - add external cache error 1241
/    gdoherty   04/10/95 - set transaction isolation level
/    lthieme    04/06/95 - fix inconsistant spelling errors
/    lthieme    04/06/95 - fix consistant spelling errors
/    cozbutun   04/04/95 - add 6580
/    nmichael   04/02/95 - merge changes from branch 1.564.720.39
/    dchatter   03/28/95 - new messages for piecewise
/    bhimatsi   03/27/95 - merge changes from branch 1.564.720.35
/    jtellez    03/22/95 - 962 - New errors for skxf
/    jklein     03/22/95 - remove error 2474
/    hasun      03/20/95 - Fix checkin errors
/    slari      03/16/95 - add thread safety changes
/    drady      03/10/95 - Oracle TRACE changes
/    aho        03/10/95 - fix ci - merge screwup
/    hjakobss   03/09/95 - event 10102
/    rlim       03/08/95 - rewrite error 4043
/    dchatter   03/06/95 - merge changes from branch 1.564.720.36
/    lchidamb   03/05/95 - add error code 24303
/    nmichael   03/04/95 - Bug 265643 - Error for binds in trigger when clause
/    gngai      03/03/95 - Added errors esfor ALTER SYSTEM DUMP UNDO
/    wbridge    03/01/95 - external cache
/    rlim       02/28/95 - rewrite error 4043
/    jklein     02/27/95 - event for skip corrupted index
/    mramache   02/22/95 - stored triggers
/    jcohen     02/16/95 - events 10804 and 10805 for ksxb and rso
/    atsukerm   02/16/95 - Sort Segment implementation
/    ksriniva   02/14/95 - document range for generic debugger
/    jklein     02/14/95 - unlimited extents
/    jwlee      02/13/95 - merge changes from branch 1.564.720.33
/    dchatter   02/13/95 - add new messages for upilog
/    hjakobss   02/10/95 - events 10092 and 10093
/    arhee      02/09/95 - merge changes from branch 1.564.720.10
/    pgreenwa   02/07/95 - add debugging event for ksi.c
/    lthieme    02/07/95 - merge changes from branch 1.564.720.34
/    wbridge    02/06/95 - standby database errors
/    lthieme    02/06/95 - issue 2495 error only for read-only tablespaces
/    jwlee      02/06/95 - error codes for resilvering testing OSDs
/    boki       02/06/95 - add error codes for table comparison feature in 7.3
/    rhari      02/05/95 - merge changes from branch 1.564.720.32
/                          error messages for utl_pg
/    jwlee      02/03/95 - Add error codes for resizable data files
/    rhari      02/02/95 - merge changes from branch 1.479.710.81
/    lthieme    02/02/95 - merge changes from branch 1.564.720.31
/    lthieme    02/02/95 - fix #260249, hold ts$ and file$ enques on resize
/    hjakobss   02/01/95 - events 10089 and 10091
/    lchidamb   01/31/95 - reserve range for UPI/OCI calls: 24300 - 24499
/    tanguyen   01/30/95 - add 2304 for OID clause in CREATE TYPE
/    hasun      01/25/95 - Modify and add errors for Rep3 - Object Groups
/    wbridge    01/23/95 - do not allow log switch in backup controlfile
/    usundara   01/19/95 - bugfix 255455 - merge from rev 1.564.720.28
/                          fix plsql error handling - new errors 6540 - 6549
/    hjakobss   01/17/95 - event 10088
/    atsukerm   01/10/95 - DEALLOCATE UNUSED space feature
/    adowning   01/10/95 - fix typos
/    wbridge    01/04/95 - add support for resilvering of OS mirrors
/    hjakobss   01/03/95 - event 10086
/    dsdaniel   12/23/94 - merge changes from branch 1.564.720.6&8&16&18&24
/    jstamos    12/21/94 - add repcat errors (1.564.720.7&20)
/    bquigley   12/21/94 - ora-1034 add cause/action
/    lchidamb   12/14/94 - merge changes from branch 1.564.720.5
/    ksriniva   12/14/94 - merge changes from branch 1.564.720.22
/    msimon     12/13/94 - merge changes from branch 1.564.720.23
/    msimon     12/12/94 - merge changes from branch 1.479.710.82
/    msimon     12/12/94 - Fixes for bug 249693 - Add event 10320
/    ksriniva   12/12/94 - add ORA-17, ORA-7445, and 10077
/    dsdaniel   12/12/94 - merge changes from branch 1.479.710.76&77&78&80
/    thayes     12/08/94 - Fix name of parameter in msg 406
/    boki       12/01/94 - adding new error numbers for schema offline instant
/    boki       12/01/94 - adding new error numbers and msgs for schema offlin
/    aho        12/01/94 - rci trace event 10610, 2095
/    jstamos    11/30/94 - merge changes from branch 1.479.710.79
/    jstamos    11/30/94 - add periods and capitalization: 23306 - 23320
/    jbellemo   11/30/94 - merge changes from branch 1.564.720.19
/    hasun      11/29/94 - Change cause/action statements for (2094,23364)
/    ksriniva   11/23/94 - change 10090 to 10095
/    jbellemo   11/23/94 - remove 1966
/    jbellemo   11/22/94 - fix up 12495, again
/    hasun      11/22/94 - Add messages for Replication factoring (23364,2094)
/    dsdaniel   11/18/94 - execution of deferred RPC disabled
/    dsdaniel   11/17/94 - merge changes from branch 1.479.710.74
/    jstamos    11/16/94 - merge changes from branch 1.479.710.75
/    jstamos    11/16/94 - add 23353 for repcat
/    dsdaniel   11/15/94 - 23352 - deferred rpc error message
/    thayes     11/14/94 - Change reference to compatible parameter
/    ksriniva   11/14/94 - add error codes for generic oradbx
/    jbellemo   11/14/94 - remove 1948
/    dchatter   11/14/94 - merge changes from branch 1.564.720.9
/    dchatter   11/14/94 - merge changes from branch 1.564.720.14
/    rhari      11/13/94 - merge changes from branch 1.564.720.11
/    jstamos    11/11/94 - merge changes from branch 1.479.710.72
/    rtaranto   11/10/94 - merge changes from branch 1.564.720.15
/    rtaranto   11/10/94 - merge changes from branch 1.479.710.73
/    rtaranto   11/10/94 - Update Cause and Action comments for event 04097
/    dchatter   11/09/94 - merge changes from branch 1.479.710.70
/    rtaranto   11/02/94 - merge changes from branch 1.564.720.12
/    jbellemo   11/02/94 - merge changes from branch 1.564.720.13
/    jbellemo   11/02/94 - merge changes from branch 1.479.710.64
/    rtaranto   10/31/94 - merge changes from branch 1.479.710.71
/    dsdaniel   10/27/94 - new replication messages
/    rhari      10/25/94 - merge changes from branch 1.479.710.63
/    arhee      10/20/94 - merge changes from branch 1.479.710.69
/    rtaranto   10/19/94 - Add event 04097
/    hjakobss   10/16/94 - event 10078
/    dchatter   10/14/94 - messages of 3125, 3126, 3127 backported from 7.2
/    dchatter   10/14/94 - change 3124 to an internal error and add 3128
/    jstamos    10/13/94 - merge changes from branch 1.479.710.58
/    dsdaniel   10/13/94 - add 1085
/    adowning   10/13/94 - merge changes from branch 1.479.710.65
/    lchidamb   10/12/94 - add 1084: invalid parameter to oci call.
/    hjakobss   10/10/94 - event 10077
/    rjenkins   10/06/94 - obsoleting 2255
/    msimon     10/05/94 - merge changes from branch 1.564.720.1  (bug 209788)
/    lchidamb   10/05/94 - changed error #3112
/    hjakobss   10/05/94 - event 10076
/    rjenkins   10/04/94 - merge changes from branch 1.564.720.2
/    arhee      10/04/94 - add event 10377
/    rjenkins   10/03/94 - merge changes from branch 1.479.710.60
/    jstamos    09/30/94 - reserve error numbers already in use
/                          for refresh groups, snapshots, and job queues
/    jbellemo   09/30/94 - fix up 12495
/    rhari      09/29/94 - some more messgaes for UTL_RAW and UTL_PG
/                          (now complete 08401 - 08499)
/    jbellemo   09/28/94 - add 12495
/    hjakobss   09/28/94 - event 10076
/    adowning   09/28/94 - add replication PL/SQL errors
/    rhari      09/27/94 - UTL_RAW & UTL_PG (8401 -- 8443)
/    msimon     09/27/94 - Sequence numbers rewrite (bug 239487)
/    msimon     09/26/94 - merge changes from branch 1.479.710.59 (bug 209788)
/    jbellemo   09/23/94 - add event 10090
/    agupta     09/15/94 - 231813 - add message for creating segment
/    rjenkins   09/09/94 - removing 2255
/    msimon     09/07/94 - Changes for bug 209788
/    jstamos    09/02/94 - externalize 23306 - 23320 for replication
/    ksriniva   08/31/94 - add WMON termination error message
/    atsukerm   08/31/94 - merge changes from branch 1.479.710.57
/    abrumm     08/22/94 - Change 1854 due to max Julian date increase by CORE
/    atsukerm   08/18/94 - new space management events
/    hjakobss   08/15/94 - event 10075
/    cozbutun   08/15/94 - change a few comments
/    gpongrac   08/10/94 - merge changes from branch 1.479.710.55
/    bhirano    08/10/94 - merge changes from branch 1.479.710.56
/    dleary     08/05/94 - add 1781-1784 for UNRECOVERABLE
/    bhirano    08/05/94 - add (unix-specific) core file size events
/    gpongrac   08/01/94 - revise message for 292 and 293
/    dsdaniel   07/28/94 - 1085 preceding error in deferred rpc
/    lthieme    07/27/94 - resolve inspection issues for resizeable datafiles
/    alingelb   07/25/94 - fix 1163
/    dsdaniel   07/21/94 - merge changes from branch 1.479.710.53
/    dsdaniel   07/21/94 - deferred rpc export error 23327
/    svenkate   07/19/94 - changes to err msg 1163
/    dsdaniel   07/11/94 - merge changes from branch 1.479.710.51
/    dsdaniel   07/11/94 - error number conflict with 7.2
/    dsdaniel   07/11/94 - dbms_sys_error upgrade
/    wbridge    07/08/94 - bug 150326: typo in error 66
/    ksriniva   07/08/94 - add trace event for kst
/    gpongrac   07/08/94 - parallel recovery factoring
/    gpongrac   07/08/94 - merge changes from branch 1.479.710.50
/    svenkate   07/07/94 - bug 210900 : changes to err msg 1163
/    ksriniva   07/07/94 - merge changes from branch 1.479.710.49
/    dchatter   07/07/94 - added error msg for Ref Cursor and Non-blocking OCI
/    ksriniva   07/06/94 - add events for latch recovery
/    hrizvi     07/06/94 - add 1657, 10510, 10511, 10512, fix 1545, 1625
/    atsukerm   07/06/94 - DBMS_SPACE errors revisited
/    pgreenwa   07/05/94 - trace event: write timing stats on OPS reco scan
/    wbridge    06/29/94 - #198847: report 1031 rather than 251
/    cbarclay   06/29/94 - add 6504 - Result Sets type mismatch
/    rjenkins   06/27/94 - 193637: reorg constraint creation
/    wbridge    06/24/94 - bug 182267 - fix some causes
/    pritto     06/22/94 - bug 221252 - add TABLESPACE to cause for 1771
/    ajasuja    06/21/94 - dbms_pipe error messages
/    nmichael   06/20/94 - Hash expressions for clusters
/    wbridge    06/16/94 - specify file number for forced checksum error
/    jloaiza    06/16/94 - add disable dml locks
/    jloaiza    06/16/94 - add compatibility for disable table lock
/    aho        06/15/94 - SYS isn't allowed to create indexes with nfb (2001)
/    jloaiza    06/14/94 - add disable dml_locks
/    lthieme    06/03/94 - Resizeable Datafiles Feature
/    jklein     05/24/94 - fix spelling error for message 6556
/    ksriniva   05/16/94 - merge changes from branch 1.479.710.47
/    ksudarsh   05/06/94 - relocate error msg
/    wbridge    04/25/94 - checksum error events
/    ksudarsh   04/21/94 - parallel query option check
/    ksriniva   04/19/94 - enhance ORA-4031 and ORA-443
/    wmaimone   04/08/94 - merge changes from branch 1.479.710.45
/    rlim       04/07/94 - merge changes from branch 1.479.710.44
/    dsdaniel   04/07/94 - merge changes from branch 1.479.710.34
/    abhide     04/07/94 - merge changes from branch 1.479.710.36
/                          (merge SQL*NET error codes)
/    jtellez    04/06/94 - add io tracing event 10705
/    ltung      04/05/94 - merge changes from branch 1.479.710.41
/    wbridge    04/04/94 - allow end hot backup after crash
/    ajasuja    04/04/94 - merge changes from branch 1.479.710.32
/    wmaimone   03/31/94 - cause/action for 1010
/    thayes     03/22/94 - merge changes from branch 1.479.710.38
/    rlim       03/21/94 - #206483 - reuse 1037 for maximum cursor memory
/                          exceeded
/    ltung      03/21/94 - add 12800, 12826 for parallel query execution
/    dpawson    03/21/94 - merge changes from branch 1.479.710.42
/    pgreenwa   03/14/94 - merge changes from branch 1.479.710.39
/    ltung      03/10/94 - events 10378, 10379
/    dpawson    03/10/94 - Merge in nCube error msgs
/                          Merge in correct Unix messages instead of obsolete
/                          Unix trusted messages
/    pgreenwa   03/08/94 - add trace event for ksq
/    hrizvi     03/08/94 - add smon events 10510, 10511
/    dpawson    03/04/94 - merge changes from branch 1.479.710.29
/    thayes     03/03/94 - Error for simulating block recovery
/    ltung      03/02/94 - merge changes from branch 1.479.710.37
/    dpawson    03/02/94 - Reserve numbers for resizable data files
/    aho        03/02/94 - add max key length to oer(1450) (bg 198813)
/    ltung      03/01/94 - parallel clause syntax errors
/    hjakobss   02/28/94 - merge changes from branch 1.479.710.20
/    jwijaya    02/23/94 - merge changes from branch 1.479.710.35
/    dpawson    02/08/94 - Reserve a range for DRS6000
/    jwijaya    02/03/94 - remove 2300-2350 old odb messages
/    dsdaniel   02/02/94 - kkxp.c code change
/    ksriniva   01/27/94 - sigh... really fix ORA-30 message for bquigley
/    ksriniva   01/27/94 - merge changes from branch 1.479.710.33
/    ajasuja    01/26/94 - remove OER-4040
/    ksriniva   01/25/94 - merge changes from branch 1.479.710.30
/    dsdaniel   01/21/94 - merge changes from branch 1.479.710.31
/    wbridge    01/20/94 - add ALTER DATABASE CLEAR LOGFILE command
/    jbellemo   01/20/94 - merge changes from branch 1.479.710.26
/    dsdaniel   01/20/94 - reassign dbms_sys_error range
/    rjenkins   01/19/94 - merge changes from branch 1.479.710.19
/    ksriniva   01/19/94 - fix Cause part of ORA-30
/    dpawson    01/19/94 - reserve osd message range
/    dsdaniel   01/18/94 - merge changes from branch 1.479.710.9&21
/    jbellemo   01/17/94 - add event 10063
/    ksriniva   01/11/94 - merge changes from branches 1.479.710.{11,15}
/    ltung      01/10/94 - 10380 - 10382, 12818 - 12820
/    jbellemo   01/07/94 - add event 10062
/    cozbutun   01/06/94 - merge changes from branch 1.479.710.24
/    cozbutun   01/05/94 - modify 4091 to say trigger or function
/    hrizvi     01/03/94 - bug 189557 - fix explanation of 1599
/    dleary     01/03/94 - make event 10383 level a bitfield
/    gpongrac   12/30/93 - change comments for 12812 and 12813
/    dsdaniel   12/27/93 - obsolete ICD error
/    sjain      12/21/93 - merge changes from branch 1.479.710.17
/    jbellemo   12/21/93 - merge changes from branch 1.479.710.18
/    jbellemo   12/21/93 - merge changes from branch 1.479.710.14
/    hjakobss   12/21/93 - trace event 10060
/    dpawson    12/21/93 - merge changes from branch 1.479.710.7
/    rjenkins   12/20/93 - creating job queue
/    jbellemo   12/17/93 - #191402: remove 1930
/    sjain      12/16/93 - add new error message for ora-6400
/    dleary     12/16/93 - add event 10383
/    ksriniva   12/10/93 - add trace event for latch operations
/    jbellemo   12/08/93 - #190089: add new message 1742 for unterminated comm
/    jwijaya    12/07/93 - add error ranges for OI/KO/KG
/    wbridge    11/23/93 - log block checksum
/    pritto     11/10/93 - merge changes from branch 1.479.710.12
/    hkodaval   11/05/93 - merge changes from branch 1.479.710.4
/    pritto     11/04/93 - merge in SQL*Net 2.1.2 error messages
/    pritto     11/02/93 - add 122
/    ltung      11/02/93 - fix parallel query messages
/    ksriniva   11/02/93 - merge changes from branch 1.417.312.18
/    dsdaniel   10/30/93 - dbms_sys_error error range
/    rjenkins   10/28/93 - adding an error message
/    ksriniva   10/22/93 - fix action part for ora-4031
/    dleary     10/20/93 - event 10384
/    dleary     10/18/93 - event 10385
/    hkodaval   10/14/93 - bug 174446: add new error about read-only tablespac
/    aho        10/13/93 - merge changes from branch 1.479.710.3
/    aho        10/13/93 - add 10606 - debug trace kkri (93.10.13)
/    aho        10/13/93 - add 10605 - debug trace kkri
/    aho        10/05/93 - forgot comment character
/    aho        10/05/93 - add event to test parallel create index (10605)
/                          change 1404 (bug 181123)
/    ksudarsh   10/01/93 - restore deleted messages
/    jklein     09/29/93 - reserve ksepec events for scafs
/    mmoore     09/22/93 - add error range for pga/appc gateway
/    pritto     08/23/93 - re-insert Trusted Oracle messages
/    ksudarsh   08/10/93 - parallel query option
/    cozbutun   08/09/93 - add 6575
/    aho        08/05/93 - add create index fastpath event
/    pritto     07/29/93 - merge in sql*net 2.1 error messages
/    wbridge    07/27/93 - disallow rolling upgrade between point releases
/    agupta     07/22/93 - add errors for cluster extent overflow
/    jcohen     07/20/93 - reserve events 10370-10386 for parallel SQL
/    hasun      01/25/95 - Modify and add errors for Rep3 - Object Groups
/    wbridge    01/23/95 - do not allow log switch in backup controlfile
/    usundara   01/19/95 - bugfix 255455 - merge from rev 1.564.720.28
/                          fix plsql error handling - new errors 6540 - 6549
/    hjakobss   01/17/95 - event 10088
/    atsukerm   01/10/95 - DEALLOCATE UNUSED space feature
/    adowning   01/10/95 - fix typos
/    wbridge    01/04/95 - add support for resilvering of OS mirrors
/    hjakobss   01/03/95 - event 10086
/    dsdaniel   12/23/94 - merge changes from branch 1.564.720.6&8&16&18&24
/    jstamos    12/21/94 - add repcat errors (1.564.720.7&20)
/    bquigley   12/21/94 - ora-1034 add cause/action
/    lchidamb   12/14/94 - merge changes from branch 1.564.720.5
/    ksriniva   12/14/94 - merge changes from branch 1.564.720.22
/    msimon     12/13/94 - merge changes from branch 1.564.720.23
/    msimon     12/12/94 - merge changes from branch 1.479.710.82
/    msimon     12/12/94 - Fixes for bug 249693 - Add event 10320
/    ksriniva   12/12/94 - add ORA-17, ORA-7445, and 10077
/    dsdaniel   12/12/94 - merge changes from branch 1.479.710.76&77&78&80
/    thayes     12/08/94 - Fix name of parameter in msg 406
/    boki       12/01/94 - adding new error numbers for schema offline instant
/    boki       12/01/94 - adding new error numbers and msgs for schema offlin
/    aho        12/01/94 - rci trace event 10610, 2095
/    jstamos    11/30/94 - merge changes from branch 1.479.710.79
/    jstamos    11/30/94 - add periods and capitalization: 23306 - 23320
/    jbellemo   11/30/94 - merge changes from branch 1.564.720.19
/    hasun      11/29/94 - Change cause/action statements for (2094,23364)
/    ksriniva   11/23/94 - change 10090 to 10095
/    jbellemo   11/23/94 - remove 1966
/    jbellemo   11/22/94 - fix up 12495, again
/    hasun      11/22/94 - Add messages for Replication factoring (23364,2094)
/    dsdaniel   11/18/94 - execution of deferred RPC disabled
/    dsdaniel   11/17/94 - merge changes from branch 1.479.710.74
/    jstamos    11/16/94 - merge changes from branch 1.479.710.75
/    jstamos    11/16/94 - add 23353 for repcat
/    dsdaniel   11/15/94 - 23352 - deferred rpc error message
/    thayes     11/14/94 - Change reference to compatible parameter
/    ksriniva   11/14/94 - add error codes for generic oradbx
/    jbellemo   11/14/94 - remove 1948
/    dchatter   11/14/94 - merge changes from branch 1.564.720.9
/    dchatter   11/14/94 - merge changes from branch 1.564.720.14
/    rhari      11/13/94 - merge changes from branch 1.564.720.11
/    jstamos    11/11/94 - merge changes from branch 1.479.710.72
/    rtaranto   11/10/94 - merge changes from branch 1.564.720.15
/    rtaranto   11/10/94 - merge changes from branch 1.479.710.73
/    rtaranto   11/10/94 - Update Cause and Action comments for event 04097
/    dchatter   11/09/94 - merge changes from branch 1.479.710.70
/    rtaranto   11/02/94 - merge changes from branch 1.564.720.12
/    jbellemo   11/02/94 - merge changes from branch 1.564.720.13
/    jbellemo   11/02/94 - merge changes from branch 1.479.710.64
/    rtaranto   10/31/94 - merge changes from branch 1.479.710.71
/    dsdaniel   10/27/94 - new replication messages
/    rhari      10/25/94 - merge changes from branch 1.479.710.63
/    arhee      10/20/94 - merge changes from branch 1.479.710.69
/    rtaranto   10/19/94 - Add event 04097
/    hjakobss   10/16/94 - event 10078
/    dchatter   10/14/94 - messages of 3125, 3126, 3127 backported from 7.2
/    dchatter   10/14/94 - change 3124 to an internal error and add 3128
/    jstamos    10/13/94 - merge changes from branch 1.479.710.58
/    dsdaniel   10/13/94 - add 1085
/    adowning   10/13/94 - merge changes from branch 1.479.710.65
/    lchidamb   10/12/94 - add 1084: invalid parameter to oci call.
/    hjakobss   10/10/94 - event 10077
/    rjenkins   10/06/94 - obsoleting 2255
/    msimon     10/05/94 - merge changes from branch 1.564.720.1  (bug 209788)
/    lchidamb   10/05/94 - changed error #3112
/    hjakobss   10/05/94 - event 10076
/    rjenkins   10/04/94 - merge changes from branch 1.564.720.2
/    arhee      10/04/94 - add event 10377
/    rjenkins   10/03/94 - merge changes from branch 1.479.710.60
/    jstamos    09/30/94 - reserve error numbers already in use
/                          for refresh groups, snapshots, and job queues
/    jbellemo   09/30/94 - fix up 12495
/    rhari      09/29/94 - some more messgaes for UTL_RAW and UTL_PG
/                          (now complete 08401 - 08499)
/    jbellemo   09/28/94 - add 12495
/    hjakobss   09/28/94 - event 10076
/    adowning   09/28/94 - add replication PL/SQL errors
/    rhari      09/27/94 - UTL_RAW & UTL_PG (8401 -- 8443)
/    msimon     09/27/94 - Sequence numbers rewrite (bug 239487)
/    msimon     09/26/94 - merge changes from branch 1.479.710.59 (bug 209788)
/    jbellemo   09/23/94 - add event 10090
/    agupta     09/15/94 - 231813 - add message for creating segment
/    rjenkins   09/09/94 - removing 2255
/    msimon     09/07/94 - Changes for bug 209788
/    jstamos    09/02/94 - externalize 23306 - 23320 for replication
/    ksriniva   08/31/94 - add WMON termination error message
/    atsukerm   08/31/94 - merge changes from branch 1.479.710.57
/    abrumm     08/22/94 - Change 1854 due to max Julian date increase by CORE
/    atsukerm   08/18/94 - new space management events
/    hjakobss   08/15/94 - event 10075
/    cozbutun   08/15/94 - change a few comments
/    gpongrac   08/10/94 - merge changes from branch 1.479.710.55
/    bhirano    08/10/94 - merge changes from branch 1.479.710.56
/    dleary     08/05/94 - add 1781-1784 for UNRECOVERABLE
/    bhirano    08/05/94 - add (unix-specific) core file size events
/    gpongrac   08/01/94 - revise message for 292 and 293
/    dsdaniel   07/28/94 - 1085 preceding error in deferred rpc
/    lthieme    07/27/94 - resolve inspection issues for resizeable datafiles
/    alingelb   07/25/94 - fix 1163
/    dsdaniel   07/21/94 - merge changes from branch 1.479.710.53
/    dsdaniel   07/21/94 - deferred rpc export error 23327
/    svenkate   07/19/94 - changes to err msg 1163
/    dsdaniel   07/11/94 - merge changes from branch 1.479.710.51
/    dsdaniel   07/11/94 - error number conflict with 7.2
/    dsdaniel   07/11/94 - dbms_sys_error upgrade
/    wbridge    07/08/94 - bug 150326: typo in error 66
/    ksriniva   07/08/94 - add trace event for kst
/    gpongrac   07/08/94 - parallel recovery factoring
/    gpongrac   07/08/94 - merge changes from branch 1.479.710.50
/    svenkate   07/07/94 - bug 210900 : changes to err msg 1163
/    ksriniva   07/07/94 - merge changes from branch 1.479.710.49
/    dchatter   07/07/94 - added error msg for Ref Cursor and Non-blocking OCI
/    ksriniva   07/06/94 - add events for latch recovery
/    hrizvi     07/06/94 - add 1657, 10510, 10511, 10512, fix 1545, 1625
/    atsukerm   07/06/94 - DBMS_SPACE errors revisited
/    pgreenwa   07/05/94 - trace event: write timing stats on OPS reco scan
/    wbridge    06/29/94 - #198847: report 1031 rather than 251
/    cbarclay   06/29/94 - add 6504 - Result Sets type mismatch
/    rjenkins   06/27/94 - 193637: reorg constraint creation
/    wbridge    06/24/94 - bug 182267 - fix some causes
/    pritto     06/22/94 - bug 221252 - add TABLESPACE to cause for 1771
/    ajasuja    06/21/94 - dbms_pipe error messages
/    nmichael   06/20/94 - Hash expressions for clusters
/    wbridge    06/16/94 - specify file number for forced checksum error
/    jloaiza    06/16/94 - add disable dml locks
/    jloaiza    06/16/94 - add compatibility for disable table lock
/    aho        06/15/94 - SYS isn't allowed to create indexes with nfb (2001)
/    jloaiza    06/14/94 - add disable dml_locks
/    lthieme    06/03/94 - Resizeable Datafiles Feature
/    jklein     05/24/94 - fix spelling error for message 6556
/    ksriniva   05/16/94 - merge changes from branch 1.479.710.47
/    ksudarsh   05/06/94 - relocate error msg
/    wbridge    04/25/94 - checksum error events
/    ksudarsh   04/21/94 - parallel query option check
/    ksriniva   04/19/94 - enhance ORA-4031 and ORA-443
/    wmaimone   04/08/94 - merge changes from branch 1.479.710.45
/    rlim       04/07/94 - merge changes from branch 1.479.710.44
/    dsdaniel   04/07/94 - merge changes from branch 1.479.710.34
/    abhide     04/07/94 - merge changes from branch 1.479.710.36
/                          (merge SQL*NET error codes)
/    jtellez    04/06/94 - add io tracing event 10705
/    ltung      04/05/94 - merge changes from branch 1.479.710.41
/    wbridge    04/04/94 - allow end hot backup after crash
/    ajasuja    04/04/94 - merge changes from branch 1.479.710.32
/    wmaimone   03/31/94 - cause/action for 1010
/    thayes     03/22/94 - merge changes from branch 1.479.710.38
/    rlim       03/21/94 - #206483 - reuse 1037 for maximum cursor memory
/                          exceeded
/    ltung      03/21/94 - add 12800, 12826 for parallel query execution
/    dpawson    03/21/94 - merge changes from branch 1.479.710.42
/    pgreenwa   03/14/94 - merge changes from branch 1.479.710.39
/    ltung      03/10/94 - events 10378, 10379
/    dpawson    03/10/94 - Merge in nCube error msgs
/                          Merge in correct Unix messages instead of obsolete
/                          Unix trusted messages
/    pgreenwa   03/08/94 - add trace event for ksq
/    hrizvi     03/08/94 - add smon events 10510, 10511
/    dpawson    03/04/94 - merge changes from branch 1.479.710.29
/    thayes     03/03/94 - Error for simulating block recovery
/    ltung      03/02/94 - merge changes from branch 1.479.710.37
/    dpawson    03/02/94 - Reserve numbers for resizable data files
/    aho        03/02/94 - add max key length to oer(1450) (bg 198813)
/    ltung      03/01/94 - parallel clause syntax errors
/    hjakobss   02/28/94 - merge changes from branch 1.479.710.20
/    jwijaya    02/23/94 - merge changes from branch 1.479.710.35
/    dpawson    02/08/94 - Reserve a range for DRS6000
/    jwijaya    02/03/94 - remove 2300-2350 old odb messages
/    dsdaniel   02/02/94 - kkxp.c code change
/    ksriniva   01/27/94 - sigh... really fix ORA-30 message for bquigley
/    ksriniva   01/27/94 - merge changes from branch 1.479.710.33
/    ajasuja    01/26/94 - remove OER-4040
/    ksriniva   01/25/94 - merge changes from branch 1.479.710.30
/    dsdaniel   01/21/94 - merge changes from branch 1.479.710.31
/    wbridge    01/20/94 - add ALTER DATABASE CLEAR LOGFILE command
/    jbellemo   01/20/94 - merge changes from branch 1.479.710.26
/    dsdaniel   01/20/94 - reassign dbms_sys_error range
/    rjenkins   01/19/94 - merge changes from branch 1.479.710.19
/    ksriniva   01/19/94 - fix Cause part of ORA-30
/    dpawson    01/19/94 - reserve osd message range
/    dsdaniel   01/18/94 - merge changes from branch 1.479.710.9&21
/    jbellemo   01/17/94 - add event 10063
/    ksriniva   01/11/94 - merge changes from branches 1.479.710.{11,15}
/    ltung      01/10/94 - 10380 - 10382, 12818 - 12820
/    jbellemo   01/07/94 - add event 10062
/    cozbutun   01/06/94 - merge changes from branch 1.479.710.24
/    cozbutun   01/05/94 - modify 4091 to say trigger or function
/    hrizvi     01/03/94 - bug 189557 - fix explanation of 1599
/    dleary     01/03/94 - make event 10383 level a bitfield
/    gpongrac   12/30/93 - change comments for 12812 and 12813
/    dsdaniel   12/27/93 - obsolete ICD error
/    sjain      12/21/93 - merge changes from branch 1.479.710.17
/    jbellemo   12/21/93 - merge changes from branch 1.479.710.18
/    jbellemo   12/21/93 - merge changes from branch 1.479.710.14
/    hjakobss   12/21/93 - trace event 10060
/    dpawson    12/21/93 - merge changes from branch 1.479.710.7
/    rjenkins   12/20/93 - creating job queue
/    jbellemo   12/17/93 - #191402: remove 1930
/    sjain      12/16/93 - add new error message for ora-6400
/    dleary     12/16/93 - add event 10383
/    ksriniva   12/10/93 - add trace event for latch operations
/    jbellemo   12/08/93 - #190089: add new message 1742 for unterminated comm
/    jwijaya    12/07/93 - add error ranges for OI/KO/KG
/    wbridge    11/23/93 - log block checksum
/    pritto     11/10/93 - merge changes from branch 1.479.710.12
/    hkodaval   11/05/93 - merge changes from branch 1.479.710.4
/    pritto     11/04/93 - merge in SQL*Net 2.1.2 error messages
/    pritto     11/02/93 - add 122
/    ltung      11/02/93 - fix parallel query messages
/    ksriniva   11/02/93 - merge changes from branch 1.417.312.18
/    dsdaniel   10/30/93 - dbms_sys_error error range
/    rjenkins   10/28/93 - adding an error message
/    ksriniva   10/22/93 - fix action part for ora-4031
/    dleary     10/20/93 - event 10384
/    dleary     10/18/93 - event 10385
/    hkodaval   10/14/93 - bug 174446: add new error about read-only tablespac
/    aho        10/13/93 - merge changes from branch 1.479.710.3
/    aho        10/13/93 - add 10606 - debug trace kkri (93.10.13)
/    aho        10/13/93 - add 10605 - debug trace kkri
/    aho        10/05/93 - forgot comment character
/    aho        10/05/93 - add event to test parallel create index (10605)
/                          change 1404 (bug 181123)
/    ksudarsh   10/01/93 - restore deleted messages
/    jklein     09/29/93 - reserve ksepec events for scafs
/    mmoore     09/22/93 - add error range for pga/appc gateway
/    pritto     08/23/93 - re-insert Trusted Oracle messages
/    ksudarsh   08/10/93 - parallel query option
/    cozbutun   08/09/93 - add 6575
/    aho        08/05/93 - add create index fastpath event
/    pritto     07/29/93 - merge in sql*net 2.1 error messages
/    wbridge    07/27/93 - disallow rolling upgrade between point releases
/    agupta     07/22/93 - add errors for cluster extent overflow
/    jcohen     07/20/93 - reserve events 10370-10386 for parallel SQL
/    pritto     07/16/93 - #(170429) add 121, mts_servers w/o mts_dispatchers
/    hrizvi     07/08/93 - fix wording 1593
/    mmoore     07/07/93 - #(141926) trigger description too long
/    glumpkin   07/07/93 - change 2256
/    dpawson    07/06/93 - reserve errors for icl unix
/    tsaulys    07/02/93 - #(155239) add 7641 for smscre()
/    tsaulys    07/02/93 - #(149634) add 7880 for sdopnf()
/    dpawson    07/01/93 - merge changes from branch 1.417.312.17
/    agupta     06/29/93 - add event to prevent forward coalesce
/    sjain      06/21/93 - add new messages for streaming
/    jwijaya    06/14/93 - add error
/    dpawson 06/11/93 - Changed message 445 to take seconds as an argument
/    ajasuja    06/10/93 - connect internal messages
/    achaudhr   06/10/93 - errors for updatable joins
/    cozbutun   05/28/93 - add errors for pls_in_sql purity stuff 
/    hjakobss   05/27/93 - name changes in 6562, add 6566, 6567 
/    hjakobss   05/27/93 - fix line feed error in 6562
/    ajasuja    05/26/93 - merge changes from branch 1.417.312.16
/    aho        05/18/93 - add event 10604 - trace parallel index creation 
/    ajasuja    05/14/93 - expand message 12434
/    glumpkin   05/10/93 - Merge change for ora-2243 
/    thayes     05/06/93 - Fix 2249 error message and cause/action 
/    gpongrac   05/06/93 - add block rcovery debugging event 
/    rlim       04/27/93 - change FIPS Flagging error message 97 
/    glumpkin   04/20/93 - Update description for 12008 
/    jbellemo   04/16/93 - add 1989 for invalid os roles 
/    tsaulys    04/12/93 - merge, change 7544 for #140423 to 7721
/    pritto     04/12/93 - merge changes from branch 1.417.312.12 
/    tsaulys    04/09/93 - #(157272) change 7538,7539,7540
/    tsaulys    04/09/93 - #(157272) add 7544,7556,7557,7558,7559,7861,7862
/    rlim       04/08/93 - add flagger msg 97 
/    ltung      04/07/93 - add 10387-89, 12815 (cache partitions > 1)
/    hkodaval   04/07/93 - Bug 26632: give obj and tablespace names for error 
/                          add 1650, 1651, 1652, 1653, 1654 and remove 1547
/    rlim       04/06/93 - add msg 960 & 962 
/    ghallmar   04/06/93 - change text for 2064 
/    mmoore     04/01/93 - #(156181) fix processing of large 'when' clauses 
/    gpongrac   04/01/93 - add new log open error (365)
/    hkodaval   03/29/93 - Bug 123364: remove recursion and hence error 1596 
/    wbridge    03/24/93 - read-only tablespaces 
/    dsdaniel   03/24/93 - commitscn function for repliation  
/    pritto     03/17/93 - #(153641) remove 110 & add 960, 962 for rlim
/    ltung      03/15/93 - merge from dve$fox (parallel query msgs) 
/    dpawson    03/15/93 - #(140423) Add msg 7544 - not enough OSD resource 
/    bquigley   03/15/93 - ora-01022,01058 
/    tsaulys    03/09/93 - #(145081) add 7541, 7543
/    hkodaval   02/26/93 - Bug 140750 - add event 10061 to disable SMON from
/                          cleaning temp segments and coalescing extents
/    jwijaya    02/22/93 - merge changes from branch 1.417.312.7 
/    jwijaya    02/22/93 - merge changes from branch 1.417.312.6 
/    jwijaya    02/17/93 - renumber 4069 and fix 4068 
/    jwijaya    02/17/93 - renumber 4069 
/    pritto     02/08/93 - #(149456) add 119, mts_listener_address syntax error
/    dleary     02/08/93 - merge changes from branch 1.286.12.1 
/    jbellemo   02/02/93 - merge changes from branch 1.417.312.5 
/    jbellemo   01/22/93 - (#147335): add message 12444 
/    achaudhr   01/21/93 - add event 10058
/    rkooi      01/20/93 - add 4069 
/    jwijaya    01/18/93 - merge changes from branch 1.417.312.3 
/    pritto     01/16/93 - merge changes from branch 1.417.312.1 
/    jwijaya    01/14/93 - bug 145876, add 4046
/    jklein     01/13/93 - merge changes from branch 1.417.312.2 
/    jklein     01/13/93 - bug 146226 - add event to disable histograms 
/    pritto     01/11/93 - #(144049) remove 481, 482
/    mmoore     01/11/93 - change message for 8176 
/    wbridge    01/07/93 - event to suppress file name for regression tests 
/    glumpkin   12/16/92 - #(141079) add sqlnet error messages 
/    glumpkin   12/16/92 - #141079 - add sqlnet error messages 
/    mmoore     12/11/92 - disable set_role in stored procs 
/    agupta     12/11/92 - add 10292 - debug drop tablespace 
/    wbridge    12/08/92 - snapshot refresh all error 
/    wbridge    12/03/92 - fix error handling for refresh all 
/    ltan       12/03/92 - modify 1545 cause and action
/    wbridge    11/30/92 - background process to refresh snapshots 
/    pritto     11/30/92 - merge in SQL*Net 2.0.12 errors 
/    epeeler    11/30/92 - modify enable constraint message 
/    sjain      11/25/92 - Add 1044 
/    rkooi      11/25/92 - fix 6563 error message 
/    jloaiza    11/25/92 - fix error 57 
/    ajasuja    11/25/92 - new error 12354 
/    rkooi      11/24/92 - A couple of changes for Brian 
/    jcleland   11/24/92 - fix error 12354 
/    jcleland   11/24/92 - -madd error 12354 
/    ghallmar   11/20/92 - add event 10281 to affect process creation timeout 
/    bquigley   11/20/92 - Put back %s at beginning of ora-4063,20000 
/    jloaiza    11/19/92 - second parameter to 4031 
/    bquigley   11/19/92 - msgs starting with %s changed 
/    ajasuja    11/19/92 - error 12445 for analyze table 
/    maporter   11/18/92 - #139480 - remove 10700 event 
/    bquigley   11/18/92 - Trusted messages 
/    bquigley   11/17/92 - ora-603 
/    jwijaya    11/14/92 - comment on event 10205 
/    rkooi      11/13/92 - add 655x for psdres 
/    bquigley   11/13/92 - update ORA-2436 
/    ghallmar   11/12/92 - add events for 2PC tracing 
/    ajasuja    11/11/92 - merge forward from 7.0.11 
/    thayes     11/10/92 - Add parameter range checking errors 
/    jcleland   11/10/92 - revise error messages 12351,12353 
/    jcleland   11/10/92 - add error message 12353 
/    bquigley   11/10/92 - update 2021 
/    cozbutun   11/09/92 - modify 2019 
/    ajasuja    11/09/92 - add MLS error 12447
/    rkooi      11/06/92 - add 6513 for pl/sql 
/    bquigley   11/05/92 - fix up merge diffs 
/    jwijaya    11/04/92 - add 6561, 6562 
/    gpongrac   11/03/92 - add event 10291 for testing tbsadf 
/    wbridge    11/02/92 - #(135186) robust lock mode inquiry 
/    jbellemo   11/02/92 - add 12461 
/    bquigley   11/02/92 - add 2028 
/    rlim       10/30/92 - add 1040 
/    glumpkin   10/30/92 - Merge unix error messages 
/    pritto     10/29/92 - add event 10258 for shared server selection
/    maporter   10/29/92 - Add 7531 vms error message for ssfccf $display 
/    bquigley   10/28/92 - make 2038,2039 clearer 
/    bquigley   10/27/92 - Add 1414 
/    pritto     10/26/92 - #(135834) add 116
/    bquigley   10/25/92 - add 1413 
/    bquigley   10/25/92 - 1484, 1486 clearer 
/    aho        10/23/92 - add event to test truncate index undo (10603)
/    rkooi      10/22/92 - reduce length (for LMS) of error 21000 
/    tsaulys    10/21/92 - Add error message 7709 for bug 33056
/    rlim       10/21/92 - add 1039 
/    ccongdon   10/21/92 - Add errors 7515, 7519, 7537, 7542, 7527, and 7533
/                          for bug 117453. 
/    pritto     10/20/92 - #(130911) move 7575,7576 to 1987,1988
/                          #(135660) add 7606  
/    jwijaya    10/19/92 - add 1083
/    bquigley   10/17/92 - ora-1409 
/    wbridge    10/16/92 - require log_files to match in all instances 
/    lwillis    10/14/92 - Add 1986 - optimizer_goal 
/    mmoore     10/13/92 - #(131686) change messages 2074,4092,0034 
/    maporter   10/13/92 - Fill in archival errors that were never entered 
/    maporter   10/12/92 - #132670 - report archiving osd errors (add 290)
/    jklein     10/12/92 - new analyze parse options 
/    ghallmar   10/10/92 - add ora-476: RECO died 
/    thayes     10/08/92 - Add error #1639
/    glumpkin   10/08/92 - fix typo in 02436 
/    wmaimone   10/01/92 - duplicate 12449 
/    mmoore     10/01/92 - remove trigger restrictions, remove error 4086 
/    jwijaya    09/28/92 - 4055 is obsolete 
/    verbrug    09/23/92 - Remove 12704 
/    thayes     09/23/92 - Fix error messages for log members 
/    rlim       09/21/92 - add 1413 and 1463
/    rkooi      09/19/92 - change error 6559 to standards 
/    pritto     09/18/92 - update message 110 
/    wmaimone   09/16/92 - add 12400,12401,12448,12449
/    achaudhr   09/14/92 - 126559: rewording 1719
/    rkooi      09/08/92 - backout 1.334 changes - postpone until 7.0.12
/    pritto     09/08/92 - #(127459) update message 114
/    glumpkin   09/07/92 - Add new snapshot error message: 12010
/    ghallmar   09/05/92 - reuse 2043: must end current transaction before ...
/    bquigley   09/04/92 - Alter any msg beginning %s so the %s appears later 
/    bquigley   09/04/92 - Alter any msg beginning %s so the %s appears later
/    mmoore     08/31/92 - #(122494) add column name to error 4086 
/    rkooi      08/26/92 - add 6503 for pl/sql 
/    pritto     08/26/92 - clarify and extend cause/action on OER(23) 
/    jklein     08/20/92 - parallel data load 
/    jbellemo   08/17/92 - fix label translation errors: 12450-12460,7610-7620
/    jwijaya    08/13/92 - add 4069 
/    gpongrac   08/10/92 - change Cause: for error 1610
/    dleary     08/06/92 - reserve events for parallel query 
/    jwijaya    08/05/92 - add a new error 
/    pritto     07/30/92 - add dispatcher error messages 
/    bquigley   07/29/92 - Add Message Standards Documentation. 
/    hrizvi     07/28/92 - fix extreneous / before 2078 
/    wmaimone   07/24/92 - MLS tech writing review 
/    bquigley   07/24/92 - Update ORA-00568 & 00057
/    hrizvi     07/21/92 - add 2093
/    thayes     07/20/92 - Add pec error number for MLS 
/    jwijaya    07/20/92 - remove database link owner from name 
/    jklein     07/16/92 - remove message 983 - obsolete 
/    hrizvi     07/16/92 - add 19, 35, 1985
/    wbridge    07/15/92 - add compatibility checking calls 
/    hrizvi     07/15/92 - add 1636, 1637 
/    gpongrac   07/15/92 - use error 373 for online log incompat problem
/    ltan       07/14/92 - add error 8176
/    pritto     07/10/92 - #(105280),#(105279) add more sz errors
/    thayes     07/01/92 - Change message for invalid thread number 
/    rlim       06/30/92 - changing text of error 2444 
/    sjain      06/26/92 - Add message for # 568 
/    rkooi      06/25/92 - get rid of arg to 6557 
/    vraghuna   06/23/92 - add 7850 for fixed= option  
/    pritto     06/17/92 - add XA error messages 
/    hrizvi     06/16/92 - add 8103 
/    ghallmar   06/14/92 - change wording of error 2047 
/    wbridge    06/10/92 - improve error simulation 
/    mmoore     06/10/92 - add error message for create or replace trigger 
/    glumpkin   06/09/92 - Add event 10053 -- optimizer stats 
/    mmoore     06/08/92 - #(111777) add error for lacking create session priv 
/    epeeler    06/08/92 - modify error message 1451 
/    jbellemo   06/05/92 - rollout 12458: obsolete 
/    hrizvi     06/05/92 - add 2091, 2092 
/    thayes     06/04/92 - Add errors for KCK module 
/    hrizvi     06/04/92 - add 1635 
/    agupta     06/03/92 - remove 1635,1636 
/    jbellemo   06/02/92 - new MLS errors: 12457,12459 
/    sjain      06/01/92 - Add/changge error messages 
/    thayes     05/29/92 - Add error for 0 file size 
/    maporter   05/29/92 - Add 475, 1380-1389
/    jklein     05/29/92 - add kdn event 
/    jcleland   05/29/92 - add message for 12336 
/    rkooi      05/27/92 - remove extra '/' lines to ease finding error ranges
/                          reserve 3300-3499 for Meiko.
/                          delete history prior to 01/01/92.
/    wbridge    05/21/92 - reword 285 
/    agupta     05/21/92 - 60972 - dtsdrv - don't drop if users temp or defaul
/    pritto     05/19/92 - #(109437) add error msg for long mts_service 
/    jloaiza    05/12/92 - add discrete transaction error 
/    ajasuja    05/12/92 - new message 12407 
/    smartin    05/05/92 - Fix kcl 160? error messages 
/    jklein     04/29/92 - fix bug 106913 - make message 4014 TRANSLATABLE 
/    mmoore     04/28/92 - #(9647) fix granting on a view to check dependents 
/    rkooi      04/26/92 - add errors for dbms_pipe icds 
/    rkooi      04/26/92 - add arg for 6557 
/    wmaimone   04/24/92 - merge changes from branch 1.270.300.4 
/    cheigham   04/23/92 - add loader out-of-memory message 
/    hrizvi     04/22/92 - fix wording of 1593, bug no. 99222, add 1556
/    mmoore     04/16/92 - add message for disallowing features in mts 
/    mmoore     04/13/92 - add error 4093 
/    wmaimone   04/06/92 - add 12458 
/    pritto     03/26/92 - merge in SQL*Net version 2.0.9.3 messages 
/    jwijaya    03/25/92 - fix 6500 
/    agupta     03/25/92 - alter table allocate extent (freelist group) errs 
/    jwijaya    03/18/92 - clean up pl/sql error messages 
/    wbridge    03/13/92 - fix create controlfile 
/    maporter   03/11/92 - Reserve NCUBE error range 
/    jklein     03/05/92 - cann't allocate extent on hash clusters 
/    rkooi      02/21/92 - change 00257 per mktg 
/    mmoore     02/19/92 - remove error 4093 
/    ajasuja    02/18/92 - add errors 12487, 12429, 12441, 12442
/    wbridge    02/17/92 - add error 1221
/    ltan       02/17/92 - change ora-1597 for system rollback segment
/    jwijaya    02/13/92 - doesn't -> does not 
/    jloaiza    02/13/92 - add oltp transaction failed error
/    mroberts   02/12/92 - remove quotes from 4043, 4052, 4053, 406x 
/    wmaimone   02/07/92 - add MAC dictionary reference errors 
/    jwijaya    02/07/92 - add an error 
/    pritto     02/06/92 - merge in SQL*Net v2.0.8 errors, add 113
/    mmoore     02/06/92 - change standard_extension 
/    bmahbod    02/04/92 - add 1634 for bug 87775 
/    rkooi      01/31/92 - better 'cause' section for error 1002 
/    smcadams   01/29/92 - add 1219, 1220, 34 
/    rkooi      01/29/92 - improve error 1011 
/    ltan       01/29/92 - modify cause and action of ora-1594 
/    rlim       01/24/92 - 6.2->7.0 merge 
/    rlim       01/22/92 - add 2022 - local view too complex for remote
/    epeeler    01/22/92 - add 2445 - exceptions table missing 
/    mroberts   01/21/92 - add 3124 (async operation interrupted)
/    jwijaya    01/16/92 - add 4029
/    jklein     01/16/92 - fix error 2170 
/    wbridge    01/13/92 - add event 10300 to avoid undo compatibility check
/    maporter   01/12/92 - merge changes from branch 1.191.51.3 
/    wbridge    01/10/92 - reword 1040
/    rlim       01/10/92 - reword 1 and include violated index name 
/    wmaimone   01/08/92 - add 12438, change syshi/low to dbhi/lo 
/    wbridge    01/08/92 - reword 1171 
/    thayes     01/07/92 - add error for renaming current log file 
/    jcleland   01/03/92 - add errors for label translation 
/    ghallmar   01/02/92 - add 2079: no new branches after tx commit 
/    maporter   12/23/91 - add message for osnsoi failure. 
/    maporter   12/21/91 - Add err 50 for bug 48037, 79392 
/    Hayes      07/29/91 - add error 10288 
/    Heigham    07/19/91 - add errors 2372-3
/    Tan        07/18/91 - change message of event 10041
/    Tan        04/17/91 - change message of error 1456
/    Jain       04/12/91 - Change the text of 1488
/
/ Copyright (c) Oracle Corporation 1999, 2001.  All rights reserved.
/
/ NAME
/   e0.msg
/ DESCRIPTION
/   Error messages for Oracle
/ NOTES
/   Language      : American
/   Character set : US7ASCII
/
/ List of ORACLE errors
/
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000.
/ The remainder of the line is the error text (max 76 characters).
/
/ Adding an error:
/   Check out this file, add the error, and check it back in.
/   Error numbers should always be ordered.
/   The second column should always be x00000.
/ Pseudo-error debugging events:
/   Error codes 10000 .. 10999 are reserved for debug event codes
/   that are not really errors.
/
/ MODIFIED
/   vzsridha    02/06/11 - add ora-499: raised when XDMG fails to initialize
/                          repeatedly
/   sanselva    01/26/11 - proj33056: ORA-851 for RMON termination
/   vgokhale    01/12/11 - Add OER-387
/   mmpandey    05/20/10 - 9714832: modify ADRCI Note, per new requirement
/   mmpandey    05/13/10 - 9713537: modify ORA-00600 Cause/Action message
/   vpantele    02/26/10 - ORA-244 and 245
/   vzsridha    04/25/09 - add exit error for XDMG process
/   jjlee       03/03/09 - add ORA-241
/   clhsu       02/23/09 - add a new process 496
/   adalee      01/08/09 - add ORA-495
/   kgiyer      11/15/08 - Bug-7503836: Shorten text for ORA-336
/   kgiyer      05/20/08 - Bug-6746478: add OER 242 and 243
/   vpantele    09/05/08 - fix ORA-752
/   rlong       08/07/08 - 
/   jgiloni     08/04/08 - Add 135-139
/   jjlee       07/15/08 - comment change
/   jiashi      06/05/08 - update ORA-235
/   mcoulter    03/27/08 - 
/   clhsu       03/07/08 - bug6513336: change ora-494 to conform language rules
/   shsong      02/13/08 - enhance OER 336 message 
/   pbagal      12/06/07 - add inst. type to 99
/   mcoulter    11/21/07 - BUG 6603046 - need to handle more error paremeters
/                          (9)
/   slahoran    10/22/07 - bug/6327593 : add ORA-44
/   yuli        09/04/07 - RECOVER UNTIL CONSISTENT
/   kesriniv    08/03/07 - add ORA-66 for ksp-invalid-sid msg
/   bbaddepu    08/01/07 - add 848-850
/   vpantele    04/25/07 - add OER 239, 240 and 494 
/   kesriniv    05/08/07 - add ORA-00098 and ORA-00099
/   bbaddepu    04/26/07 - enhance 840 and 839 messages
/   banaras     02/07/07 - lock_sga and memory_target are not compatible
/   bbaddepu    01/19/07 - enhance 845 msg
/   siroych     12/27/06 - add 846
/   kumamage    08/01/06 - add soft internal error
/   rvingral    07/24/06 - add OER(493)
/   tyurek      06/13/06 - define 00491 for RMS0 
/   yohu        06/01/06 - add OER(492) 
/   bbaddepu    05/23/06 - add 843, 845
/   siroych     05/19/06 - add OER 844
/   bbaddepu    04/30/06 - add 839, 840/1/2
/   siroych     04/11/06 - add OER 837, 838
/   vpantele    02/15/06 - Add error 752 for lost write detection 
/   jiashi      03/27/06 - remove OER(343), modify OER(346)
/   avaliani    03/29/06 - incorporate erros_us feedback
/   ramekuma    02/23/06 - ddl_waitlock: update definition of ORA 54 
/   ltominna    01/25/06 - remote op fail error OER(43) 
/   avaliani    11/21/05 - reserve OER(39)
/   bbaddepu    07/13/05 - add diag events notes 
/   seeda       06/30/05 - 4226133: ORA-64 doesn't report caller description 
/   mjstewar    06/24/05 - add OER(751)
/   yuli        06/23/05 - add 725 
/   jiashi      02/25/05 - modify OER(63), obsolete OER(66) 
/   hmankude    02/03/05 - Bug 4160349: new msg for ckpt death 
/   jiashi      12/16/04 - modify messages for 216, 217, 219
/   kumamage    12/14/04 - add message for 453 
/   avaliani    11/30/04 - add OER(569) 
/   pokumar     09/08/04 - add event 833 
/   pokumar     07/15/04 - add message 832 
/   wojeil      07/27/04 - bug-3449667:add error message for enabling 
/                          USE_INDIRECT_DATA_BUFFERS on non-VLM platforms 
/   pokumar     06/23/04 - add event 831 for stress testing 
/   sridsubr    04/18/04 - Add service name error msg 42
/   tbosman     02/11/04 - numa 
/   tbosman     10/02/03 - 
/   tbosman     09/20/03 - attach failed 
/   tbosman     08/20/03 - add PSP error 
/   eyho        05/24/04 - remove OER 99 
/   jiashi      05/16/04 - update OER 302 
/   rlong       11/06/03 - OSM->ASM 
/   tsepez      11/04/03 - RBAL/ORB* termination messages 
/   pokumar     10/28/03 - add 830 
/   pokumar     10/08/03 - add event 829 for stress testing 
/   rasivara    09/25/03 - correct typo in ORA-288 message 
/   cluu        08/29/03 - add err msg 105,109,110,111,112,117,118,133,134
/   kpatel      08/18/03 - add error 828 
/   pokumar     07/29/03 - add error message 827
/   asundqui    07/14/03 - add Resource Manager abort_sql/kill_session messages
/   pokumar     05/30/03 - change text of 824
/   pokumar     05/01/03 - add sga-tuning error messages
/   pokumar     04/18/03 - enhance ora-371 to include size recommendation
/   tlahiri     03/18/03 - Add sga_target too large message
/   vsrihari    02/27/03 - reuse 397 for instance recovery abort
/   tlahiri     01/23/03 - Add error for MMAN process start failure
/   pritto      12/05/02 - Fix typo in 486
/   lilin       01/06/03 - change messages with thread no. to include instance
/   pritto      12/05/02 - Fix typo in 486
/   kumamage    12/14/02 - add error 450
/   bbaddepu    11/19/02 - modify err msg 218.
/   tlahiri     12/10/02 - Add error messages for SGA tuning
/   jiashi      09/24/02 - add error message 740, 741 
/   banand      03/15/02 - recovery thru resetlogs : change 342
/   cluu        10/07/02 - remove unused messages: 117,124,118
/   cluu        10/06/02 - remove unused messages: 105,111,112,120,121
/   swerthei    04/26/02 - block change tracking; add 487 for CTWR
/   yuli        10/03/02 - add 750
/   yuli        09/20/02 - obsolete alter database convert
/   kumamage    09/04/02 - add internal error message
/   pritto      07/01/02 - Only one umbilicus per db instance
/   jarnett     05/10/02 - bug 2314669 - make DX overflow a user error.
/   jwlee       05/08/02 - add error 479.
/   pritto      10/22/01 - Rename PSM to OSM.
/   pritto      10/15/01 - Add OSM Background message
/   wojeil      02/11/02 - adding 385.
/   yuli        01/16/02 - tablespace rename project
/   yuli        02/08/02 - 10i irreversible compatibility project
/   msusaira    12/07/01 - add error messages for H.A.R.D project
/   vkarra      11/20/01 - add error message for auto segment space management
/   smuthuli    10/18/01 - add 478
/   pritto      10/02/01 - Update detached process number range.
/   sdizdar     02/23/01 - added 0217
/   mwjohnso    07/26/01 - modify ora-298 text
/   mjaeger     07/05/01 - bug 479696: 00295: alter db datafile/tempfile <fno>
/   bsinha      07/20/01 - fix distributed autonomous txn
/   ilam        06/18/01 - Add 485 error for DIAG
/   bsinha      06/13/01 - autonomous-distributed interop
/   cluu        04/27/01 - add listener error messages
/   eyho        03/06/01 - RAC name changes
/   qcao        02/14/01 - fix bug 407350
/   anithrak    03/05/01 - Enhance ORA-379 message to add block size
/   vjoshi      12/13/00 - change error message
/   robermar    11/22/00 - Detect Multiple strand redo
/   heneman     10/21/00 - Rename MTS.
/   jarnett     08/17/00 - bug 1217450 - disallow autonomous in distributed
/   vsrihari    07/19/00 - add 299 for block media recovery
/   smukkama    07/20/00 - change 374 - db_block_size must be multiple of 512
/   vsrihari    06/12/00 - add 399 for change vector corruption
/   vsrihari    06/06/00 - fix ORA-396 message argument
/   vsrihari    05/24/00 - add 398 for instance recovery abort
/   tlahiri     05/08/00 - Add dynamic cache error messages
/   smukkama    03/04/00 - Add 380,381,382 - multiple block size project
/   apadmana    01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW
/   eyho        02/14/00 - add 484 error for LMS
/   vsrihari    02/02/00 - add msg 397 for two-pass recovery
/   jarnett     07/02/99 - bug 853211 - allow local transaction disable on V8
/   pogilvie    06/15/99 - testing error 607
/   gcandea     02/11/99 - Add 127 and 128 for ALTER SYSTEM SHUTDOWN
/   robermar    10/22/98 - Error message 396 for two-pass recovery
/   drehfiel    09/10/98 - updating to follow message standards
/   skray       08/28/98 - edit message text for 38
/   skray       08/14/98 - add 37, 38
/   drehfiel    08/13/98 - editing action for message ORA-00001
/   agreenbl    05/28/98 - Fix text for 00093, 00094
/   mcoyle      04/03/98 - Add ops-aware oradebug mesgs
/   mcoyle      03/02/98 - Add errors for ops-aware oradebug
/   emagrath    02/26/98 - Add new archive log/state parameter support
/   mwjohnso    02/17/98 - Add 298 & 299
/   heneman     12/03/97 - Add 2 MTS refuse error codes
/   bchang      09/26/97 - 000439: first character should be lower case
/   tlahiri     09/23/97 - add 379
/   swerthei    08/13/97 - add 296, 297
/-------------------------------------------------------------------------------
00000, 00000, "normal, successful completion"
// *Cause:  Normal exit.
// *Action: None.
00001, 00000, "unique constraint (%s.%s) violated"
// *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
//         For Trusted Oracle configured in DBMS MAC mode, you may see
//         this message if a duplicate entry exists at a different level.
// *Action: Either remove the unique restriction or do not insert the key.
/0002     reserved for v2 compatibility (null column)
/0003     reserved for v2 compatibility (column value truncated)
/0004     reserved for v2 compatibility (end-of-fetch)
/0009     reserved for v2 compatibility
/
/ 10 - 49 user session and session switching errors
/
00017, 00000, "session requested to set trace event"
// *Cause:  The current session was requested to set a trace event by another
//          session.
// *Action: This is used internally; no action is required.
00018, 00000, "maximum number of sessions exceeded"
// *Cause:  All session state objects are in use.
// *Action: Increase the value of the SESSIONS initialization parameter.
00019, 00000, "maximum number of session licenses exceeded"
// *Cause: All licenses are in use.
// *Action: Increase the value of the LICENSE MAX SESSIONS initialization
//          parameter.
00020, 00000, "maximum number of processes (%s) exceeded"
// *Cause:  All process state objects are in use.
// *Action: Increase the value of the PROCESSES initialization parameter.
00021, 00000, "session attached to some other process; cannot switch session"
// *Cause:  The user session is currently used by others.
// *Action: Do not switch to a session attached to some other process.
00022, 00000, "invalid session ID; access denied"
// *Cause: Either the session specified does not exist or the caller
//         does not have the privilege to access it.
// *Action: Specify a valid session ID that you have privilege to access,
//          that is either you own it or you have the CHANGE_USER privilege.
00023, 00000, "session references process private memory; cannot detach session"
// *Cause:  An attempt was made to detach the current session when it contains
//          references to process private memory.
// *Action: A session may contain references to process memory (PGA) if it has
//          an open network connection, a very large context area, or operating
//          system privileges.  To allow the detach, it may be necessary to
//          close the session's database links and/or cursors.  Detaching a
//          session with operating system privileges is always disallowed.
00024, 00000, "logins from more than one process not allowed in single-process mode"
// *Cause:  Trying to login more than once from different processes for
//          ORACLE started in single-process mode.
// *Action: Logoff from the other process.
00025, 00000, "failed to allocate %s"
// *Cause:  Out of memory.
// *Action: Restart with larger sga heap.
00026, 00000, "missing or invalid session ID"
// *Cause:  Missing or invalid session ID string for ALTER SYSTEM KILL SESSION.
// *Action: Retry with a valid session ID.
00027, 00000, "cannot kill current session"
// *Cause:  Attempted to use ALTER SYSTEM KILL SESSION to kill the current
//          session.
// *Action: None.
00028, 00000, "your session has been killed"
// *Cause:  A privileged user has killed your session and you are no longer
//          logged on to the database.
// *Action: Login again if you wish to continue working.
00029, 00000, "session is not a user session"
// *Cause:  The session ID specified in an ALTER SYSTEM KILL SESSION command
//          was not a user session (for example, recursive, etc.).
// *Action: Retry with a user session ID.
00030, 00000, "User session ID does not exist."
// *Cause:  The user session ID no longer exists, probably because the
//          session was logged out.
// *Action: Use a valid session ID.
00031, 00000, "session marked for kill"
// *Cause:  The session specified in an ALTER SYSTEM KILL SESSION command
//          cannot be killed immediately (because it is rolling back or blocked
//          on a network operation), but it has been marked for kill.  This
//          means it will be killed as soon as possible after its current
//          uninterruptable operation is done.
// *Action: No action is required for the session to be killed, but further
//          executions of the ALTER SYSTEM KILL SESSION command on this session
//          may cause the session to be killed sooner.
00032, 00000, "invalid session migration password"
// *Cause:  The session migration password specified in a session creation
//          call was invalid (probably too long).
// *Action: Retry with a valid password (less than 30 chars).
00033, 00000, "current session has empty migration password"
// *Cause:  An attempt was made to detach or clone the current session and
//          it has an empty migration password.  This is not allowed.
// *Action: Create the session with a non-empty migration password.
00034, 00000, "cannot %s in current PL/SQL session"
// *Cause:  An attempt was made to issue a commit or rollback from a PL/SQL
//          object (procedure, function, package) in a session that has this
//          disabled (by 'alter session disable commit in procedure')
// *Action: Enable commits from PL/SQL in this session, or do not attempt
//          to use commit or rollback in PL/SQL when they are disabled
//          in the current session.
00035, 00000, "LICENSE_MAX_USERS cannot be less than current number of users"
// *Cause:
// *Action:
00036, 00000, "maximum number of recursive SQL levels (%s) exceeded"
// *Cause:  An attempt was made to go more than the specified number
//          of recursive SQL levels.
// *Action: Remove the recursive SQL, possibly a recursive trigger.
00037, 00000, "cannot switch to a session belonging to a different server group"
// *Cause:  An attempt was made to switch to a session in a different server
//          group.  This is not allowed.
// *Action: Make sure the server switches to a session that belongs to its
//          server group.
00038, 00000, "Cannot create session: server group belongs to another user"
// *Cause:  An attempt was made to create a non-migratable session in a server
//          group that is owned by a different user.
// *Action: A server group is owned by the first user who logs into a server
//          in the server group in non-migratable mode.  All subsequent
//          non-migratable mode logins must be made by the user who owns
//          the server group.  To have a different user login in non-migratable
//          mode, the ownership of the server group will have to be changed.
//          This can be done by logging off all current sessions and detaching
//          from all existing servers in the server group and then having the
//          new user login to become the new owner.
00039, 00000, "error during periodic action"
// *Cause:  An unexpected error occurred while executing a periodically invoked
//          action.
// *Action: Check the error stack for detailed error information.
00040, 00000, "active time limit exceeded - call aborted"
// *Cause:  The Resource Manager SWITCH_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
//          database administrator for more information.
00041, 00000, "active time limit exceeded - session terminated"
// *Cause:  The Resource Manager SWITCH_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
//          database administrator for more information.
00042, 0000, "Unknown Service name %s"
// *Cause:    An attempt was made to use an invalid application service.
// *Action:   Use a valid service name from SERVICE$ or add a new
//            service using the DBMS_SERVICE package.
00043, 00000, "remote operation failed"
// *Cause:  Execution of the inter-instance operation failed.
// *Action: Check the status of the target instance.  The operation may 
//          have partially executed.  Verify the result of the intended 
//          operation.
00044, 00000, "timed_statistics must be TRUE when statistics_level is not BASIC"
// *Cause:  The user attempted to set timed_statistics to FALSE when
//          statistics_level was not BASIC. timed_statistics is required to be
//          TRUE to collect meaningful statistics when statistics_level is
//          set to TYPICAL or ALL.
// *Action: Either set timed_statistics to TRUE or set statistics_level to
//          BASIC.
00050, 00000, "operating system error occurred while obtaining an enqueue"
// *Cause:  Could not obtain the operating system resources necessary
//          to cover an oracle enqueue.  This is normally the result
//          of an operating system user quota that is too low.
// *Action: Look up the operating system error in your system documentation
//          and perform the needed action.
00051, 00000, "timeout occurred while waiting for a resource"
// *Cause:  Usually due to a dead instance.
// *Action: Check for any dead, unrecovered instances and recover them.
00052, 00000, "maximum number of enqueue resources (%s) exceeded"
// *Cause:  Ran out of enqueue resources.
// *Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.
00053, 00000, "maximum number of enqueues exceeded"
// *Cause:  Ran out of enqueue state objects.
// *Action: Increase the value of the ENQUEUES initialization parameter.
00054, 00000, "resource busy and acquire with NOWAIT specified or timeout expired"
// *Cause:  Interested resource is busy.
// *Action: Retry if necessary or increase timeout.
00055, 00000, "maximum number of DML locks exceeded"
// *Cause:  Ran out of DML lock state objects.
// *Action: Increase the value of the DML_LOCKS initialization parameter
//          and warm start.
00056, 00000, "DDL lock on object '%s.%s' is already held in an incompatible mode"
// *Cause:  An attempt was made to acquire a DDL lock that is already locked.
// *Action: This happens if you attempt to drop a table that has parse locks
//    on it.
00057, 00000, "maximum number of temporary table locks exceeded"
// *Cause:  The number of temporary tables equals or exceeds the number of
//          temporary table locks.  Temporary tables are often created by
//          large sorts.
// *Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization
//          parameter and warm start.
00058, 00000, "DB_BLOCK_SIZE must be %s to mount this database (not %s)"
// *Cause:  DB_BLOCK_SIZE initialization parameter is wrong for the database
//          being mounted. It does not match the value used to create the
//          database.
// *Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database
//          that matches the value.
00059, 00000, "maximum number of DB_FILES exceeded"
// *Cause:  The value of the DB_FILES initialization parameter was exceeded.
// *Action: Increase the value of the DB_FILES parameter and warm start.
00060, 00000, "deadlock detected while waiting for resource"
// *Cause:  Transactions deadlocked one another while waiting for resources.
// *Action: Look at the trace file to see the transactions and resources
//          involved. Retry if necessary.
00061, 00000, "another instance has a different DML_LOCKS setting"
// *Cause: The shared instance being started is using DML locks, and the
//   running instances are not, or vice-versa.
// *Action: Ensure that all instances' INIT.ORA files specify
//          the DML_LOCKS parameter as 0 or all as non-zero.
00062, 00000, "DML full-table lock cannot be acquired; DML_LOCKS is 0"
// *Cause: The instance was started with DML_LOCKS = 0, and the statement
//   being executed needs a full-table lock (S, X, or SSX).
// *Action: Restart the instance with DML_LOCKS not equal to zero, and
//          reexecute the statement.
00063, 00000, "maximum number of log files exceeded %s"
// *Cause:  The number of log files specificied exceeded the maximum number
//          of log files supported in this release.
// *Action: Re-create the control file with the highest number of log files
//          no greater than the maximum supported in this release.
00064, 00000, "object is too large to allocate on this O/S (%s,%s,%s)"
// *Cause:  An initialization parameter was set to a value that required
//          allocating more contiguous space than can be allocated on this
//          operating system.
// *Action: Reduce the value of the initialization parameter.
00065, 00000, "initialization of FIXED_DATE failed"
// *Cause:  The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
// *Action: Make sure the initialization parameter is in the correct date
//          format.
00066, 00000, "SID %s contains an illegal character"
// *Cause:  The specified SID contains an illegal character which cannot occur
//          in an SPFILE setting.  Illegal characters include ,#"'=() and
//          whitespace.
// *Action: Use a SID that does not contain a special character or whitespace.
00067, 00000, "invalid value %s for parameter %s; must be at least %s"
// *Cause:  The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
00068, 00000, "invalid value %s for parameter %s, must be between %s and %s"
// *Cause:  The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
00069, 00000, "cannot acquire lock -- table locks disabled for %s"
// *Cause: A command was issued that tried to lock the table indicated in
//         the message. Examples of commands that can lock tables are:
//         LOCK TABLE, ALTER TABLE ... ADD (...), and so on.
// *Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry
//          the command.
/
/ 70 .. 90 generic debugger errors
/
00070, 00000, "command %s is not valid"
// *Cause:  An invalid debugger command was specified.
// *Action: Type HELP to see the list of available commands.
00071, 00000, "process number must be between 1 and %s"
// *Cause:  An invalid process number was specified.
// *Action: Specify a valid process number.
00072, 00000, "process \"%s\" is not active"
// *Cause:  An invalid process was specified.
// *Action: Specify a valid process.
00073, 00000, "command %s takes between %s and %s argument(s)"
// *Cause:  An incorrect number of arguments was specified.
// *Action: Specify the correct number of arguments.  Type HELP
//          to see the list of commands and their syntax.
00074, 00000, "no process has been specified"
// *Cause:  No debug process has been specified.
// *Action: Specify a valid process.
00075, 00000, "process \"%s\" not found in this instance"
// *Cause:  The specified process was not logged on to the current instance.
// *Action: Specify a valid process.
00076, 00000, "dump %s not found"
// *Cause:  An attempt was made to invoke a dump that does not exist.
// *Action: Type DUMPLIST to see the list of available dumps.
00077, 00000, "dump %s is not valid"
// *Cause:  An attempt was made to invoke an invalid dump.
// *Action: Try another dump.
00078, 00000, "cannot dump variables by name"
// *Cause:  An attempt was made to dump a variable by name on a system that
//          does not support this feature.
// *Action: Try the PEEK command.
00079, 00000, "variable %s not found"
// *Cause:  An attempt was made to dump a variable that does not exist.
// *Action: Use a valid variable name.
00080, 00000, "invalid global area specified by level %s"
// *Cause:  An attempt was made to dump an invalid global area.
// *Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA.
//          Use <extra + level> to dump global area <level> as well as <extra>
//          bytes for every pointer; <extra> must be a multiple of 4.
00081, 00000, "address range [%s, %s) is not readable"
// *Cause:  An attempt was made to read/write an invalid memory address range.
// *Action: Try another address or length.
00082, 00000, "memory size of %s is not in valid set of [1], [2], [4]%s%s%s%s%s"
// *Cause:  An invalid length was specified for the POKE command.
// *Action: Use a valid length (either 1, 2, 4, or possibly 8).
00083, 00000, "warning: possibly corrupt SGA mapped"
// *Cause:  Even though there may be SGA corruptions, the SGA was mapped.
// *Action: Use the DUMPSGA command to dump the SGA.
00084, 00000, "global area must be PGA, SGA, or UGA"
// *Cause:  An attempt was made to dump an invalid global area.
// *Action: Specify either PGA, SGA, or UGA.
00085, 00000, "current call does not exist"
// *Cause:  An invalid attempt was made to dump the current call heap.
// *Action: Wait until the process starts a call.
00086, 00000, "user call does not exist"
// *Cause:  An invalid attempt was made to dump the user call heap.
// *Action: Wait until the process starts a call.
00087, 00000, "command cannot be executed on remote instance"
// *Cause:  Cluster database command issued for non cluster database
//          ORADEBUG command.
// *Action: Issue the command without the cluster database syntax.
00088, 00000, "command cannot be executed by shared server "
// *Cause:  Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server.
00089, 00000, "invalid instance number in ORADEBUG command "
// *Cause:  An invalid instance number was specified in a cluster database
//          ORADEBUG command.
// *Action: Reissue the command with valid instance numbers.
00090, 00000, "failed to allocate memory for cluster database ORADEBUG command "
// *Cause:  Could not allocate memory needed to execute cluster database
//          oradebug.
// *Action: Reissue the command on each instance with single-instance oradebug.
/ 91 .. 95 ksm large_pool_size and large_pool_min_alloc size errors
00091, 00000, "LARGE_POOL_SIZE must be at least %s"
// *Cause: The value of LARGE_POOL_SIZE is below the minimum size.
// *Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
00092, 00000, "LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC"
// *Cause: The value of LARGE_POOL_SIZE is less than the value of
//         LARGE_POOL_MIN_ALLOC.
// *Action: Increase the value of LARGE_POOL_SIZE past the value of
//         LARGE_POOL_MIN_ALLOC.
00093, 00000, "%s must be between %s and %s"
// *Cause: The parameter value is not in a valid range.
// *Action: Modify the parameter value to be within the specified range.
00094, 00000, "%s requires an integer value"
// *Cause: The parameter value is not an integer.
// *Action: Modify the parameter value to be an integer.
/
00096, 00000, "invalid value %s for parameter %s, must be from among %s"
// *Cause:  The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
/
00097, 00000, "use of Oracle SQL feature not in SQL92 %s Level"
// *Cause: Usage of Oracle's SQL extensions.
// *Action:
00098, 00000, "creating or mounting the database requires a parameter file"
// *Cause: An attempt was made to create or mount the database when the
//         instance was started without a parameter file.
// *Action: Restart the instance with a parameter file.
00099, 00000, "warning: no parameter file specified for %s instance"
// *Cause:  Even though no parameter file was specified, the instance was
//          started with all default values.
// *Action: None.
00100, 00000, "no data found"
// *Cause: An application made reference to unknown or inaccessible data.
// *Action: Handle this condition within the application or make appropriate
//          modifications to the application code.
//             NOTE: If the application uses Oracle-mode SQL instead of
//             ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
/
/ 101 .. 149 shared server errors
/
00101, 00000, "invalid specification for system parameter DISPATCHERS"
// *Cause: The syntax for the DISPATCHERS parameter is incorrect.
// *Action: Refer to the manual for correct syntax.
00102, 00000, "network protocol %s cannot be used by dispatchers"
// *Cause: The network specified in DISPATCHERS does not have the
//         functionality required by the dispatchers.
// *Action: Refer to the manual on network protocols supported by the
//          dispatchers.
00103, 00000, "invalid network protocol; reserved for use by dispatchers"
// *Cause: The network specified in the SQL*Net connect string is reserved
//         for use by the dispatchers.
// *Action: Specify other network protocols in the connection string.
00104, 00000, "deadlock detected; all public servers blocked waiting for resources"
// *Cause: All available public servers are servicing requests that require
//         resources locked by a client which is unable to get a public
//         server to release the resources.
// *Action: Increase the limit for the system parameter MAX_SHARED_SERVERS
//          as the system will automaticaly start
//          up new servers to break the deadlock until the number of
//          servers reaches the value specified in MAX_SHARED_SERVERS.
00105, 00000, "too many dispatcher configurations"
// *Cause: Too many dispatcher configurations have been specified.
//         No more can be added.
// *Action: Consolidate the dispatcher configurations if possible.
00106, 00000, "cannot startup/shutdown database when connected to a dispatcher"
//  *Cause: An attempt was made to startup/shutdown database when connected to
//          a shared server via a dispatcher.
// *Action: Re-connect as user INTERNAL without going through the dispatcher.
//          For most cases, this can be done by connect to INTERNAL without
//          specifying a network connect string.
00107, 00000, "failed to connect to ORACLE listener process"
// *Cause: Most likely due to the fact that ORACLE listener has not been
//   started.
// *Action: Start ORACLE listener if it has not been started. Or else
//    contact your ORACLE representative.
00108, 00000, "failed to set up dispatcher to accept connection asynchronously"
// *Cause: Most likely due to the fact that the network protocol used by the
//   the dispatcher does not support aynchronous operations.
// *Action: Contact your ORACLE representative.
00109, 00000, "invalid value for attribute %s: %s"
// *Cause: The value specified for the attribute was incorrect.
// *Action: Refer to the manual for the proper values.
00110, 00000, "invalid value %s for attribute %s, must be between %s and %s"
// *Cause: The value specified for the attribute was incorrect.
// *Action: Specify a value within the range allowed.
00111, 00000, "invalid attribute %s"
// *Cause: The specified attribute was not recognized.
// *Action: Refer to the manual for the proper keyword to use to specify
//          a dispatcher attribute.
00112, 00000, "value of %s is null"
// *Cause: The attribute was specified with no value.
// *Action: Specify a non-null value.
00113, 00000, "protocol name %s is too long"
// *Cause: A protocol name specified in the DISPATCHERS system parameter
//         is too long.
// *Action: Use a valid protocol name for the DISPATCHERS value.
00114, 00000, "missing value for system parameter SERVICE_NAMES"
// *Cause: No value was specified for the SERVICE_NAMES system parameter,
//         nor for the DB_NAME parameter.
// *Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file.
//          By default, SERVICE_NAMES is the value of DB_NAME unless
//          SERVICE_NAMES is explicitly specified.
00115, 00000, "connection refused; dispatcher connection table is full"
// *Cause: A connection request was refused by a dispatcher because the
//         dispatcher cannot support any more connections.
// *Action: Connect to a different dispatcher, or use a dedicated server.
00116, 00000, "SERVICE_NAMES name is too long"
// *Cause: A service name specified in the SERVICE_NAMES system parameter
//         is too long.
// *Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
00117, 00000, "PROTOCOL, ADDRESS or DESCRIPTION must be specified"
// *Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.
// *Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION
//          to specify the listening address for dispatchers.
00118, 00000, "Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified"
// *Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
// *Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION
//          to specify the listening address for dispatchers.
00119, 00000, "invalid specification for system parameter %s"
// *Cause: The syntax for the specified parameter is incorrect.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00122, 00000, "cannot initialize network configuration"
// *Cause:  ORACLE could not initialize SQL*Net version 2.
// *Action: Check the error stack for detailed information.
00123, 00000, "idle public server terminating"
// *Cause: Too many idle servers were waiting on the common queue.
// *Action: This error is used internally, no action is required.
00125, 00000, "connection refused; invalid presentation"
// *Cause:  The PRESENTATION in the CONNECT_DATA of the TNS address
//          DESCRIPTION is not correct or is not supported.
// *Action: Correct the PRESENTATION specified in the TNS address.
00126, 00000, "connection refused; invalid duplicity"
// *Cause:  The DUPLICITY in the CONNECT_DATA of the TNS address
//          DESCRIPTION is not correct or is not supported.
// *Action: Correct the DUPLICITY specified in the TNS address.
00127, 00000, "dispatcher %s does not exist"
// *Cause:  There is currently no dispatcher running with the specified
//          name.
// *Action: Retry with a name of the form "D###" denoting an existing
//          dispatcher process.
00128, 00000, "this command requires a dispatcher name"
// *Cause:  Wrong syntax for ALTER SYSTEM SHUTDOWN
// *Action: Use correct syntax:
//    ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name'
00129, 00000, "listener address validation failed '%s'"
// *Cause:  An error was encountered while validating the listener address.
// *Action: Resolve error or contact your ORACLE representative.
00130, 00000, "invalid listener address '%s'"
// *Cause:  The listener address specification is not valid.
// *Action: Make sure that all fields in the listener address
//          (protocol, port, host, key, ...) are correct.
00131, 00000, "network protocol does not support registration '%s'"
// *Cause:  The specified protocol does not support async notification.
// *Action: Refer to the manual for information on supported network
//          protocols.
00132, 00000, "syntax error or unresolved network name '%s'"
// *Cause:  Listener address has syntax error or cannot be resolved.
// *Action: If a network name is specified, check that it corresponds
//          to an entry in TNSNAMES.ORA or other address repository
//          as configured for your system. Make sure that the entry
//          is syntactically correct.
00133, 00000, "value of %s is too long"
// *Cause: The value specified for the attribute was too long.
// *Action: Use shorter names and keywords or remove unneeded blanks.
00134, 00000, "invalid DISPATCHERS specification #%s"
// *Cause: The syntax for the n-th DISPATCHERS specification was incorrect.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00135, 00000, "missing attribute %s"
// *Cause: The indicated mandatory attribute was not specified.
// *Action: Specify a non-null value for the attribute.
00136, 00000, "invalid LISTENER_NETWORKS specification #%s"
// *Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00137, 00000, "invalid LISTENER_NETWORKS specification with NAME=%s"
// *Cause: The syntax for the LISTENER_NETWORKS specification with the
//         indicated NAME was invalid.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00138, 00000, "all addresses specified for attribute %s are invalid"
// *Cause: All of the specified addresses or aliases for the attribute were 
//         invalid.
// *Action: Specify at least one valid address or alias.
00139, 00000, "duplicate attribute %s"
// *Cause: The indicated attribute was specified more than once.
// *Action: Specify the attribute at most once.
/
/ 150 .. 159 Oracle*XA errors
/
00150, 00000, "duplicate transaction ID"
// *Cause:  Attempted to start a new transaction with an ID already in use
//          by an existing transaction.
// *Action: Check your application.
00151, 00000, "invalid transaction ID"
// *Cause:  The specified transaction ID does not correspond to an existing
//          valid transaction.
// *Action: Check your application.
00152, 00000, "current session does not match requested session"
// *Cause:  The current session is not the same as the session that was
//          passed into a upixado() call.
// *Action: Check your application.
00153, 00000, "internal error in XA library"
// *Cause:  The XA library could not access thread-specific pointers.
// *Action: Contact customer support.
00154, 00000, "protocol error in transaction monitor"
// *Cause:  The transaction monitor returned TMJOIN on an AX_REG call but
//          the transaction was locally suspended.
// *Action: Contact the transaction monitor customer support.
00155, 00000, "cannot perform work outside of global transaction"
// *Cause:  The application tried to perform some work on either an Oracle
//          7.3 server or an Oracle8 server with local transactions disabled
//          while outside of a global transaction.
// *Action: Check if the application is connected to an Oracle 7.3 server. The
//          Transaction monitor must not return a NULL XID on an AX_REG call
//          when the resource manager is Oracle 7.3.  If the application is
//          connected to an Oracle8 server, either set nolocal=f in the
//          xa_open string or start a global transaction prior to attempting
//          the work.


//
/
/ 160 .. 199 Distributed transaction errors (continued)
/
00160, 00000, "global transaction length %s is greater than maximum (%s)"
// *Cause:  An external global transaction ID with a too large length field
//          was passed in.
// *Action: Report the problem to your external transaction coordinator
//          vendor.
00161, 00000, "transaction branch length %s is illegal (maximum allowed %s)"
// *Cause:  An external transaction branch ID with a length either too large
//          or 0 was passed in.
// *Action: Report the problem to your external transaction coordinator
//          vendor.
00162, 00000, "external dbid length %s is greater than maximum (%s)"
// *Cause:  An external database name with too large a length field
//          was passed in.
// *Action: Report the problem to your external transaction coordinator
//          vendor.
00163, 00000, "internal database name length %s is greater than maximum (%s)"
// *Cause:  An internal database name with a too large length field
//          was passed in.
// *Action: Report the problem to your external transaction coordinator
//          vendor.
00164, 00000, "distributed autonomous transaction disallowed within migratable distributed transaction"
// *Cause:  A request was made by the application to start a distributed
//          autonomous transaction when the application was in a migratable 
//          distributed transaction.
// *Action: Roll back or commit the current distributed transaction first.
00165, 00000, "migratable distributed autonomous transaction with remote operation is not allowed"
// *Cause:  A request was made by the application to start a migratable 
//          distributed autonomous transaction with remote operation.
// *Action: 
/
00166, 00000, "remote/local nesting level is too deep"
// *Cause:  Too many remote table operations required a reverse trip 
//          back to the local site, for example to execute a local
//          function on a remote table.
// *Action: Rearrange the query or co-locate the functions with the tables.
/
/ 200 .. 249 control file management errors
/
00200, 00000, "control file could not be created"
// *Cause:  It was not possible to create the control file.
// *Action: Check that there is sufficient disk space and no conflicts in
//          filenames and try to create the control file again.
00201, 00000, "control file version %s incompatible with ORACLE version %s"
// *Cause:  The control file was created by incompatible software.
// *Action: Either restart with a compatible software release or use
//          CREATE CONTROLFILE to create a new control file that is
//          compatible with this release.
00202, 00000, "control file: '%s'"
// *Cause:  This message reports the name file involved in other messages.
// *Action: See associated error messages for a description of the problem.
00203, 00000, "using the wrong control files"
// *Cause:  The mount ID in the control file is not the same as the
//         mount ID in the control file used by the first instance to
//         mount this database. The control files are for the same database
//         but they are not the same files. Most likely one instance is using
//         a backup control file.
// *Action: Check that the correct control files were specified.
00204, 00000, "error in reading (block %s, # blocks %s) of control file"
// *Cause:  A disk I/O failure was detected on reading the control file.
// *Action: Check if the disk is online, if it is not, bring it online and try
//          a warm start again.  If it is online, then you need to recover
//          the disk.
00205, 00000, "error in identifying control file, check alert log for more info"
// *Cause:  The system could not find a control file of the specified name and
//   size.
// *Action: Check that ALL control files are online and that they are the same
//         files that the system created at cold start time.
00206, 00000, "error in writing (block %s, # blocks %s) of control file"
// *Cause:  A disk I/O failure was detected on writing the control file.
// *Action: Check if the disk is online, if it is not, bring it online and try
//   a warm start again.  If it is online, then you need to
//            recover the disk.
00207, 00000, "control files are not for the same database"
// *Cause:  The database ID in the control file is not the same as the
//         database ID in the control file used by the first instance to
//         mount this database. Most likely one of the mounts used the wrong
//         control file or there are two databases with the same name.
// *Action: Check that the control file is for the correct database and is
//         not an old version.
00208, 00000, "number of control file names exceeds limit of %s"
// *Cause:  An attempt was made to use more control files than Oracle supports.
// *Action: Shut down Oracle. Reduce the number of control files specified in
//          the CONTROL_FILES parameter in the initialization parameter
//          file, and restart Oracle. Delete usused files.
00209, 00000, "control file blocksize mismatch, check alert log for more info"
// *Cause: The block size in the control file header does not match the
//         size specified in the DB_BLOCK_SIZE parameter.
// *Action: Look at the alert log for more information.
00210, 00000, "cannot open the specified control file"
// *Cause:  Cannot open the control file.
// *Action: Check to make sure the control file exists and is not locked by
//   some other program.
00211, 00000, "control file does not match previous control files"
// *Cause:  A control file was specified that belongs to another database.
// *Action: Find and install the correct control file.
00212, 00000, "block size %s below minimum required size of %s bytes"
// *Cause:  The block size specified was too small. Space for the
//   system overhead is required.
// *Action: Specify a larger block size and retry the operation.
00213, 00000, "cannot reuse control file; old file size %s, %s required"
// *Cause:  To reuse a control file, it must be the same size as
//    the one previously used.
// *Action: Either do not specify REUSE, or specify a matching combination of
//          MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and
//          MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE
//          statement.
00214, 00000, "control file '%s' version %s inconsistent with file '%s' version %s"
// *Cause: An inconsistent set of control files, datafiles/logfiles, and redo
//         files was used.
// *Action: Use a consistant set of control files, datafiles/logfiles, and redo
//         log files. That is, all the files must be for the same database
//         and from the same time period.
00215, 00000, "must be at least one control file"
// *Cause: No control file is specified or the control file specified does
//         not exist.
// *Action: Specify at least one valid control file and retry the operation.
00216, 00000, "control file could not be resized for migration from 8.0.2"
// *Cause:  The control file created by release 8.0.2 was missing some record 
//          types.  These record types are automatically added by resizing 
//          the control file during mount.  The resize has failed.
// *Action: Look in the alert log for the reason that the resize has failed. 
//          If indicated in the alert log, give the control file more space.
//          Otherwise, use the CREATE CONTROLFILE script dumped to the trace 
//          file to create a new control file.
00217, 00000, "control file could not be resized for new record types"
// *Cause:  The control file was missing some new record types supported
//          by this release.  These record types are automatically added 
//          by resizing the contol file during mount.  The resize has failed.
// *Action: Look in the alert log for the reason that the resize has failed.  
//          If indicated in the alert log, give the control file more space.
//          Otherwise, use the CREATE CONTROLFILE script dumped to the trace 
//          file to create a new control file.
00218, 00000, "block size %s of control file '%s' does not match DB_BLOCK_SIZE (%s)"
// *Cause:  The block size as stored in the control file header is
//          different from the value of the initialization parameter
//          DB_BLOCK_SIZE.  This might be due to an incorrect setting of
//          DB_BLOCK_SIZE, or else might indicate that the control file has
//          either been corrupted or belongs to a different database.
// *Action: Restore a good copy of the control file. If the control file is 
//          known to be clean set the DB_BLOCK_SIZE to match control file 
//          headers block size value.
00219, 00000, "required control file size (%s logical blocks) exceeds maximum allowable size (%s logical blocks)"
// *Cause:  An invocation of CREATE DATABASE or CREATE CONTROLFILE
//          was executed specifying a combination of parameters that would 
//          require the control file size in blocks to exceed the maximum
//          allowable value.
// *Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a
//          different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS,
//          MAXLOGHISTORY, and MAXINSTANCES clauses.
00220, 00000, "control file not mounted by first instance, check alert log for more info"
// *Cause:  The specified control file has a different mount ID than the
//          other control files that are being mounted. This means that
//          the first instance to mount the database did not use this
//          control file.
// *Action: Find and install the correct control file.
00221, 00000, "error on write to control file"
// *Cause:  An error occurred when writing to one or more of the control files.
// *Action: See accompanying messages.
00222, 00000, "operation would reuse name of a currently mounted control file"
// *Cause:  The filename supplied as a parameter to the ALTER DATABASE BACKUP
//          CONTROLFILE command or to cfileSetSnapshotName matches the
//          name of the specified currently mounted control file.
// *Action: Retry the operation with a different filename.
00223, 00000, "convert file is invalid or incorrect version"
// *Cause:  An Oracle7 to Oracle8 convert file contains invalid data
//          or was created with an different version of the migration utility.
//          This error can also be caused by incorrect ORACLE_HOME environment
//          variable when ALTER DATABASE CONVERT command is issued.
// *Action: Use a correct version of the convert file or regenerate it with
//          the migration utility. Make sure that the migration utility is the
//          same version as the Oracle8 RDBMS executable and that the
//          ORACLE_HOME environment variable is properly set.
00224, 00000, "control file resize attempted with illegal record type (%s)"
// *Cause:  An attempt was made to expand or shrink the control file by calling
//          cfileResizeSection using an invalid value for the RECORD_TYPE
//          parameter.
// *Action: Use a value for the RECORD_TYPE parameter that specifies a
//          valid record type other than type 0 (valid range is 1-16).
00225, 00000, "expected size %s of control file differs from actual size %s"
// *Cause:  The expected size of the control file as stored in its
//          header was different than the actual operating system file size.
// This usually indicates that the control file was corrupted.
// *Action: Restore a good copy of the control file.
00226, 00000, "operation disallowed while alternate control file open"
// *Cause:  The attempted operation could not be executed at this time because
//          this process had an alternate control file open for fixed table
//          access.
// *Action: Retry the operation after calling cfileUseCurrent.
00227, 00000, "corrupt block detected in control file: (block %s, # blocks %s)"
// *Cause:  A block header corruption or checksum error was detected on reading
//          the control file.
// *Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP
//          CONTROLFILE command.
00228, 00000, "length of alternate control file name exceeds maximum of %s"
// *Cause:  The specified filename, which was supplied as a parameter
//          to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum
//          filename length for this operating system.
// *Action: Retry the operation with a shorter filename.
00229, 00000, "operation disallowed: already hold snapshot control file enqueue"
// *Cause:  The attempted operation cannot be executed at this time because
//          this process currently holds the snapshot control file enqueue.
// *Action: Retry the operation after calling cfileUseCurrent to release the
//          snapshot control file enqueue.
00230, 00000, "operation disallowed: snapshot control file enqueue unavailable"
// *Cause:  The attempted operation cannot be executed at this time because
//          another process currently holds the snapshot control file enqueue.
// *Action: Retry the operation after the concurrent operation that is holding
//          the snapshot control file enqueue terminates.
00231, 00000, "snapshot control file has not been named"
// *Cause:  During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot
//          it was detected that no filename for the snapshot control file had
//          previously been specified.
// *Action: Specify a name for the snapshot control file by calling
//          cfileSetSnapshotName.
00232, 00000, "snapshot control file is nonexistent, corrupt, or unreadable"
// *Cause:  The snapshot control file was found to be nonexistent, corrupt,
//          or unreadable during an invocation of cfileUseSnapshot.
// *Action: Call cfileMakeAndUseSnapshot again (or for the first time).
00233, 00000, "copy control file is corrupt or unreadable"
// *Cause:  The specified copy control file was found to be corrupt or
//          unreadable during an invocation of cfileUseCopy.
// *Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP
//          CONTROLFILE command and specify the same filename that was
//          specified for cfileUseCopy.
00234, 00000, "error in identifying or opening snapshot or copy control file"
// *Cause:  A snapshot or copy control file of the specified name
//    could not be found or opened during an invocation of
//          cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
// *Action: Re-create the snapshot or copy control file using
//          cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE,
//          respectively.
00235, 00000, "control file read without a lock inconsistent due to concurrent update"
// *Cause:  Concurrent update activity on a control file caused a process 
//    to read inconsistent information from the control file 
//          without a lock.
// *Action: Retry the operation.
00236, 00000, "snapshot operation disallowed: mounted control file is a backup"
// *Cause:  Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot,
//          or cfileUseSnapshot when the currently mounted control file is a
//          backup control file.
// *Action: Mount a current control file and retry the operation.
00237, 00000, "snapshot operation disallowed: control file newly created"
// *Cause:  An attempt to invoke cfileMakeAndUseSnapshot with a currently
//          mounted control file that was newly created with CREATE CONTROLFILE
//         was made.
// *Action: Mount a current control file and retry the operation.
00238, 00000, "operation would reuse a filename that is part of the database"
// *Cause:  The filename supplied as a parameter to the ALTER DATABASE BACKUP
//          CONTROLFILE command or to cfileSetSnapshotName matches the name of
//          a file that is currently part of the database.
// *Action: Retry the operation with a different filename.
00239, 00000, "timeout waiting for control file enqueue: held by '%s' for more than %s seconds"
// *Cause:  The specified process waited the maximum allowed time for the control file enqueue.
// *Action: Restart the blocking instance indicated in the incident trace file
//          or reboot the blocking node.
00240, 00000, "control file enqueue held for more than %s seconds"
// *Cause:  The current process did not release the control file enqueue within
//          the maximum allowed time.
// *Action: Reissue any commands that failed and contact Oracle Support
//          Services with the incident information.
00241, 00000, "operation disallowed: control file inconsistent with data dictionary"
// *Cause:  The control file was either recently created via CREATE
//          CONTROLFILE or an incomplete recovery has been done.
//          Thus, the datafiles in the control file and the ones in the
//          data dictionary may not match.
// *Action: Open the database, then retry the operation.
00242, 00000, "maximum allowed filename records used up in control file"
// *Cause:  Failed to create a new filename record entry in the control file
//          because the maximum allowed filename records have been allocated
//          and are in use.
// *Action: Free up controlfile filename section entries by dropping unwanted
//          tablespaces/datafiles/redofiles.
00243, 00000, "failed to expand control file filename section by %s records"
// *Cause:  Failed to expand control file filename section. See alert log for 
//          more details.
// *Action: Retry the operation after increasing disk space for controlfile 
//          expansion.
00244, 00000, "concurrent control file backup operation in progress"
// *Cause:  Failed to create a control file backup because concurrent control
//          file backup operation was in progress.
// *Action: Retry backup creation later.
00245, 00000, "control file backup failed; target is likely on a local file system"
// *Cause:  Failed to create a control file backup because some process
//          signaled an error during backup creation. This is likely caused
//          by the backup target being on a local file system so it could not
//          be accessed by other instances. It can also be caused by other
//          I/O errors to the backup target. Any process of any instance that
//          starts a read/write control file transaction must have access
//          to the backup control file during backup creation.
// *Action: Check alert files of all instances for further information.
00246, 00000, "control file backup failed; error accessing backup target"
// *Cause:  An attempt to create a control file backup failed because some process
//          signaled an I/O error when accessing the backup target.
// *Action: Check alert and trace files for further information.
/
/ 250 .. 299 archival & media recovery errors
/
00250, 00000, "archiver not started"
// *Cause:  An attempt was made to stop automatic archiving, but the
//          archiver process was not running.
// *Action: No action required.
00251, 00000, "LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string %s"
// *Cause:  The destination specified by the LOG_ARCHIVE_DUPLEX_DEST
//          parameter is the same as the destination specified by an ALTER
//          SYSTEM ARCHIVE LOG START TO command.
// *Action: Specify a different destination for parameter
//          LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the
//          ALTER SYSTEM command.
00252, 00000, "log %s of thread %s is empty, cannot archive"
// *Cause:  A log must be used for redo generation before it can be archived.
//         The specified redo log was not been used since it was introduced
//          to the database. However it is possible that instance death during
//         a log switch left the log empty.
// *Action: Empty logs do not need to be archived. Do not attempt to
//          archive the redo log file.
00253, 00000, "character limit %s exceeded by archive destination string %s"
// *Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
//         command was too long.
// *Action: Retry the ALTER SYSTEM command using a string shorter than the
//          limit specified in the error message.
00254, 00000, "error in archive control string '%s'"
// *Cause: The specified archive log location is invalid in the archive
//         command or the LOG_ARCHIVE_DEST initialization parameter.
// *Action: Check the archive string used to make sure it refers to a valid
// online device.
00255, 00000, "error archiving log %s of thread %s, sequence # %s"
// *Cause: An error occurred during archiving.
// *Action: Check the accompanying message stack for more detailed
//          information.
//
//         If the online log is corrupted,
//          then the log can be cleared using the UNARCHIVED option. This will
//          make any existing backups useless for recovery to any time after
//          the log was created, but will allow the database to generate redo.
00256, 00000, "cannot translate archive destination string %s"
// *Cause:  The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
//          command could not be translated.
// *Action: Check the accompanying message stack for more detailed information.
//          Then, retry the ALTER SYSTEM command using a different string.
00257, 00000, "archiver error. Connect internal only, until freed."
// *Cause:  The archiver process received an error while trying to archive
// a redo log.  If the problem is not resolved soon, the database
// will stop executing transactions. The most likely cause of this
// message is the destination device is out of space to store the
// redo log file.
// *Action:  Check archiver trace file for a detailed description
//  of the problem. Also verify that the
// device specified in the initialization parameter
// ARCHIVE_LOG_DEST is set up properly for archiving.
00258, 00000, "manual archiving in NOARCHIVELOG mode must identify log"
// *Cause: The database is in NOARCHIVELOG mode and a command to manually
//          archive a log did not specify the log explicitly by sequence
//          number, group number or filename.
// *Action: Specify log by filename, by group number or by thread and
//          sequence number.
00259, 00000, "log %s of open instance %s (thread %s) is the current log, cannot archive"
// *Cause:  An attempt was made to archive the current log of an open
//          thread. This is not allowed because the redo log file may
//          still be in use for the generation of redo entries.
// *Action: Force a log switch in the instance where the thread is open.
//          If no instances are open, open the database so that instance
//          recovery can recover the thread.
00260, 00000, "cannot find online log sequence %s for thread %s"
// *Cause: The log sequence number supplied to the archival command does
//         not match any of the online logs for the thread. The log might
//         have been reused for another sequence number, it might have been
//         dropped, the sequence number might be greater than the current
//         log sequence number, or the thread might not have any logs.
// *Action: Check the ARCHIVE statement, then specify a valid log sequence
//          number. Specify a valid log sequence number.
00261, 00000, "log %s of thread %s is being archived or modified"
// *Cause:  The log is either being archived by another process or an
//          administrative command is modifying the log. Operations that
//          modify the log include clearing, adding a member, dropping a
//          member, renaming a member, and dropping the log.
// *Action: Wait for the current operation to complete and try again.
00262, 00000, "current log %s of closed thread %s cannot switch"
// *Cause:  The log cannot be cleared or manually archived because it is
//          the current log of a closed thread, and it is not possible to
//          switch logs so another log is current. All other logs for the
//          thread need to be archived, or cleared, and cannot be reused.
// *Action: Archive another log in the same thread first, or complete the
//          clearing. See attached errors for the reason the switch cannot
//          be completed.
00263, 00000, "there are no logs that need archiving for thread %s"
// *Cause:  An attempt was made to manually archive the unarchived logs in this
//         thread but no logs needed archiving.
// *Action: No action required.
00264, 00000, "no recovery required"
// *Cause:  An attempt was made to perform media recovery on files that do not  //         need any type of recovery.
// *Action: Do not attempt to perform media recovery on the selected
//          files. Check to see that the filenames were entered properly.
//          If not, retry the command with the proper filenames.
00265, 00000, "instance recovery required, cannot set ARCHIVELOG mode"
// *Cause:  The database either crashed or was shutdown with the ABORT
//          option. Media recovery cannot be enabled because the online
//          logs may not be sufficient to recover the current datafiles.
// *Action: Open the database and then enter the SHUTDOWN command with the
//          NORMAL or IMMEDIATE option.
00266, 00000, "name of archived log file needed"
// *Cause:  During media recovery, the name of an archived redo log file
//          was requested, but no name was entered.
// *Action: Mount the correct redo log file and enter its name when it
//          is requested.
00267, 00000, "name of archived log file not needed"
// *Cause:  During media recovery, the name of an archived redo log file
//          was entered, but no name was requested.
// *Action: Continue media recovery, but do not enter a new log name.
00268, 00000, "specified log file does not exist '%s'"
// *Cause:  The given redo log file does not exist.
// *Action:  Check the spelling and capitalization of the filename and
//           retry the command.
00269, 00000, "specified log file is part of thread %s not %s"
// *Cause:  The given redo log file is not part of the given thread
// *Action:  Check that the thread of the redo log file matches the
//           thread on the command line. If not, use a redo log file
//           from the appropriate thread. Retry the command after
//           correcting the error.
00270, 00000, "error creating archive log %s"
// *Cause:  An error was encountered when either creating or opening
//          the destination file for archiving.
// *Action: Check that the archive destination is valid and that there
//          is sufficient space on the destination device.
00271, 00000, "there are no logs that need archiving"
// *Cause:  An attempt was made to archive the unarchived redo log
//          files manually, but there are no files that need to be archived.
// *Action: No action required.
00272, 00000, "error writing archive log %s"
// *Cause:  An I/O error occurred while archiving a redo log file.
// *Action: Check that the output device is still available and correct
//          any device errors that may have occurred. Also, make certain
//          that sufficient space for archiving is available on the
//          output device.
00273, 00000, "media recovery of direct load data that was not logged"
// *Cause:  A media recovery session encountered a table that was loaded
//          by the direct loader without logging any redo information. Some
//          or all of the blocks in this table are now marked as corrupt.
// *Action: The table must be dropped or truncated so that the corrupted
//          blocks can be reused. If a more recent backup of the file is
//          available, try to recover this file to eliminate this error.
00274, 00000, "illegal recovery option %s"
// *Cause:  An illegal option was specified for a recovery command.
// *Action: Correct the syntax and retry the command.
00275, 00000, "media recovery has already been started"
// *Cause: An attempt was made to start a second media recovery operation
//         in the same session.
// *Action: Complete or cancel the first media recovery session or
//            start another session to perform media recovery.
00276, 00000, "CHANGE keyword specified but no change number given"
// *Cause:  The CHANGE keyword was specified on the command line, but
//          no change number was given.
// *Action:  Retry the command using a valid change number after the CHANGE
//          keyword.
00277, 00000, "illegal option to the UNTIL recovery flag %s"
// *Cause:  Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the 
//          UNTIL keyword.
// *Action: Correct the syntax.
00278, 00000, "log file '%s' no longer needed for this recovery"
// *Cause:  The specified redo log file is no longer needed for the current
//          recovery.
// *Action: No action required. The archived redo log file may be removed
//          from its current location to conserve disk space, if needed.
//          However, the redo log file may still be required for another
//          recovery session in the future.
00279, 00000, "change %s generated at %s needed for thread %s"
// *Cause: The requested log is required to proceed with recovery.
// *Action:  Please supply the requested log with "ALTER DATABASE RECOVER
//           LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE
//           RECOVER CANCEL".
00280, 00000, "change %s for thread %s is in sequence #%s"
// *Cause:  This message helps to locate the redo log file with the
//          specified change number requested by other messages.
// *Action: Use the information provided in this message to specify the
//          required archived redo log files for other errors.
00281, 00000, "media recovery may not be performed using dispatcher"
// *Cause:  An attempt was made to use a dispatcher process for media
//          recovery. Memory requirements disallow this recovery method.
// *Action: Connect to the instance via a dedicated server process to
//          perform media recovery.
00282, 00000, "UPI %s call not supported, use ALTER DATABASE RECOVER"
// *Cause: The given UPI call is no longer supported.
// *Action: Use the ALTER DATABASE RECOVER command for all recovery actions.
00283, 00000, "recovery session canceled due to errors"
// *Cause: An error during recovery was determined to be fatal enough to end
//         the current recovery session.
// *Action: More specific messages will accompany this message. Refer to
//          the other messages for the appropriate action.
00284, 00000, "recovery session still in progress"
// *Cause: An error during recovery was determined to be minor enough to allow
//         the current recovery session to continue.
// *Action: More specific messages will accompany this message. Refer to
//          the other messages for the appropriate action.
00285, 00000, "TIME not given as a string constant"
// *Cause:  UNTIL TIME was not followed by a string constant for the time.
// *Action: Enter the time enclosed in single quotation marks.
00286, 00000, "no members available, or no member contains valid data"
// *Cause:  None of the members of a redo log file group are available, or
//          the available members do not contain complete data.
// *Action: If a member is temporarily offline, attempt to make it available.
//          Make sure that the correct filenames are being used, especially
//          if the redo log file is being accessed from a remote location.
00287, 00000, "specified change number %s not found in thread %s"
// *Cause:  The given change number does not appear in any of the online
//          redo logs for the given thread.
// *Action: Check the statement to make certain a valid change number
//          is given. Perhaps try to use the NEXT option for archiving logs.
00288, 00000, "to continue recovery type ALTER DATABASE RECOVER CONTINUE"
// *Cause:  During media recovery, a new log is not required but the
//          continuation command is necessary to do a checkpoint and
//          report errors.
// *Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
00289, 00000, "suggestion : %s"
// *Cause:  This message reports the next redo log filename that is needed,
//          according to the initialization parameters LOG_ARCHIVE_DEST and
//           LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST
//           and LOG_ARCHIVE_FORMAT are the same now as when the required redo
//          log file was archived.
// *Action: Consider using this filename for the next log needed for recovery.
00290, 00000, "operating system archival error occurred. See error below"
// *Cause:  While attempting to archive to a redo log file, the server
//          encountered an unexpected operating system error.
// *Action: Correct the operating system error given in the messages and
//          retry the operation. See also your operating system-specific
//          Oracle documentation.
00291, 0000, "numeric value required for PARALLEL option"
// *Cause:  A recovery command was specified incorrectly.  The PARALLEL option
//          must be followed by a numeric argument that specifies the degree
//          of parallelism.
// *Action: Re-enter the command with a numeric argument specifying the
//          degree of parallelism desired.
00292, 00000, "parallel recovery feature not installed"
// *Cause:  A parallel recovery was requested when the parallel
//          recovery option is not installed.
// *Action: Delete the PARALLEL clause from the RECOVER command. Also,
//          delete the RECOVERY_PARALLELISM parameter in the initialization
//          file.
00293, 00000, "control file out of sync with redo log"
// *Cause:  The redo log file and control file are out of sync because a
//          non-current controle file was specified when the instance
//          was started.
// *Action: Retry the RECOVER command using the current control file, or retry
//          the RECOVER command using the USING BACKUP CONTROLFILE clause.
00294, 00000, "invalid archivelog format specifier '%s'"
// *Cause:  An invalid format specifier was found in the LOG_ARCHIVE_FORMAT
//          initialization parameter.  The only characters permitted
//          following the % symbol are s, S, t, and T.
// *Action: Correct the initialization file and re-start the instance.
00295, 00000, "datafile/tempfile number %s is invalid, must be between 1 and %s"
// *Cause:  An invalid file number was specified.
// *Action: Specify a valid datafile or tempfile number
//          and retry the operation.
00296, 00000, "maximum number of files (%s) exceeded for RECOVER DATAFILE LIST"
// *Cause:  The RECOVER DATAFILE LIST command specified more datafiles than
//          are allowed by the DB_FILES initialization parameter.
//          This error occurs when doing recovery with Recovery Manager, and
//          the instance has been started with a DB_FILES parameter specifying
//          fewer datafiles than recovery manager needs to recover to satisfy
//          the user's RECOVER command.
// *Action: Re-start the instance with a higher value for DB_FILES.
00297, 00000, "must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START"
// *Cause:  The RECOVER DATAFILE START command was issued, but no RECOVER
//          DATAFILE LIST commands had been issued.  This only happens when
//          doing recovery with Recovery Manager, and is an internal error in
//          Recovery Manager, because Recovery Manager should always issue
//          RECOVER DATAFILE LIST before RECOVER DATAFILE START.
// *Action: Contact customer support
00298, 00000, "Missing or invalid attribute value"
// *Cause:  A non-zero integer value is required when the following keyword
//          attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
// *Action: Correct the syntax and retry the command.
00299, 00000, "must use file-level media recovery on data file %s"
// *Cause:  The control file does not contain an entry for this file, so
//          block media recovery cannot be done.
// *Action: Restore the data file and perform file-level media recovery.
/
/ 300..369 - Redo File errors
/
00300, 00000, "illegal redo log block size %s specified - exceeds limit of %s"
// *Cause:  The specified block size of the redo log is greater than the
//    maximum block size for the operating system.
// *Action: Create the redo log on a device with a smaller block size
00301, 00000, "error in adding log file '%s' - file cannot be created"
// *Cause:  The creation of the redo log file failed
// *Action: Check:       1) there is enough storage space on the device
//   2) the name of the file is valid
//   3) the device is online
//   4) an IO error occurred
// Also, it is possible REUSE was specified on the command line and
//         a file of the incorrect size exists. Either do not specify REUSE
//          or use a file of the correct size.
00302, 00000, "limit of %s logs exceeded"
// *Cause:  The maximum number of redo log files has been exceeded.
// *Action: Use the CREATE CONTROLFILE command with a larger value
//          for MAXLOGFILES if the compatibility is lower than 10.2.0.
//    Otherwise, allocate more storage space for the control file.
00303, 00000, "cannot process Parallel Redo"
// *Cause:  A redo log containing Parallel Redo has been detected.
//          The current Oracle release cannot process this format of redo.
// *Action: Use a later release that supports Parallel Redo.
//          to process this log.
00304, 00000, "requested INSTANCE_NUMBER is busy"
// *Cause:  An instance tried to start by using a value of the
//          initialization parameter INSTANCE_NUMBER that is already in use.
// *Action: Either
// a) specify another INSTANCE_NUMBER,
// b) shut down the running instance with this number
// c) wait for instance recovery to complete on the instance with
//    this number.
00305, 00000, "log %s of thread %s inconsistent; belongs to another database"
// *Cause:  The database ID in the redo log file does not match the database
//          ID in the control file. This redo log file is not from the
//          current database.
// *Action: Specify the correct redo log file, then retry the operation.
00306, 00000, "limit of %s instances in this database"
// *Cause:  Starting this instance would exceed the maximum number
// of instances allowed for this database.  This message occurs
// only with STARTUP shared and multiple instances.
// *Action: You cannot start more than the lower of
//    a) port-specific limit as to the number of instances
//    b) the number of instances specified at create-database time
00307, 00000, "requested INSTANCE_NUMBER out of range, maximum is %s"
// *Cause:  The initialization parameter INSTANCE_NUMBER specified a
//          number that was out of range.
// *Action: Change INSTANCE_NUMBER to a valid range and restart the
//          instance. The minimum value is one and the maximum value is
//          the lower of the operating system-specific maximum or
//          the MAXINSTANCES option specified in the CREATE DATABASE
//          statement. See also your operating system-specific Oracle
//          documentation.
00308, 00000, "cannot open archived log '%s'"
// *Cause:  The system cannot access a required archived redo log file.
// *Action: Check that the off line log exists, the storage device is
//          online, and the archived file is in the correct location.
//          Then attempt to continue recovery or restart the recovery
//          session.
00309, 00000, "log belongs to wrong database"
// *Cause:  The system cannot access the archived redo log because it
//          belongs to another database.
// *Action: Specify the correct redo log file, then retry the operation.
00310, 00000, "archived log contains sequence %s; sequence %s required"
// *Cause:  The archived log is out of sequence, probably because it
//          is corrupted or the wrong redo log filename was specified
/           during recovery.
// *Action: Specify the correct redo log file; then retry the operation.
00311, 00000, "cannot read header from archived log"
// *Cause:  An I/O error occurred when attempting to read the log file header
//          from the specified archived redo log file.
// *Action: Other messages will accompany this message. See the
//          associated messages for the appropriate action to take.
00312, 00000, "online log %s thread %s: '%s'"
// *Cause:  This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the
//          associated messages for the appropriate action to take.
00313, 00000, "open failed for members of log group %s of thread %s"
// *Cause:  The online log cannot be opened. May not be able to find file.
// *Action: See accompanying errors and make log available.
00314, 00000, "log %s of thread %s, expected sequence# %s doesn't match %s"
// *Cause:  The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00315, 00000, "log %s of thread %s, wrong thread # %s in header"
// *Cause:  The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00316, 00000, "log %s of thread %s, type %s in header is not log file"
// *Cause:  The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00317, 00000, "file type %s in header is not log file"
// *Cause:  This is not an archived log file.
// *Action: Find the correct file and try again.
00318, 00000, "log %s of thread %s, expected file size %s doesn't match %s"
// *Cause:  On header read the file size indicated in the control
//    file did not match the file size contained in the log file.
// *Action: Restore correct file or reset logs.
00319, 00000, "log %s of thread %s has incorrect log reset status"
// *Cause:  Check of log file header at database open found that an online
//          log has log reset data that is different from the control file.
//          The log is probably an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
00320, 00000, "cannot read file header from log %s of thread %s"
// *Cause:  The file is not available.
// *Action: Restore the log file.
00321, 00000, "log %s of thread %s, cannot update log file header"
// *Cause:  Cannot write to the log file.
// *Action: Restore the access to the file.
00322, 00000, "log %s of thread %s is not current copy"
// *Cause:  Check of log file header at database open found that an online
//          log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
00323, 00000, "Current log of thread %s not useable and all others need archiving"
// *Cause:  Attempt to open thread failed because it is necessary to switch
//          redo generation to another online log, but all the other logs
//          need to be archived before they can be used.
// *Action: Archive the logs for the thread then retry open.
00324, 00000, "log file '%s' translated name '%s' too long, %s characters exceeds %s limit"
// *Cause:  the translated name for a log file is too long.
// *Action: Choose a untranslated name that yields a shorter translated name.
00325, 00000, "archived log for thread %s, wrong thread # %s in header"
// *Cause:  The archived log is corrupted or for another thread. Can not
//          use the log for applying redo.
// *Action: Find correct archived log.
00326, 00000, "log begins at change %s, need earlier change %s"
// *Cause:  The archived log supplied for recovery was generated after the
//          log that is needed. Can not yet use the log for applying redo.
// *Action: Find correct archived log.
00327, 00000, "log %s of thread %s, physical size %s less than needed %s"
// *Cause:  A log file has shrunk in size. This is likely
//    to have been caused by operator or operating system error.
// *Action: Restore the log file from backup.  If backup is not available,
//    drop this log and re-create.  If the database was shut down
//    cleanly, no further action should be required; otherwise
//    incomplete recovery may be required.
00328, 00000, "archived log ends at change %s, need later change %s"
// *Cause:  The archived log supplied for recovery was generated before the
//          log that is needed. Can not use the log for applying redo.
// *Action: Find correct archived log.
00329, 00000, "archived log begins at change %s, need change %s"
// *Cause:  The archived log is not the correct log. An earlier log is needed.
// *Action: Restore the correct log file.
00330, 00000, "archived log ends at change %s, need change %s"
// *Cause:  The archived log is not the correct log. A later log is needed.
// *Action: Restore the correct log file.
00331, 00000, "log version %s incompatible with ORACLE version %s"
// *Cause:  The log was written by incompatible version of Oracle.
// *Action: Recover the database with the compatible software, shut it
//    down cleanly, then restart with current software.
00332, 00000, "archived log is too small - may be incompletely archived"
// *Cause:  The log is smaller than the space allocated in it. May be the
//          result of a shutdown abort while it was being written by the
//          archiver.
// *Action: Get a complete version of this log and use it for recovery. There
//          should either be an online version of it or a copy that was
//          successfully archived.
00333, 00000, "redo log read error block %s count %s"
// *Cause:  An IO error occurred while reading the log described in the
//          accompanying error.
// *Action: Restore accessibility to file, or get another copy of the file.
00334, 00000, "archived log: '%s'"
// *Cause:  Reporting filename for details of another error
// *Action: See associated error messages
00335, 00000, "online log %s: No log with this number, log does not exist"
// *Cause:  Reporting filename for details of another error
// *Action: See associated error messages
00336, 00000, "log file size %s blocks is less than minimum %s blocks"
// *Cause:  The log file size as specified in create database is too small.
// *Action: Increase the log file size.
00337, 00000, "log file '%s' does not exist and no size specified"
// *Cause:  An attempt to add a log found neither an existing file
//    nor a size for creating the file.
// *Action: Specify a size for the log file.
00338, 00000, "log %s of thread %s is more recent than control file"
// *Cause:  The control file change sequence number in the log file is
//         greater than the number in the control file. This implies that
//         the wrong control file is being used. Note that repeatedly causing
//         this error can make it stop happening without correcting the real
//         problem. Every attempt to open the database will advance the
//         control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to
//         make the control file current. Be sure to follow all restrictions
//         on doing a backup control file recovery.
00339, 00000, "archived log does not contain any redo"
// *Cause:  The archived log is not the correct log. It is a copy of a log file
//          that has never been used for redo generation, or was an online
//          log being prepared to be the current log.
// *Action: Restore the correct log file.
00340, 00000, "IO error processing online log %s of thread %s"
// *Cause:  An IO error occurred on the named online log.
// *Action: Restore accessibility to file, or restore file from backup.
00341, 00000, "log %s of thread %s, wrong log # %s in header"
// *Cause:  The internal information in an online log file does not
//    match the control file.
// *Action: Restore correct file or reset logs.
00342, 00000, "archived log does not have expected resetlogs SCN %s"
// *Cause:  Recovery was given a log that does not belong to current 
//          incarnation or one of the parent incarnation. There should be
//          another log that contains the correct redo.
// *Action: Supply the correct log file.
00344, 00000, "unable to re-create online log '%s'"
// *Cause:  An I/O failure occurred when attempting to re-create an online as
//          part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE
//          CLEAR LOGFILE command.
// *Action: Correct the file/device as indicated by accompanying errors.
00345, 00000, "redo log write error block %s count %s"
// *Cause:  An IO error has occurred while writing the log
// *Action: Correct the cause of the error, and then restart the system.
//    If the log is lost, apply media/incomplete recovery.
00346, 00000, "log member marked as STALE and closed"
// *Cause:  A log file member was no longer complete.
// *Action: Correct the underlying problem by referring to the other error
//          messages found with this one.
00347, 00000, "log %s of thread %s, expected block size %s doesn't match %s"
// *Cause:  On header read the blocksize indicated in the control
//    file did not match the blocksize contained in the log file.
// *Action: Restore correct file or reset logs.
00348, 00000, "single-process redo failure. Must abort instance"
// *Cause:  A failure occurred during a critical portion of the log code
//    during single process operation.  This error does not occur
//    during normal multi-process operation.
// *Action: Shutdown abort and warmstart the database.
00349, 00000, "failure obtaining block size for '%s'"
// *Cause:  The operating system was unable to determine the blocksize
//    for the given filename.
// *Action: Consult the accompanying error message, and correct the
//    device or specify another filename.
00350, 00000, "log %s of instance %s (thread %s) needs to be archived"
// *Cause:  The command cannot be done because the log has not been archived,
//          and media recovery has been enabled.
// *Action: Archive the log or disable media recovery. If the command supports
//          an UNARCHIVED option then it can be used. However this may result
//          in making backups unuseable, and forcing the drop of some offline
//          files.
00351, 00000, "recover-to time invalid"
// *Cause:  The time specified in a recover-until statement must
//    be after January 1st 1988.
// *Action: Specify a time after January 1st 1988.
00352, 00000, "all logs for thread %s need to be archived - cannot enable"
// *Cause:  Attempting to enable a thread with all logs needing to be
//          archived, and media recovery has been enabled. There is no log
//          that can be made the new current log for the thread.
// *Action: Archive a log for the thread or disable media recovery.
00353, 00000, "log corruption near block %s change %s time %s"
// *Cause:  Some type of redo log corruption has been discovered. This error
//          describes the location of the corruption. Accompanying errors
//          describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
//          recovery up to the indicated change or time.
00354, 00000, "corrupt redo log block header"
// *Cause:  The block header on the redo block indicated by the accompanying
//          error, is not reasonable.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.
00355, 00000, "change numbers out of order"
// *Cause:  A change number found in the redo log is lower than a previously
//          encountered change number. The log is corrupted in some way. The
//          corruption may be at the earlier change or at this one.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time.
00356, 00000, "inconsistent lengths in change description"
// *Cause:  A change record in the redo log contains lengths that do not add
//          up to a consistent value. The log is corrupted in some way.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time.
00357, 00000, "too many members specified for log file, the maximum is %s"
// *Cause:  An add logfile or add logfile member command would result in a
//          log with too many members.  The number of members is set when the
//          database is created.
// *Action: Use fewer log file members.
00358, 00000, "Too many file members specified, the maximum is %s"
// *Cause:  A create or alter statement specified too many members in a
//          parenthesised file list.
// *Action: Specify a number of file members that is within the port-defined
//          limit.
00359, 00000, "logfile group %s does not exist"
// *Cause:  An add logfile member or drop logfile request specified a logfile
//          group number that does not exist.
// *Action: Check the configuration of the log files and reissue the command.
00360, 00000, "not a logfile member: %s"
// *Cause:  A filename was given to drop logfile member that is not a
//          part of the database, or which is a data file.
// *Action: Supply a valid logfile member name.
00361, 00000, "cannot remove last log member %s for group %s"
// *Cause:  An attempt has been made to remove the last member of a log file
//          group.
// *Action: If desired, delete the entire log, by using DROP LOGFILE.
00362, 00000, "member is required to form a valid logfile in group %s"
// *Cause:  A request to drop a logfile member was denied because it would
//          remove data required to form a complete logfile.
// *Action: If desired, delete the entire log (after archiving if required),
//          by using DROP LOGFILE;
00363, 00000, "log is not the archived version"
// *Cause:  The log given to recovery is a backup of the online version from
//          the time it was the current log. The archived version of the log
//          would not be marked as end of thread. This error can also be
//          caused by failing to list the current log of an enabled thread
//          in a CREATE CONTROLFILE command.
// *Action: Find the archived version of the log and supply its name. If this
//          is media recovery immediately following a CREATE CONTROLFILE, be
//          sure the current log for this thread was included.
00364, 00000, "cannot write header to new log member"
// *Cause:  An i/o error occurred when attempting to write the header to a
//          log member that is being added to an existing group.
// *Action: See accompanying errors. Fix problem or use another file.
00365, 00000, "the specified log is not the correct next log"
// *Cause:  The specified log failed to pass checks to ensure it corresponds
//          to the log that was just applied.  This is probably the result
//          of using a log that was generated against a cold backup image
//          of the database.
// *Action: Find the log that was generated by this copy of the database
//          and give that filename to recovery.
00366, 00000, "log %s of thread %s, checksum error in the file header"
// *Cause:  The file header for the redo log contains a checksum that does
//          not match the value calculated from the file header as read from
//          disk. This means the file header is corrupted
// *Action: Find and install correct version of log or reset logs.
00367, 00000, "checksum error in log file header"
// *Cause:  The file header for the redo log contains a checksum that does
//          not match the value calculated from the file header as read from
//          disk. This means the file header is corrupted
// *Action: Find the correct file and try again.
00368, 00000, "checksum error in redo log block"
// *Cause:  The redo block indicated by the accompanying error, is not
//          vaild. It has a checksum that does not match the block contents.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time. If this happens when archiving,
//          archiving of the problem log can be skipped by clearing the log
//          with the UNARCHIVED option. This must be followed by a backup of
//          every datafile to insure recoverability of the database.
// *Action: Restore correct file or reset logs.
00369, 00000, "Current log of thread %s not useable and other log being cleared"
// *Cause:  Attempt to open thread failed because it is necessary to switch
//          redo generation to another online log, but all the other logs are
//          being cleared or need to be archived before they can be used.
// *Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then
//          wait for it to complete. Otherwise reissue the CLEAR command. If
//          there are other online logs for the thread, that are not being
//          cleared, then archive the logs.
/
/ 370-389 kcb external errors
/
00370, 00000, "potential deadlock during kcbchange operation"
// *Cause:  Error code used internally by software. Should never be reported
// *Action: Treat as internal error. See error 600.
00371, 00000, "not enough shared pool memory, should be atleast %s bytes"
// *Cause:  Init.ora parameter shared_pool_size is too small
// *Action: Increase the parameter value
00372, 00000, "file %s cannot be modified at this time"
// *Cause:  attempting to modify the contents of a file that cannot be
//          modified. The file is most likely part of a read only tablespace
//          but may be in the process of going offline, or the database may
//          be in the process of closing.
// *Action: check the status of the file and its tablespace
00373, 00000, "online log version %s incompatible with ORACLE version %s"
// *Cause:  The online log was written by incompatible version of Oracle.
//    Can occur when the log file was created by either a new or
//    older version of Oracle.
// *Action: Recover the database with the compatible software, shut it
//    down cleanly, then restart with current software.
00374, 00000, "parameter db_block_size = %s invalid ; must be a multiple of %s in the range [%s..%s]"
// *Cause:  invalid value for db_block_size parameter
// *Action: adjust parameter and restart
00375, 00000, "Cannot allocate buffer cache state object"
// *Document: NO
// *Cause: No state obeject elements on freelist
// *Action: None.
00376, 00000, "file %s cannot be read at this time"
// *Cause:  attempting to read from a file that is not readable. Most likely
//          the file is offline.
// *Action: Check the state of the file. Bring it online
00377, 00000, "Frequent backups of file %s causing write operation to stall"
// *Cause:  Backups are occurring too frequently on this file. Each time a new
//          backup is started for a file, any writes which have been previously
//          issued (but not completed) have to be re-issued. If hot backups
//          are started very, very frequently, it is possible that some writes
//          will be re-issued repeatedly and never complete.
// *Action: Increase the interval between begin hot-backup commands for this
//          file.
//
00378, 00000, "buffer pools cannot be created as specified"
// *Cause:  Either the number of buffers or the number of lru latches is
//          too small to satisfy the specified buffer pool configuration.
// *Action: Either increase the number of buffers and/or number of lru latches
//          or configure smaller buffer pools.
//
00379, 00000, "no free buffers available in buffer pool %s for block size %sK"
// *Cause:  All buffers in the specified buffer pool for the specified block size
//          are in use and no free buffers are available.
// *Action: Increase the number of buffers in the specified pool for the specified
//          block size
//
00380, 00000, "cannot specify db_%sk_cache_size since %sK is the standard block size"
// *Cause:  User specified the parameter db_nk_cache_size (where n is one of
//          2,4,8,16,32), while the standard block size for this database is
//          equal to n Kbytes. This is illegal.
// *Action: Specify the standard block size cache using db_cache_size (DEFAULT
//          pool) (and db_recycle_cache_size, db_keep_cache_size if additional
//          buffer pools are required). Do NOT use the corresponding
//          db_nk_cache_size parameter for the standard block size.
//
00381, 00000, "cannot use both new and old parameters for buffer cache size specification"
// *Cause:  User specified one or more of { db_cache_size ,
//          db_recycle_cache_size, db_keep_cache_size,
//          db_nk_cache_size (where n is one of 2,4,8,16,32),
//          db_cache_advice } AND one or more of { db_block_buffers,
//          buffer_pool_keep , buffer_pool_recycle }. This is illegal.
// *Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new
//          ones. Don't specify both. If old size parameters are specified in
//          the parameter file, you may want to replace them with new parameters
//          since the new parameters can be modified dynamically and allow
//          you to configure additional caches for additional block sizes.
//          Cache advisory can only be enabled with the new cache parameters. 
//
00382, 00000, "%s not a valid block size, valid range [%s..%s]"
// *Cause:  User specified a value for db_nk_cache_size where n is one of
//          {2, 4, 8, 16, 32}, but nk is not a valid block size for this
//          platform.
// *Action: Remove corresponding parameter from the "init.ora" file and
//          restart the instance.
00383, 00000, "DEFAULT cache for blocksize %s cannot be reduced to zero"
// *Cause:  User attempted to reduce db_cache_size to zero, or attempted to
//          to reduce db_<n>K_cache_size to zero while there were still online
//          tablespaces with blocksize <n>K. Note that since the SYSTEM tablespace
//          cannot be taken offline, it is always illegal to set db_cache_size to zero.
// *Action: Offline any tablespaces with the corresponding blocksize and then
//          perform the operation again.
00384, 00000, "Insufficient memory to grow cache"
// *Cause:  The system could not allocate sufficient memory to grow the
//          cache to the specified size.
// *Action: Attempt a smaller increase in the value of the parameter.
00385, 00000, "cannot enable Very Large Memory with new buffer cache parameters"
// *Cause:  User specified one or more of { db_cache_size ,
//          db_recycle_cache_size, db_keep_cache_size,
//          db_nk_cache_size (where n is one of 2,4,8,16,32) }
//          AND use_indirect_data_buffers is set to TRUE. This is illegal.
// *Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2)
//          parameters.
00386, 00000, "use_indirect_data_buffers not supported"
// *Cause:  The system could not allocate sufficient memory to grow the
//          cache to the specified size.
// *Action: Attempt a smaller increase in the value of the parameter.
00387, 00000, "version of the block on disk may be stale"
// *Document: NO
// *Cause: Error code used internally by software. Used during flashback
//         before image logging to to indicate that on-disk version of the 
//         block may be stale. This error is not expected to be user visible.
// *Action: None.
// 
//
/
/ 390-399: more Redo log errors
/
00390, 00000, "log %s of thread %s is being cleared, cannot become current log"
// *Cause:  An attempt to switch to a new online log for the redo thread
//          failed because no reusable log could be found. This log is being
//          cleared and will be useable when the clearing completes. The
//          command that began the clearing may have terminated without
//          completing the clearing.
// *Action: If the clear command is still executing then wait for its
//          completion. If it terminated then reissue the clear command, or
//          drop the log.
00391, 00000, "All threads must switch to new log format at the same time"
// *Cause:  An attempt to switch the current log of a single thread is not
//          allowed because the compatiblity requirements force a new log
//          format version number. When changing log formats, all threads
//          must switch to the new format at the same time.
// *Action: Open the database to cause the coordinated log switch. If that
//          is not possible then return to the same software version and
//          compatibility setting last used to open the database.
00392, 00000, "log %s of thread %s is being cleared, operation not allowed"
// *Cause:  An operation encountered this online log in the middle of being
//          cleared.  The command that began the clearing may have terminated
//          without completing the clearing.
// *Action: If the clear command is still executing then wait for its
//          completion. If it terminated then reissue the clear command, or
//          drop the log.
00393, 00000, "log %s of thread %s is needed for recovery of offline datafiles"
// *Cause:  Log cannot be cleared because the redo in it is needed to recover
//          offline datafiles. It has not been archived so there is no
//          other copy available. If the log is cleared the tablespaces
//          containing the files will have to be dropped.
// *Action: Archive the log then repeat the clear command. If archiving is not
//          possible, and dropping the tablespaces is acceptible, then add the
//          clause UNRECOVERABLE DATAFILE at the end of the clear command.
00394, 00000, "online log reused while attempting to archive it"
// *Cause:  It has been detected that an online log that is being archived
//          has been reused
// *Action: Cannot archive the logfile anymore since it has been overwritten
00395, 00000, "online logs for the clone database must be renamed"
// *Cause:  A clone database open forces logfile renaming to avoid
//          overwriting the primary logfiles
// *Action  Rename the logfiles manually or using the log_file_name_convert
//          initialization parameter
00396, 00000, "error %s required fallback to single-pass recovery"
// *Cause:  The indicated error caused two-pass instance or
//          crash recovery to fail.  Recovery was retried with an
//          alternate (slower) method to avoid the error.
// *Action  Correct the cause of the indicated error (also recorded)
//          so that future instance or crash recovery can succeed with the
//          two-pass algorithm. This usually requires making more main
//          memory available to the recovery process.
00397, 00000, "instance recovery process terminated with error"
// *Cause:  The foreground process doing instance recovery died. 
// *Action: Check the foreground trace file for the cause of recovery failure.
00398, 00000, "abort thread recovery due to reconfiguration"
// *Cause:  Global enqueue service reconfiguration occurred during
//          instance/crash recovery.
// *Action: This is used internally, no action is required.
00399, 0000, "corrupt change description in redo log"
// *Cause:  A change vector in the redo log failed validation checks.
// *Action: Do recovery with a good version of the log or do time based
//          recovery up to the indicated time.
/
/ 400-420: KCK errors
/
00400, 00000, "invalid release value %s for parameter %s"
// *Cause:  The release level given for the specified init parameter is
//          invalid.
// *Action: Correct the parameter value in the parameter file and retry.
00401, 00000, "the value for parameter %s is not supported by this release"
// *Cause:  The value specified cannot be supported by this release of
//          the software.
// *Action: Choose an appropriate value, or remove the parameter value to
//          use the default value.
00402, 00000, "database changes by release %s cannot be used by release %s"
// *Cause:  Changes have been made to the database that require a newer
//          software release or that violate the compatibility parameters.
// *Action: Use a version of the software that can understand the changes or
//          relax the compatibility requirements in the init file.
00403, 00000, "%s (%s) is not the same as other instances (%s)"
// *Cause:  Another instance has set the compatible or compatible no
//          recovery parameters differently than this instance.
// *Action: Change the parameters of the current instance to match other
//          instances already running.
00404, 00000, "Convert file not found: '%s'"
// *Cause:  The file used for converting the database from V7 to V8 could
//          not be found.
// *Action: Verify that the migration process has been started on this
//          database and that the convert filename is accessable.
00405, 00000, "compatibility type \"%s\""
// *Cause:  Reporting a type associated with another error.
// *Action: See accompanying error
00406, 00000, "COMPATIBLE parameter needs to be %s or greater"
// *Cause:  The COMPATIBLE initialization parameter is not high
//          enough to allow the operation. Allowing the command would make
//          the database incompatible with the release specified by the
//          current COMPATIBLE parameter.
// *Action: Shutdown and startup with a higher compatibility setting.
00407, 00000, "rolling upgrade from release %s.%s to %s.%s is not allowed"
// *Cause:  Another instance executing software at a different point release
//          already has the database mounted.
// *Action: Shutdown all instances then startup with the new software.
00408, 00000, "parameter %s is set to TRUE"
// *Cause:  Reporting the parameter that resulted in the compatibility error.
// *Action: Shutdown and startup with a higher compatibility setting.
00409, 00000, "COMPATIBLE needs to be %s or higher to use AUTO SEGMENT SPACE MANAGEMENT"
// *Cause:  This is due to migrating from an older release of Oracle with
//          tablespaces created using AUTO SEGMENT SPACE MANAGEMENT.
//          To open the database, the COMPATIBLE parameter needs to 
//          be set to the specified value.
// *Action: Shutdown and startup with the specified compatibility setting.
/
/ 436-439: Oracle licensing ercs
/
00436, 00000, "ORACLE is not licensed.  Contact Oracle Corp. for assistance"
// *Cause:
// *Action:
00437, 00000, "ORACLE feature is not licensed.  Contact Oracle Corp. for assistance"
// *Cause:  ORACLE feature is not licensed.
// *Action: Contact ORACLE for assistance.
00438, 00000, "%s Option not installed"
// *Cause:  The specified option is not installed.
// *Action: Purchase and install the option.
00439, 00000, "feature not enabled: %s"
// *Cause:  The specified feature is not enabled.
// *Action: Do not attempt to use this feature.
/
/ 440-460 Detached process startup errors
/
00443, 00000, "background process \"%s\" did not start"
// *Cause:  The specified process did not start.
// *Action: Ensure that the executable image is in the correct place with
//    the correct protections, and that there is enough memory.
00444, 00000, "background process \"%s\" failed while starting"
// *Cause:  Usually due to a bad (or non-existent) background process image.
// *Action: Get a good background process image.
00445, 00000, "background process \"%s\" did not start after %s seconds"
// *Cause:  The specified process did not start after the specified time.
// *Action: Ensure that the background did not die and leave a trace file.
00446, 00000, "background process started when not expected"
// *Cause:  The background process specified started up AFTER the RDBMS was
//    already running.
// *Action: If nobody at your site started the process, then this is an
//    internal error.
00447, 00000, "fatal error in background process"
// *Cause:  One of the background processes died unexpectedly.
// *Action: Warm start the system.
00448, 00000, "normal completion of background process"
// *Cause:  One of the background processes completed normally (i.e. exited).
//   The background process thinks that somebody asked it to exit.
// *Action: Warm start the system.
00449, 00000, "background process '%s' unexpectedly terminated with error %s"
// *Cause:  A foreground process needing service from a background
//    process has discovered the process died.
// *Action: Consult the error code, and the trace file for the process.
00450, 00000, "background process '%s' did not start"
// *Cause:  The specified process did not start.
// *Action: Consult the error code, and the trace file for the process.
00451, 00000, "foreground process died unexpectedly"
// *Cause: The foreground process for the new connection did not start.
// *Action: Reconnect to Oracle.
00452, 00000, "foreground process unexpectedly terminated with error %s"
// *Cause: The foreground process for the new connection did not start.
// *Action: Reconnect to Oracle.
00453, 00000, "backgroud process '%s' is dead"
// *Cause: The background process that was being messaged was dead 
//         or its incarnation was invalid.
// *Action: Restart the background process.
/
/ 469-486 Detached process death errors (signaled in foreground)
/
00469, 00000, "CKPT process terminated with error"
// *Cause:  The checkpoint process died
// *Action: Warm start instance
00470, 00000, "LGWR process terminated with error"
// *Cause:  The log writer process died
// *Action: Warm start instance
00471, 00000, "DBWR process terminated with error"
// *Cause:  The database writer process died
// *Action: Warm start instance
00472, 00000, "PMON  process terminated with error"
// *Cause:  The process cleanup process died
// *Action: Warm start instance
00473, 00000, "ARCH process terminated with error"
// *Cause:  The archive process died
// *Action: Warm start instance
00474, 00000, "SMON process terminated with error"
// *Cause:  The system cleanup process died
// *Action: Warm start instance
00475, 00000, "TRWR process terminated with error"
// *Cause:  The system tracing process died
// *Action: Warm start instance
00476, 00000, "RECO process terminated with error"
// *Cause:  The distributed transaction (two-phase commit) recovery process
//          died.
// *Action: Warm start instance
00477, 00000, "SNP* process terminated with error"
// *Cause:  A materialized view refresh process died
// *Action: PMON will restart SNP process shortly.  If SNP process does not
//          get started, contact Oracle support.
00478, 00000, "SMON process terminated due to error %s"
// *Cause: SMON was unable to service the requests due to error in 
//         cleanup of resources
// *Action: Warm start instance
00479, 00000, "RVWR process terminated with error %s"
// *Cause:  The RVWR process died
// *Action: Warm start instance
00480, 00000, "LCK* process terminated with error"
// *Cause:  A system lock process died
// *Action: Warm start instance
00481, 00000, "LMON process terminated with error"
// *Cause:  The global enqueue service monitor process died
// *Action: Warm start instance
00482, 00000, "LMD* process terminated with error"
// *Cause:  A global enqueue service daemon process died
// *Action: Warm start instance
00483, 00000, "During shutdown a process abnormally terminated"
// *Cause: One of the background processes did not exit normally at or near
//    the time of shutdown.
// *Action: Use shutdown abort.
00484, 00000, "LMS* process terminated with error"
// *Cause:  A global cache service process died
// *Action: Warm start instance
00485, 00000, "DIAG process terminated with error %s"
// *Cause:  A global diagnostic process died
// *Action: Wait for process to restart
00486, 00000, "ASMB process terminated with error"
// *Cause:  An ASM background process died.
// *Action: Warm start instance.  Also check that ASM Instance is running.
00487, 00000, "CTWR process terminated with error"
// *Cause:  The change tracking process died
// *Action: Warm start instance
00488, 00000, "RBAL process terminated with error"
// *Cause:  The ASM rebalance coordinator process died.
// *Action: Warm start instance.
00489, 00000, "ARB* process terminated with error"
// *Cause:  An ASM rebalance worker process died.
// *Action: Wait for process to restart.
00490, 00000, "PSP process terminated with error"
// *Cause:  The process spawner died
// *Action: Warm start instance
00491, 00000, "RMS0 process terminated with error"
// *Cause:  The RAC Management Process died
00492, 00000, "GTX* process terminated with error"
// *Cause:  A global transaction background process died.
// *Action: Warm start instance
00493, 00000, "GMON process terminated with error"
// *Cause:  The ASM disk group monitor process died
// *Action: Warm start instance
00494, 00000, "enqueue %s held for too long (more than %s seconds) by 'inst %s, osid %s'"
// *Cause:  The specified process did not release the enqueue within
//          the maximum allowed time.
// *Action: Reissue any commands that failed and contact Oracle Support
//          Services with the incident information.
00495, 00000, "GEN0 process terminated with error"
// *Cause:  The generic background processing process died.
// *Action: Warm start the instance.
00496, 00000, "LMHB process terminated with error"
// *Cause:  The LM heartbeat monitor process died.
// *Action: Warm start the instance.
00497, 00000, "XDMG process terminated with error"
// *Cause:  The Cell automation manager process terminated with error.
// *Action: PMON will restart XDMG process shortly.  If XDMG process does not
//          restart, contact Oracle Support Services.
00498, 00000, "XDWK process terminated with error"
// *Cause:  The Cell automation worker actions process terminated with error.
// *Action: PMON will restart XDWK process shortly.  If XDWK process does not
//          restart, contact Oracle Support Services.
00499, 00000, "XDMG repeatedly failed to initialize terminating the instance."
// *Cause:  The Cell automation manager process repeatedly failed to
//          initialize.
// *Action: Examine the alert log for the reason prior attempts to start
//          XDMG failed. If it is due to user error or bad configuration,
//          fix it and restart the instance. Otherwise, contact Oracle
//          Support Services.
/
/ 00500-00565
/
00566, 00000, "cannot request processor group - NUMA not enabled"
// *Cause:  Cannot start process in a requested processor group when
//          the NUMA feature is disabled.
// *Action: Start the process without requesting a NUMA processor group.
/
00567, 00000, "Requested processor group %s is too large (maximum %s)"
// *Cause:  The process could not be started in the requested processor group.
// *Action: Start the process in another processor group.
/
00568, 00000, "Maximum number of interrupt handlers exceeded"
// *Cause: User specified too many ^c handlers
// *Action: Remove some old handlers.
/
00569, 00000, "Failed to acquire global enqueue."
// *Cause:  A prior error occurred on one of the instances in the cluster. 
//          Typically errors are caused by shared pool resource contention.
// *Action: Check for and resolve prior errors on all instances in the cluster.
//          If there is shared pool resource contention, increase the 
//          SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, 
//          CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization 
//          parameters.
/
/ 00570-00599 SQL*Connect Opening & Reading Files
/
00574, 00000, "osndnt: $CANCEL failure (break)"
// *Cause:
// *Action:
00575, 00000, "osndnt: $QIO failure (send out-of-band break)"
// *Cause:
// *Action:
00576, 00000, "in-band break protocol error"
// *Cause:
// *Action:
00577, 00000, "out-of-band break protocol error"
// *Cause:
// *Action:
00578, 00000, "reset protocol error"
// *Cause:
// *Action:
00579, 00000, "osndnt: server received malformed connection request"
// *Cause:
// *Action:
00580, 00000, "protocol versions do not match"
// *Cause:
// *Action:
00581, 00000, "osndnt: cannot allocate context area"
// *Cause:
// *Action:
00582, 00000, "osndnt: cannot deallocate context area"
// *Cause:
// *Action:
00583, 00000, "osndnt: $TRNLOG failure"
// *Cause:
// *Action:
00584, 00000, "cannot close connection"
// *Cause:
// *Action:
00585, 00000, "host name has incorrect form"
// *Cause:
// *Action:
00586, 00000, "osndnt: LIB$ASN_WTH_MBX failure"
// *Cause:
// *Action:
00587, 00000, "cannot connect to remote host"
// *Cause:
// *Action:
00588, 00000, "message from host was too short"
// *Cause:
// *Action:
00589, 00000, "message from host had incorrect data length"
// *Cause:
// *Action:
00590, 00000, "message from host had incorrect message type"
// *Cause:
// *Action:
00591, 00000, "incorrect number of bytes written"
// *Cause:
// *Action:
00592, 00000, "osndnt: $QIO failure (mailbox queue)"
// *Cause:
// *Action:
00593, 00000, "osndnt: $DASSGN failure (network device)"
// *Cause:
// *Action:
00594, 00000, "osndnt: $DASSGN failure (mailbox)"
// *Cause:
// *Action:
00595, 00000, "osndnt: $QIO failure (receive)"
// *Cause:
// *Action:
00596, 00000, "osndnt: $QIO failure (send)"
// *Cause:
// *Action:
00597, 00000, "osndnt: $QIO failure (mailbox requeue)"
// *Cause:
// *Action:
00598, 00000, "osndnt: $QIO failure (mailbox read)"
// *Cause:
// *Action:
00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: This is the generic internal error number for Oracle program
//         exceptions. It indicates that a process has encountered a low-level,
//         unexpected condition. The first argument is the internal message 
//         number. This argument and the database version number are critical in
//         identifying the root cause and the potential impact to your system.
// 
// *Action: Visit My Oracle Support to access the ORA-00600 Lookup tool
//          (reference Note 600.1) for more information regarding the specific
//          ORA-00600 error encountered.
//
//          An Incident has been created for this error in the Automatic 
//          Diagnostic Repository (ADR). When logging a service request, use 
//          the Incident Packaging Service (IPS) from the Support Workbench
//          or the ADR Command Interpreter (ADRCI) to automatically package the
//          relevant trace information (reference My Oracle Support Note 411.1).
//
//          The following information should also be gathered to help determine 
//          the root cause:
//             - changes leading up to the error
//             - events or unusual circumstances leading up to the error
//             - operations attempted prior to the error
//             - conditions of the operating system and databases at the time 
//               of the error
//
//          Note: The cause of this message may manifest itself as different 
//          errors at different times. Be aware of the history of errors that 
//          occurred before this internal error.
00601, 00000, "cleanup lock conflict"
// *Cause:  PMON process runs into lock conflict trying to recovery processes
// *Action: This is trapped internally, no action necessary
00602, 00000, "internal programming exception"
// *Cause:  Internal programming exception
// *Action: Report as bug
/ Caution: following error code not relocatable
00603, 00000, "ORACLE server session terminated by fatal error"
// *Cause:  An ORACLE server session was in an unrecoverable state.
// *Action: Login to ORACLE again so a new server session will be created
/           automatically.  Examine the session trace file for more
/           information.
00604, 00000, "error occurred at recursive SQL level %s"
// *Cause:  An error occurred while processing a recursive SQL statement
//   (a statement applying to internal dictionary tables).
// *Action: If the situation described in the next error on the stack
//   can be corrected, do so; otherwise contact Oracle Support.
/
/0605     reserved for v2 compatibility
/
00606, 00000, "Internal error code"
// *Cause:  A call to deferred upi functions was made in non deferred mode
// *Action: Report as a bug.
00607, 00000, "Internal error occurred while making a change to a data block"
// *Cause:  An internal error or memory exception occurred while Oracle was
//          applying redo to a data block.
// *Action: call Oracle Support
00608, 00000, "testing error [%s] [%s] [%s] [%s] [%s]"
// *Cause:  Internal error reserved for testing.
// *Action: call Oracle Support
00609, 00000, "could not attach to incoming connection"
// *Cause:  Oracle process could not answer incoming connection
// *Action: If the situation described in the next error on the stack
//         can be corrected, do so; otherwise contact Oracle Support.
00610, 00000, "Internal error code"
// *Cause:  Oracle process started too late
// *Action: This error should never be seen by the customer. Contact
//          Oraclce Support
00700, 00000, "soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause:  Internal inconsistency that will not crash a process
// *Action: Report as a bug - the first argument is the internal error.
00701, 00000, "object necessary for warmstarting database cannot be altered"
// *Cause:  Attempt to alter or drop a database object (table, cluster, or
//    index) which are needed for warmstarting the database.
// *Action: None.
00702, 00000, "bootstrap verison '%s' inconsistent with version '%s'"
// *Cause:  The reading version of the boostrap is incompatible with
//          the current bootstrap version.
// *Action: Restore a version of the software that is compatible with this
//          bootstrap version.
00703, 00000, "maximum number of row cache instance locks exceeded"
// *Cause:  There are not enough row cache enqueues.
// *Action: Increase the row cache enqueue parameter and warm start the system.
00704, 00000, "bootstrap process failure"
// *Cause:  Failure in processing bootstrap data - see accompanying error.
// *Action: Contact your customer support representative.
00705, 00000, "inconsistent state during start up; shut down the instance, then restart it"
// *Cause:  A previous attempt to start an instance was terminated.
// *Action: Shut down the instance completely, then restart it.
00706, 00000, "error changing format of file '%s'"
// *Cause:  An attempt to change the block0 format of the specified file
//          failed because the file is read-only or offline.
// *Action: Make the file read-write or bring the file online and set
//          the BLK0_FMTCHG event.
/
/ 00710 - 00719 reserved for tablespace rename feature
/
00710, 00000, "new tablespace name is the same as the old tablespace name"
// *Cause:  An attempt to rename a tablespace failed because the new
//          name is the same as the old name.
// *Action: No action required.
00711, 00000, "new tablespace name is invalid"
// *Cause:  An attempt to rename a tablespace failed because the new name
//          is invalid.
// *Action: Choose a valid new name and retry the command.
00712, 00000, "cannot rename system tablespace"
// *Cause:  An attempt to rename the system tablespace failed.
// *Action: No action required.
/
/  event 720 - 739 is reserved for compatibility issues
/
00720, 00000, "ALTER DATABASE RESET COMPATIBILITY command has been de-supported"
// *Cause:  ALTER DATABASE RESET COMPATIBILITY command has been de-supported
//          since Oracle 10i.
// *Action: No action required.
00721, 00000, "changes by release %s cannot be used by release %s"
// *Cause:  An attempt to import a tablespace failed because the tablespace
//          contains changes that require a newer software release or that 
//          violate the compatibility parameters.
// *Action: Use a version of the software that can understand the changes or
//          relax the compatibility requirements in the initialization 
//          parameter file.
00722, 00000, "Feature \"%s\""
// *Cause:  Reporting name of the feature for details of another error.
// *Action: See associated error message.
00723, 00000, "Initialization parameter COMPATIBLE must be explicitly set"
// *Cause:  Oracle detected that the initialization parameter COMPATIBLE was
//          not explicitly specified, and the compatibility of the database is
//          lower than the default value of the COMPATIBLE parameter. In order
//          to use the new compatible setting, the intialization parameter
//          must be explicitly set by the user.
// *Action: Explicitly set the value of COMPATIBLE parameter either in PFILE
//          or SPFILE, whichever is used.
00724, 00000, "ALTER DATABASE CONVERT command has been de-supported"
// *Cause:  ALTER DATABASE CONVERT command has been de-supported since 
//          Oracle 10i.
// *Action: No action required.
00725, 00000, "Desupported ALTER DATABASE SET STANDBY clause specified: %s"
// *Cause:  A deprecated ALTER DATABASE SET STANDBY was specified.
// *Action: No action required.
/
/  event 740 - 741 is reserved for file size overflow issues
/
00740, 00000, "datafile size of (%s) blocks exceeds maximum file size"
// *Cause:  The user specified datafile size exceeded maximum file size.
// *Action: Please check REFERENCE for maximum size.  Reduce the size and retry.
00741, 00000, "logfile size of (%s) blocks exceeds maximum logfile size"
// *Cause:  The user specified logfile size exceeded maximum logfile size.
// *Action: Please check REFERENCE for maximum size.  Reduce the size and retry.
/
/  event 742 - 815 is reserved for recovery issues
/
00750, 00000, "database has been previously mounted and dismounted"
// *Cause:  The instance has already mounted and dismounted the database,
//          which is only allowed once in its lifetime. 
// *Action: Shut down the database. 
00751, 00000, "could not obtain resilvering status for file"
// *Cause: An error occurred while obtaining the mirror resilvering status
//         of a file.
// *Action: Refer to other error messages shown for additional details of
//          the problem.
00752, 00000, "recovery detected a lost write of a data block"
// *Cause: A write of a data block to storage was lost during
//         normal database operation on the primary database.
// *Action: Shutdown the primary database and activate the physical standby
//          database to failover. See the Data Guard Concepts and Administration
//          guide for details.
00816, 00000, "error message translation failed"
// *Cause:
// *Action:
/
/ event 820-850 reserved for sga auto management issues
00820, 00000, "Specified value of sga_max_size is too small, needs to be at least %sM"
// *Cause: The specified value of sga_max_size is too small for the SGA to
//         accommodate all of the necessary SGA components such as the 
//         log buffer, buffer pools, shared pool, etc. 
// *Action: Set sga_max_size to the recommended value or reduce the values
//          of any SGA component size parameters you have specified. 
00821, 00000, "Specified value of sga_target %sM is too small, needs to be at least %sM"
// *Cause: The specified value of sga_target is too small for the SGA to
//         accommodate all of the necessary SGA components such as the 
//         log buffer, buffer pools, shared pool, etc. 
// *Action: Set sga_target to the recommended value or reduce the values
//          of any SGA component size parameters you have specified. 
00822, 00000, "MMAN process terminated with error"
// *Cause: The Memory Management process died.
// *Action: Warm start instance
00823, 00000, "Specified value of sga_target greater than sga_max_size"
// *Cause: The specified value of sga_target is greater than sga_max_size.
// *Action: Increase sga_max_size to match up with sga_target or decrease
//          sga_target to match up with sga_maxsize.
00824, 00000, "cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings"
// *Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings.
// *Action: Check the other error messages for additional information.
00825, 00000, "cannot set DB_BLOCK_BUFFERS if SGA_TARGET or MEMORY_TARGET is set"
// *Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.
// *Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters, 
//          and do not use DB_BLOCK_BUFFERS which is an old cache parameter.
00826, 00000, "cannot set SGA_TARGET or MEMORY_TARGET for an ASM instance"
// *Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance.
// *Action: Do not set SGA_TARGET or MEMORY_TARGET.
00827, 00000, "could not shrink sga_target to specified value"
// *Cause: Attempted to shrink the SGA to the specified value but did not
//         succeed because the SGA components could not be shrunk as they
//         were already at their minimum sizes.
// *Action: Do not set sga_target to a value below the current value without
//          first shrinking the individual SGA components.
00828, 00000, "specified value of shared_pool_reserved_size inconsistent with internal settings"
// *Cause: Unable to set shared_pool_reserved_size to specified value if
//         SGA_TARGET set, either because the specified value is too
//         small, or because it is too large for the current internal
//         size of shared pool. More details can be found in the alert log.
// *Action: If possible, do not set shared_pool_reserved_size without setting
//         shared_pool_size if SGA_TARGET set. Examine the alert log for
//         information about current internal size of shared pool, and valid
//         range of values for shared_pool_reserved_size.
00829, 00000, "event to stress test self tuning SGA feature by forcing partial granules transfers"
// *Document: NO
// *Cause:
// *Action:
00830, 00000, "cannot set statistics_level to BASIC with auto-tune SGA enabled"
// *Cause: The user attempted to set statistics_level to BASIC with auto-tune
//         SGA enabled which cannot be done because auto-tune SGA cannot work
//         with statistics_level set to BASIC.
// *Action: Disable auto-tune SGA and try setting the statistics_level to
//          BASIC again.
00831, 00000, "event to stress test self tuning SGA feature by doing random memory broker resizes"
// *Document: NO
// *Cause:
// *Action:
00832, 00000, "no streams pool created and cannot automatically create one"
// *Cause: A database feature which needs STREAMS SGA was being used, however,
//         the streams_pool_size parameter was not defined and the value of 
//         db_cache_size was too small to permit an automatic transfer of SGA
//         to the streams pool from the buffer cache.
// *Action: Please set the parameter streams_pool_size or set SGA_TARGET.
00833, 00000, "event to test cancellation and cache protection by pinning buffers for deferred mode requests"
// *Document: NO
// *Cause:
// *Action:
00834, 00000, "Simulate 4031 during an immediate mode request in auto-sga"
// *Document: NO
// *Cause:
// *Action: Set _memory_management_tracing=23 to track this event.
00835, 00000, "Simulate memory broker disabling for code coverage"
// *Document: NO
// *Cause:
// *Action: It will be reenabled on next SGA_TARGET resize
00836, 00000, "Simulate memory transfer from system memory for startup request"
// *Document: NO
// *Cause: For code coverage.
// *Action: None.
00837, 00000, "Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET"
// *Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET.
// *Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET.
00838, 00000, "Specified value of MEMORY_TARGET is too small, needs to be at least %sM"
// *Cause: The specified value of MEMORY_TARGET was less than the sum of the 
//         specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
// *Action: Set MEMORY_TARGET to at least the recommended value.
00839, 00000, "SGA_TARGET cannot be modified to the specified value"
// *Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
// *Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low.
00840, 00000, "PGA_AGGREGATE_TARGET cannot be modified to the specified value"
// *Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
// *Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
00841, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: MEMORY_TARGET parameter was not supported on this system as 
//         shmfs was disabled.
// *Action: Refer to documentation for a list of supported systems.
00842, 00000, "DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or MEMORY_TARGET"
// *Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET.
// *Action: Remove the incompatible parameter setting.
00843, 00000, "Parameter not taking MEMORY_MAX_TARGET into account"
// *Cause: The parameter was larger than MEMORY_MAX_TARGET.
// *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET.
00844, 00000, "Parameter not taking MEMORY_TARGET into account"
// *Cause: The parameter was larger than MEMORY_TARGET.
// *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_TARGET.
00845, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
// *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
00846, 00000, "could not shrink MEMORY_TARGET to specified value"
// *Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not
//         succeed because the PGA and SGA components could not be shrunk.
// *Action: Do not set MEMORY_TARGET to a value below the current value without
//          first shrinking the individual memory components.
00847, 00000, "MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA cannot be set together"
// *Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set
// *Action:Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to TRUE.
00848, 00000, "STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET"
// *Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET.
// *Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL or ALL to use SGA_TARGET or MEMORY_TARGET.
00849, 00000, "SGA_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s."
// *Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.
// *Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET.
00850, 00000, "PGA_AGGREGATE_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s."
// *Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value.
// *Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET.
00851, 00000, "SGA_MAX_SIZE %s cannot be set to more than MEMORY_TARGET %s."
// *Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.
// *Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET.
00852, 00000, "Rolling migration monitor process terminated."
// *Cause:  The ASM rolling migration monitor process died.
// *Action: Warm start the instance.
/ MODIFIED
/   smangala  03/28/11 - Backport 11679567: correct 1280 action
/   avaliani  04/09/10 - reuse ORA-01088
/   sslim     02/16/10 - Add 1379 testing event
/   ineall    08/12/09 - Bug 8658899: Add ORA-1366: failed to find all redo
/                        logs required for terminal apply
/   jjlee     03/03/09 - change 1110 and 1156
/   yohu      11/20/08 - update 1086
/   aamor     10/02/08 - bug 6793044: update 976 error
/   rlong     09/25/08 - 
/   smangala  09/17/08 - bug7114186: fix PSBY terminal log handling
/   shsong    08/07/08 - 
/   jgalanes  08/06/08 - Add 1362 and 1363 for invalid parameters to mine_value
/                        & column_present
/   jjlee     07/15/08 - comment change
/   shsong    03/05/08 - Update 1188
/   jgalanes  01/11/07 - Add 1357 & 1358 for LogMiner logs version < dictionary
/                        version
/   gviswana  10/13/06 - Update Cause, Action for 980
/   smangala  09/21/04 - update 1345 text and remove unused messages
/   jgalanes  09/14/06 - Add error # 1339 for LogMiner build error
/   abrown    05/10/06 - add KRVX_STATUS_UNSUPPORTED_DDL 
/   abrown    06/08/05 - bug 3776830: unwind dictionary 
/   mtao      03/25/05 - add 1375/1376, Reader detected redo log corruption
/   gmulagun  02/20/05 - bug 4140708 cannot audit SYS users
/   mjstewar  01/26/05 - Add 1148 
/   psuvarna  09/28/04 - #3909055: rectify error message ORA-01438
/   jnesheiw  11/04/04 - Add global name mismatch error 
/   abrown    08/04/04 - better error msg when supplemental logging off 
/   jnesheiw  05/06/04 - revise 1341 
/   smangala  04/16/04 - add 1346: LogMiner missed a branch 
/   jnesheiw  03/01/04 - fix tense in 1329
/   lilin     01/21/04 - add 912 input too long 
/   jwlee     11/16/03 - fix typo in ORA-1167 
/   abrown    08/26/03 - fix logmnr 9i specific actions 
/   banand    02/27/03 - bug 2707377
/   jkundu    12/06/02 - change log-based replication to Streams
/   sdizdar   10/28/02 - 
/   molagapp  07/26/02 - recovery area project
/   rjanders  10/02/02 - Enhance 1154 cause/action
/   dvoss     10/07/02 - add 1355 and 1356
/   rjenkins  07/31/02 - reuse 911 for alternative quotes
/   ajadams   05/30/02 - purge unused LogMiner messages
/   rjanders  05/24/02 - Fix ORA-1126 message.
/   mtao      06/04/02 - logminer message 1301
/   ajadams   05/28/02 - LogMiner 10i status enhancements
/   mdilman   05/09/02 - DB begin/end backup: change 1140, 1232 and 1260
/   molagapp  04/23/02 - change 1264, 1269
/   bgarin    08/05/02 - Change text for logminer corrupt redo log
/   jkundu    01/23/02 - logminer error messages 1373, 1374
/   jkundu    11/20/01 - adding logminer error message
/   abrown    10/23/01 - dbms_logmnr_d.set_tablespace needs real error msgs
/   tcondie   11/07/01 - grabtrans 'ycao_ora904'
/   ycao      11/05/01 - change ora-904 message
/   aime      10/09/01 -
/   ajadams   10/08/01 - logminer messages
/   asundqui  10/04/01 - bug 2029014: added 1279
/   tcondie   10/18/01 - Modify ORA-932 to take 2 args.
/   mjstewar  08/28/01 - Add file name to ORA-1276
/   qiwang    08/08/01 - more logmnr error msg
/   bsinha    08/02/01 - extend 1010 for autonomous txn
/   smangala  07/02/01 - add 1344.
/   ygu       06/18/01 - add more err msg for logminer
/   qiwang    06/04/01 - more logmnr error msgs
/   eyho      07/26/01 - remove obsoleted messages
/   mdilman   07/02/01 - bug 1815522: added 1277, 1278
/   msusaira  06/14/01 - modify 1257 error mesg
/   mjstewar  04/04/01 - New OMF message.
/   jingliu   03/06/01 - fix error in message 1298, 1466
/   eyho      03/06/01 - RAC name changes
/   dgprice   01/11/01 - bug 1394096 define buffer size limits error
/   yuli      01/18/01 - 1539879: change Cause and Action part of 1114
/   amsrivas  12/12/00 - 1029386: modify 1153 - resetlogs/backup conflict.
/   mjstewar  12/13/00 - Automated standby file management
/   nlee      11/13/00 - Forward merge fix for bug 553250.
/   gkulkarn  10/30/00 - Add LogMiner Out-of-Memory Error
/   rpang     09/15/00 - Updated the cause of "unsupported character set" error
/   yuli      10/24/00 - Update message of 1092
/   gkulkarn  08/01/00 - Reserve more error numbers for LogMiner
/   ajadams   07/07/00 - logminer dictionary message
/   aime      06/29/00 - Fix compile error
/   mjstewar  06/13/00 - OMF errors
/   ajadams   06/26/00 - even more Logminer errors
/   ajadams   06/21/00 - more LogMiner messages
/   jkundu    06/09/00 - adding Logminer trace event
/   apareek   04/14/00 - change 1162 text
/   gkulkarn  05/14/00 - Update Error #01312
/   rjenkins  03/29/00 - change 1441
/   ajadams   03/31/00 - add error code 1315 for logmnr
/   robermar  04/18/00 - Inspection Comments
/   apadmana  01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW
/   gkulkarn  02/01/00 - Add LogMiner sql function error messgaes
/   mjstewar  01/18/00 - Automatic removal of OS files.
/   robermar  01/27/00 - DB End Backout
/   msusaira  12/19/99 - add err 1257
/   vsrihari  07/14/99 - add file locks error message
/   jkundu    07/06/99 - adding more LogMiner messages
/   nireland  04/14/99 - Imporove action text for ORA-1220. #863107
/   swerthei  10/28/98 - noarchivelog -> NOARCHIVELOG in 1108
/   swerthei  10/20/98 - modify 1108 for bug 719176 - online/backup conflict
/   vsrihari  08/29/98 - modifying file identify error message
/   fsanchez  08/19/98 - fix_kcv_mig                                           
/   mcusson   05/29/98 - adding error message for LogMiner
/   swerthei  04/21/98 - messages for Oracle-managed hot-backup mode
/
/ 900-999 parse errors -
/ carried over from V5 - desirable to add arguments wherever possible
/
00900, 00000, "invalid SQL statement"
// *Cause:
// *Action:
00901, 00000, "invalid CREATE command"
// *Cause:
// *Action:
00902, 00000, "invalid datatype"
// *Cause:
// *Action:
00903, 00000, "invalid table name"
// *Cause:
// *Action:
00904, 00000, "%s: invalid identifier"
// *Cause:
// *Action:
00905, 00000, "missing keyword"
// *Cause:
// *Action:
00906, 00000, "missing left parenthesis"
// *Cause:
// *Action:
00907, 00000, "missing right parenthesis"
// *Cause:
// *Action:
00908, 00000, "missing NULL keyword"
// *Cause:
// *Action:
00909, 00000, "invalid number of arguments"
// *Cause:
// *Action:
00910, 00000, "specified length too long for its datatype"
// *Cause: for datatypes CHAR and RAW, the length specified was > 2000;
//         otherwise, the length specified was > 4000.
// *Action:  use a shorter length or switch to a datatype permitting a
//           longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
00911, 00000, "invalid character"
// *Cause: identifiers may not start with any ASCII character other than
//         letters and numbers.  $#_ are also allowed after the first
//         character.  Identifiers enclosed by doublequotes may contain
//         any character other than a doublequote.  Alternative quotes 
//         (q'#...#') cannot use spaces, tabs, or carriage returns as 
//         delimiters.  For all other contexts, consult the SQL Language 
//         Reference Manual.
// *Action:
00912, 00000, "input parameter too long"
// *Cause: one of your input strings was too long
// *Action:shorten the input parameter length
00913, 00000, "too many values"
// *Cause:
// *Action:
00914, 00000, "missing ADD keyword"
// *Cause:
// *Action:
00915, 00000, "network access of dictionary table not currently allowed"
// *Cause:
// *Action:
00917, 00000, "missing comma"
// *Cause:
// *Action:
00918, 00000, "column ambiguously defined"
// *Cause:
// *Action:
00919, 00000, "invalid function"
// *Cause:
// *Action:
00920, 00000, "invalid relational operator"
// *Cause:
// *Action:
00921, 00000, "unexpected end of SQL command"
// *Cause:
// *Action:
00922, 00000, "missing or invalid option"
// *Cause:
// *Action:
00923, 00000, "FROM keyword not found where expected"
// *Cause:
// *Action:
00924, 00000, "missing BY keyword"
// *Cause:
// *Action:
00925, 00000, "missing INTO keyword"
// *Cause:
// *Action:
00926, 00000, "missing VALUES keyword"
// *Cause:
// *Action:
00927, 00000, "missing equal sign"
// *Cause:
// *Action:
00928, 00000, "missing SELECT keyword"
// *Cause:
// *Action:
00929, 00000, "missing period"
// *Cause:
// *Action:
00930, 00000, "missing asterisk"
// *Cause:
// *Action:
00931, 00000, "missing identifier"
// *Cause:
// *Action:
00932, 00000, "inconsistent datatypes: expected %s got %s"
// *Cause:
// *Action:
00933, 00000, "SQL command not properly ended"
// *Cause:
// *Action:
00934, 00000, "group function is not allowed here"
// *Cause:
// *Action:
00935, 00000, "group function is nested too deeply"
// *Cause:
// *Action:
00936, 00000, "missing expression"
// *Cause:
// *Action:
00937, 00000, "not a single-group group function"
// *Cause:
// *Action:
00938, 00000, "not enough arguments for function"
// *Cause:
// *Action:
00939, 00000, "too many arguments for function"
// *Cause:
// *Action:
00940, 00000, "invalid ALTER command"
// *Cause:
// *Action:
00941, 00000, "missing cluster name"
// *Cause:
// *Action:
00942, 00000, "table or view does not exist"
// *Cause:
// *Action:
00943, 00000, "cluster does not exist"
// *Cause:
// *Action:
00944, 00000, "insufficient number of clustered columns"
// *Cause:
// *Action:
00945, 00000, "specified clustered column does not exist"
// *Cause:
// *Action:
00946, 00000, "missing TO keyword"
// *Cause:
// *Action:
00947, 00000, "not enough values"
// *Cause:
// *Action:
00948, 00000, "ALTER CLUSTER statement no longer supported"
// *Cause:
// *Action:
00949, 00000, "illegal reference to remote database"
// *Cause:
// *Action:
00950, 00000, "invalid DROP option"
// *Cause:
// *Action:
00951, 00000, "cluster not empty"
// *Cause:
// *Action:
00952, 00000, "missing GROUP keyword"
// *Cause:
// *Action:
00953, 00000, "missing or invalid index name"
// *Cause: An index name of the form [ <identifier> . ] <identifier> is
//  expected but not present. If OIDINDEX clause, index name must be
//        <identifier>
// *Action:  Enter an appropriate index name.
00954, 00000, "missing IDENTIFIED keyword"
// *Cause:
// *Action:
00955, 00000, "name is already used by an existing object"
// *Cause:
// *Action:
00956, 00000, "missing or invalid auditing option"
// *Cause:  AUDIT or NOAUDIT statement contains an invalid auditing option.
// *Action:  Use a valid option.
00957, 00000, "duplicate column name"
// *Cause:
// *Action:
00958, 00000, "missing CHECK keyword"
// *Cause:
// *Action:
00959, 00000, "tablespace '%s' does not exist"
// *Cause:
// *Action:
00960, 00000, "ambiguous column naming in select list"
// *Cause: A column name in the order-by list matches more than one select
//         list columns.
// *Action: Remove duplicate column naming in select list. 
00961, 00000, "bad datetime/interval value"
// *Cause:
// *Action:
00962, 00000, "too many group-by / order-by expressions"
// *Cause: The group-by or order-by column list contain more than 1000
//         expressions.
// *Action: Use 1000 or less expressions in the group-by or order-by list.
00963, 00000, "unsupported interval type"
// *Cause:
// *Action:
00964, 00000, "table name not in FROM list"
// *Cause: The table name referred in the select list is not specified in the
//   from list.
// *Action: Make sure the name is correctly specified and matches one of the
//    names in the from list.
00965, 00000, "column aliases not allowed for '*'"
// *Cause: The statement is trying to alias the * expression in the select
//   list which is not legal.
// *Action: Remove the alias.
00966, 00000, "missing TABLE keyword"
// *Cause:
// *Action:
00967, 00000, "missing WHERE keyword"
// *Cause:
// *Action:
00968, 00000, "missing INDEX keyword"
// *Cause:
// *Action:
00969, 00000, "missing ON keyword"
// *Cause:
// *Action:
00970, 00000, "missing WITH keyword"
// *Cause:
// *Action:
00971, 00000, "missing SET keyword"
// *Cause:
// *Action:
00972, 00000, "identifier is too long"
// *Cause:  An identifier with more than 30 characters was specified.
// *Action:  Specify at most 30 characters.
00973, 00000, "invalid row count estimate"
// *Cause:
// *Action:
00974, 00000, "invalid PCTFREE value (percentage)"
// *Cause:
// *Action:
00975, 00000, "date + date not allowed"
// *Cause:
// *Action:
00976, 00000, "Specified pseudocolumn or operator not allowed here."
// *Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or
//         CONNECT_BY_ISCYCLE was specified at an illegal location.
// *Action: Remove LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or 
//          CONNECT_BY_ISCYCLE.
00977, 00000, "duplicate auditing option"
// *Cause:  AUDIT or NOAUDIT statement specifies an option more than once
// *Action:  Either use ALL with no other auditing options or make sure
//    no option is listed more than once.
00978, 00000, "nested group function without GROUP BY"
// *Cause:
// *Action:
00979, 00000, "not a GROUP BY expression"
// *Cause:
// *Action:
00980, 00000, "synonym translation is no longer valid"
// *Cause: A synonym did not translate to a legal target object. This 
//         could happen for one of the following reasons:
//         1. The target schema does not exist.
//         2. The target object does not exist.
//         3. The synonym specifies an incorrect database link.
//         4. The synonym is not versioned but specifies a versioned
//            target object.
// *Action: Change the synonym definition so that the synonym points at
//          a legal target object.
00981, 00000, "cannot mix table and system auditing options"
// *Cause: Table and system-wide auditing options were specified in the
//   same AUDIT or NOAUDIT statement.
// *Action: You must issue table and system options in separate
//    statements.
00982, 00000, "missing plus sign"
// *Cause:
// *Action:
00983, 00000, "cannot audit or noaudit SYS user actions"
// *Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
// *Action: Execute the statement again with a valid user.
00984, 00000, "column not allowed here"
// *Cause:
// *Action:
00985, 00000, "invalid program name"
// *Cause:
// *Action:
00986, 00000, "missing or invalid group name(s)"
// *Cause:
// *Action:
00987, 00000, "missing or invalid username(s)"
// *Cause:
// *Action:
00988, 00000, "missing or invalid password(s)"
// *Cause:
// *Action:
00989, 00000, "too many passwords for usernames given"
// *Cause:
// *Action:
00990, 00000, "missing or invalid privilege"
// *Cause:
// *Action:
00991, 00000, "only MAC privileges may be granted to procedures"
// *Cause:  Object privileges or non-MAC system privileges
//          were granted to the procedure.
// *Action: Only grant MAC privileges using the PROCEDURE clause.
00992, 00000, "invalid format for REVOKE command"
// *Cause:
// *Action:
00993, 00000, "missing GRANT keyword"
// *Cause:
// *Action:
00994, 00000, "missing OPTION keyword"
// *Cause:
// *Action:
00995, 00000, "missing or invalid synonym identifier"
// *Cause:
// *Action:
00996, 00000, "the concatenate operator is ||, not |"
// *Cause:
// *Action:
00997, 00000, "illegal use of LONG datatype"
// *Cause:
// *Action:
00998, 00000, "must name this expression with a column alias"
// *Cause:
// *Action:
00999, 00000, "invalid view name"
// *Cause:
// *Action:
/
/ parse errors continue at 1700
/
/ 1000-1099 program interface errors
/
01000, 00000, "maximum open cursors exceeded"
// *Cause:
// *Action:
01001, 00000, "invalid cursor"
// *Cause:
// *Action:
01002, 00000, "fetch out of sequence"
// *Cause: This error means that a fetch has been attempted from a cursor
//         which is no longer valid.  Note that a PL/SQL cursor loop
//         implicitly does fetches, and thus may also cause this error.
//         There are a number of possible causes for this error, including:
//         1) Fetching from a cursor after the last row has been retrieved
//            and the ORA-1403 error returned.
//         2) If the cursor has been opened with the FOR UPDATE clause,
//            fetching after a COMMIT has been issued will return the error.
//         3) Rebinding any placeholders in the SQL statement, then issuing
//            a fetch before reexecuting the statement.
// *Action: 1) Do not issue a fetch statement after the last row has been
//             retrieved - there are no more rows to fetch.
//          2) Do not issue a COMMIT inside a fetch loop for a cursor
//             that has been opened FOR UPDATE.
//          3) Reexecute the statement after rebinding, then attempt to
//             fetch again.
01003, 00000, "no statement parsed"
// *Cause:
// *Action:
01004, 00000, "default username feature not supported; logon denied"
// *Cause:
// *Action:
01005, 00000, "null password given; logon denied"
// *Cause:
// *Action:
01006, 00000, "bind variable does not exist"
// *Cause:
// *Action:
01007, 00000, "variable not in select list"
// *Cause:
// *Action:
01008, 00000, "not all variables bound"
// *Cause:
// *Action:
01009, 00000, "missing mandatory parameter"
// *Cause:
// *Action:
01010, 00000, "invalid OCI operation"
// *Cause: One of the following:
//         1) You attempted an invalid OCI operation.
//         2) You are using an Oracle client application linked with 
//            version 7.1 (or higher) libraries, the environment variable
//            ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to
//            connect to a version 7.0 (or lower) Oracle Server.
//         3) You are connected to a version 7.1 (or higher) Oracle Server,
//            the initialization parameter DBLINK_ENCRYPT_LOGIN is set to
//            TRUE, and you attempted to use a database link pointing to a
//            version 7.0 (or lower) Oracle Server.
//         4) You are connected to a version 9.0.2(or higher) Oracle Server
//            and you attempted to use a database link pointing to a version
//            9.0.1(or lower) Oracle Server for distributed autonomous 
//            transaction.
// *Action: For the above causes:
//         1) Do not use the invalid OCI operation.
//         2) If you do not wish to use encrypted connect passwords in your 
//            distributed database, set ORA_ENCRYPT_LOGIN to FALSE.
//            If you wish to use encrypted connect passwords, you must upgrade
//            all Oracle Servers to version 7.1 (or higher).
//         3) If you do not wish to use encrypted database links in your
//            distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE.
//            If you wish to use encrypted database links, you must upgrade
//            all Oracle Servers to version 7.1 (or higher).
//         4) Do not attempt distributed autonomous transaction on version
//            9.0.1(or lower) Oracle Server.
01011, 00000, "Cannot use v7 compatibility mode when talking to v6 server"
// *Cause:
// *Action: Use v6 sql language type. You may need to use the
//          'SET COMPATIBILITY V6' command
01012, 00000, "not logged on"
// *Cause:
// *Action:
01013, 00000, "user requested cancel of current operation"
// *Cause:
// *Action:
01014, 00000, "ORACLE shutdown in progress"
// *Cause:
// *Action:
01015, 00000, "logon called recursively"
// *Cause:
// *Action:
01016, 00000, "This function can be called only after a fetch"
// *Cause: Cursor in an invalid state.
// *Action: Make sure that the oci/upi function is called after fetch.
01017, 00000, "invalid username/password; logon denied"
// *Cause:
// *Action:
01018, 00000, "column does not have a LONG datatype"
// *Cause:
// *Action:
01019, 00000, "unable to allocate memory in the user side"
// *Cause: The user side memory allocator returned error.
// *Action: Increase the processes heap size or switch to the old set of calls.
01020, 00000, "unknown context state"
// *Cause:
// *Action:
01021, 00000, "invalid context size specified"
// *Cause:
// *Action:
01022, 00000, "database operation not supported in this configuration"
// *Cause: The attempted database operation does not conform to the user
//         programming interface (UPI) for the two communicating
//         ORACLE servers. 
// *Action: You may need to upgrade one or more of your ORACLE servers or
//          re-link your user side application with new libraries. Report
//          the problem to Worldwide Customer Support. 
01023, 00000, "Cursor context not found (Invalid cursor number)"
// *Cause: The cursor number is not a valid open cursor.
// *Action: Make sure that the cursor is open.
01024, 00000, "invalid datatype in OCI call"
// *Cause:
// *Action:
01025, 00000, "UPI parameter out of range"
// *Cause:  An integer parameter to a upi function is out of range.
// *Action:  This usually indicates an error in a tool built on top
//     of the oracle dbms.  Report the error to your customer
//     support representative.
01026, 00000, "multiple buffers of size > 4000 in the bind list"
// *Cause: More than one long buffer in the bind list.
// *Action: Change the buffer size to be less than 4000 for the bind variable 
//          bound to a normal column.
01027, 00000, "bind variables not allowed for data definition operations"
// *Cause:  An attempt was made to use a bind variable in a SQL data definition
//    operation.
// *Action:  Such bind variables are not allowed.
01028, 00000, "internal two task error"
// *Cause: Received send long message but don't have the cursor context.
// *Action: Report as a bug.
01029, 00000, "internal two task error"
// *Cause: Received a request to send the long again when there is no long
// *Action: Report as a bug
01030, 00000, "SELECT ... INTO variable does not exist"
// *Cause: The SELECT... INTO specified in the bind call does not 
//         correspond to a variable in the SQL statement.
// *Action: If it is not possible to correct the statement, call customer
//          support.
01031, 00000, "insufficient privileges"
// *Cause: An attempt was made to change the current username or password
//         without the appropriate privilege. This error also occurs if
//         attempting to install a database without the necessary operating
//         system privileges.
//         When Trusted Oracle is configure in DBMS MAC, this error may occur
//         if the user was granted the necessary privilege at a higher label
//         than the current login.
// *Action: Ask the database administrator to perform the operation or grant
//          the required privileges.
//          For Trusted Oracle users getting this error although granted the
//          the appropriate privilege at a higher label, ask the database
//          administrator to regrant the privilege at the appropriate label.
01032, 00000, "no such userid"
// *Cause: This is an internal error message related to Export/Import.
// *Action: Contact customer support.
01033, 00000, "ORACLE initialization or shutdown in progress"
// *Cause: An attempt was made to log on while Oracle is being started up
//         or shutdown.
// *Action: Wait a few minutes. Then retry the operation.
01034, 00000, "ORACLE not available"
// *Cause: Oracle was not started up. Possible causes include the following:
//         - The SGA requires more space than was allocated for it.
//         - The operating-system variable pointing to the instance is
//           improperly defined.
// *Action: Refer to accompanying messages for possible causes and correct
//          the problem mentioned in the other messages. 
//          If Oracle has been initialized, then on some operating systems,
//          verify that Oracle was linked correctly. See the platform
//          specific Oracle documentation.
01035, 00000, "ORACLE only available to users with RESTRICTED SESSION privilege"
// *Cause: Logins are disallowed because an instance started in restricted
//         mode. Only users with RESTRICTED SESSION system privilege can
//         log on.
// *Action: Request that Oracle be restarted without the restricted option or
//          obtain the RESTRICTED SESSION system privilege.
01036, 00000, "illegal variable name/number"
// *Cause: Unable to find bind context on user side
// *Action: Make sure that the variable being bound is in the sql statement.
01037, 00000, "maximum cursor memory exceeded"
// *Cause: Attempting to process a complex sql statement which consumed all
//   available memory of the cursor.
// *Action: Simplify the complex sql statement.
01038, 00000, "cannot write database file version %s with ORACLE version %s"
// *Cause: Attempting to write datafile headers in an old format. The new
//         format can not be used until after the database has been verified
//         as being compatible with this software version.
// *Action: Open the database to advance to the new file formats, then repeat
//         the operation. If the operation is required before the database
//         can be opened, then use the previous software release to do the
//         operation.
01039, 00000, "insufficient privileges on underlying objects of the view"
// *Cause: Attempting to explain plan on other people's view without
//         the necessary privileges on the underlying objects of the view.
// *Action: Get necessary privileges or do not perform the offending operation.
01040, 00000, "invalid character in password; logon denied"
// *Cause: There are multibyte characters in the password or some characters
//         in the password are not in US7ASCII range.
// *Action: Resubmit password with valid characters.
01041, 00000, "internal error. hostdef extension doesn't exist"
// *Cause: Pointer to hstdef extension in hstdef is null.
// *Action: Report as a bug
01042, 00000, "detaching a session with open cursors not allowed"
// *Cause: An attempt was made to detach a seesio n which had open cursors.
// *Action: Close all the cursors before detaching the session.
01043, 00000, "user side memory corruption [%s], [%s], [%s], [%s]"
// *Cause: The application code corrupted some of the usr memory used by oracle
// *Action: Make sure that the application code is not overwriting memory.
01044, 00000, "size %s of buffer bound to variable exceeds maximum %s"
// *Cause: An attempt was made to bind a buffer whose total size would exceed
//         the maximum size allowed.  Total array size for arrays is
//         calculated as: (element_size)*(number of elements)
// *Action: Reduce buffer size.
01045, 00000, "user %s lacks CREATE SESSION privilege; logon denied"
// *Cause: A connect was attempted to a userid which does not have
//         create session privilege.
// *Action: Grant the user CREATE SESSION privilege.
01046, 00000, "cannot acquire space to extend context area"
// *Cause:
// *Action:
01047, 00000, "The above error occurred in schema=%s, package=%s, procedure=%s"
// *Cause:
// *Action: Informational message
01048, 0000, "Couldn't find the specified procedure in the given context"
// *Cause: The procedure user specified in deferred RPC doesn't exist.
// *Action: Check to make sure that the procedure exists and is visible to the
//          replication process.
01049, 00000, "Bind by name is not spupportted in streamed RPC"
// *Cause: A newer version of server is talking with this version requesting an
//         operation not supported in this version.
// *Action:
01050, 00000, "cannot acquire space to open context area"
// *Cause:
// *Action:
01051, 00000, "deferred rpc buffer format invalid"
// *Cause: The deferred rpc data in sys.def$_call is corrupted.
// *Action: Contact your customer support representive.
01052, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST is not specified"
// *Cause:  A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not
//          specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to
//          two.
// *Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or
//          reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one.
01053, 00000, "user storage address cannot be read"
// *Cause:
// *Action:
01054, 00000, "user storage address cannot be written"
// *Cause:
// *Action:
01055, 00000, "Object datatypes not supported for bind or define in this mode"
// *Cause: Bind or Define used for objects with an invalid mode
// *Action: Change the mode.
01057, 00000, "invalid or ambiguous block.field reference in user exit"
// *Cause:
// *Action:
01058, 00000, "internal New Upi interface error"
// *Cause: Attempt to delete non existant hstdef extension.
// *Action: Report as a bug.
01059, 00000, "parse expected before a bind or execute"
// *Cause: The client application attempted to bind a variable or execute
//         a cursor opened in a PL/SQL block before the statement was parsed.
// *Action: Ensure the statement is parsed before a bind or execute.
01060, 00000, "array binds or executes not allowed"
// *Cause: The client application attempted to bind an array of cursors or
//         attempted to repeatedly execute against a PL/SQL block with a bind
//         variable of type cursor.
// *Action: Bind a single cursor or execute the PL/SQL block once.
01061, 00000, "cannot start up a V8 server using a V7 client application"
// *Cause: You are using an Oracle client application linked with version 7
//         (or lower) libraries and you attempted to start up a V8 (or 
//         higher) server.
// *Action: Use a client application linked with V8 (or higher) libraries.60
01062, 00000, "unable to allocate memory for define buffer"
// *Cause: Exceeded the maximum buffer size for current plaform
// *Action: Use piecewise fetch with a smaller buffer size
/ 1070 - 1099: V6 program interface errors
01070, 00000, "Using an old version of Oracle for the server"
// *Cause: Using pre 7.0.10.1 version of oracle for server
// *Action: Upgrade server to post 7.0.10.1 version
01071, 00000, "cannot perform operation without starting up ORACLE"
// *Cause:  Obvious
// *Action:
01072, 00000, "cannot stop ORACLE; ORACLE not running"
// *Cause:  Obvious
// *Action:
01073, 00000, "fatal connection error: unrecognized call type"
// *Cause:  An illegal internal operation was attempted.
// *Action:  Contact your customer support representative.
01074, 00000, "cannot shut down ORACLE; inside a login session - log off first"
// *Cause:  Obvious
// *Action:
01075, 00000, "you are currently logged on"
// *Cause:  Attempt to login while logged in.
// *Action:
01076, 00000, "multiple logons per process not yet supported"
// *Cause:  Obvious
// *Action:
01077, 00000, "background process initialization failure"
// *Cause:  Failure during initialization of ORACLE background processes.
// *Action:  Further diagnostic information should be in the error stack
//     or in the trace file.
01078, 00000, "failure in processing system parameters"
// *Cause:  Failure during processing of INIT.ORA parameters during
//    system startup.
// *Action:  Further diagnostic information should be in the error stack.
01079, 00000, "ORACLE database was not properly created, operation aborted"
// *Cause:  There was an error when the database or control file was created.
// *Action:  Check what error was signaled when the database was first
//     created or when the control file was recreated. Take appropriate
//           actions to recreate the database or a new control file.
01080, 00000, "error in shutting down ORACLE"
// *Cause:  Failure during system shutdown.
// *Action:  Further diagnostic information should be in the error stack.
01081, 00000, "cannot start already-running ORACLE - shut it down first"
// *Cause:  Obvious
// *Action:
01082, 00000, "'row_locking = always' requires the transaction processing option"
// *Cause:  "row_locking = always" is specified in INIT.ORA file.
//    This feature is not supported by ORACLE without the
//    transaction processing option.
// *Action: Remove it from INIT.ORA file or set it to "default" or "intent".
01083, 00000, "value of parameter \"%s\" is inconsistent with that of other instances"
// *Cause:  The value of the given parameter is required to be the same for all
//          instances in the cluster database configuration.  ROW_LOCKING and
//          SERIALIZABLE are 2 examples.
// *Action: Change the value of the parameter in INIT.ORA file to match
//          that of other cluster database instances.
01084, 00000, "invalid argument in OCI call"
// *Cause: The failing OCI call contains an argument with an invalid value.
// *Action: Use valid argument values. For more information, see the 
//          Programmer's Guide to the Oracle Call Interfaces and the
//          appropriate programming language supplement.
01085, 00000, "preceding errors in deferred rpc to \"%s.%s.%s\""
// *Cause:  Errors were encountered when the named procedure was executed 
//          as a deferred remoted procedure call.
// *Action: Correct the cause of the preceding errors.
01086, 00000, "savepoint '%s' never established in this session or is invalid"
// *Cause:  An attempt was made to roll back to a savepoint that was never
//          established in this session, or was invalid.
// *Action: Try rolling back to the savepoint from the session where it is established.
01087, 00000, "cannot start up ORACLE - currently logged on"
// *Cause:
// *Action: Logoff and then issue the STARTUP command.
01088, 00000, "shutdown in progress - operation not permitted until restart"
// *Cause:  The SHUTDOWN command was used to shut down a running Oracle
//          instance but the shutdown operation was not complete.
// *Action: Wait for the instance to be restarted or contact your
//          database administrator.
01089, 00000, "immediate shutdown in progress - no operations are permitted"
// *Cause:  The SHUTDOWN IMMEDIATE command was used to shut down
//   a running ORACLE instance, so your operations have been
//   terminated.
// *Action: Wait for the instance to be restarted, or contact your DBA.
01090, 00000, "shutdown in progress - connection is not permitted"
// *Cause:  The SHUTDOWN command was used to shut down a running
//   ORACLE instance, so you cannot connect to ORACLE.
// *Action: Wait for the instance to be restarted, or contact your DBA.
01091, 00000, "failure during startup force"
// *Cause:  Unable to destroy the old SGA.
// *Action: Manually remove the old SGA and reissue the STARTUP command
01092, 00000, "ORACLE instance terminated. Disconnection forced"
// *Cause:  The instance this process was connected to was terminated
//    abnormally, probably via a shutdown abort. This process
//    was forced to disconnect from the instance.
// *Action: Examine the alert log for more details. When the instance has been 
//          restarted, retry action.
01093, 00000, "ALTER DATABASE CLOSE only permitted with no sessions connected"
// *Cause:  There is at least one more session other than the current one
//         logged into the instance.  ALTER DATABASE CLOSE is not permitted.
// *Action: Find the other sessions and log them out and resubmit the command
01094, 00000, "ALTER DATABASE CLOSE in progress. Connections not permitted"
// *Cause:
// *Action:
01095, 00000, "DML statement processed zero rows"
// *Cause:  During a call to OTEX, an update, delete, or insert statement
//          being executed processed zero rows.  The execution
//          of statements by OTEX was halted at this point. 
// *Action: 
01096, 00000, "program version (%s) incompatible with instance (%s)"
// MERGE: 1095 RENUMBERED TO 1096
// *Cause: A program is trying to connect to an instance using a different
//         version of code than the database was started with.  This is
//         not allowed.
// *Action: Either relink the program with the same version as the database or
//          restart the database using the old version of code.
01097, 00000, "cannot shutdown while in a transaction - commit or rollback first"
// *Cause:  Obvious
// *Action:
01098, 00000, "program Interface error during Long Insert"
// *Cause:  
// *Action: 
01099, 00000, "cannot mount database in SHARED mode if started in single process mode"
// *Cause:  Obvious
// *Action:
/
/ 1100 to 1279: db file errors (continue at 63000)
/
01100, 00000, "database already mounted"
// *Cause:  A database is already mounted in this instance.
// *Action:
01101, 00000, "database being created currently mounted by some other instance"
// *Cause:  Some other instance has the database of same name currently mounted
//   and you are trying to create it.
// *Action: Either change the database name or shutdown the other instance.
01102, 00000, "cannot mount database in EXCLUSIVE mode"
// *Cause:  Some other instance has the database mounted exclusive or shared.
// *Action: Shutdown other instance or mount in a compatible mode.
01103, 00000, "database name '%s' in control file is not '%s'"
// *Cause:  The database name in the control file does not match your
//   database name.
// *Action: Either find the correct control file or change your database name.
01104, 00000, "number of control files (%s) does not equal %s"
// *Cause:  The number of control files used by this instance disagrees with
//   the number of control files in an existing instance.
// *Action: Check to make sure that all control files are listed.
01105, 00000, "mount is incompatible with mounts by other instances"
// *Cause:  An attempt to mount the database discovered that another instance
//         mounted a database by the same name, but the mount is not
//         compatible. Additional errors are reported explaining why.
// *Action: See accompanying errors.
01106, 00000, "database must be closed before dismounting"
// *Cause:  Obvious
// *Action:
01107, 00000, "database must be mounted for media recovery"
// *Cause:  An attempt to perform media recovery was made but the database is
//   not mounted.
// *Action: Mount the database.
01108, 00000, "file %s is in backup or media recovery"
// *Cause:  Either media recovery is actively being applied to the file, or
//          it is being backed up while the database is in NOARCHIVELOG mode.
//          It cannot be used for normal database access or crash recovery.
// *Action: Complete or cancel the media recovery session or backup.
01109, 00000, "database not open"
// *Cause:  A command was attempted that requires the database to be open. 
// *Action: Open the database and try the command again
01110, 00000, "data file %s: '%s'"
// *Cause:  Reporting file name for details of another error. The reported
//          name can be of the old file if a data file move operation is
//          in progress.
// *Action: See associated error message.
01111, 00000, "name for data file %s is unknown - rename to correct file"
// *Cause:  The data file was missing from a CREATE CONTROLFILE command or
//          backup control file recovery was done with a control file that
//          was saved before the file was created.
// *Action: Rename the MISSING file to the name of the real file.
01112, 00000, "media recovery not started"
// *Cause:  An attempt to continue media recovery is being made but media
//    recovery was not started.
// *Action: None.
01113, 00000, "file %s needs media recovery"
// *Cause:  An attempt was made to online or open a database with a file that
//   is in need of media recovery.
// *Action: First apply media recovery to the file.
01114, 00000, "IO error writing block to file %s (block # %s)"
// *Cause:  The device on which the file resides is probably offline. If the 
//          file is a temporary file, then it is also possible that the device
//          has run out of space. This could happen because disk space of
//          temporary files is not necessarily allocated at file creation time.
// *Action: Restore access to the device or remove unnecessary files to free
//          up space.
01115, 00000, "IO error reading block from file %s (block # %s)"
// *Cause:  Device on which the file resides is probably offline
// *Action: Restore access to the device
01116, 00000, "error in opening database file %s"
// *Cause:  Usually the file is not accessible.
// *Action: Restore the database file.
01117, 00000, "adding file '%s' with illegal block size:  %s; limit is %s"
// *Cause:  An attempt was made to add a database file with a block size
//   that is greater than the maximum block size allowed.
// *Action: Retry the DDL command with a smaller block size.
01118, 00000, "cannot add any more database files: limit of %s exceeded"
// *Cause:  There is no more room in the control file for adding database
//          files.
// *Action: Resize the control file or drop other tablespaces.
01119, 00000, "error in creating database file '%s'"
// *Cause:  Usually due to not having enough space on the device.
// *Action:
01120, 00000, "cannot remove online database file %s"
// *Cause:  Attempting to drop a datafile when it is online
// *Action: Take file offline before dropping.
01121, 00000, "cannot rename database file %s - file is in use or recovery"
// *Cause:  Attempted to use ALTER DATABASE RENAME to rename a
//          datafile that is online in an open instance or is being recovered.
// *Action: Close database in all instances and end all recovery sessions.
01122, 00000, "database file %s failed verification check"
// *Cause:  The information in this file is inconsistent with information
//   from the control file. See accompanying message for reason.
// *Action: Make certain that the db files and control files are the correct
//   files for this database.
01123, 00000, "cannot start online backup; media recovery not enabled"
// *Cause: An attempt to start backup of an on-line tablespace failed because
//  media recovery is not enabled.
// *Action: Enable media recovery and retry this operation.
01124, 00000, "cannot recover data file %s - file is in use or recovery"
// *Cause:  An attempt to do media recovery found that the file was not 
//          available for recovery. Either it is online and the database is
//          open in some instance, or another process is curently doing 
//          media recovery on the file.
// *Action: Do not do media recovery.
01125, 00000, "cannot disable media recovery - file %s has online backup set"
// *Cause: An attempt to disable media recovery found that an online backup is
//  still in progress.
// *Action: End the backup of the offending tablespace and retry this command.
01126, 00000, "database must be mounted in this instance and not open in any instance"
// *Cause:  Obvious
// *Action:
01127, 00000, "database name '%s' exceeds size limit of %s characters"
// *Cause:  Obvious
// *Action:
01128, 00000, "cannot start online backup - file %s is offline"
// *Cause: An attempt to start an online backup found that one of the files is
//        offline.
// *Action: Bring the offending files online and retry this command or do a
//         cold backup.
01129, 00000, "user's default or temporary tablespace does not exist"
// *Cause:  The user's default or temporary tablespace was dropped.
// *Action: Reassign the default or temporary tablespace.
01130, 00000, "database file version %s incompatible with ORACLE version %s"
// *Cause:
// *Action:
01131, 00000, "DB_FILES system parameter value %s exceeds limit of %s"
// *Cause:
// *Action:
01132, 00000, "length of database file name '%s' exceeds limit of %s characters"
// *Cause:
// *Action:
01133, 00000, "length of log file name '%s' exceeds limit of %s characters"
// *Cause:
// *Action:
01134, 00000, "database mounted exclusive by another instance"
// *Cause:
// *Action:
01135, 00000, "file %s accessed for DML/query is offline"
// *Cause:  Attempted to access a data file that is offline
// *Action: Bring the data file back online
01136, 00000, "specified size of file %s (%s blocks) is less than original size of %s blocks"
// *Cause:  A file size was specified in the AS clause of ALTER DATABASE
//          CREATE DATAFILE, and the size was smaller the the size needed
// *Action: Create the file with a larger size.
01137, 00000, "data file %s is still in the middle of going offline"
// *Cause: It was not possible to get the lock for a file that is offline when
// attempting to bring it online. The most likely cause is that the
// lock is still held by the instance that is took it offline.
// *Action: Wait a bit and try to online the file again.
01138, 00000, "database must either be open in this instance or not at all"
// *Cause:  The requested operation can not be done when the database is
//          mounted but not open in this instance, and another instance has
//          the database open.
// *Action: Execute the operation in an open instance, open the datbase in
//          this instance, or close the database in the other instances.
01139, 00000, "RESETLOGS option only valid after an incomplete database recovery"
// *Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there
//  has been no incomplete recovery session.
// *Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS
01140, 00000, "cannot end online backup - all files are offline or readonly"
// *Cause: All the files were found to be offline or readonly when attempting 
//         to end an online backup.
// *Action: None. Online backup does not need to be ended for this tablespace.
01141, 00000, "error renaming data file %s - new file '%s' not found"
// *Cause: An attempt to change a data file's name in the control file
//   failed because no file was found with the new name.
// *Action: Make sure that the data file has been properly renamed by the
//   operating system and retry.
01142, 00000, "cannot end online backup - none of the files are in backup"
// *Cause: None of the files were found to be in online backup when attempting
//        to end an online backup.
// *Action: None. Online backup does not need to be ended for this tablespace.
01143, 00000, "cannot disable media recovery - file %s needs media recovery"
// *Cause: An attempt to disable media recovery found a file that needs media
//         recovery, thus media recovery cannot be disabled.
// *Action: Recover the offending file or drop the tablespace it belongs to
//   and retry this command.
01144, 00000, "File size (%s blocks) exceeds maximum of %s blocks"
// *Cause:  Specified file size is larger than maximum allowable size value.
// *Action: Specify a smaller size.
01145, 00000, "offline immediate disallowed unless media recovery enabled"
// *Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE
//         ... OFFLINE is only allowed if database is in ARCHIVELOG mode.
// *Action:Take tablespace offline normally or shutdown abort. Reconsider your
//         backup strategy. You could do this if you were archiving your logs.
01146, 00000, "cannot start online backup - file %s is already in backup"
// *Cause: When starting an online backup it was noticed that an online backup
//         was already started for one of the data files. 
// *Action:End the first backup before beginning another.
01147, 00000, "SYSTEM tablespace file %s is offline"
// *Cause: A file belonging to the SYSTEM tablespace has been marked offline
//   by the DBA. The database cannot be started until all SYSTEM
//   tablespace files are online and openable.
// *Action: Bring the file online.
01148, 00000, "cannot refresh file size for datafile %s"
// *Cause:  An operating system or device error occurred when retrieving the
//          file's size. The device on which the file resides may have been
//          offline.
// *Action: Restore access to the device.
01149, 00000, "cannot shutdown - file %s has online backup set"
// *Cause: An attempt to shutdown normally found that an online backup is
//        still in progress.
// *Action: End the backup of the offending tablespace and retry this command.
01150, 00000, "cannot prevent writes - file %s has online backup set"
// *Cause: An attempt to make a tablespace read only or offline normal found
//          that an online backup is still in progress. It will be necessary
//          to write the file header to end the backup, but that would not
//          be allowed if this command succeeded.
// *Action: End the backup of the offending tablespace and retry this command.
01151, 00000, "use media recovery to recover block, restore backup if needed"
// *Cause:  Error 1172 occurred.
// *Action: This is additional information for error 1172.
01152, 00000, "file %s was not restored from a sufficiently old backup "
// *Cause:  An incomplete recovery session was started, but an insufficient
//   number of logs were applied to make the database consistent. This
//         file is still in the future of the last log applied. The most
//         likely cause of this error is forgetting to restore the file
//         from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the database is consistent or
//   restore the database file from an older backup and repeat recovery.
01153, 00000, "an incompatible media recovery is active"
// *Cause: Attempted to start an incompatible media recovery or open resetlogs
//         during media recovery or RMAN backup . Media recovery sessions
//         are incompatible if they attempt to recover the same data file.
//         Incomplete media recovery or open resetlogs is incompatible with
//         any media recovery. Backup or restore by RMAN is incompatible
//         with open resetlogs
// *Action: Complete or cancel the other media recovery session or RMAN backup
01154, 00000, "database busy. Open, close, mount, and dismount not allowed now"
// *Cause: Some operation is in progress that expects the opened/mounted state
//   of this instance to remain the same.
// *Action: Wait for the operation to complete then retry. If attempting to
//   do a shutdown, SHUTDOWN ABORT will work.  If this is a shutdown
//         of a standby database that is operating in NO DATA LOSS mode, you
//         must shutdown the primary database first.
01155, 00000, "the database is being opened, closed, mounted or dismounted"
// *Cause: The requested operation needs the instance to be in a particular
//   state but the state is being changed.
// *Action: Wait for the open, close, mount, or dismount to complete then
//   retry the operation. If necessary, a SHUTDOWN ABORT will always
//   work.
01156, 00000, "recovery or flashback in progress may need access to files"
// *Cause: Either media recovery, instance recovery, or flashback was
//         in progress. The recovery or flashback in progress may need
//         the files to which this operation is being applied.
// *Action: Wait for recovery or flashback to complete.
01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause:  The background process was either unable to find one of the data 
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.
01158, 00000, "database %s already mounted"
// *Cause:  Another instance has a database by this name mounted.
// *Action: Find which instance is still running.  Perhaps you have not lost
//    the control files after all.
01159, 00000, "file is not from same database as previous files - wrong database id"
// *Cause: Not all of the files specified in CREATE CONTROLFILE are from the
//  same database. The database ID of this file does not match that
//        from the first file specified.
// *Action: Please double check the list of files provided to the CREATE
01160, 00000, "file is not a %s"
// *Cause: The named file in the DATAFILE or LOGFILE section of the CREATE
//  CONTROLFILE command does not appear to be as stated.
// *Action:  Please double check the mentioned file.
01161, 00000, "database name %s in file header does not match given name of %s"
// *Cause: The database name given at the command line does not match the
//  database name found in the file header.
// *Action: Chance are good that the database name specified at the command
//  line is incorrect.  Resolve the descepency, and resubmit the command.
//        If you are attempting to change the database name, be sure to 
//        use the SET DATABASE option.
01162, 00000, "block size %s in file header does not match configured block sizes"
// *Cause: CREATE CONTROLFILE discovered that the block size for this file
//         is incompatible with any of the configured cache blocksizes in 
//         the INIT.ORA file. 
// *Action:Configure the appropriate cache for this block size using one of the 
//         various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, 
//         db_16k_cache_size, db_32K_cache_size) parameters.
01163, 00000, "SIZE clause indicates %s (blocks), but should match header %s"
// *Cause: The size specified in bytes in the SIZE clause of the CREATE 
//         CONTROLFILE statement does not equate to the number of blocks 
//         recorded in the header.
// *Action: Specify the correct filename and size ( in bytes ).
01164, 00000, "MAXLOGFILES may not exceed %s"
// *Cause:  MAXLOGFILES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGFILES
01165, 00000, "MAXDATAFILES may not exceed %s"
// *Cause:  MAXDATAFILES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXDATAFILES
01166, 00000, "file number %s is larger than %s (%s)"
// *Cause: File mentioned in CREATE CONTROLFILE has a file number which is
//         larger than that specified for MAXDATAFILES or MAXLOGFILES.
// *Action: Increase the maximum specified on the command line.
01167, 00000, "two files are the same file/group number or the same file"
// *Cause: There is an overlap of file numbers in the files specified on
//  the command line or the same file is specified twice. If they are
//        not the exact same file then one is likely to be a backup of the
//        other. If they are two members of the same log they must be specified
//        together in a group file spec.  This message will also appear if
//        the same control file appears more than once in the control_files
//        parameter in the init.ora file.  If this happens, check for
//        additional error messages.
// *Action: Confirm that the file mentioned is not a repeat of a file already
// mentioned in the command. If they are different files then omit the
//       earlier backup. If they are members of the same log, insure they are
//       in the same group file specification.  If this message appears because
//       of a duplicate control file, check the control_files parameter in the
//       init.ora file and see if a file is specified more than once.
//       If all files names appear to be unique, check to make sure that the
//       actual control files themselves are unique.  For example, in UNIX
//       check for a symbolic or a hard link to another control file in the list.
01168, 00000, "physical block size %s does not match size %s of other members"
// *Cause:  The file is located on a device with a different physical block
//          size than the other members in the group
// *Action: Use a physical device with matching block size.
01169, 00000, "DATAFILE number 1 not found.  Must be present"
// *Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.
// *Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE
// command.
01170, 00000, "file not found '%s'"
// *Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be
//   accessible by the process for CREATE CONTROLFILE.
// *Action: The file specified probably contains a typing error.  Double
//   check command and the existance of all files and then resubmit.
01171, 00000, "datafile %s going offline due to error advancing checkpoint"
// *Cause:  The checkpoint in the file header could not be advanced. See
//         accompanying errors for the reason. The datafile will be taken
//         offline the same as for a write error of a data block.
// *Action: See accompanying errors for details. Restore access to the file,
//         do media recovery, and bring it back online.
01172, 00000, "recovery of thread %s stuck at block %s of file %s"
// *Cause: Crash recovery or instance recovery could not apply a change to a
//         block because it was not the next change. This can happen if the 
//         block was corrupted and then repaired during recovery.
// *Action: Do a RECOVER DATAFILE for the file containing the block. If this
//         does not resolve the problem then restore the file from a backup
//         and  recover it.
01173, 00000, "data dictionary indicates missing data file from system tablespace"
// *Cause:  Either the database has been recovered to a point in time in the
//    future of the control file or a datafile from the system tablespace was
//    omitted from the create control file command previously issued.
// *Action: For the former problem you need to recover the database from a
//    more recent control file. For the latter problem, simply recreate the
//    control file checking to be sure that you include all the datafiles in
//    the system tablespace.
01174, 00000, "DB_FILES is %s buts needs to be %s to be compatible"
// *Cause:  The maximum number of database files supported by this instance 
//         is not the same as for the other instances. All instances must
//         be able to open all the files any instance can open.
// *Action: Change the value of the DB_FILES parameter to be compatible
01175, 00000, "data dictionary has more than the %s files allowed by the instance"
// *Cause:  The data dictionary is found to have more files than that which can
//     be supported by this instance.
// *Action: Shutdown the instance and restart with a larger number of db_files
01176, 00000, "data dictionary has more than the %s files allowed by the controlfie"
// *Cause: After a CREATE CONTROLFILE, the data dictionary was found to have
//    more datafiles than that supported by the control file.
// *Action: Recreate the control file with a larger MAXDATAFILES.
01177, 00000, "data file does not match dictionary - probably old incarnation"
// *Cause:  When comparing the control file with the data dictionary after
//          a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this
//          datafile was inconsistent with the dictionary. Most likely the
//          file is a backup of a file that was dropped from the database,
//          and the same file number was reused for a new file. It may also
//          be that an incomplete recovery stopped at a time when this file
//          number was used for another datafile.
// *Action: Do a CREATE CONTROLFILE with the correct file or none at all.
01178, 00000, "file %s created before last CREATE CONTROLFILE, cannot recreate"
// *Cause:  Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
//          datafile that existed at the last CREATE CONTROLFILE command.
//          The information needed to recreate the file was lost with the
//          control file that existed when the file was added to the database.
// *Action: Find a backup of the file, and recover it. Do incomplete recovery
//          to time before file was originally created.
01179, 00000, "file %s does not exist"
// *Cause:  During datafile recovery, a file was listed which was not part
//    for the database.
// *Action:  Recheck the datafile name.  Remember to use double quotes at the
//    SQLDBA command line and remember that the file name is translated in the
//    environment of the SQLDBA.
01180, 00000, "can not create datafile 1"
// *Cause:  Attempting to create datafile 1 using ALTER DATABASE CREATE
//          DATAFILE.
// *Action: Recover file from a backup or recreate database.
01181, 00000, "file %s created before last known RESETLOGS, cannot recreate"
// *Cause:  Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
//          datafile that existed before the last known RESETLOGS.
// *Action: Find a backup of the file, and recover it. Do incomplete recovery
//          to time before file was originally created.
01182, 00000, "cannot create database file %s - file is in use or recovery"
// *Cause:  Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
//          datafile that is online in an open instance or is being recovered.
// *Action: Close database in all instances and end all recovery sessions
01183, 00000, "cannot mount database in SHARED mode"
// *Cause:  Some other instance has the database mounted exclusive.
// *Action: Shutdown other instance then mount shared.
01184, 00000, "logfile group %s already exists"
// *Cause:  An ALTER DATABASE ADD LOGFILE command specified a log number for
//          the new log which is already in use.
// *Action: Specify a different logfile number, or let the database choose
//          an unused value.
01185, 00000, "logfile group number %s is invalid"
// *Cause:  An ALTER DATABASE ADD LOGFILE command specified a log number for
//          the new log which is too large.
// *Action: Specify a correct logfile number.
01186, 00000, "file %s failed verification tests"   
// *Cause:  The data file did not pass the checks to insure it is part of the
//         database. See the accompanying error messages for the reason the   
//         verification failed.   
// *Action: Make the correct file available to the database. Then, either open
//         the database, or execute ALTER SYSTEM CHECK DATAFILES.  
01187, 00000, "cannot read from file %s because it failed verification tests"
// *Cause:  The data file did not pass the checks to insure it is part of the
//         database. Reads are not allowed until it is verified.
// *Action: Make the correct file available to the database. Then, either open
//         the database, or execute ALTER SYSTEM CHECK DATAFILES.  
01188, 00000, "The block size specified %s does not match header block size %s"
// *Cause:  The block size specified in the BLOCKSIZE clause of the CREATE 
//          CONTROLFILE statement does not equate to the block size 
//          recorded in the log file header.
// *Action: Specify the correct block size.
01189, 00000, "file is from a different RESETLOGS than previous files"
// *Cause:  In a CREATE CONTROLFILE command either this file or all previous
//          files were backups from before the last RESETLOGS. This may also
//          occur if this is a file that is offline and has been offline since
//          before the last RESETLOGS.
// *Action: If the file was taken offline normal before the last RESETLOGS,
//          and is still offline, omit it from the CREATE CONTROLFILE command.
//          Rename and online the file after the database is open. Otherwise
//          find the version of the mentioned file consistent with the rest
//          of the datafiles and resubmit the command.
01190, 00000, "control file or data file %s is from before the last RESETLOGS"
// *Cause: Attempting to use a data file when the log reset information in
//          the file does not match the control file. Either the data file
//          or the control file is a backup that was made before the most
//          recent ALTER DATABASE OPEN RESETLOGS.
// *Action: Restore file from a more recent backup.
01191, 00000, "file %s is already offline - cannot do a normal offline"
// *Cause:  When attempting to do a normal tablespace offline it was discovered
//          that one of the files in the tablespace was already offline.
// *Action: Either bring the datafile online first, or use another tablespace
//          offline option.
01192, 00000, "must have at least one enabled thread"
// *Cause:  You must specify at least two logfiles from at least one thread
//        at the create contolfile command line.
// *Action:  Find the missing logfiles and resubmit the command with the newly
//        found logfiles included in the command line.
01193, 00000, "file %s is not the same file seen at start of recovery"
// *Cause: A different copy of the file was accessed the last time media
//         recovery looked at the file header. A backup of the file was
//         restored or the meaning of the file name changed during recovery.
// *Action:Ensure the correct file is available, then retry recovery.
01194, 00000, "file %s needs more recovery to be consistent"
// *Cause:  An incomplete recovery session was started, but an insufficient
//   number of logs were applied to make the file consistent. The
//         reported file was not closed cleanly when it was last opened by
//         the database. It must be recovered to a time when it was not being
//         updated. The most likely cause of this error is forgetting to
//         restore the file from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the file is consistent or restore
//    the file from an older backup and repeat recovery.
01195, 00000, "online backup of file %s needs more recovery to be consistent"
// *Cause:  An incomplete recovery session was started, but an insufficient
//   number of logs were applied to make the file consistent. The
//         reported file is an online backup which must be recovered to the
//         time the backup ended.
// *Action: Either apply more logs until the file is consistent or
//   restore the database files from an older backup and repeat recovery.
01196, 00000, "file %s is inconsistent due to a failed media recovery session"
// *Cause:  The file was being recovered but the recovery did not terminate
//          normally. This left the file in an inconsistent state. No more
//          recovery was successfully completed on this file.
// *Action:Either apply more logs until the file is consistent or restore
//    the backup again and repeat recovery.
01197, 00000, "thread %s only contains one log"
// *Cause:  During CREATE CONTROLFILE all threads represented in the logs
//   must be represented by at least two logs.  A "last log" and a second
//   log.  The named thread does not contain two such logs.
// *Action:  Either find more logs from the named thread.  Or use the
//        RESETLOGS option to CREATE CONTROLFILE.
01198, 00000, "must specify size for log file if RESETLOGS"
// *Cause:  File sizes must be given for all logfiles if doing a CREATE
//          CONTROLFILE with the RESETLOGS option.
// *Action: Resubmit the command with the appropriate logfile size.
01199, 00000, "file %s is not in online backup mode"
// *Cause: Attempting to end an online backup for a file that is not in online
//         backup.
// *Action: Do not enter command since it is not needed.
01200, 00000, "actual file size of %s is smaller than correct size of %s blocks"
// *Cause:  The size of the file as returned by the operating system is smaller
//         than the size of the file as indicated in the file header and the
//         control file. Somehow the file has been truncated. Maybe it is the
//         result of a half completed copy.
// *Action: Restore a good copy of the data file and do recovery as needed.
01201, 00000, "file %s header failed to write correctly"
// *Cause:  An I/O error was reported for the file header.  The error was 
//         trapped and a second attempt will be made.
// *Action: The file probably will require recovery.  Further error messages 
//         will indicate what is needed.
01202, 00000, "wrong incarnation of this file - wrong creation time"
// *Cause:  The creation time in the file header is not the same as the
//         creation time in the control file. This is probably a copy of a
//         file that was dropped.
// *Action: Restore a current copy of the data file and do recovery as needed.
01203, 00000, "wrong incarnation of this file - wrong creation SCN"
// *Cause:  The creation SCN in the file header is not the same as the
//         creation SCN in the control file. This is probably a copy of a
//         file that was dropped.
// *Action: Restore a current copy of the data file and do recovery as needed.
01204, 00000, "file number is %s rather than %s - wrong file"
// *Cause:  The file number in the file header is not correct. This is probably
//         a restored backup of the wrong file, but from the same database.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01205, 00000, "not a data file - type number in header is %s"
// *Cause:  The file type in the header is not correct for a data file. This
//         is probably a log file or control file. If the type is not a small 
//         non-zero positive number then the header is corrupted.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01206, 00000, "file is not part of this database - wrong database id"
// *Cause:  The database ID in the file header does not match the database id
//         in the control file. The file may be from a different database, or
//         it may not be a database file at all. If the database was rebuilt,
//         this may be a file from before the rebuild. Note that if you see 
//         this error when the file is supposed to be plugged in from another
//         database via the Transportable Tablespace feature, it means the 
//         database ID in the file header does not match the one expected.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01207, 00000, "file is more recent than control file - old control file"
// *Cause:  The control file change sequence number in the data file is 
//         greater than the number in the control file. This implies that
//         the wrong control file is being used. Note that repeatedly causing
//         this error can make it stop happening without correcting the real
//         problem. Every attempt to open the database will advance the
//         control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to 
//         make the control file current. Be sure to follow all restrictions 
//         on doing a backup control file recovery.
01208, 00000, "data file is an old version - not accessing current version"   
// *Cause:  The checkpoint in the file header is less recent than in the   
//         control file. If opening a database that is already open by another 
//         instance, or if another instance just brought this file online,
//         the file accessed by this instance is probably a different version.
//         Otherwise, a backup of the file probably was restored 
//         while the file was in use.  
// *Action: Make the correct file available to the database. Then, either open
//         the database, or execute ALTER SYSTEM CHECK DATAFILES.  
01209, 00000, "data file is from before the last RESETLOGS"   
// *Cause:  The reset log data in the file header does not match the   
//         control file. If the database is closed or the file is offline,  
//         the backup is old because it was taken before the last ALTER   
//         DATABASE OPEN RESETLOGS command. If opening a database that is   
//         open already by another instance, or if another instance just   
//         brought this file online, the file accessed by this instance is 
//         probably a different version. Otherwise, a backup of the file 
//         probably was restored while the file was in use.   
// *Action: Make the correct file available to the database. Then, either open
//         the database, or execute ALTER SYSTEM CHECK DATAFILES.  
01210, 00000, "data file header is media corrupt"
// *Cause: The file header block is internally inconsistent. The beginning
//         of the block has a header with a checksum and other data for
//         insuring the consistancy of the block. It is possible that
//         the last disk write did not operate correctly. The most likely
//         problem is that this is not a datafile for any database.
// *Action: Have operating system make correct file available to database.
//         If the trace file dump indicates that only the checksum is wrong,
//         restore from a backup and do media recovery.
01211, 00000, "Oracle7 data file is not from migration to Oracle8"
// *Cause: The file is not a copy of the file LAST used under Oracle7. This
//         datafile is either a backup taken from before the migration, or 
//         the database was opened by Oracle7 after the migration utility was
//         run. When converting a database from Oracle7 to Oracle8, the migration
//         program MUST be the LAST utility to access the database under Oracle7.
//         Only the datafiles that were current when the migration was done
//         may be accessed by Oracle8. 
// *Action: Have operating system make correct data file available to database,
//         or repeat the Oracle7 to Oracle8 migration. Make sure that
//         database is NOT opened after migration utility is run.
01212, 00000, "MAXLOGMEMBERS may not exceed %s"
// *Cause:  MAXLOGMEMBERS specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGMEMBERS
01213, 00000, "MAXINSTANCES may not exceed %s"
// *Cause:  MAXINSTANCES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXINSTANCES
01214, 00000, "MAXLOGHISTORY may not exceed %s"
// *Cause:  MAXLOGHISTORY specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGHISTORY
01215, 00000, "enabled thread %s is missing after CREATE CONTROLFILE"
// *Cause:  A CREATE CONTROLFILE statement was given which did not
//          list all the enabled threads for the database.
// *Action: Reissue the CREATE CONTROLFILE statement, including all enabled
//          threads.
01216, 00000, "thread %s is expected to be disabled after CREATE CONTROLFILE"
// *Cause:  A thread that was given during CREATE CONTROLFILE is enabled, but
//          the datafiles indicate that it should be disabled.  This is
//          probably because the logs supplied to the CREATE CONTROLFILE
//          are old (from before the disabling of the thread).
// *Action: This thread is not required to run the database.  The CREATE
//          CONTROLFILE statement can be reissued without the problem thread,
//          and, if desired, the thread can be recreated after the database
//          is open.
01217, 00000, "logfile member belongs to a different logfile group"
// *Cause:  A member of a multiple-member logfile group specified in a
//          CREATE CONTROLFILE is not part of the same group as previous
//          members.
// *Action: Group together the correct members for the CREATE CONTROLFILE
//          command.
01218, 00000, "logfile member is not from the same point-in-time"
// *Cause:  A member of a multiple-member logfile group is from a different
//          point in time.  One of the members specified may be an older
//          (backup) copy of the log.
// *Action: Find the correct version of the log, or leave it out of the
//          CREATE CONTROLFILE command.
01219, 00000, "database not open: queries allowed on fixed tables/views only"
// *Cause:  A query was issued against an object not recognized as a fixed
//          table or fixed view before the database has been opened.
// *Action: Re-phrase the query to include only fixed objects, or open the
//          database.
01220, 00000, "file based sort illegal before database is open"
// *Cause:  A query issued against a fixed table or view required a temporary
//          segment for sorting before the database was open.  Only in-memory
//          sorts are supported before the database is open.
// *Action: Re-phrase the query to avoid a large sort, increase the values
//          of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE 
//          initialization parameters to enable the sort to be done in memory.
01221, 00000, "data file %s is not the same file to a background process"
// *Cause:  When the database writer opens the data file, it is accessing a
//          different physical file than the foreground doing the recovery.
//          The timestamp set in the file header by the foreground was not
//          found by the background. It may be that the background process
//          could not read the file at all.
// *Action: Look in the DBWR trace file for the error it recieved when
//          attempting to read the file header. Reconfigure the operating
//          system as needed to have the file name successfully access the
//          same file when opened by a background process.
01222, 00000, "MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s"
// *Cause:  Attemping to create a database or control file that does not have
//          room for at least two logs per thread of redo. A thread of redo
//          must have two online logs in order to be enabled. It does not make
//          sense to allow more redo threads than can be supported by the logs.
// *Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
01223, 00000, "RESETLOGS must be specified to set a new database name"
// *Cause:  The SET database name option was specified to CREATE CONTROLFILE,
//          but RESETLOGS was not specified. The database name can only be
//          changed when opening the database with RESETLOGS.
// *Action: Either add the RESETLOGS option or drop the SET option to
//          CREATE CONTROLFILE.
01224, 00000, "group number in header %s does not match GROUP %s"
// *Cause: Group number specified at CREATE CONTROLFILE does not match the
//         group number stored in the header. Most likely the specification
//         is wrong.
// *Action: Omit the GROUP option or give the correct one.
01225, 00000, "thread number %s is greater than MAXINSTANCES %s"
// *Cause: The log is for a thread greater than the MAXINSTANCES argument.
// *Action:Increase the value for MAXINSTANCES and resubmit the command.
01226, 00000, "file header of log member is inconsistent with other members"
// *Cause: The log file member in the accompanying error is for the same group
//         as the previous members, but other fields in the header are
//         different. Either a file header is corrupted, or some file is a
//         member of a deleted log.
//*Action: Find the correct log member or omit this member from the command.
01227, 00000, "log %s is inconsistent with other logs"
// *Cause: The log file in the accompanying error is inconsistent with the 
//         contents of other logs given in the CREATE CONTROLFILE command.
//         Either a file header is corrupted, or some file is an old copy
//         rather than the current version. The problem may not be with the
//         log listed since all that can be detected is that there is an
//         inconsistancy. All log files listed in the command must be the
//         current versions of the online logs.
//*Action: Find the correct online logs or use the RESETLOGS option.
01228, 00000, "SET DATABASE option required to install seed database"
// *Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE
//         command when installing a seed database. The database does not have
//         a database ID because it is intended to be installed at multiple
//         sites, and each site needs to be a different database with its own
//         database id. Both the SET DATABASE and RESETLOGS options must be
//         specified to create the control file for this database.
//*Action: Resubmit command with the SET DATABASE and RESETLOGS options.
01229, 00000, "data file %s is inconsistent with logs"
// *Cause: The data file in the accompanying error is inconsistent with the 
//         contents of the logs given in the CREATE CONTROLFILE command.
//         The most likely cause is that one or more of the online logs
//         was missing from the command. It is also possible that one or
//         more of the logs is an old copy rather than the current version.
//         All online log files must be listed in the command and must be the
//         current versions of the online logs.
//*Action: Find the correct online logs or use the RESETLOGS option.
01230, 00000, "cannot make read only - file %s is offline"
// *Cause: An attempt to make a tablespace read only found that one of its
//         files is offline.
// *Action: Bring the file online and retry this command.
01231, 00000, "cannot make read write - file %s is offline"
// *Cause: An attempt to make a tablespace read write found that one of its
//         files is offline.
// *Action: Bring the file online and retry this command.
01232, 00000, "cannot start online backup - file %s is being made read-only"
// *Cause: An attempt to start an online backup found that one of the files is
//         in transition to read-only mode.
// *Action: Wait for the transition to complete and then retry the command, if
//         this is an ALTER DATABASE BEGIN BACKUP command, or take the backup
//         without any begin or end commands, if this is an ALTER TABLESPACE
//         BEGIN BACKUP command.
01233, 00000, "file %s is read only - cannot recover using backup control file"
// *Cause: An attempt to do media recovery using a backup control file found
//        that one of the files is marked read only. Read only files do not
//        normally need to be recovered, but recovery with a backup
//        control file must recover all online files.
// *Action: If the file really is read only, take it offline before the
//         recovery, and bring the read only tablespace online after the
//         database is open. If the file does need recovery use a control file
//         from the time the file was read-write. If the correct control file
//         is not available, use CREATE CONTROLFILE to make one.
01234, 00000, "cannot end backup of file %s - file is in use or recovery"
// *Cause: Attempted to end an online backup of file when the file is busy.
//        Some operation such as recovery or rename may be active, or there
//        may still be some instance that has the database open with this
//        file online.
// *Action: If there is an instance with the database open then the backup
//        can be ended there by using the ALTER TABLESPACE command. Otherwise
//        wait for the completion of the other operation.
01235, 00000, "END BACKUP failed for %s file(s) and succeeded for %s"
// *Cause: One or more of the files in an end backup command failed. Some other
//        files given in the same command may have succeeded.
// *Action: See the accompanying error messages for the reason the backups
//        could not be ended. Any files not listed in the error messages were
//        successful.
01236, 00000, "Error %s occurred during initialization of file header access"
// *Cause:  The indicated error occurred while doing initialization 
//         processing of file headers.
// *Action: The error indicated should be corrected.  An attempt is made to 
//         recover from this error by using a slower access algorithm.
01237, 00000, "cannot extend datafile %s"
// *Cause:  An operating system error occurred during the resize.
// *Action: Fix the cause of the operating system error and retry the command.
01238, 00000, "cannot shrink datafile %s"
// *Cause:  An operating system error occurred during the resize.
// *Action: The error is ignored, operation continues normally.
01239, 00000, "database must be in ARCHIVELOG mode to use external cache"
// *Cause:  An online file uses an external cache, but the database is in
//          NOARCHIVELOG mode. Since an external cache may require media
//          recovery this can not be allowed.
// *Action: Change database to be in ARCHIVELOG mode or do not use an
//          external cache.
01240, 00000, "too many data files to add in one command"
// *Cause:  The command specifies adding more data files than can be done in
//          one command. It is necessary to fit all the file names into one
//          log entry, but that would make the entry too large.
// *Action: If this is a CREATE TABLESPACE command, create with fewer files
//          then add the other files later. If this is an ADD DATAFILE command,
//          break it up into multiple commands.
01241, 00000, "an external cache has died"
// *Cause:  The external cache may have been restarted.
// *Action: Take the file mentioned in the error stack offline, perform media
//          recovery, bring the file online, and retry the attempted 
//          operation.  You may also restart all instances to make sure 
//          they access all data files through consistent external caches.
01242, 00000, "data file suffered media failure: database in NOARCHIVELOG mode"
// *Cause:  The database is in NOARCHIVELOG mode and a database file was
//          detected as inaccessible due to media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
//          and restart the instance.
01243, 00000, "system tablespace file suffered media failure"
// *Cause:  A system tablespace file was detected as inaccessible due to
//          media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
//          and restart the instance.
01244, 00000, "unnamed datafile(s) added to control file by media recovery"
// *Cause:  Media recovery with a backup control file or a control file that
//          was rebuilt, encountered the creation of a datafile that was not
//          in the control file. An entry has been added to the control file
//          for the new datafiles, but with the file name UNNAMEDnnnn, where
//          nnnn is the file number. Attached errors describe the file names
//          that were originally used to create the files. 
// *Action: Rename the files to valid file names and resume recovery. If
//          necessary the command ALTER DATABASE CREATE DATAFILE may be used
//          to create a file suitable for recovery and do the rename. If the
//          file is not going to be recovered then take it offline with the
//          FOR DROP option.
01245, 00000, "offline file %s will be lost if RESETLOGS is done"
// *Cause:  Attempting to do an OPEN RESETLOGS with a file that will be lost
//          because it is offline. The file was not taken offline with the
//          FOR DROP option.
// *Action: Either bring the file online and recover it, or take it offline
//          with the FOR DROP option.
01246, 00000, "recovering files through TSPITR of tablespace %s"
// *Cause:  The files named in the accompanying errors are backups that were
//          made before a tablespace point in time recovery of this tablespace.
//          They cannot be recovered to a time after the point in time
//          recovery.
// *Action: Restore more recent backups and recover them.
01247, 00000, "database recovery through TSPITR of tablespace %s"
// *Cause:  Recovery of the whole database encountered redo indicating there
//          was a point in time recovery of the tablespace. The new version
//          of the files in the tablespace should be included in the recovery,
//          but that was not done.
// *Action: If the tablespace should not be recovered, take its file offline
//          for drop. If it should be recovered, then restore or rename as
//          needed and restart the recovery.
01248, 00000, "file %s was created in the future of incomplete recovery"
// *Cause:  Attempting to do a RESETLOGS open with a file entry in the
//          control file that was originally created after the UNTIL time 
//          of the incomplete recovery.
//          Allowing such an entry may hide the version of the file that 
//          is needed at this time.  The file number may be in use for 
//          a different file which would be lost if the RESETLOGS was allowed.
// *Action: If more recovery is desired then apply redo until the creation
//          time of the file is reached. If the file is not wanted and the
//          same file number is not in use at the stop time of the recovery,
//          then the file can be taken offline with the FOR DROP option.
//          Otherwise a different control file is needed to allow the RESETLOGS.
//          Another backup can be restored and recovered, or a control file can
//          be created via CREATE CONTROLFILE.
01249, 00000, "archiving not allowed in a clone database"
// *Cause:  Attempting to archive an online redo log or enable archiving
//          for a clone database.
// *Action: Do not attempt to archive from a clone. The archive log destination
//          could easily be the same as the primary database destroying its
//          archived logs. If archiving is needed then recreate database as
//          not a clone.
01250, 00000, "Error %s occurred during termination of file header access"
// *Cause:  The indicated error occurred while terminating the   
//         processing of file headers.  The error was other than a write
//         error.
// *Action: The indicated error should be corrected.  
01251, 00000, "Unknown File Header Version read for file number %s"
// *Cause:  Read of the file header returned a record but its version cannot  
//         be identified.  Either the header has been corrupted, or the file
//         is not a valid database file.
// *Action: Have the operating system make the correct file available to  
//         the database, or recover the file.  
01252, 00000, "cannot prevent writes - file %s in recovery manager backup"
// *Cause: An attempt to make a tablespace read only or offline normal found
//          that a recovery manager proxy backup is in progress.  If the file
//          is made offline or read-only, then the file header cannot be
//          updated when the backup is complete.
// *Action: Wait for the Recovery Manager backup to complete and retry this
//          command.
01253, 00000, "cannot start online backup - file %s in recovery manager backup"
// *Cause: The specified file is being backed up by Recovery Manager.
// *Action: Wait for the Recovery Manager proxy backup to complete before
//          starting another backup.
01254, 00000, "cannot end online backup - file %s in recovery manager backup"
// *Cause: The specified file is being backed up by Recovery Manager.
// *Action: Wait for the Recovery Manager proxy backup to complete.  Recovery
//          Manager backup mode cannot be initiated or terminated manually.
01255, 00000, "cannot shutdown - file %s in recovery manager backup"
// *Cause: An attempt to shutdown normally found that a Recovery Manager
//         backup is still in progress.
// *Action: Wait for the Recovery Manager proxy backup to complete and retry
//          this command.
01256, 00000, "error in locking database file %s"
// *Cause:  The file is in use by another database instance.
// *Action: Determine which database instance legitimately owns the file. 
01257, 00000, "cannot reuse database file %s, unknown file size"
// *Cause:  The size of the raw partion cannot be determined
// *Action: Add the datafile/logfile by specifying the size parameter.
01258, 00000, "unable to delete temporary file %s"
// *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES 
//         or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES
//         operation was not able to delete a temporary file in the 
//         database.
// *Action: Subsequent errors describe the operating system error that
//          prevented the file deletion.  Fix the problem, if possible, and
//          manually purge the file.
01259, 00000, "unable to delete datafile %s"
// *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation
//         was not able to delete a datafile in the tablespace.
// *Action: Subsequent errors describe the operating system error that
//          prevented the file deletion.  Fix the problem, if possible, and
//          manually purge the file.
01260, 00000, "warning: END BACKUP succeeded but some files found not to be in backup mode"
// *Cause: END BACKUP completed successfully for all files that were in online
//         backup mode. However one or more modifiable files were found not
//         to be in online backup mode. Backup of those files (if it was done)
//         can be invalid and, if restored, can result in an inconsistent
//         database.
// *Action: Check the alert log for a list of the files that were found not 
//          to be in backup mode. If there is a possibility that those files
//          have been modified during online backup, then replace their 
//          backups with new ones.
01261, 00000, "Parameter %s destination string cannot be translated"
// *Cause: The value for the specified parameter contained a destination
//         string that could not be translated.
// *Action: Use a valid destination string in the specified parameter.
01262, 00000, "Stat failed on a file destination directory"
// *Cause: Unable to get information about an Oracle managed files
//         destination directory.
// *Action: Check the permissions on the directory or use a different
//          directory name.
01263, 00000, "Name given for file destination directory is invalid"
// *Cause: The name given for an Oracle managed files destination 
//         does not correspond to a directory.
// *Action: Use a different name.
01264, 00000, "Unable to create %s file name"
// *Cause: Unable to create an Oracle managed file name.
// *Action: Check previous error messages for the reason Oracle
//          was unable to create the file name.  Take corrective
//          action, if possible, and retry the command.
01265, 00000, "Unable to delete %s %s"
// *Cause: An error prevented the file from being deleted.
// *Action: See the subsequent error messsages that describe the operating
//          system error that prevented the file from being deleted. If
//          possible, fix the problem and manually delete the file.
01266, 00000, "Unable to create unique file name"
// *Cause: Unable to create a unique file name for an Oracle managed file.
//         Oracle tried several names but each file name was already in use
//         in the default destination directory for the file type.
// *Action: Retry the operation.  If that fails, also, it may be 
//          necessary to change the default destination directory for
//          the file type and then retry.
01267, 00000, "Failure getting date/time"
// *Cause: Could not get date/time when trying to create unique
//         file name.
// *Action: Internal error - contact Oracle Customer Support. 
01268, 00000, "invalid TEMPFILE clause for alter of permanent TABLESPACE"
// *Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for 
//         a permanent tablespace.
// *Action: Retry with a DATAFILE clause.
01269, 00000, "Destination parameter string is too long"
// *Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or
//         DB_RECOVERY_FILE_DEST parameter was too long.
// *Action: Replace the destination value for the specified parameter with
//          a shorter character string.
01270, 00000, "%s operation is not allowed if STANDBY_PRESERVES_NAMES is true"
// *Cause: An operation that renames or adds/drops a file was attempted
//         at a standby database and STANDBY_PRESERVES_NAMES is true.
// *Action: Set STANDBY_PRESERVES_NAMES false if the operation must be
//          performed.
01271, 00000, "Unable to create new file name for file %s"
// *Cause: During standby database recovery an error occurred when trying
//         to create a new file name for the indicated file.
// *Action: Use the ALTER DATABASE CREATE DATAFILE command with a new
//          unique name and then resume the standby database recovery.
01272, 00000, "REUSE only allowed when a file name is provided."
// *Cause: The REUSE parameter was specified in a command without a 
//         file name.
// *Action: Either supply a file name or remove the REUSE parameter.
01273, 00000, "STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = %s or higher"
// *Cause: The COMPATIBLE initialization parameter was not set to the 
//         correct value for setting STANDBY_FILE_MANAGEMENT to AUTO.
// *Action: Restart the instance with COMPATIBLE set to the correct release.
// *Cause: Automated standby file management was disabled, so an added file
01274, 0000, "cannot add datafile '%s' - file could not be created"
// *Cause: Automated standby file management was disabled, so an added file
//         could not automatically be created on the standby.
//         The error from the creation attempt is displayed in another message.
//         The control file file entry for the file is 'UNNAMEDnnnnn'.
// *Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
//          file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart
//          standby recovery.
01275, 00000, "Operation %s is not allowed if standby file management is automatic."
// *Cause: An operation that renames, adds, or drops a file was attempted
//         at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
// *Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be
//          performed.
01276, 00000, "Cannot add file %s.  File has an Oracle Managed Files file name."
// *Cause: An attempt was made to add to the database a datafile, log file, 
//         control file, snapshot control file, backup control file,
//         datafile copy, control file copy or backuppiece with an Oracle
//         Managed Files file name.
// *Action: Retry the operation with a new file name.
01277, 00000, "file '%s' already exists"
// *Cause:  An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'
//          command specified a file name which is already in use.
// *Action: Either specify a different file name, or add the REUSE parameter
//          to the command to overwrite the existing file.
01278, 00000, "error creating file '%s'"
// *Cause:  An operating system error occurred while attempting to create a
//          trace file specified in the command ALTER DATABASE BACKUP 
//          CONTROLFILE TO TRACE AS 'filename'.
// *Action: Check the error stack for more detailed information.
01279, 00000, "db_files too large"
// *Cause:  db_files has been set too high to be supported by the system.
// *Action: Decrease the number of db_files.
/
/        1280-1399 LogMiner errors
/
01280, 00000, "Fatal LogMiner error."
// *Cause: An internal error occurred inside LogMiner.
// *Action: Check the alert log and trace files for further information.
01281, 00000, "SCN range specified is invalid"
// *Cause: StartSCN may be greater than EndSCN, or the SCN specified may be 
//         invalid.
// *Action: Specify a valid SCN range.
01282, 00000, "date range specified is invalid"
// *Cause: startTime may be greater than endTime.  startTime or endTime may be
//         greater than year 2110.  startTime may be less than year 1988.
// *Action: Specify a valid date range.
01283, 00000, "Options specified is invalid"
// *Cause: The specified options parameter is invalid for the procedure.
// *Action: Specify valid Options parameter.
01284, 00000, "file %s cannot be opened"
// *Cause: The file or directory may not exist or may be inaccessible.  
//         Pathname exceeds 256 characters.
// *Action: Ensure that the file and the directory exist and are accessible.
01285, 00000, "error reading file %s"
// *Cause: The file or directory may not exist or is inaccessible.
// *Action: Specify valid file or directory. Make sure that file and directory
//          are accessible.
01286, 00000, "start interval required"
// *Cause: Options were supplied which require a starting time or starting SCN
// *Action: Specify a starting interval (time or SCN).
01287, 00000, "file %s is from a different database incarnation"
// *Cause: The logfile is produced by a different incarnation of the database.
// *Action: Add a logfile that is produced by the same incarnation.
01288, 00000, "cannot apply this DDL to the Logminer Dictionary"
// *Cause: A command that is not supported by Logminer was present in
//         a logfile.  Commands that change the character set of the database
//         are not supported by Logminer.
//         "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.
// *Action: Do not execute unsupported commands when using Streams, Logical
//          Standby, or Logminer. Turn off DDL tracking in order for Logminer
//          to skip unsupported commands.
01289, 00000, "cannot add duplicate logfile %s"
// *Cause: The logfile specified has already been added to the list of 
//         logfiles.
// *Action: Specify a different logfile.
01290, 00000, "cannot remove unlisted logfile %s"
// *Cause: The user attempted to remove a logfile that is not present in the
//         list.
// *Action: Specify a valid logfile.
01291, 00000, "missing logfile"
// *Cause:  Not all logfiles corresponding to the time or scn range specified
//          have been added to the list. 
// *Action: Check the v$logmnr_logs view to determine the missing scn 
//          range, and add the relevant logfiles.
01292, 00000, "no log file has been specified for the current LogMiner session"
// *Cause:  No logfile has been specified for the LogMiner session.
// *Action: Specify atleast one log file.
01293, 00000, "mounted database required for specified LogMiner options" 
// *Cause:  Options were specified which required the database to be mounted 
// *Action: Specify different options or mount the database.
01294, 00000, "error occurred while processing information in dictionary file %s, possible corruption"
// *Cause:    The dictionary file is corrupt.
// *Action:   Get a new dictionary file.
01295, 00000, "DB_ID mismatch between dictionary %s and logfiles"
// *Cause: The dictionary file is produced by a database that is different
//         from that produced the logfiles.
// *Action: Specify a compatible dictionary file.
01296, 00000, "character set mismatch between dictionary %s and logfiles"
// *Cause: The character set of the database that produced the dictionary
//         file is different from the charatcter set of the database
//         that produced the logfiles.
// *Action: Specify a dictionary file with the same character set.
01297, 00000, "redo version mismatch between dictionary %s and logfiles"
// *Cause: The redo version of the database generating the dictionary is
//         different from the one generating the logfiles.
// *Action: 
01298, 00000, "conflicting dictionary option"
// *Cause:  More than one dictionary source was specified or DDL_DICT_TRACKING
//          was specified with DICT_FROM_ONLINE_CATALOG.
// *Action: 
01299, 00000, "dictionary %s corresponds to a different database incarnation"
// *Cause:  The dictionary file was extracted from a different incarnation of
//          the database.
// *Action: Specify a dictionary file extracted from the correct database
//          incarnation.
01300, 00000, "writable database required for specified LogMiner options"
// *Cause:  Options were specified which required the database to be writable. 
// *Action: Specify different options or open the database for write access.
01301, 00000, "error writing to file during flat file build"
// *Cause: Error writing to file during flat file build
// *Action: 
01302, 00000, "dictionary build options missing or incorrect"
// *Cause: Missing dictionary build options or incorrectly specified options
// *Action: Specify either a build to redo log or to flat file.  If build to
//    flat file, specify filename and directory.        
01303, 00000, "subordinate process error: %u.  Check alert and trace logs"
// *Cause: A process subordinate to this Logminer process has exited with
//         this error status.
// *Action: Search for this error in the alert log and trace files for
//    additional information.
01304, 00000, "subordinate process error.  Check alert and trace logs"
// *Cause: A process subordinate to this Logminer process has exited with an
//         error condition.
// *Action: Look in the alert log and trace files for additional information.
01306, 00000, "dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents"
// *Cause: A select was issued from v$logmnr_contents without first invoking
//         the dbms_logmnr.start_logmnr() procedure. 
// *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing
//          a select from the v$logmnr_contents view.
01307, 00000, "no LogMiner session is currently active"
// *Cause: A select was issued from v$logmnr_contents without first invoking
//         the dbms_logmnr.start_logmnr() procedure. Otherwise, 
//         dbms_logmnr.end_logmnr() was called without a prior call to 
//         dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile()
// *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing
//          a select from the v$logmnr_contents view.
01308, 00000, "initialization parameter utl_file_dir is not set"
// *Cause: utl_file_dir is not set in the initialization file.
// *Action: Set utl_file_dir to the appropriate directory.
01309, 00000, "invalid session"
// *Cause: The specified Logminer session ID or session handle is invalid.
// *Action: Use a valid Logminer session ID or session handle.
01310, 00000, "requested return type not supported by the lcr_mine function"
// *Cause: The return type requested by the user is not supported by lcr_mine"
// *Action: Pick a return type supported by the lcr_mine function"
01311, 00000, "Illegal invocation of the mine_value function"
// *Cause: An attempt was made to use mine_value  function on a column 
//         other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS
//         or SYS.V$LOGMNR_CONTENTS fixed table/view.
// *Action: Rewrite the SQL statement with a legal invocation of mine_value
01312, 00000, "Specified table/column  does not exist"
// *Cause: The table/column specified in the lcr_mine call does not exist
//         at the the specified SCN. The table/column definition has to exist
//         at the start SCN specified for lcr_mine to be able to identify
//         the table/column correctly.
// *Action: Create a LogMiner session at a start SCN at which the table 
//          definition is available.
01313, 00000, "LogMiner dictionary column type different from specified type"
// *Cause: The return type specified for the column in lcr_mine call 
//         is different from the actual type of the column.
// *Action: Rewrite the lcr_mine invocation with the right return type.
01314, 00000, "Name of the column to be mined should be a string literal"
// *Cause: The fully qualified name of the column to be mined 
//         by the LogMiner functions should be string literal. 
// *Action: If the fully qualified name of the column to be mined is a.b.c.d,
//          enclose the column name in quotes as in 'a.b.c.d'.
01315, 00000, "Log file has been added or removed during select"
// *Cause: A redo log file has been added or removed while selecting 
//         on the v$logmnr_logs fixed view.
// *Action: Re-issue the SQL select statement on the v$logmnr_logs view.
01316, 00000, "Already attached to a Logminer session"
// *Cause: A Logminer attach session was issued while already attached 
//         to a Logminer session.
// *Action: Detach from the current Logminer session and attach to the 
//          requested session.
01317, 00000, "Not attached to a Logminer session"
// *Cause: A command or procedure was issued which requires an attached 
//         Logminer session.
// *Action: Attach to a Logminer session before issuing the command or 
//          procedure.
01319, 00000, "Invalid Logminer session attribute"
// *Cause: A session attribute was supplied which is invalid.
// *Action: Re-issue with valid session attribute.
01320, 00000, "Invalid Logminer dictionar attribute"
// *Cause: A Logminer dictionary attribute was supplied which is invalid.
// *Action: Re-issue with valid dictionary attribute.
01321, 00000, "No Logminer Dictionary for requested start SCN"
// *Cause: The requested session start SCN is less than the SCN of any
//         available Logminer Dictionary build.  It is not possible to
//         unwind a Logminer Dictionary to the requested start SCN.
// *Action: Re-issue the start_logminer request with a start SCN for
//          which a Logminer Dictionary is available.
01322, 00000, "No such table"
// *Cause: An non-existent table was supplied to Logminer include_src_tbl()
//         or exclude_src_table().
// *Action: Re-issue with valid table name.
01323, 00000, "Invalid state"
// *Cause: A Logminer routine was called from the wrong state.
// *Action:
01324, 00000, "cannot add file %s due to DB_ID mismatch"
// *Cause: The logfile is produced by a different database than other logfiles
//         already added to the list.
// *Action: Specify a logfile produced by the same database.
01325, 00000, "archive log mode must be enabled to build into the logstream"
// *Cause: Database does not have archivelog mode enabled.
// *Action: Mount the database, then issue commands to enable archivelog mode.
//              startup pfile=init.ora mount
//              alter database archivelog
//              alter database open
01326, 00000, "compatability of 9.0 or greater required to build into the logstream"
// *Cause: Compatibility mode set to some value less than 9.0
// *Action: Ensure that init.ora parameter establishing a compatability of
//          9.0 or greater is set.  For example:
//              compatible=9.0.0.0.0
01327, 00000, "failed to exclusively lock system dictionary as required by build"
// *Cause: Other users are performing DDL operations.
// *Action:
01328, 00000, "only one build operation may occur at one time"
// *Cause: Another processes is simultaneously attempting to run build();
// *Action: Wait until the other processes completes.
01329, 00000, "unable to truncate required build table"
// *Cause: The table may be missing, or locked by another user.
// *Action:
01330, 00000, "problem loading a required build table"
// *Cause:
// *Action:
01331, 00000, "general error while running build"
// *Cause:
// *Action:
01332, 00000, "internal Logminer Dictionary error"
// *Cause: Unexpected error condition
// *Action: Check trace and/or alert logs
01333, 00000, "failed to establish Logminer Dictionary"
// *Cause: No previously established Logminer Dictionary is available
//         and a complete gather of a source system data dictionary was not
//         found in the logstream.  build() may not have been run
//         to force the gathering of a source system data dictiony.
//         Or add_log_file() may not have been called to add all log
//         files which contain the complete gathered system data dictionary.
// *Action: If build() was not employed prior to this mining session
//         the Logminer Ad Hoc user may elect to employ an alternate
//         dictionary such as the current system catalog or a previously
//         built flat file dictionary.  Other Logminer clients must run
//         build() prior to mining.  If build() has been run, ensure that
//         all logfiles which comprise the gathered system dictionary
//         have beed added.  The following query, run on the system which
//         build() was run, can be helpful in identifying the requried files.
//
//         select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log;
//
//         Minimally a set of files beginning with one which has
//         DICTIONARY_BEGIN = 'YES' and all following log files through
//         one marked DICTIONARY_END = 'YES' must be added.
01334, 00000, "invalid or missing logminer dictionary processes context"
// *Cause: Unexpected internal error condition
// *Action:
01335, 00000, "feature not yet implemented"
// *Cause:
// *Action:
01336, 00000, "specified dictionary file cannot be opened"
// *Cause: The dictionary file or directory does not exist or is inaccessible.
// *Action: Make sure that the dictionary file and directory exist and are
//          accessible.
01337, 00000, "log file has a different compatibility version"
// *Cause: The logfile has a different compatibility version then the rest 
//         of the logfile in the session"
// *Action: Make sure that the logfile has the same compatibility version
//          as the rest of the logfiles in the session.
//
01338, 00000, "Other process is attached to LogMiner session"
// *Cause: Can not do this when other process is attached to LogMiner session.
// *Action:
01339, 0000,  "LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary"
// *Cause: Unexpected result while accessing system catalog metadata.
// *Action: Check the alert log.
01340, 00000, "NLS error"
// *Cause: Could not load NLS package.
// *Action:
01341, 00000, "LogMiner out-of-memory"
// *Cause: The LogMiner session requires more system resources than is 
//         currently available.
// *Action: Allocate more SGA for LogMiner.
01342, 00000, "LogMiner can not resume session due to inability of staging checkpointed data"
// *Cause: Logmnr can not resume session because there is not enough SGA 
//         memory available to read in checkpointed data.  Logminer 
//         periodically checkpoints data to enable faster crash recovery.
// *Action: Specify a bigger max_sga for the given LogMiner session and
//          try again. 
01343, 00000, "LogMiner encountered corruption in the logstream"
// *Cause:  Log file is missing a range of scn values.
// *Action: Verify the contiguity of the scn range reprented by the log files 
//          added to LogMiner.
01344, 00000, "LogMiner coordinator already attached"
// *Cause: A coordinator process is already attached to the specified
//         logminer context.
// *Action: Detach from the active coordinator session and retry the attach.
01345, 00000, "Must be a LogMiner coordinator process"
// *Cause: A LogMiner client attempted to perform a privileged operation.
// *Action: Issue the operation from the coordinator process.
01346, 00000, "LogMiner processed redo beyond specified reset log scn"
// *Cause: LogMiner has detected a new branch with resetlogs scn information
//         prior to redo already mined.
// *Action: Contact your customer support representative.
01347, 00000, "Supplemental log data no longer found"
// *Cause: The source database instance producing log files for this LogMiner 
//         session was altered to no longer log supplemental data.
// *Action: Destroy this Logminer session.  Re-enable supplemental log data 
//          on the source system and create a new LogMiner session.
01348, 00000, "LogMiner testing event"
// *Cause: 
// *Action: 
01349, 00000, "LogMiner tracing event"
// *Cause: 
// *Action: 
01350, 00000, "must specify a tablespace name"
// *Cause: Invocation failed to specify a valid tablespace
// *Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include
//          the name of a valid tablespace.
01351, 00000, "tablespace given for Logminer dictionary does not exist"
// *Cause: The tablespace name given as a parameter to
//         DBMS_LOGMNR_D.SET_TABLESPACE
//         does not exist.
// *Action: Check spelling of the tablespace name.  If spelling is correct
//          verify that the named tablespace has already been created.
//          DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
01352, 00000, "tablespace given for Logminer spill does not exist"
// *Cause: The tablespace name given as the parameter to
//         DBMS_LOGMNR_D.SET_TABLESPACE
//         does not exist.
// *Action: Check spelling of the tablespace name.  If spelling is correct
//          verify that the named tablespace has already been created.
//          DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
01353, 00000, "existing Logminer session"
// *Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while
//         a Logminer session(s) was active.
// *Action: First cause all Logminer sessions to be closed.  A Logminer
//          session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR
//          or as the result of using Oracle features such as 
//          Data Guard SQL Apply or Streams which use Logminer.
//          Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
01354, 00000, "Supplemental log data must be added to run this command"
// *Cause:  An attempt was made to perform an operation that required
//          that supplemental log data be enabled.
// *Action: Execute a command such as
//            ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
//          and then reissue the command that failed with this error.
01355, 00000, "logminer tablespace change in progress"
// *Cause:  The tables used by logminer are in the process of being
//          moved to another tablespace.
// *Action: Wait until the move is complete and try again.
01356, 00000, "active logminer sessions found"
// *Cause:  Logminer sessions are currently active.
// *Action: End all logminer sessions and retry.
01358, 00000, "LogMiner version is less than mined dictionary version"
// *Cause:  An attempt was made to mine a LogMiner dictionary from redo logs.
//          The version of the Oracle database that created the logs was higher
//          than the Oracle database version that attempted to mine the logs.
// *Action: Mine the logs using a newer version of the Oracle database having a
//          version number that is equal to or greater than the dictionary
//          version.
01360, 00000, "invalid token"
// *Cause: 
// *Action: 
01361, 00000, "global name mismatch"
// *Cause :  The database global name where the log file was generated did not
//           match the user-specified global name of the Streams Capture process.
// *Action:  Start a new capture process and ensure that the user-specified
//           global name matches that of the database that generated the log
//           file.
//          
01362, 00000, "Specified SQL_REDO_UNDO parameter is invalid"
// *Cause: The specified input value for the parameter was not a valid number.
// *Action: Specify a valid number and try again.
//          
01363, 00000, "Specified COLUMN_NAME parameter is NULL"
// *Cause: NULL was specified for input value of parameter.
// *Action: Specify a non-NULL value and try again.
//          
01364, 00000, "waiting for branch at SCN %s"
// *Cause:  LogMiner reader process has completed mining of physical standby
//          terminal logs up to the stop SCN. LogMiner reader is now waiting
//          for logs from the new branch.
// *Action: No action necessary. This informational statement is provided
//          to record the event for diagnostic purposes. If there is a problem
//          with log transport, the files can be registered manually using the
//          ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
//
01365, 00000, "waiting for new branch registration"
// *Cause:  LogMiner reader process has completed mining of physical standby
//          terminal logs up to the stop SCN. The builder process is now
//          waiting for logs from the new branch to be registered before
//          continuing.
// *Action: No action necessary. This informational statement is provided
//          to record the event for diagnostic purposes. If there is a problem
//          with log transport, the files may be registered manually using the
//          ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
//
01366, 00000, "failed to find redo logs required for terminal apply"
// *Cause:  LogMiner failed to find all the expected log files required
//          to complete the terminal apply, requested using the
//          FINISH APPLY clause. During terminal apply, LogMiner does not 
//          wait for logs to be registered.  It expects all logs between
//          the starting point and the last log on any redo branch 
//          that it will or could mine through, to be present at the 
//          mining site. 
// *Action: Examine system.logmnr_log$ to see which logs are known to 
//          LogMiner. Then, locate or restore any missing logs and use the
//          ALTER DATABASE REGISTER LOGICAL LOGFILE statement to register 
//          them. Alternatively, do not use the FINISH APPLY clause, but if
//          activating a logical standby, only do this when you are sure that 
//          the missing log files can not be located and registered as this 
//          can lead to data loss.
//
01370, 00000, "Specified restart SCN is too old"
// *Cause: specified restart scn is too old, logmnr could not
//         find a proper checkpoint.
// *Action: Specify a bigger restart SCN to try again
//          
01371, 00000, "Complete LogMiner dictionary not found"
// *Cause: One or more log files containing the LogMiner dictionary was not 
//         found.
// *Action: Add into LogMiner all log files containing the dictionary.
//          
01372, 00000, "Insufficient processes for specified LogMiner operation"
// *Cause:  The number of processes requested by the caller can not
//          be allocated
// *Action: Increase number of parallel servers allocated to the instance
//    
01373, 00000, "insufficient memory for staging persistent LogMiner session"
// *Cause:  The maximum number of concurrent persistent LogMiner sessions 
//          allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter.
//          Not enough memory has been set aside at instance startup to
//          allocate the new LogMiner session.
// *Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
//  
01374, 00000, "_log_parallelism_max greater than 1 not supported in this release"
// *Cause:  LogMiner does not mine redo records generated with
//          _log_parallelism_max set to a value greater than 1.
// *Action: 
//           
01375, 00000, "Corrupt logfile %s recovered"
// *Cause:  A corrupt logfile has been recovered by RFS
// *Action: None.  Logical Standby should automatically restart.  If logfile is
//          still corrupt, may need to manually copy and reregister the logfile
//          on the standby.
//
01376, 00000, "LogMiner testing event"
// *Cause: 
// *Action: 
01377, 00000, "Invalid log file block size"
// *Cause: An invalid value was specified in the BLOCKSIZE clause.
// *Action: Use correct syntax.
01378, 00000, "The logical block size (%s) of file %s is not compatible with the disk sector size (media sector size is %s and host sector size is %s)"
// *Cause: One of the following occurred:
//         (1) An attempt was made to create a file.
//         (2) A file was moved to disks with different sector size.
// *Action: Create file or move file to the proper disk.
01379, 00000, "LogMiner testing event"
// *Cause: 
// *Action: 
01380, 00000, "Instance %s (thread %s) has less than two %s block size log files"
// *Cause: One of the following occurred:
//         (1) An attempt was made to switch to specified block size logs for 
//             all threads.
//         (2) An attemp was made to open a thread.
// *Action: Add log files to the thread that signals error, and try again.
01381, 00000, "Dropping log %s would leave less than two log files with block size %s for instance %s (thread %s)"
// *Cause: The database was migrated to use a specified log block size.
//         Dropping all the logs specified would leave fewer than the required
//         two log files with the specified block size per enabled thread.
// *Action: Either drop fewer logs or disable the thread before deleting the
//          logs. It may be possible to clear the log rather than drop it.
01382, 00000, "Thread %s failed to open log file %s. The log file's block size (%s) is larger than the disk sector size (%s)"
// *Cause: Log file was created on bigger sector disks, and moved to smaller
//         sector disks.
// *Action: Move the log file back to bigger sector disks.
01383, 00000, "Thread %s failed to open %s block size log file '%s' on %s sector native-mode disks"
// *Cause: Log file was copied from smaller sector disks to larger sector 
//         native-mode disks.
// *Action: Move the log file back to smaller sector disks.
/
/ 1384 - 1398 Reserved for 4K block size log file errors
/
/
01399, 00000, "LogMiner public event"
// *Cause: 
// *Action: 
/
/        1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE
/
/ 1400-1499 SQL execute phase errors
/
01400, 00000, "cannot insert NULL into (%s)"
// *Cause: An attempt was made to insert NULL into previously listed objects.
// *Action: These objects cannot accept NULL values.
01401, 00000, "inserted value too large for column"
// *Cause: The value inserted was too large for the given column.
// *Action: Do not insert a value greater than what the column can hold.
01402, 00000, "view WITH CHECK OPTION where-clause violation"
// *Cause:
// *Action:
01403, 00000, "no data found"
// *Cause: No data was found from the objects.
// *Action: There was no data from the objects which may be due to end of fetch.
01404, 00000, "ALTER COLUMN will make an index too large"
// *Cause:
// *Action:
01405, 00000, "fetched column value is NULL"
// *Cause:
// *Action:
01406, 00000, "fetched column value was truncated"
// *Cause: The fetched column values were truncated.
// *Action: Use the right data types to avoid truncation.
01407, 00000, "cannot update (%s) to NULL"
// *Cause:
// *Action:
01408, 00000, "such column list already indexed"
// *Cause:
// *Action:
01409, 00000, "NOSORT option may not be used; rows are not in ascending order"
// *Cause: Creation of index with NOSORT option when rows were not ascending.
//         For non-unique indexes the rowid is considered part of the index
//         key. Therefore, if you create an index nosort and two of the rows
//         in the table have the same key and are stored in ascending order,
//         but get split accross two extents where the dba of the first block
//         in the second extent is less than the dba of the last block in the
//         first extent, then the create index nosort may fail. 
// *Action: Create the index without the NOSORT option, or ensure table is
//          stored in one extent.
01410, 00000, "invalid ROWID"
// *Cause:
// *Action:
01411, 00000, "cannot store the length of column in the indicator"
// *Cause: Tried to fetch a column of size more than 64K and couldn't store
//         the length of the column in the given indicator of size 2 bytes.
// *Action: Use the new bind type with call backs to fetch the long column.
01412, 00000, "zero length not allowed for this datatype"
// *Cause: The length for type 97 is 0
// *Action: Specify the  correct length.
01413, 00000, "illegal value in packed decimal number buffer"
// *Cause: The user buffer bound by the user as packed decimal number
//         contained an illegal value.
// *Action: Use a legal value.
01414, 00000, "invalid array length when trying to bind array"
// *Cause: An attempt was made to bind an array without either a current
//         array length pointer or a zero maximum array length.
// *Action: Sepcify a valid length.
01415, 00000, "too many distinct aggregate functions"
// *Cause: The query contains more distinct aggregates than can be processed.
//         The current limit is 255.
// *Action: Reduce the number of distinct aggregate functions in the query.
01416, 00000, "two tables cannot be outer-joined to each other"
// *Cause:
// *Action:
01417, 00000, "a table may be outer joined to at most one other table"
// *Cause:  a.b (+) = b.b and a.c (+) = c.c is not allowed
// *Action: Check that this is really what you want, then join b and c first
//          in a view.
01418, 00000, "specified index does not exist"
// *Cause:
// *Action:
01419, 00000, "datdts: illegal format code"
// *Cause:
// *Action:
01420, 00000, "datstd: illegal format code"
// *Cause:
// *Action:
01421, 00000, "datrnd/dattrn: illegal precision specifier"
// *Cause:
// *Action:
01422, 00000, "exact fetch returns more than requested number of rows"
// *Cause: The number specified in exact fetch is less than the rows returned.
// *Action: Rewrite the query or change number of rows requested
01423, 00000, "error encountered while checking for extra rows in exact fetch"
// *Cause:
// *Action: See the following error and take appropriate action.
01424, 00000, "missing or illegal character following the escape character"
// *Cause: The character following the escape character in LIKE pattern is
//         missing or not one of the escape character, '%', or '_'.
// *Action: Remove the escape character or specify the missing character.
01425, 00000, "escape character must be character string of length 1"
// *Cause: Given escape character for LIKE is not a character string of
//         length 1.
// *Action: Change it to a character string of length 1.
01426, 00000, "numeric overflow"
// *Cause: Evaluation of an value expression causes an overflow/underflow.
// *Action: Reduce the operands.
01427, 00000, "single-row subquery returns more than one row"
// *Cause:
// *Action:
01428, 00000, "argument '%s' is out of range"
// *Cause:  
// *Action: 
01429, 00000, "Index-Organized Table: no data segment to store overflow row-pieces"
// *Cause: No overflow segment defined.
// *Action: Add overflow segment.
01430, 00000, "column being added already exists in table"
// *Cause:
// *Action:
01431, 00000, "internal inconsistency in GRANT command"
// *Cause:
// *Action:
01432, 00000, "public synonym to be dropped does not exist"
// *Cause:
// *Action:
01433, 00000, "synonym to be created is already defined"
// *Cause:
// *Action:
01434, 00000, "private synonym to be dropped does not exist"
// *Cause:
// *Action:
01435, 00000, "user does not exist"
// *Cause:
// *Action:
01436, 00000, "CONNECT BY loop in user data"
// *Cause:
// *Action:
01437, 00000, "cannot have join with CONNECT BY"
// *Cause:
// *Action:
01438, 00000, "value larger than specified precision allowed for this column"
// *Cause: When inserting or updating records, a numeric value was entered 
//         that exceeded the precision defined for the column.
// *Action: Enter a value that complies with the numeric column's precision,
//          or use the MODIFY option with the ALTER TABLE command to expand
//          the precision.
01439, 00000, "column to be modified must be empty to change datatype"
// *Cause:
// *Action:
01440, 00000, "column to be modified must be empty to decrease precision or scale"
// *Cause:
// *Action:
01441, 00000, "cannot decrease column length because some value is too big"
// *Cause:
// *Action:
01442, 00000, "column to be modified to NOT NULL is already NOT NULL"
// *Cause:
// *Action:
01443, 00000, "internal inconsistency; illegal datatype in resultant view column"
// *Cause:
// *Action:
01444, 00000, "internal inconsistency; internal datatype maps to invalid external type"
// *Cause:
// *Action:
01445, 00000, "cannot select ROWID from, or sample, a join view without a key-preserved table"
// *Cause:
// *Action:
01446, 00000, "cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc."
// *Cause:
// *Action:
01447, 00000, "ALTER TABLE does not operate on clustered columns"
// *Cause:
// *Action:
01448, 00000, "index must be dropped before changing to desired type"
// *Cause:
// *Action:
01449, 00000, "column contains NULL values; cannot alter to NOT NULL"
// *Cause:
// *Action:
01450, 00000, "maximum key length (%s) exceeded"
// *Cause:
// *Action:
01451, 00000, "column to be modified to NULL cannot be modified to NULL"
// *Cause: the column may already allow NULL values, the NOT NULL constraint
//         is part of a primary key or check constraint.
// *Action: if a primary key or check constraint is enforcing the NOT NULL
//          constraint, then drop that constraint.
01452, 00000, "cannot CREATE UNIQUE INDEX; duplicate keys found"
// *Cause:
// *Action:
01453, 00000, "SET TRANSACTION must be first statement of transaction"
// *Cause: self-evident
// *Action: commit (or rollback) transaction, and re-execute
01454, 00000, "cannot convert column into numeric datatype"
// *Cause:
// *Action:
01455, 00000, "converting column overflows integer datatype"
// *Cause:
// *Action:
01456, 00000, "may not perform insert/delete/update operation inside a READ ONLY transaction"
// *Cause: A non-DDL insert/delete/update or select for update operation
//         was attempted
// *Action: commit (or rollback) transaction, and re-execute
01457, 00000, "converting column overflows decimal datatype"
// *Cause:
// *Action:
01458, 00000, "invalid length inside variable character string"
// *Cause:
// *Action:
01459, 00000, "invalid length for variable character string"
// *Cause:
// *Action:
01460, 00000, "unimplemented or unreasonable conversion requested"
// *Cause:
// *Action:
01461, 00000, "can bind a LONG value only for insert into a LONG column"
// *Cause:
// *Action:
01462, 00000, "cannot insert string literals longer than 4000 characters"
// *Cause:
// *Action:
01463, 00000, "cannot modify column datatype with current constraint(s)"
// *Cause: An attempt was made to modify the datatype of column which
//         has referential constraints; or has check constraints which
//         only allows changing the datatype from CHAR to VARCHAR or
//         vise versa.
// *Action: Remove the constraint(s) or do not perform the offending operation.
01464, 00000, "circular grant (granting to grant ancestor) of table or view"
// *Cause:
// *Action:
01465, 00000, "invalid hex number"
// *Cause:
// *Action:
01466, 00000, "unable to read data - table definition has changed"
// *Cause: Query parsed after tbl (or index) change, and executed
//   w/old snapshot
// *Action: commit (or rollback) transaction, and re-execute
01467, 00000, "sort key too long"
// *Cause:
// *Action:
01468, 00000, "a predicate may reference only one outer-joined table"
// *Cause:
// *Action:
01469, 00000, "PRIOR can only be followed by a column name"
// *Cause: Attempting to specify "PRIOR <something>" where <something> is not
//   a column name.
// *Action: Only a column name can follow PRIOR.  Replace with a column name.
01470, 00000, "In-list iteration does not support mixed operators"
// *Cause: Constants of different types are specified in an in-list.
// *Action: Use constants of same type for in-lists.
01471, 00000, "cannot create a synonym with same name as object"
// *Cause:
// *Action:
01472, 00000, "cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc."
// *Cause:
// *Action:
01473, 00000, "cannot have subqueries in CONNECT BY clause"
// *Cause:
// *Action:
01474, 00000, "cannot have START WITH or PRIOR without CONNECT BY"
// *Cause:
// *Action:
01475, 00000, "must reparse cursor to change bind variable datatype"
// *Cause:
// *Action:
01476, 00000, "divisor is equal to zero"
// *Cause:
// *Action:
01477, 00000, "user data area descriptor is too large"
// *Cause:
// *Action:
01478, 00000, "array bind may not include any LONG columns"
// *Cause:  User is performing an array bind with a bind variable whose
//   maximum size is greater than 2000 bytes.
// *Action: Such bind variables cannot participate in array binds.
//   Use an ordinary bind operation instead.
01479, 00000, "last character in the buffer is not Null"
// *Cause: A bind variable of type 97 does not contain null at the last
//         position
// *Action: Make the last character null
01480, 00000, "trailing null missing from STR bind value"
// *Cause:  A bind variable of type 5 (null-terminated string) does
//   not contain the terminating null in its buffer.
// *Action: Terminate the string with a null character
01481, 00000, "invalid number format model"
// *Cause:  The user is attempting to either convert a number to a string
//          via TO_CHAR or a string to a number via TO_NUMBER and has 
//          supplied an invalid number format model parameter.
// *Action:  Consult your manual.
01482, 00000, "unsupported character set"
// *Cause: The character set used to perform the operation, such as
//        the CONVERT function, is not a supported character set.
// *Action:  Use one of the supported character sets.
01483, 00000, "invalid length for DATE or NUMBER bind variable"
// *Cause:  A bind variable of type DATE or NUMBER is too long.
// *Action:  Consult your manual for the maximum allowable length.
01484, 00000, "arrays can only be bound to PL/SQL statements"
// *Cause:  You tried to bind an array to a non-PL/SQL statement.
// *Action:  
01485, 00000, "compile bind length different from execute bind length"
// *Cause:  You bound a buffer of type DTYVCS (VARCHAR with the two byte 
//          length in front) and at execute time the length in the first two 
//          bytes is more than the maximum buffer length (given in the bind 
//          call).  The number of elements in the array and the current number 
//          of elements in the array cannot be more than the maximum size of
//          the array.
// *Action:  
01486, 00000, "size of array element is too large"
// *Cause:  You tried to bind a data value which was either too large for the 
//          datatype (for example, NUMBER) or was greater than 4000 bytes 
//          (for example, VARCHAR or LONG).
// *Action:  
01487, 00000, "packed decimal number too large for supplied buffer"
// *Cause: An impossible request for decimal to oracle number conversion was
//         made
// *Action: This conversion cannot be performed
01488, 00000, "invalid nibble or byte in the input data"
// *Cause: An impossible request for decimal to oracle number conversion was 
//         made
// *Action: This conversion cannot be performed
01489, 00000, "result of string concatenation is too long"
// *Cause: String concatenation result is more than the maximum size.
// *Action: Make sure that the result is less than the maximum size.
/
/ 1490 - 1499 Analyze Parse and Execution Errors
/
01490, 00000, "invalid ANALYZE command"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
01491, 00000, "CASCADE option not valid"
// *Cause: The CASCADE option is only valid for tables or clusters.
// *Action: Do not specify CASCADE
01492, 00000, "LIST option not valid"
// *Cause: The LIST option is only valid for tables or clusters.
// *Action: Do not specify LIST
01493, 00000, "invalid SAMPLE size specified"
// *Cause:  The specified SAMPLE size is out of range
// *Action: Specify a value within the proper range.
01494, 00000, "invalid SIZE specified"
// *Cause:  The specified histogram SIZE value was out of range.
// *Action: Specify a value within the proper range.
01495, 00000, "specified chain row table not found"
// *Cause:  The specified table either does not exist or user does not have
//          the proper privleges.
// *Action: Specify the correct table to use.
01496, 00000, "specified chain row table form incorrect"
// *Cause:  The specified table does not have the proper field definitions.
// *Action: Specify the correct table to use.
01497, 000000, "illegal option for ANALYZE CLUSTER"
// *Cause:  The FOR COLUMNS <column-list> clause may not be used with
//          ANALYZE CLUSTER.
// *Action: Retry with a legal syntax.
01498, 00000, "block check failure - see trace file"
// *Cause:
// *Action:
01499, 00000, "table/index cross reference failure - see trace file"
// *Cause:
// *Action:
/
/ Copyright (c) Oracle Corporation 1999, 2001.  All rights reserved.
/
/ NAME
/   e1500.msg
/ DESCRIPTION
/   Error messages for Oracle
/ NOTES
/   Language      : American
/   Character set : US7ASCII
/
/ List of ORACLE errors
/
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000.
/ The remainder of the line is the error text (max 76 characters).
/
/ Adding an error:
/   Check out this file, add the error, and check it back in.
/   Error numbers should always be ordered.
/   The second column should always be x00000.
/ Pseudo-error debugging events:
/   Error codes 10000 .. 10999 are reserved for debug event codes
/   that are not really errors.
/
/ MODIFIED
/   mabhatta    04/20/09 - rename us.oracle.com to example.com
/   jjlee       03/03/09 - edit ORA-1516
/   ssonawan    11/17/08 - bug 7503761: edit 1931 
/   ptearle     02/05/09 - add documentation for ORA-2014
/   kquinn      02/13/09 - 5687266: ensure ora-1722 is documented
/   yohu        11/20/08 - update 2051
/   nmacnaug    10/16/08 - change error message
/   madhanap    09/12/08 - bug 7387947: removing %s and %d from timezone region
/                          errors
/   mabhatta    08/06/08 - edit 1554
/   yuli        05/28/08 - edit 1679
/   mbastawa    03/26/08 - add 01805
/   dapte       03/12/08 - add documentation for err-1795
/   dkoppar     03/11/08 - #(6835153) add err mesg for divide by zero
/   yohu        02/19/08 - change ORA-01640 to for in-doubt txn only
/   yohu        03/25/07 - more information for ORA-2051
/   mabhatta    11/30/06 - changing 1535 message to include rbs using _SYSSMU
/                          prefix
/   akruglik    09/17/06 - modify Cause of msg 1752 to exclude read-only views
/                          since an attempt to delete from a read-only view
/                          will now be reported as msg 42399
/   akruglik    09/12/06 - replace EDITIONING VIEW with Editioning View
/   akruglik    09/01/06 - Column Map Views got rechristened as Editioning
/                          Views
/   akruglik    05/10/06 - correct text of CAUSE for msg 1702 per request from 
/                          errors_us 
/   akruglik    03/01/06 - Add a mention of use of a view in a definition of an
/                          Editioning View among causes of msg 1702 
/   yohu        11/28/05 - change 2079 
/   bemeng      04/21/05 - explicitly specify unit of size for out-of-space msg
/   gmulagun    02/14/05 - bug 4177854 change 1999
/   nireland    02/24/05 - Explicitly specify unit of size. #4050567 
/   qyu         11/15/04 - change 1874 
/   mdilman     09/16/04 - change 1566 to more generic
/   nmanappa    05/13/04 - change message 1994 for password file 
/   molagapp    04/25/04 - change 1537
/   rjenkins    07/08/03 - add a comment
/   lilin       12/16/02 - Eliminate Thread Number add/change error messages
/   jarnett     11/21/02 - bug 2634530 - delete reference to 
/                          distributed_transactions
/   ddas        10/16/02 - OPTIMIZER_GOAL parameter is obsolete
/   asundqui    09/05/02 - update error 1506 to only mention init.ora parameter
/   swerthei    09/20/02 - block change tracking
/   sdizdar     09/03/02 - reuse 1586
/   mjstewar    09/29/02 - Add flashback cause to ORA-1588
/   jmuller     08/08/02 - Bug 2462292: clarify ORA-2064 documentation
/   mjstewar    07/24/02 - Add Flashback action to ORA-1507
/   yuli        04/15/02 - remove 1576 
/   snutakki    10/24/01 - 1970332: Add new error mesg 1560
/   mjaeger     07/05/01 - bug 479696: 01516: alter db datafile/tempfile <fno>
/-------------------------------------------------------------------------------
/ 1500 - 1699 V6 Execution errors
/
01500, 00000, "failure in getting date/time"
// *Cause:  During create database or alter tablespace, there was a failure
//    in getting the date and time.
// *Action: Contact your customer support representative.
01501, 00000, "CREATE DATABASE failed"
// *Cause:  An error occurred during create database
// *Action: See accompanying errors.
01502, 00000, "index '%s.%s' or partition of such index is in unusable state"
// MERGE: 1489 RENUMBERED TO 1502
// *Cause: An attempt has been made to access an index or index partition
//         that has been marked unusable by a direct load or by a DDL
//         operation
// *Action: DROP the specified index, or REBUILD the specified index, or
//         REBUILD the unusable index partition
01503, 00000, "CREATE CONTROLFILE failed"
// *Cause:  An error occurred during CREATE CONTROLFILE
// *Action: See accompanying errors.
01504, 00000, "database name '%s' does not match parameter db_name '%s'"
// *Cause:  The name in a database create or mount does not match the name
//          given in the INIT.ORA parameter db_name.
// *Action: correct or omit one of the two names.
01505, 00000, "error in adding log files"
// *Cause:  During create or alter database, error(s) occurred when
//   adding new log files.
// *Action:  Check error stack for detailed error information.
01506, 00000, "missing or illegal database name"
// *Cause:  No db_name INIT.ORA aprameter was specified.
// *Action:  The database name must be given in the db_name
//    INIT.ORA parameter.
01507, 00000, "database not mounted"
// *Cause:  A command was attempted that requires the database to be mounted.
// *Action:  If you are using the ALTER DATABASE statement via the SQLDBA
//     startup command, specify the MOUNT option to startup;
//     else if you are directly doing an ALTER DATABASE DISMOUNT,
//     do nothing; else specify the MOUNT option to ALTER DATABASE.
//           If you are doing a backup or copy, you must first mount the
//           desired database.
//           If you are doing a FLASHBACK DATABASE, you must first mount
//           the desired database.
01508, 00000, "cannot create database; error in file '%s' at line %s"
// *Cause: CREATE DATABASE was unable to process the specified file.
// *Action: Check the offending line in the specified file.
01509, 00000, "specified name '%s' does not match actual '%s'"
// *Cause: The database name specified in ALTER DATABASE does not
//  match the name of the currently mounted database.
// *Action:  Correct the database name spelling or DISMOUNT the mounted
//    database.
01510, 00000, "error in deleting log files"
// *Cause:  During ALTER DATABASE, an error occurred while dropping
//   log files.
// *Action:  Check the error stack for detailed error information.
01511, 00000, "error in renaming log/data files"
// *Cause: An error occurred during the ALTER DATABASE RENAME FILE command.
// *Action:  Check the error stack for detailed error information.
01512, 00000, "error renaming log file %s - new file %s not found"
// *Cause: An attempt to change a log file's name in the control file
//   failed because no file was found with the new name.
// *Action: Make sure that the log file has been properly renamed by the
//   operating system and retry.
01513, 00000, "invalid current time returned by operating system"
// *Cause:  The operating system returned a time that was not between
//          1988 and 2121.
// *Action: Correct the time kept by the operating system.
01514, 00000, "error in log specification: no such log"
// *Cause:  A log file name, or list of member names, did not correspond
//          to an existing log.
// *Action: Specify an existing log file.
01515, 00000, "error dropping log group %s: no such log"
// *Cause:  ALTER DATABASE is attempting to drop a log file which
//   is not known to the database control file.
// *Action:  Specify the name of an existing log file.
01516, 00000, "nonexistent log file, data file, or temporary file \"%s\""
// *Cause:  An attempt was made to use ALTER DATABASE to rename
//          a log file, data file, or temporary file; or to change attributes
//          of a data file or temporary file (for example, resize, autoextend,
//          online or offline); or to re-create or move a data file.
//          The attempt failed because the specified file
//          is not known to the database's control file
//          or is not of a type supported by the request.
// *Action: Specify the name or number of an existing file
//          of the correct type, as appropriate.
//          Check the relevant V$ table for a list of possible files.
01517, 00000, "log member: '%s'"
// *Cause:  Used to print member names
// *Action: See top level error for information
01518, 00000, "CREATE DATABASE must specify more than one log file"
// *Cause: Only one log file was specified in the CREATE DATABASE statement.
// *Action:  Specify at least two log files.
01519, 00000, "error while processing file '%s' near line %s"
// *Cause:  CREATE DATABASE encountered a problem while processing
//    specified file.  The specified file is bad.
// *Action: Retry your system installation procedure or contact
//    your customer support representative.
01520, 00000, "number of data files to add (%s) exceeds limit of %s"
// *Cause: CREATE TABLESPACE statement specifies more files than
//  is permitted for this database.
// *Action:  Use fewer files or re-create the database with a
//    larger value of MAXDATAFILES.
01521, 00000, "error in adding data files"
// *Cause:  During CREATE or ALTER TABLESPACE, an error was detected
//   while adding data files.
// *Action:  Check the error stack for detailed error information.
01522, 00000, "file '%s' to be renamed does not exist"
// *Cause:  During ALTER TABLESPACE RENAME, a file to be renamed was not
//   found in the database control file.
// *Action:  Specify the correct file name.
01523, 00000, "cannot rename data file to '%s' - file already part of database"
// *Cause:  During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME,
//   the new name of a file is already present in the control file.
// *Action:  Rename the file to a name not already being used as part of
//    the database.
01524, 00000, "cannot create data file as '%s' - file already part of database"
// *Cause:  During ALTER DATABASE CREATE DATAFILE,
//   the new name of a file is already present in the control file.
// *Action:  Create the file as a name not already being used as part of
//    the database.
01525, 00000, "error in renaming data files"
// *Cause:  An error occurred when renaming files as part of ALTER TABLESPACE.
// *Action:  Check the error stack for detailed information.
//    All files are renamed except for those mentioned in the
//    error stack.
01526, 00000, "error in opening file '%s'"
// *Cause:  CREATE DATABASE was not able to open the specified file.
//   This is probably due to a system installation error.
// *Action:  Retry your system installation procedure or contact
//    your customer support representative.
01527, 00000, "error while reading file"
// *Cause:  CREATE DATABASE was not able to read the specified file.
//   This is probably due to a system installation error.
// *Action:  Retry your system installation procedure or contact
//    your customer support representative.
01528, 00000, "EOF while processing SQL statement"
// *Cause:  CREATE DATABASE unexpectedly hit EOF while reading the
//    specified file.  The sql.bsq file is bad.
// *Action:  Retry your system installation procedure or contact
//    your customer support representative.
01529, 00000, "error closing file '%s'"
// *Cause:  CREATE DATABASE was not able to close the specified file.
// *Action:  Retry your system installation procedure or contact
//    your customer support representative.
01530, 00000, "a database already mounted by the instance"
// *Cause:  During ALTER DATABASE MOUNT, an attempt is being made to mount
//   a database on an instance in which a database is or has previously
//   been mounted.
// *Action:  If you wish to mount the database, shutdown the instance
//    and then startup the instance and retry the operation.
01531, 00000, "a database already open by the instance"
// *Cause:  During ALTER DATABASE, an attempt was made to open
//   a database on an instance for which there is already
//   an open database.
// *Action:  If you wish to open a new database on the instance, first
//    shutdown the instance and then startup the instance and
//    retry the operation.
01532, 00000, "cannot create database; instance being started elsewhere"
// *Cause:  During CREATE DATABASE, another user appears to be
//   simultaneously altering the instance.
// *Action:  Make sure no one else is simultaneously altering the
//    instance.  If no one is, contact your customer support
//    representative; otherwise, retry the operation.
01533, 00000, "cannot rename file '%s'; file does not belong to tablespace"
// *Cause:  During ALTER TABLESPACE RENAME, a file to be renamed was not
//   found in the argument tablespace.
// *Action:  Specify the correct file name or the correct tablespace name.
01534, 00000, "rollback segment '%s' doesn't exist"
// *Cause:  During ALTER or DROP ROLLBACK SEGMENT, the specified
//   rollback segment name is unknown.
// *Action:  Use the correct rollback segment name.
01535, 00000, "rollback segment '%s' already exists or given name has prefix _SYSSMU"
// *Cause:  Specified rollback segment already exists or given name starts with
//           _SYSSMU.
// *Action:  Use a different name. Note that _SYSSMU is an illegal prefix to
//           an RBU segment.
01536, 00000, "space quota exceeded for tablespace '%s'"
// *Cause:  The space quota for the segment owner in the tablespace has
//          been exhausted and the operation attempted the creation of a
//          new segment extent in the tablespace.
// *Action: Either drop unnecessary objects in the tablespace to reclaim
//          space or have a privileged user increase the quota on this
//          tablespace for the segment owner.
01537, 00000, "cannot add file '%s' - file already part of database"
// *Cause:  During CREATE or ALTER TABLESPACE, a file being added is already
//   part of the database.
// *Action:  Use a different file name.
01538, 00000, "failed to acquire any rollback segment"
// *Cause: Failed to acquire any rollback segment during startup in shared mode
// *Action: Startup in exclusive mode to create one more public segment or
//   specify available private segments in the INIT.ORA parameter
//   rollback_segments_required, then startup in shared mode
01539, 00000, "tablespace '%s' is not online"
// *Cause: Failed to either make a tablespace read-only or offline because
//         it is not online. A tblespace must be online before it can
//         become read-only or offline normal.
// *Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY
//         options to force all files offline. Bring the tablespace online
//         before making it read-only.
01540, 00000, "tablespace '%s' is not offline"
// *Cause: Failed to bring a tablespace online because it is not offline
// *Action: Check the status of the tablespace
01541, 00000, "system tablespace cannot be brought offline; shut down if necessary"
// *Cause: Tried to bring system tablespace offline
// *Action: Shutdown if necessary to do recovery
01542, 00000, "tablespace '%s' is offline, cannot allocate space in it"
// *Cause: Tried to allocate space in an offline tablespace
// *Action: Bring the tablespace online or create the object in other
//          tablespace
01543, 00000, "tablespace '%s' already exists"
// *Cause: Tried to create a tablespace which already exists
// *Action: Use a different name for the new tablespace
01544, 00000, "cannot drop system rollback segment"
// *Cause: Tried to drop system rollback segment
// *Action: None
01545, 00000, "rollback segment '%s' specified not available"
// *Cause: Either:
//         1) An attempt was made to bring a rollback segment online that is
//            unavailable during startup; for example, the rollback segment
//            is in an offline tablespace.
//         2) An attempt was made to bring a rollback segment online that is
//            already online.  This is because the rollback segment is
//            specified twice in the ROLLBACK_SEGMENTS parameter in the
//            initialization parameter file or the rollback segment is already
//            online by another instance.
//         3) An attempt was made to drop a rollback segment that is
//            currently online.
//         4) An attempt was made to alter a rollback segment that is
//            currently online to use unlimited extents.
//         5) An attempt was made to online a rollback segment that is
//            corrupted. This is because the rollback is specified in
//            _corrupted_rollback_segments parameter in initialization
//            parameter file.
// *Action: Either:
//         1) Make the rollback segment available; for example, bring an
//            offline tablespace online.
//         2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name
//            is a duplicate or if another instance has already acquired the
//            rollback segment.
//         3) Bring the rollback segment offline first. This may involve
//            waiting for the active transactions to finish, or, if the
//            rollback segment needs recovery, discover which errors are
//            holding up the rolling back of the transactions and take
//            appropriate actions.
//         4) Same as 3).
//         5) Remove the name from the _corrupted_rollback_segments parameter.
01546, 00000, "tablespace contains active rollback segment '%s'"
// *Cause: Tried to make a tablespace that contains active rollback segment(s)
//  offline or read-only
// *Action: Shutdown instances that use the active rollback segments in the
//   tablespace and then make the tablespace offline or read-only
01547, 00000, "warning: RECOVER succeeded but OPEN RESETLOGS would get error below"
// *Cause: Media recovery with one of the incomplete recovery options ended
//  without error.  However, if the ALTER DATABASE OPEN RESETLOGS command
//        were attempted now, it would fail with the specified error.
//        The most likely cause of this error is forgetting to restore one or
//        more datafiles from a sufficiently old backup before executing the
//        incomplete recovery.
// *Action: Rerun the incomplete media recovery using different datafile
//         backups, a different control file, or different stop criteria.
01548, 00000, "active rollback segment '%s' found, terminate dropping tablespace"
// *Cause: Tried to drop a tablespace that contains active rollback segment(s)
// *Action: Shutdown instances that use the active rollback segments in the
//   tablespace and then drop the tablespace
01549, 00000, "tablespace not empty, use INCLUDING CONTENTS option"
// *Cause: Tried to drop a non-empty tablespace
// *Action: To drop all the objects in the tablespace, use the INCLUDING
//   CONTENTS option
01550, 00000, "cannot drop system tablespace"
// *Cause: Tried to drop system tablespace
// *Action: None
01551, 00000, "extended rollback segment, pinned blocks released"
// *Cause: Doing recursive extent of rollback segment, trapped internally
//  by the system
// *Action: None
01552, 00000, "cannot use system rollback segment for non-system tablespace '%s'"
// *Cause: Tried to use the system rollback segment for operations involving
//  non-system tablespace. If this is a clone database then this will
//        happen when attempting any data modification outside of the system
//        tablespace. Only the system rollback segment can be online in a
//        clone database.
// *Action: Create one or more private/public segment(s), shutdown and then
//   startup again. May need to modify the INIT.ORA parameter
//   rollback_segments to acquire private rollback segment. If this is
//         a clone database being used for tablspace point in time recovery
//         then this operation is not allowed.  If the non-system tablespace
//         has AUTO segment space management, then create an undo tablespace.
01553, 00000, "MAXEXTENTS must be no smaller than the %s extents currently allocated"
// *Cause: The number of extents allocated is greater than the MAXEXTENTS
//   specified.
// *Action: Specify a larger MAXEXTENTS value.
01554, 00000, "transaction concurrency limit reached reason:%s params:%s, %s"
// *Cause: Too many concurrent transactions
// *Action: Shutdown the system, modify the INIT.ORA parameters transactions,
//   rollback_segments or rollback_segments_required, then
//   startup again.
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
//   overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
//          setting. Otherwise, use larger rollback segments
01556, 00000, "MINEXTENTS for rollback segment must be greater than 1"
// *Cause: Specified MINEXTENTS of less than 2 for rollback segment
// *Action: Specify larger MINEXTENTS
01557, 00000, "rollback segment extents must be at least %s blocks"
// *Cause: Specified extent of less than minimum size for rollback segment
// *Action: Specify larger extents
01558, 00000, "out of transaction ID's in rollback segment %s"
// *Cause: All the available transaction id's have been used
// *Action: Shutdown the instance and restart using other rollback segment(s),
//    then drop the rollback segment that has no more transaction id's.
01559, 00000, "MAXEXTENTS for rollback segment must be greater than 1"
// *Cause: Specified MAXEXTENTS of less than 2 for rollback segment
// *Action: Specify larger MAXEXTENTS
01560, 00000, "LIKE pattern contains partial or illegal character"
// *Cause: like pattern is not formed correctly  
// *Action: make sure like pattern is specified correctly 
01561, 00000, "failed to remove all objects in the tablespace specified"
// *Cause: Failed to remove all objects when dropping a tablespace
// *Action: Retry the drop tablespace until all objects are dropped
01562, 00000, "failed to extend rollback segment number %s"
// *Cause: Failure occurred when trying to extend rollback segment
// *Action: This is normally followed by another error message that caused
//   the failure. You may take the rollback segment offline to perform
//         maintainence. Use the alter rollback segment offline command
//         to take the rollback segment offline.
01563, 00000, "rollback segment is PUBLIC, need to use the keyword PUBLIC"
// *Cause: Did not use the keyword PUBLIC to identified public rollback segment
// *Action: Use the keyword PUBLIC when identifying public rollback segment
01564, 00000, "rollback segment is not PUBLIC"
// *Cause: The rollback segment segment identified is not public
// *Action: Do not use the keyword PUBLIC when identifying private rollback
//   segment
01565, 00000, "error in identifying file '%s'"
// *Cause:  An error occurred while trying to identify a file.
// *Action:  Check the error stack for detailed information.
01566, 00000, "file specified more than once in ALTER DATABASE"
// *Cause: The list of files supplied to the command contained at least one
//  duplicate.
// *Action: Remove the duplicate file specification and retry.
01567, 00000, "dropping log %s would leave less than 2 log files for instance %s (thread %s)"
// *Cause:  Dropping all the logs specified would leave fewer than the required
//   two log files per enabled thread.
// *Action:  Either drop fewer logs or disable the thread before deleting the
//    logs. It may be possible to clear the log rather than drop it.
01568, 00000, "cannot set space quota on PUBLIC"
// MERGE: 1568 PROBABLY OBSOLETE
// *Cause: Trying to set space quota on a tablespace for PUBLIC.
// *Action: If trying to grant system-wide or tablespace-wide space priviledges
//   to all users, use GRANT RESOURCE [ON <tablespace>] TO PUBLIC.
01569, 00000, "data file too small for system dictionary tables"
// *Cause: The datafile specified during creation of the database is too
//   small to hold the system dictionary tables.
// *Action: Recreate the database by specifying a larger file or more files.
01570, 00000, "MINEXTENTS must be no larger than the %s extents currently allocated"
// *Cause: The number of extents allocated is smaller than the MINEXTENTS
//         specified.
// *Action: Specify a smaller MINEXTENTS value.
01571, 00000, "redo version %s incompatible with ORACLE version %s"
// *Cause:  This software version can not read the current redo logs, and
//          either crash recovery is required or there are offline database
//          files that need media recovery. If a file name is listed then
//          it needs media recovery.
// *Action: Shutdown and startup using the compatible software. Do any required
//          media recovery, and open the database. Shutdown and then startup
//    using current software. If the file is going to be dropped then
//          take it offline with the DROP option to skip this check.
01572, 00000, "rollback segment '%s' cannot be brought online, %s extents exceeded"
// *Cause: The number of extents in the rollback segment exceeds the hard limit.
//         It cannot be brought online for writing.
// *Action: Drop and recreate the rollback segment.
01573, 00000, "shutting down instance, no further change allowed"
// *Cause: Some process tries to make changes while the db is being shutdown
// *Action: None
01574, 00000, "maximum number of concurrent transactions exceeded"
// *Cause: the limit on the number of concurrent transactions has been hit
// *Action: shutdown the system, increase the INIT.ORA parameter 'transactions'
//    , and then restart the system.
01575, 00000, "timeout waiting for space management resource"
// *Cause: failed to acquire necessary resource to do space management.
// *Action: Retry the operation.
01576, 00000, "The instance %s is not enabled"
// *Cause:  The thread associated with instance is not enabled.
// *Action: Enable the thread associated with the instance using
//           ALTER DATABASE ENABLE INSTANCE command.
01577, 00000, "cannot add log file '%s' - file already part of database"
// *Cause:  During CREATE or ALTER DATABASE, a file being added is already
//   part of the database.
// *Action:  Use a different file name.
01578, 00000, "ORACLE data block corrupted (file # %s, block # %s)"
// *Cause:  The data block indicated was corrupted, mostly due to software
//    errors.
// *Action: Try to restore the segment containing the block indicated. This
//    may involve dropping the segment and recreating it. If there
//    is a trace file, report the errors in it to your ORACLE
//    representative.
01579, 00000, "write error occurred during recovery"
// *Cause:  A write error occurred during recovery
// *Action: Consult trace files for the nature of the write error, and
//    correct error.
01580, 00000, "error creating control backup file %s"
// *Cause:  An operating system error occurred while attempting to create a
//    control file backup.
// *Action:  Check the error stack for more detailed information
01581, 00000, "attempt to use rollback segment (%s) new extent (%s) which is being allocated"
// *Cause:  Undo generated to extend a rollback segment run out of current
//          undo block space and is attempting to write into the new extent
//          which has not been completely allocated.
// *Action: The rollback segment extending will be rollbacked by the system,
//          no more extension will be possible untill the next extent is
//          freed up by rolling back or committing other transactions.
01582, 00000, "unable to open control file for backup"
// *Cause:  An operating system error occurred while attempting to open a
//    control file for backup.
// *Action:  Check the error stack for more detailed information
01583, 00000, "unable to get block size of control file to be backed up"
// *Cause:  An operating system error occurred while attempting to
//    get the block size of a control file for backup.
// *Action:  Check the error stack for more detailed information
01584, 00000, "unable to get file size of control file to be backed up"
// *Cause:  An operating system error occurred while attempting to
//    get the file size of a control file for backup.
// *Action:  Check the error stack for more detailed information
01585, 00000, "error identifying backup file %s"
// *Cause:  An operating system error occurred when attempting to identify
//    the file to be used for control file backup.
// *Action:  Check the error stack for more detailed information
01586, 00000, "database must be mounted EXCLUSIVE and not open for this operation"
// *Cause:  Attempting to DROP DATABASE when the database is not mounted 
//          EXCLUSIVE.
// *Action: Mount the database in EXCLUSIVE mode.
01587, 00000, "error during control file backup file copy"
// *Cause:
//
// *Action:
01588, 00000, "must use RESETLOGS option for database open"
// *Cause: An earlier attempt to open the database with the RESETLOGS option
//         did not complete, or recovery was done with a control file backup,
//         or a FLASHBACK DATABASE was done.
// *Action: Use the RESETLOGS option when opening the database.
01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open"
// *Cause:  Either incomplete or backup control file recovery has been
//          performed. After these types of recovery you must specify either
//          the RESETLOGS option or the NORESETLOGS option to open your
//          database.
// *Action: Specify the appropriate option.
01590, 00000, "number of segment free list (%s) exceeds maximum of %s"
// *Cause:  storage parameter FREELIST GROUPS is too large.
// *Action: Reduce storage parameters FREELIST GROUPS
01591, 00000, "lock held by in-doubt distributed transaction %s"
// *Cause:  Trying to access resource that is locked by a dead two-phase commit
//          transaction that is in prepared state.
// *Action: DBA should query the pending_trans$ and related tables, and attempt
//          to repair network connection(s) to coordinator and commit point.
//          If timely repair is not possible, DBA should contact DBA at commit
//          point if known or end user for correct outcome, or use heuristic
//          default if given to issue a heuristic commit or abort command to
//          finalize the local portion of the distributed transaction.
01592, 00000, "error converting Version 7 rollback segment (%s) to Oracle 8 format"
// *Cause:  Look at the accompanying internal error; Version 7 database may not
//          have shutdown cleanly.
// *Action: Investigate the internal error; may have to reload the Version 7
// *Action: Investigate the internal error; may have to reload the Version 7
//          database (from backup) and shutdown the database cleanly.
01593, 00000, "rollback segment optimal size (%s blks) is smaller than the computed initial size (%s blks)"
// *Cause:  Specified OPTIMAL size is smaller than the cumulative size of the
//          initial extents during create rollback segment.
// *Action: Specify a larger OPTIMAL size.
01594, 00000, "attempt to wrap into rollback segment (%s) extent (%s) which is being freed"
// *Cause:  Undo generated to free a rollback segment extent is attempting
//          to write into the same extent due to small extents and/or too
//          many extents to free
// *Action: The rollback segment shrinking will be rollbacked by the system;
//          increase the optimal size of the rollback segment.
01595, 00000, "error freeing extent (%s) of rollback segment (%s))"
// *Cause:  Some error occurred while freeing inactive rollback segment extents.
// *Action: Investigate the accompanying error.
01596, 00000, "cannot specify system in %s parameter"
// *Cause:  The system rollback segment is specified in the INIT.ORA parameter
//          referred to in the error message
// *Action: change the INIT.ORA parameter
01597, 00000, "cannot alter system rollback segment online or offline"
// *Cause:  Tried to online or offline the system rollback segment
// *Action: None
01598, 00000, "rollback segment '%s' is not online"
// *Cause:  Could have been taken offline before by DBA or cleaned up
//          by SMON.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
//          to make sure the rollback segment is actually online.
01599, 00000, "failed to acquire rollback segment (%s), cache space is full"
// *Cause:  the amount statically allocated is not enough based on
//          max_rollback_segments parameter.
// *Action: For now take another rollback segment offline or increase the
//          parameter max_rollback_segments
01600, 00000, "at most one \"%s\" in clause \"%s\" of %s"
// *Cause:  The INIT.ORA parameter was mis-specified.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01601, 00000, "illegal bucket size in clause \"%s\" of %s"
// *Cause:  The bucket size was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01603, 00000, "illegal grouping size in clause \"%s\" of %s"
// *Cause:  The grouping size was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01604, 00000, "illegal number range in clause \"%s\" of %s"
// *Cause:  The number range was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01605, 00000, "missing numbers in clause \"%s\" of %s"
// *Cause:  The numbers were missing for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01606, 00000, "parameter not identical to that of another mounted instance"
// *Cause:  A parameter was different on two instances.
// *Action: Modify the initialization parameter and restart.
01607, 00000, "cannot add logfile to the specified instance"
// *Cause:  The limit on the number of instances supported by the 
//          control file has been reached.
// *Action: Use an instance name supported by the control file, or resize
//          the thread record and/or checkpoint progress record secions of the
//          control file.
01608, 00000, "cannot bring rollback segment '%s' online, its status is (%s)"
// *Cause:  Could have been brought online before by DBA or left as a result
//          of process crash.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
01609, 00000, "log %s is the current log for thread %s - cannot drop members"
// *Cause:  A member of the current log for a thread cannot be dropped.
// *Action: If the thread is opened, request a log switch by the instance
//          that is using it.  If it is not open, disable the thread, manually
//          archive the log, or clear it.
01610, 00000, "recovery using the BACKUP CONTROLFILE option must be done"
// *Cause:  Either an earlier database recovery session specified BACKUP
//          CONTROLFILE, or the control file was recreated with the RESETLOGS
//          option, or the control file being used is a backup control file.
//    After that only BACKUP CONTROLFILE recovery is allowed
//          and it must be followed by a log reset at the next database open.
// *Action: Perform recovery using the BACKUP CONTROFILE option.
01611, 00000, "thread number %s is invalid - must be between 1 and  %s"
// *Cause:  A thread number in a command is greater than the number of threads
//          supported by the control file.
// *Action: Use a thread number that is valid, or resize the thread record
//          and/or checkpoint progress record sections of the control file.
01612, 00000, "instance %s (thread %s) is already enabled"
// *Cause:  An attempt was made to enable a thread that is already enabled.
// *Action: Either use this thread or enable another thread.
01613, 00000, "instance %s (thread %s) only has %s logs - at least 2 logs required to enable."
// *Cause:  The thread cannot be enabled because it only has two online log
//          files associated with it.
// *Action: Add logs to the thread or pick another thread to enable
01614, 00000, "instance %s (thread %s) is busy - cannot enable"
// *Cause:  The mount enqueue for the thread could not be acquired when
//          attempting to enable the thread. This probably means that another
//          process has already started enabling this thread.
// *Action: Wait and try again, or find another thread to enable.
01615, 00000, "instance %s (thread %s) is mounted - cannot disable"
// *Cause:  Some instance, possibly this one, has allocated the thread for its
//          use. The thread can not be disabled while in use.
// *Action: Shut the instance down cleany using the thread.
01616, 00000, "instance %s (thread %s) is open - cannot disable"
// *Cause:  The thread is not closed. The last instance to use the thread died
//          leaving the thread open. A thread cannot be disabled until it is
//          closed. It is still required for crash or instance recovery.
// *Action: If the database is open, instance recovery should close the thread
//          soon - wait a few minutes. Otherwise open the database - crash
//          recovery will close the thread.
01617, 00000, "cannot mount: %s is not a valid thread number"
// *Cause:  The INIT.ORA parameter "thread" is not between 1 and the
//          number of threads allowed by the control file.
// *Action: Shut down the instance, change the INIT.ORA parameter and
//          startup, or resize the thread record and/or checkpoint progress
//          record sections of the control file.
01618, 00000, "redo thread %s is not enabled - cannot mount"
// *Cause:  The INIT.ORA parameter "thread" requests a thread that is not
//          enabled. A thread must be enabled before it can be mounted.
// *Action: Shutdown the instance, change the INIT.ORA parameter and startup
//          mounting a different thread. If the database is open in another
//          instance then the thread may be enabled.
01619, 00000, "thread %s is mounted by another instance"
// *Cause:  The INIT.ORA parameter "thread" requests a thread that has been
//          mounted by another instance. Only one instance may use a thread.
// *Action: Shutdown the instance, change the INIT.ORA parameter and startup
//          mounting a different thread.
01620, 00000, "no public threads are available for mounting"
// *Cause:  The INIT.ORA parameter "thread" is zero, its default value.
//          There are no threads which have been publicly enabled, and not
//          mounted.
// *Action: Shutdown the instance, change the INIT.ORA parameter to a thread
//          which is privately enabled and not mounted. If the database is
//          open in another instance, then a thread may be publicly enabled.
01621, 00000, "cannot rename member of current log if database is open"
// *Cause:  This is a rename command for  a member of the current log for
//          an open thread.  If the database is open anywhere, the log may be
//          in use, so the rename cannot be done.
// *Action: Wait until the log is not current, or mount the database
//          exclusively.
01622, 00000, "thread number must be specified - default not specific"
// *Cause:  The thread was not specified when adding a log, and the currently
//          mounted thread was chosen by default at mount time. Since the
//          current thread was not specified explicitly the user cannot know
//          which thread the log will be added to.
// *Action: Explicitly specify the thread number either in the INIT.ORA
//          parameter "thread", or in the add command.
01623, 00000, "log %s is current log for instance %s (thread %s) - cannot drop"
// *Cause:  A thread's current log cannot be dropped even if the thread is
//          closed. A disabled thread usually does not have a current log,
//          but a half completed disable may need to be disabled again.
// *Action: If the database is not open then disable the thread. If the
//          database is open and an instance has the thread open, then the
//          instance can be requested to switch logs. If the database is
//          closed the log can be archived or cleared to force a switch.
01624, 00000, "log %s needed for crash recovery of instance %s (thread %s)"
// *Cause:  A log cannot be dropped or cleared until the thread's checkpoint
//          has advanced out of the log.
// *Action: If the database is not open, then open it. Crash recovery will
//          advance the checkpoint. If the database is open force a global
//          checkpoint. If the log is corrupted so that the database cannot
//          be opened, it may be necessary to do incomplete recovery until
//          cancel at this log.
01625, 00000, "rollback segment '%s' does not belong to this instance"
// *Cause:  Trying to shrink or take a rollback segment offline that does not
//          belong to this instance.
// *Action:
01626, 00000, "rollback segment number '%s' cannot handle more transactions"
// *Cause:  Too many transactions in this segment.
// *Action: Choose a different rollback segment, or reduce the number
//          of concurrent transactions.
01627, 00000, "rollback segment number '%s' is not online"
// *Cause:  Could have been taken offline before by DBA or cleaned up
//          by SMON.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
//          to make sure the rollback segment is actually online.
01628, 00000, "max # extents (%s) reached for rollback segment %s"
// *Cause:  An attempt was made to extend a rollback segment that was
//          already at the MAXEXTENTS value.
// *Action: If the value of the MAXEXTENTS storage parameter is less than
//          the maximum allowed by the system, raise this value.
01629, 00000, "max # extents (%s) reached saving undo for tablespace %s"
// *Cause:  Save undo for the offline tablespace at max extents
// *Action: Check the storage parameters for the system tablespace. The
//          tablespace needs to be brought back online so the undo can be
//          applied .
01630, 00000, "max # extents (%s) reached in temp segment in tablespace %s"
// *Cause:  A temp segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
//          maximum, you can raise that. Otherwise, raise pctincrease for the
//          tablespace
01631, 00000, "max # extents (%s) reached in table %s.%s"
// *Cause:  A table tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params
01632, 00000, "max # extents (%s) reached in index %s.%s"
// *Cause:  An index tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params.
01633, 00000, "Real Application Clusters Option needed for this operation"
// *Cause: System doesn't have Real Application Clusters configured
// *Action: Obtain Real Application Clusters option
01634, 00000, "rollback segment number '%s' is about to go offline"
// *Cause:  The rollback segment specified was marked to go offline by DBA.
// *Action: Bring the rollback segment online first.
01635, 00000, "rollback segment #%s specified not available"
// *Cause: (same as 1545)
// *Action: (same as 1545)
01636, 00000, "rollback segment '%s' is already online"
// *Cause: The instance is trying to online an already online RS
// *Action:
01637, 00000, "rollback segment '%s' is being used by another instance (#%s)"
// *Cause: The instance is trying to online a RS already in use by another
//         instance
// *Action:
01638, 00000, "parameter %s does not allow ORACLE version %s to mount cluster database"
// *Cause: The recovery compatible parameter is set too low to allow this
//         software version to mount in cluster database mode.
// *Action:Either use an earlier software release or advance the
//         recovery_compatible parameter. If this happens when no
//         recovery_compatible parameter has been specified then set it
//         to the current software release.
01639, 00000, " instance %s has no thread assigned to it"
// *Cause: There is no mapping from instance to thread for this instance in 
//         the control file.
// *Action:Make sure that this instance has a thread assigned to it by adding
//         logfiles to this instance or by starting the instance with an
//         existing thread which will automatically create a mapping.
01640, 00000, "cannot make tablespace read-only with changes by in-doubt transactions"
// *Cause: An attempt was made to alter a tablespace read-only while there were 
//         changes in the tablespace made by in-doubt distributed transactions.
//         The in-doubt transactions must commit or rollback to ensure that
//         there is no undo for a tablespace before it can be made read-only.
// *Action: Any in-doubt transactions that made changes to the tablespace must
//          be resolved.
01641, 00000, "tablespace '%s' is not online - cannot add data file"
// *Cause: Attempting to add a datafile to a tablespace that has been set
//         to read-only or offline.
// *Action: Make the tablespace online and read write then add the datafile.
01642, 00000, "begin backup not needed for read-only tablespace '%s'"
// *Cause: Attempting to begin or end a backup for a tablespace that has
//         been set to read-only.
// *Action: Take the backup without any begin or end commands. The files
//         are not being modified so the backup will be consistent.
01643, 00000, "system tablespace can not be made read-only"
// *Cause: Attempting to set the system tablespace to read-only. The system
//         tablespace must remain read write for database operation.
// *Action: Leave system tablespace read write.
01644, 00000, "tablespace '%s' is already read-only"
// *Cause: Attempting to make tablespace read-only that is already read-only.
// *Action: Leave tablespace read-only, or make read write then make
//         read-only again.
01645, 00000, "previous attempt to make read write is half complete"
// *Cause: A failure while making the tablespace read write left it read
//         only, but the checkpoint was advanced. The tablespace will not
//         be useable after a resetlogs if its files are offline.
// *Action: Repeat the command to make the tablespace read write.
01646, 00000, "tablespace '%s' is not read-only - cannot make read write"
// *Cause: Attempting to make a tablespace read write that is not read-only.
//         It may be either online or offline.
// *Action: Leave tablespace read write.
01647, 00000, "tablespace '%s' is read-only, cannot allocate space in it"
// *Cause: Tried to allocate space in a read-only tablespace
// *Action: Create the object in another tablespace
01648, 00000, "log %s is the current log of disabled instance %s (thread %s)"
// *Cause: An attempt to enable the thread failed after it was half completed.
//         This log was left as the current log even though the thread is still
//         disabled. Since a log switch cannot be done until the thread is
//         enabled, the log can not be cleared or archived.
// *Action:Complete the thread enable by issuing the enable command again.
01649, 00000, "operation not allowed with a backup control file"
// *Cause: An attempt is being made to perform a command that does not make
//         sense when the control file is a restored backup.
// *Action:Wait until after the database has been opened and try again.
01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          a rollback segment in the tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01651, 00000, "unable to extend save undo segment by %s for tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for 
//          saving undo entries for the indicated offline tablespace.
// *Action: Check the storage parameters for the SYSTEM tablespace. The
//          tablespace needs to be brought back online so the undo can be
//          applied.
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01653, 00000, "unable to extend table %s.%s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for 
//          a table segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01654, 00000, "unable to extend index %s.%s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          an index segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01655, 00000, "unable to extend cluster %s.%s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          a cluster segment in tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01656, 00000, "max # extents (%s) reached in cluster %s.%s"
// *Cause:  A cluster tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params
01657, 00000, "invalid SHRINK option value"
// *Cause: The specified value must be an integer.
// *Action:  Choose an appropriate integer value.
01658, 00000, "unable to create INITIAL extent for segment in tablespace %s"
// *Cause:  Failed to find sufficient contiguous space to allocate INITIAL
//          extent for segment being created.
// *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
//          tablespace or retry with a smaller value for INITIAL
01659, 00000, "unable to allocate MINEXTENTS beyond %s in tablespace %s"
// *Cause:  Failed to find sufficient contiguous space to allocate MINEXTENTS
//          for the segment being created.
// *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
//          tablespace or retry with smaller value for MINEXTENTS, NEXT or
//          PCTINCREASE
01660, 00000, "tablespace '%s' is already permanent"
// *Cause: Attempting to make tablespace permanent that is already permanent.
// *Action: Leave tablespace permanent.
01661, 00000, "tablespace '%s' is already temporary"
// *Cause: Attempting to make tablespace temporary that is already temporary.
// *Action: Leave tablespace permanent.
01662, 00000, "tablespace '%s' is non-empty and cannot be made temporary"
// *Cause: Tried to convert a non-empty tablespace to a temporary tablespace
// *Action: To drop all the objects in the tablespace.
01663, 00000, "the contents of tablespace '%s' is constantly changing"
// *Cause: The contents of the tablespace is always changing between PERMANENT
//         and TEMPORARY.
// *Action: To decide what the tablespace contents should be and stay with it.
01664, 00000, "Transaction which has expanded the Sort Segment has aborted"
// *Cause: Internal Error.
// *Action: Contact Oracle Support.
01665, 00000, "control file is not a standby control file"
// *Cause:  Attempting to mount, recover or activate a standby database
//          without a standby control file.
// *Action: Create a standby control file before attempting to use the database
//          as a standby database.
01666, 00000, "control file is for a standby database"
// *Cause:  Attempting to mount, recover, or open a standby database without
//          the appropriate command option to designate a standby database.
// *Action: Use the standby option or appropriate commands, or mount with
//          the primary control file.
01667, 00000, "cannot add any more tablespaces: limit of %s exceeded"
// *Cause:  There is no more room in the control file for adding tablespaces.
// *Action: Resize the control file or drop other tablespaces.
01668, 00000, "standby database requires DROP option for offline of data file"
// *Cause:  Attempting to take a datafile offline in a standby database without
//          specifying the DROP option. Files that are offline in a standby
//          database are not recovered, and are likely to be unusable if
//          the standby is activated. Note that specifying DROP does not
//          prevent bringing the file online later.
// *Action: Specify the DROP option or leave the file online.
01669, 00000, "standby database control file not consistent"
// *Cause:  Attempting to activate a standby database with a control file that
//          has not been recovered to the same point as the data files. Most
//          likely the control file was just copied from the primary database
//          and has not been used for recovery.
// *Action: Recover the standby database until all the files are consistent.
01670, 00000, "new datafile %s needed for standby database recovery"
// *Cause:  Standby database recovery noticed that a file was added to the
//          primary database, but is not available on the standby.
// *Action: Either copy the file from the primary database or do an ALTER
//          DATABASE CREATE DATAFILE command on the standby to create a
//          file to recover.
01671, 00000, "control file is a backup, cannot make a standby control file"
// *Cause:  The currently mounted control file is a backup control file, and
//          attempting to create a control file for a standby database.
// *Action: Complete any needed recovery and open the database with the
//          resetlogs option.
01672, 00000, "control file may be missing files or have extra ones"
// *Cause:  Attempting to create a standby control file, but the control file
//          was either recently created via CREATE CONTROLFILE or an incomplete
//          recovery has been done. Thus the datafiles in the control file
//          and the ones in the data dictionary may not match.
// *Action: Open the database, then retry the operation.
01673, 00000, "data file %s has not been identified"
// *Cause:  This data file was not in the control file after an incomplete
//          recovery or CREATE CONTROLFILE. Since information from its
//          header is needed for standby database recovery, we can not
//          create a standby control file.
// *Action: Find the file and bring it online. If desired it may be taken
//          offline again. If you intend to drop this file, then taking it
//          offline with the DROP option will avoid this error.
01674, 00000, "data file %s is an old incarnation rather than current file"
// *Cause:  Recovery encountered redo that indicates this file was dropped
//          from the database and another file was added using the same file
//          number. This implies that a CREATE CONTROLFILE command was given
//          the old file which was dropped rather than the latest file.
// *Action: Rebuild the control file using CREATE CONTROLFILE, and give the
//          correct file.
01675, 00000, "max_commit_propagation_delay inconsistent with other instances"
// *Cause:  The max_commit_propagation_delay INIT.ORA parameter is
//          inconsistent with those in other instances.
// *Action: Make sure all instances have the same max_commit_propagation_delay.
01676, 00000, "standby file name convert of '%s' exceeds maximum length of %s"
// *Cause:  When the given file name is converted to the name used for the
//          standby database, the converted name is bigger than the maximum
//          allowed file name.
// *Action: Change initialization parameter DB_FILE_STANDBY_NAME_CONVERT or
//          LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name.
01677, 00000, "standby file name convert parameters differ from other instance"
// *Cause: The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT
//         initialization parameters are not the same as in other instances
//         that already have the database mounted.
// *Action: Change initialization parameters DB_FILE_STANDBY_NAME_CONVERT and
//          LOG_FILE_STANDBY_NAME_CONVERT to match other instances.
01678, 00000, "parameter %s must be pairs of pattern and replacement strings"
// *Cause: The initialization parameter does not have even number of strings
//         for its value. The odd numbered strings are patterns to be found in
//         file names. The even numbered strings are used to replace the
//         corresponding patterns when found in file names.
// *Action:Specify even number of strings for the parameter, or omit the
//         parameter.
01679, 00000, "database is being opened"
// *Cause: An attempt was made to activate a standby database when the
//        database was in the middle of being opened.
// *Action: Wait for database open to finish and retry the ACTIVATE command.
01680, 00000, "unable to extend LOB segment by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          a LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01681, 00000, "max # extents (%s) reached in LOB segment in tablespace %s"
// *Cause:  A LOB segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
//          maximum, you can raise that. Otherwise, raise pctincrease for the
//          tablespace
01682, 00000, "read-only DB cannot allocate temporary space in tablespace %s"
// *Cause:  Temporary space (usually for sorting) could not be allocated in
//          either main storage or a tempfile. An attempt was made to
//          allocate the space from the tablespace named, but the database is
//          opened read-only. The database open requires a sort work space.
// *Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE
//          initialization parameter), or create a temporary tablespace before
//          making the database read-only.  Use ALTER TABLESPACE ADD TEMPFILE
//          statement to add temporary files to the temporary tablespace.
01683, 00000, "unable to extend index %s.%s partition %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          index segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01684, 00000, "max # extents (%s) reached in table %s.%s partition %s"
// *Cause:  A table tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params
01685, 00000, "max # extents (%s) reached in index %s.%s partition %s"
// *Cause:  An index tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params.
01686, 00000, "max # files (%s) reached for the tablespace %s"
// *Cause:  The number of files for a given tablespace has reached its maximum
//          value
// *Action: Resize existing files in the tablespace, or partition the objects
//          among multiple tablespaces, or move some objects to a different
//          tablespace.
01687, 00000, "specified logging attribute for tablespace '%s' is same as the existing"
// *Cause: Attempting to change the tablespace default logging attribute
//         (LOGGING or NOLOGGING) to be the same as the existing logging
//         attribute
// *Action: Change the specified logging attribute
01688, 00000, "unable to extend table %s.%s partition %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          table segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01689, 00000, "syntax error in clause \"%s\" of %s"
// *Cause:  There was a syntax in the INIT.ORA parameter.
// *Action: Fix the syntax error and restart the instance.
01690, 00000, "sort area size too small"
// *Cause:  sort area size too small to fit two records in memory
// *Action: increase sort_area_size
01691, 00000, "unable to extend lob segment %s.%s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01692, 00000, "unable to extend lob segment %s.%s partition %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent of the required number of blocks for
//          LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.
01693, 00000, "max # extents (%s) reached in lob segment %s.%s"
// *Cause:  A LOB segment tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params.
01694, 00000, "max # extents (%s) reached in lob segment %s.%s partition %s"
// *Cause:  A LOB segment tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params.
01695, 00000, "error converting rollback segment %s to version 8.0.2"
// *Cause:   Version 8.0.1 database may not have shutdown cleanly
// *Action:  May have to reload the 8.0.1 database and shutdown cleanly
01696, 00000, "control file is not a clone control file"
// *Cause:  Attempting to mount, a database as a clone when it is already
//          mounted by another instance not as a clone or attempting to use
//          a current control file for a clone.
// *Action: Mount without the clone option or use a backup control file and
//          shutdown the other instances before mounting as a clone.
01697, 00000, "control file is for a clone database"
// *Cause:  Attempting to mount a clone database without the appropriate
//          command option to designate a clone database.
// *Action: Use the clone option or appropriate commands, or mount with
//          the primary control file.
01698, 00000, "a clone database may only have SYSTEM rollback segment online"
// *Cause:  Attempting to online a rollback segment in a clone database.
// *Action: Do not use this command.
01699, 00000, "tablespace '%s' is being imported for point in time recovery"
// *Cause:  Attempting to online a tablespace or begin another point in
//          time import while a point in time import is already in progress
// *Action: Wait until the import complets
//
/
/ 1700 - 1799 Parse errors continued from 900 - 999
/
01700, 00000, "duplicate username in list"
// *Cause:
// *Action:
01701, 00000, "a cluster is not appropriate here"
// *Cause:
// *Action:
01702, 00000, "a view is not appropriate here"
// *Cause:  Among other possible causes, this message will be produced if an
//          attempt was made to define an Editioning View over a view.
// *Action: An Editioning View may only be created over a base table.
01703, 00000, "missing SYNONYM keyword"
// *Cause:
// *Action:
01704, 00000, "string literal too long"
// *Cause:  The string literal is longer than 4000 characters.
// *Action:  Use a string literal of at most 4000 characters.
//    Longer values may only be entered using bind variables.
01705, 00000, "an outer join cannot be specified on a correlation column"
// *Cause:
// *Action:
01706, 00000, "user function result value was too large"
// *Cause:
// *Action:
01707, 00000, "missing LIST keyword"
// *Cause:
// *Action:
01708, 00000, "ACCESS or SESSION expected"
// *Cause:
// *Action:
01709, 00000, "program does not exist"
// *Cause:
// *Action:
01710, 00000, "missing OF keyword"
// *Cause:
// *Action:
01711, 00000, "duplicate privilege listed"
// *Cause:
// *Action:
01712, 00000, "you cannot grant a privilege which you do not have"
// *Cause:
// *Action:
01713, 00000, "GRANT OPTION does not exist for that privilege"
// *Cause:
// *Action:
01714, 00000, "error in execution of user function"
// *Cause:
// *Action:
01715, 00000, "UNIQUE may not be used with a cluster index"
// *Cause:  An attempt was made to create a cluster index with the
//  UNIQUE attribute.
// *Action:  Remove UNIQUE from the CREATE INDEX statement.
01716, 00000, "NOSORT may not be used with a cluster index"
// *Cause:  An attempt was made to create a cluster index using
//    the NOSORT option.
// *Action:  Remove NOSORT from the CREATE INDEX statement.
01717, 00000, "seccta: invalid access mode token passed"
// *Cause:
// *Action:
01718, 00000, "BY ACCESS | SESSION clause not allowed for NOAUDIT"
// *Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.
// *Action: Remove BY ACCESS | SESSION.
01719, 00000, "outer join operator (+) not allowed in operand of OR or IN"
// *Cause:  An outer join appears in an or clause.
// *Action: If A and B are predicates, to get the effect of (A(+) or B),
//          try (select where (A(+) and not B)) union all (select where (B)).
01720, 00000, "grant option does not exist for '%s.%s'"
// *Cause:  A grant was being performed on a view and the grant option was
//          not present for an underlying object.
// *Action: Obtain the grant option on all underlying objects of the view.
01721, 00000, "USERENV(COMMITSCN) invoked more than once in a transaction"
// *Cause: The USERENV('COMMITSCN') function can only be used once in a
//         transaction.
// *Action: Re-write the transactioin to use USERENV('COMMITSCN') only once
01722, 00000, "invalid number"
// *Cause: The specified number was invalid.
// *Action: Specify a valid number.
01723, 00000, "zero-length columns are not allowed"
// *Cause: Columns with zero length were not allowed.
// *Action: Correct the use of the column. 
01724, 00000, "floating point precision is out of range (1 to 126)"
// *Cause: The specified number had an invalid range.
// *Action: Use a floating point precision that is in the correct precision.
01725, 00000, "USERENV('COMMITSCN')  not allowed here"
// *Cause: The function USERENV('COMMITSCN') is only allowed as a top-level
//         expression in the VALUES clause of an INSERT statement, and on
//         the right-hand side of an assignment in an UPDATE statement.
// *Action: Correct the use of the function.
01726, 00000, "a table is not appropriate here"
// *Cause:
// *Action:
01727, 00000, "numeric precision specifier is out of range (1 to 38)"
// *Cause:
// *Action:
01728, 00000, "numeric scale specifier is out of range (-84 to 127)"
// *Cause:
// *Action:
01729, 00000, "database link name expected"
// *Cause:
// *Action:
01730, 00000, "invalid number of column names specified"
// *Cause:
// *Action:
01731, 00000, "circular view definition encountered"
// *Cause:
// *Action:
01732, 00000, "data manipulation operation not legal on this view"
// *Cause:
// *Action:
01733, 00000, "virtual column not allowed here"
// *Cause:
// *Action:
01734, 00000, "illegal parameters - EXTENT MIN higher than EXTENT MAX"
// *Cause: A wrong value is specified for the parameter.
// *Action: Correct the parameter and reissue the statement.
01735, 00000, "invalid ALTER TABLE option"
// *Cause:
// *Action:
01736, 00000, "[NOT] SUCCESSFUL expected"
// *Cause:
// *Action:
01737, 00000, "valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE"
// *Cause:
// *Action:  Valid lock modes are SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE,
//           SHARE ROW EXCLUSIVE, and SHARE UPDATE.
01738, 00000, "missing IN keyword"
// *Cause:
// *Action:
01739, 00000, "missing MODE keyword"
// *Cause:
// *Action:
01740, 00000, "missing double quote in identifier"
// *Cause:
// *Action:
01741, 00000, "illegal zero-length identifier"
// *Cause:
// *Action:
01742, 00000, "comment not terminated properly"
// *Cause:   The indicated comment or hint begun with the /* token did not
//           have the terminating */.
// *Action:  Properly terminate the comment or hint with a */.
01743, 00000, "only pure functions can be indexed"
// *Cause: The indexed function uses SYSDATE or the user environment.
// *Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS).  SQL
//          expressions must not use SYSDATE, USER, USERENV(), or anything
//          else dependent on the session state.  NLS-dependent functions
//          are OK.
01744, 00000, "inappropriate INTO"
// *Cause:
// *Action:
01745, 00000, "invalid host/bind variable name"
// *Cause:
// *Action:
01746, 00000, "indicator variable not permitted here"
// *Cause:
// *Action:
01747, 00000, "invalid user.table.column, table.column, or column specification"
// *Cause:
// *Action:
01748, 00000, "only simple column names allowed here"
// *Cause:
// *Action:
01749, 00000, "you may not GRANT/REVOKE privileges to/from yourself"
// *Cause:
// *Action:
01750, 00000, "UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column"
// *Cause:
// *Action:
01751, 00000, "Invalid dump undo option"
// *Cause: An invalid option is specified in the ALTER DUMP UNDO command.
// *Action: Correct and reissue the command.
01752, 00000, "cannot delete from view without exactly one key-preserved table"
// *Cause: The deleted table had 
//         - no key-preserved tables,
//         - more than one key-preserved table, or 
//         - the key-preserved table was an unmerged view.
// *Action: Redefine the view or delete it from the underlying base tables.
01753, 00000, "column definition incompatible with clustered column definition"
// *Cause:
// *Action:
01754, 00000, "a table may contain only one column of type LONG"
// *Cause: An attempt was made to add a LONG column to a table which already
//         had a LONG column. Note that even if the LONG column currently
//         in the table has already been marked unused, another LONG column
//         may not be added until the unused columns are dropped.
// *Action: Remove the LONG column currently in the table by using the ALTER
//         TABLE command.
01755, 00000, "Must specify an extent number or block number"
// *Cause: Expecting an extent or block number but something else was
//         specified.
// *Action: Correct the error and reissue the command.
01756, 00000, "quoted string not properly terminated"
// *Cause:
// *Action:
01757, 00000, "Must specify an object number"
// *Cause: Expecting an object number but something else was specified.
// *Action: Correct the error and reissue the command.
01758, 00000, "table must be empty to add mandatory (NOT NULL) column"
// *Cause:
// *Action:
01759, 00000, "user function is incorrectly defined"
// *Cause:
// *Action:
01760, 00000, "illegal argument for function"
// *Cause:
// *Action:
01761, 00000, "DML operation does not map to a unique table in the join"
// *Cause: The primary table is the base table against which the update,
//         insert or delete operation is finally being done. For delete
//         either there is no primary table in the join query or there is
//         more than one. For update or insert the columns specified map
//         to more than one base table.
// *Action: Change the join specification.
01762, 00000, "vopdrv: view query block not in FROM"
// *Cause:
// *Action:
01763, 00000, "update or delete involves outer joined table"
// *Cause: For deletes, the table being deleted from is outer joined to some
//         other table. For updates, either the table being updated is outer-
//         joined to some other table, or some table reachable from the primary
//         table is being outer joined to a table not reachable from the
//         primary table.
// *Action: Change the join specification.
01764, 00000, "new update value of join is not guaranteed to be unique"
// *Cause: A row of a join query table is being updated using a row of a
//         table that is not guaranteed to have exactly one value for the
//         row being updated.
// *Action: Change the join specification.
01765, 00000, "specifying owner's name of the table is not allowed"
// *Cause: An attempt was made to rename the object with dotted object name. 
// *Action: Do not specify username.tablename  in query for table name.
01766, 00000, "dictionary table not allowed in this context"
// *Cause:
// *Action:
01767, 00000, "UPDATE ... SET expression must be a subquery"
// *Cause:
// *Action:
01768, 00000, "number string too long"
// *Cause:
// *Action:
01769, 00000, "duplicate CLUSTER option specifications"
// *Cause: During a CREATE of a clustered table, the user attempted to specify
//  more than one CLUSTER option.
// *Action: Remove the extra CLUSTER option.
01770, 00000, "CLUSTER option not allowed in CREATE CLUSTER command"
// *Cause:
// *Action:
01771, 00000, "illegal option for a clustered table"
// *Cause: During a CREATE or ALTER of a clustered table, the user attempted
//  to enter one or more of the following options:
//  INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE.
//  These options may only be specified for the cluster itself.
// *Action: Remove the illegal option(s).
01772, 00000, "Must specify a value for LEVEL"
// *Cause: Expecting the value of LEVEL but something else was specified.
// *Action: Correct the error and reissue the command.
01773, 00000, "may not specify column datatypes in this CREATE TABLE"
// *Cause:
// *Action:
01774, 00000, "Dump undo option specified more than once"
// *Cause: The same option for ALTER DUMP UNDO was specified twice.
// *Action: Remove the redundant options and reissue the command.
01775, 00000, "looping chain of synonyms"
// *Cause:
// *Action:
01776, 00000, "cannot modify more than one base table through a join view"
// *Cause: Columns belonging to more than one underlying table were either
//         inserted into or updated.
// *Action: Phrase the statement as two or more separate statements.
01777, 00000, "WITH GRANT OPTION not allowed in this system"
// *Cause:
// *Action:
01778, 00000, "maximum subquery nesting level exceeded"
// *Cause:
// *Action:
01779, 00000, "cannot modify a column which maps to a non key-preserved table"
// *Cause: An attempt was made to insert or update columns of a join view which
//         map to a non-key-preserved table.
// *Action: Modify the underlying base tables directly.
01780, 00000, "string literal required"
// *Cause:
// *Action:
/
01781, 00000, "UNRECOVERABLE cannot be specified without AS SELECT"
// *Cause: UNRECOVERABLE was specified in a CREATE TABLE statement
//         without also specifying a populating subquery with an AS clause.
// *Action: Do not specify UNRECOVERABLE.
/
01782, 00000, "UNRECOVERABLE cannot be specified for a cluster or clustered table"
// *Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement
//         specified UNRECOVERABLE.
// *Action: Do not specify UNRECOVERABLE.
/
01783, 00000, "only one RECOVERABLE or UNRECOVERABLE clause may be specified"
// *Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified
//         more than once, or both RECOVERABLE and UNRECOVERABLE were specified
//         in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.
// *Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and
//          reissue the statement.
/
01784, 00000, "RECOVERABLE cannot be specified with database media recovery disabled"
// *Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE
//         when the database was running in NOARCHIVELOG mode.  Since logs
//   are not being archived, they will be overwritten and the object
//   being created cannot be recovered from a backup taken before the
//   object was created.
// *Action: Do not specify RECOVERABLE, or restart the database with media
//    recovery enabled.
/
01785, 00000, "ORDER BY item must be the number of a SELECT-list expression"
// *Cause:
// *Action:
01786, 00000, "FOR UPDATE of this query expression is not allowed"
// *Cause:
// *Action:
01787, 00000, "only one clause allowed per query block"
// *Cause:
// *Action:
01788, 00000, "CONNECT BY clause required in this query block"
// *Cause:
// *Action:
01789, 00000, "query block has incorrect number of result columns"
// *Cause:
// *Action:
01790, 00000, "expression must have same datatype as corresponding expression"
// *Cause:
// *Action:
01791, 00000, "not a SELECTed expression"
// *Cause:
// *Action:
01792, 00000, "maximum number of columns in a table or view is 1000"
// *Cause: An attempt was made to create a table or view with more than 1000
//         columns, or to add more columns to a table or view which pushes
//         it over the maximum allowable limit of 1000. Note that unused
//         columns in the table are counted toward the 1000 column limit.
// *Action: If the error is a result of a CREATE command, then reduce the
//         number of columns in the command and resubmit. If the error is
//         a result of an ALTER TABLE command, then there are two options:
//         1) If the table contained unused columns, remove them by executing
//            ALTER TABLE DROP UNUSED COLUMNS before adding new columns;
//         2) Reduce the number of columns in the command and resubmit.
01793, 00000, "maximum number of index columns is 32"
// *Cause:
// *Action:
01794, 00000, "maximum number of cluster columns is 32"
// *Cause:
// *Action:
01795, 00000, "maximum number of expressions in a list is 1000"
// *Cause:    Number of expressions in the query exceeded than 1000.
//            Note that unused column/expressions are also counted  
//            Maximum number of expressions that are allowed are 1000.
// *Action:   Reduce the number of expressions in the list and resubmit.
01796, 00000, "this operator cannot be used with lists"
// *Cause:
// *Action:
01797, 00000, "this operator must be followed by ANY or ALL"
// *Cause:
// *Action:
01798, 00000, "missing EXCEPTION keyword"
//  *Cause:
//  *Action:
01799, 00000, "a column may not be outer-joined to a subquery"
//  *Cause: <expression>(+) <relop> (<subquery>) is not allowed.
//  *Action: Either remove the (+) or make a view out of the subquery.
//           In V6 and before, the (+) was just ignored in this case.
/
/        parse errors continued at 2000
/
/ 1800 - 1899 Date function errors
/ 1800 - 1809 Overflow conditions
/
01800, 00000, "a literal in the date format was too large to process"
// *Cause:
// *Action:
01801, 00000, "date format is too long for internal buffer"
// *Cause:
// *Action:
01802, 00000, "Julian date is out of range"
// *Cause:
// *Action:
01803, 00000, "failure in getting date/time"
// *Cause:
// *Action:
01804, 00000, "failure to initialize timezone information"
// *Cause: The timezone information file was not properly read.
// *Action: Please contact Oracle Customer Support.
01805, 00000, "possible error in date/time operation"
// *Cause: The timezone files on client and server do not match.
//         Operation can potentially result in incorrect results based on 
//         local timezone file.
// *Action: Please ensure client and server timezone versions are same.
/
/ 1810 - 1829 Conflicting date input format
/
01810, 00000, "format code appears twice"
// *Cause:
// *Action:
01811, 00000, "Julian date precludes use of day of year"
// *Cause:
// *Action:
01812, 00000, "year may only be specified once"
// *Cause:
// *Action:
01813, 00000, "hour may only be specified once"
// *Cause:
// *Action:
01814, 00000, "AM/PM conflicts with use of A.M./P.M."
// *Cause:
// *Action:
01815, 00000, "BC/AD conflicts with use of B.C./A.D."
// *Cause:
// *Action:
01816, 00000, "month may only be specified once"
// *Cause:
// *Action:
01817, 00000, "day of week may only be specified once"
// *Cause:
// *Action:
01818, 00000, "'HH24' precludes use of meridian indicator"
// *Cause:
// *Action:
01819, 00000, "signed year precludes use of BC/AD"
// *Cause:
// *Action:
01820, 00000, "format code cannot appear in date input format"
// *Cause:
// *Action:
01821, 00000, "date format not recognized"
// *Cause:
// *Action:
01822, 00000, "era format code is not valid with this calendar"
// *Cause:
// *Action:
/
/ 1830 - 1899 Failed input conversions
/
01830, 00000, "date format picture ends before converting entire input string"
// *Cause:
// *Action:
01831, 00000, "year conflicts with Julian date"
// *Cause:
// *Action:
01832, 00000, "day of year conflicts with Julian date"
// *Cause:
// *Action:
01833, 00000, "month conflicts with Julian date"
// *Cause:
// *Action:
01834, 00000, "day of month conflicts with Julian date"
// *Cause:
// *Action:
01835, 00000, "day of week conflicts with Julian date"
// *Cause:
// *Action:
01836, 00000, "hour conflicts with seconds in day"
// *Cause:
// *Action:
01837, 00000, "minutes of hour conflicts with seconds in day"
// *Cause:
// *Action:
01838, 00000, "seconds of minute conflicts with seconds in day"
// *Cause:
// *Action:
01839, 00000, "date not valid for month specified"
// *Cause:
// *Action:
01840, 00000, "input value not long enough for date format"
// *Cause:
// *Action:
01841, 00000, "(full) year must be between -4713 and +9999, and not be 0"
// *Cause: Illegal year entered
// *Action: Input year in the specified range
01842, 00000, "quarter must be between 1 and 4"
// *Cause:
// *Action:
01843, 00000, "not a valid month"
// *Cause:
// *Action:
01844, 00000, "week of year must be between 1 and 52"
// *Cause:
// *Action:
01845, 00000, "week of month must be between 1 and 5"
// *Cause:
// *Action:
01846, 00000, "not a valid day of the week"
// *Cause:
// *Action:
01847, 00000, "day of month must be between 1 and last day of month"
// *Cause:
// *Action:
01848, 00000, "day of year must be between 1 and 365 (366 for leap year)"
// *Cause:
// *Action:
01849, 00000, "hour must be between 1 and 12"
// *Cause:
// *Action:
01850, 00000, "hour must be between 0 and 23"
// *Cause:
// *Action:
01851, 00000, "minutes must be between 0 and 59"
// *Cause:
// *Action:
01852, 00000, "seconds must be between 0 and 59"
// *Cause:
// *Action:
01853, 00000, "seconds in day must be between 0 and 86399"
// *Cause:
// *Action:
01854, 00000, "julian date must be between 1 and 5373484"
// *Cause: An invalid Julian date was entered.
// *Action: Enter a valid Julian date between 1 and 5373484.
01855, 00000, "AM/A.M. or PM/P.M. required"
// *Cause:
// *Action:
01856, 00000, "BC/B.C. or AD/A.D. required"
// *Cause:
// *Action:
01857, 00000, "not a valid time zone"
// *Cause:
// *Action:
01858, 00000, "a non-numeric character was found where a numeric was expected"
// *Cause: The input data to be converted using a date format model was
//  incorrect.  The input data did not contain a number where a number was
//  required by the format model.
// *Action:  Fix the input data or the date format model to make sure the
//  elements match in number and type.  Then retry the operation.
01859, 00000, "a non-alphabetic character was found where an alphabetic was expected"
// *Cause: The input data to be converted using a date format model was
//  incorrect.  The input data did not contain a letter where a letter was
//  required by the format model.
// *Action:  Fix the input data or the date format model to make sure the
//  elements match in number and type.  Then retry the operation.
01860, 00000, "week of year must be between 1 and 53"
// *Cause:
// *Action:
01861, 00000, "literal does not match format string"
// *Cause:  Literals in the input must be the same length as literals in
//  the format string (with the exception of leading whitespace).  If the
//  "FX" modifier has been toggled on, the literal must match exactly,
//  with no extra whitespace.
// *Action: Correct the format string to match the literal.
01862, 00000, "the numeric value does not match the length of the format item"
// *Cause: When the FX and FM format codes are specified for an input date,
//  then the number of digits must be exactly the number specified by the
//  format code.  For example, 9 will not match the format specifier DD but
//  09 will.
// *Action: Correct the input date or turn off the FX or FM format specifier
//  in the format string.
01863, 00000, "the year is not supported for the current calendar"
// *Cause: The year is not supported for the current calendar.
// *Action:  Please check the documentation to find out what years are
//  supported for the current calendar.
01864, 00000, "the date is out of range for the current calendar"
// *Cause: Your calendar doesn't extend to the specified date.
// *Action: Specify a date which is legal for this calendar.
01865, 00000, "not a valid era"
// *Cause: Era input does not match a known era.
// *Action: Provide a valid era on input.
01866, 00000, "the datetime class is invalid"
// *Cause: This is an internal error.
// *Action: Please contact Oracle Worldwide Support.
01867, 00000, "the interval is invalid"
// *Cause: The character string you specified is not a valid interval.
// *Action: Please specify a valid interval.
01868, 00000, "the leading precision of the interval is too small"
// *Cause: The leading precision of the interval is too small to store the
//  specified interval.
// *Action: Increase the leading precision of the interval or specify an
//  interval with a smaller leading precision.
01869, 00000, "reserved for future use"
// *Cause:
// *Action:
01870, 00000, "the intervals or datetimes are not mutually comparable"
// *Cause: The intervals or datetimes are not mutually comparable.
// *Action: Specify a pair of intervals or datetimes that are mutually
//  comparable.
01871, 00000, "the number of seconds must be less than 60"
// *Cause: The number of seconds specified was greater than 59.
// *Action: Specify a value for seconds that is 59 or smaller.
01872, 00000, "reserved for future use"
// *Cause:
// *Action:
01873, 00000, "the leading precision of the interval is too small"
// *Cause: The leading precision of the interval is too small to store the
//  specified interval.
// *Action: Increase the leading precision of the interval or specify an
//  interval with a smaller leading precision.
01874, 00000, "time zone hour must be between -12 and 14"
// *Cause: The time zone hour specified was not in the valid range.
// *Action: Specify a time zone hour between -12 and 14.
01875, 00000, "time zone minute must be between -59 and 59"
// *Cause: The time zone minute specified was not in the valid range.
// *Action: Specify a time zone minute between -59 and 59.
01876, 00000, "year must be at least -4713"
// *Cause: The specified year was not in range.
// *Action: Specify a year that is greater than or equal to -4713.
01877, 00000, "string is too long for internal buffer"
// *Cause: This is an internal error.
// *Action: Please contact Oracle Worldwide Support.
01878, 00000, "specified field not found in datetime or interval"
// *Cause: The specified field was not found in the datetime or interval.
// *Action: Make sure that the specified field is in the datetime or interval.
01879, 00000, "the hh25 field must be between 0 and 24"
// *Cause: The specified hh25 field was not in the valid range.
// *Action: Specify an hh25 field between 0 and 24.
01880, 00000, "the fractional seconds must be between 0 and 999999999"
// *Cause: The specified fractional seconds were not in the valid range.
// *Action: Specify a value for fractional seconds between 0 and 999999999.
01881, 00000, "timezone region ID is invalid"
// *Cause: The region ID referenced an invalid region.
// *Action: Contact Oracle Support Services.
01882, 00000, "timezone region not found"
// *Cause: The specified region name was not found.
// *Action: Contact Oracle Support Services.
01883, 00000, "overlap was disabled during a region transition"
// *Cause: The region was changing state and the overlap flag
//         was disabled.
// *Action: Please contact Oracle Customer Support.
01884, 00000, "divisor is equal to zero"
// *Cause: An attempt was made to divide by zero.
// *Action: Avoid zero divisor.
01890, 00000, "NLS error detected"
// *Cause: An NLS error was detected.
// *Action: Look for additional error messages and take appropriate action.
//  If there are no additional errors, call Oracle Worldwide Support.
01891, 00000, "Datetime/Interval internal error"
// *Cause: Internal error.
// *Action: Please contact Oracle Worldwide Support.
01898, 00000, "too many precision specifiers"
// *Cause: While trying to truncate or round dates, extra data was found in the
//  date format picture
// *Action: Check the syntax of the date format picture and retry.
01899, 00000, "bad precision specifier"
// *Cause:
// *Action:
/
/ 1900 - 1999 V6 parse errors
/
01900, 00000, "LOGFILE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01901, 00000, "ROLLBACK keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01902, 00000, "SEGMENT keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01903, 00000, "EVENTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01904, 00000, "DATAFILE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01905, 00000, "STORAGE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01906, 00000, "BACKUP keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01907, 00000, "TABLESPACE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01908, 00000, "EXISTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01909, 00000, "REUSE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01910, 00000, "TABLES keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01911, 00000, "CONTENTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01912, 00000, "ROW keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01913, 00000, "EXCLUSIVE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01914, 00000, "invalid auditing option for sequence numbers"
// *Cause:  AUDIT or NOAUDIT on a sequence number specifies an auditing option
//    that is not legal for sequence numbers.
// *Action:  The following options may not be used for sequence numbers
//    and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK,
//    RENAME, UPDATE, REFERENCES, EXECUTE
01915, 00000, "invalid auditing option for views"
// *Cause:  AUDIT or NOAUDIT on a view specifies an auditing option that is
//    not legal for views.
// *Action: The following options may not be used for views
//    and should be removed:  ALTER, INDEX, REFERENCES, EXECUTE
01916, 00000, "keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected"
// *Cause: An expected keyword was not used for datafile/tempfile clause
// *Action: Use correct syntax.
01917, 00000, "user or role '%s' does not exist"
// *Cause:  There is not a user or role by that name.
// *Action: Re-specify the name.
01918, 00000, "user '%s' does not exist"
// *Cause:  User does not exist in the system.
// *Action: Verify the user name is correct.
01919, 00000, "role '%s' does not exist"
// *Cause:  Role by that name does not exist.
// *Action: Verify you are using the correct role name.
01920, 00000, "user name '%s' conflicts with another user or role name"
// *Cause:  There is already a user or role with that name.
// *Action: Specify a different user name.
01921, 00000, "role name '%s' conflicts with another user or role name"
// *Cause:  There is already a user or role with that name.
// *Action: Specify a different role name.
01922, 00000, "CASCADE must be specified to drop '%s'"
// *Cause:  Cascade is required to remove this user from the system.  The
//          user own's object which will need to be dropped.
// *Action: Specify cascade.
01923, 00000, "CASCADE aborted, objects locked by another user"
// *Cause:  Cannot drop the user's objects; someone has them locked.
// *Action: Use the lock monitor to determine who has the objects locked.
01924, 00000, "role '%s' not granted or does not exist"
// *Cause:  Set role can only be performed with roles granted
//          directly to your account. (e.g. a sub-role cannot be enabled)
// *Action: Don't try to set the role.
01925, 00000, "maximum of %s enabled roles exceeded"
// *Cause:  The INIT.ORA parameter "max_enabled_roles" has been exceeded.
// *Action: Increase max_enabled_roles and warm start the database.
01926, 00000, "cannot GRANT to a role WITH GRANT OPTION"
// *Cause:  Role cannot have a privilege with the grant option.
// *Action: Perform the grant without the grant option.
01927, 00000, "cannot REVOKE privileges you did not grant"
// *Cause:  You can only revoke privileges you granted.
// *Action: Don't revoke these privileges.
01928, 00000, "GRANT option not granted for all privileges"
// *Cause:  In order to grant a privilege, you must first have the privilege
//          with the grant option.
// *Action: Obtain the privilege with the grant option and try again.
01929, 00000, "no privileges to GRANT"
// *Cause:  "ALL" was specified but the user doesn't have any privileges
//          with the grant option.
// *Action: Don't grant privileges on that object.
01930, 00000, "auditing the object is not supported"
// *Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited.
// *Action: Don't attempt to AUDIT the object.
01931, 00000, "cannot grant %s to a role"
// *Cause:  REFERENCES, INDEX, SYSDBA, SYSOPER or SYSASM
//          privilege could not be granted to a role.
// *Action: Grant privilege directly to the user.
01932, 00000, "ADMIN option not granted for role '%s'"
// *Cause:  The operation requires the admin option on the role.
// *Action: Obtain the grant option and re-try.
01933, 00000, "cannot create a stored object using privileges from a role"
// *Cause:  An attempt was made to create a stored object using privileges
//          from a role.  Stored objects cannot use privileges from roles.
// *Action: Grant the privileges required to the user directly.
01934, 00000, "circular role grant detected"
// *Cause:  Roles cannot be granted circularly.  Also, a role cannot be
//          granted to itself.
// *Action: Do not perform the grant.
01935, 00000, "missing user or role name"
// *Cause:  A user or role name was expected.
// *Action: Specify a user or role name.
01936, 00000, "cannot specify owner when creating users or roles"
// *Cause:  Users and roles do not have owners.
// *Action: Don't specify an owner.
01937, 00000, "missing or invalid role name"
// *Cause:  A valid role name was expected.
// *Action: Specify a valid role name.
01938, 00000, "IDENTIFIED BY must be specified for CREATE USER"
// *Cause:  Cannot create a user without specifying a password or
//          "IDENTIFIED EXTERNALLY".
// *Action: Specify one of the password clauses.
01939, 00000, "only the ADMIN OPTION can be specified"
// *Cause:  System privileges and Roles can only be granted with the admin
//          option.  The grant option cannot be used with these privileges.
// *Action: Specify the admin option.
01940, 00000, "cannot drop a user that is currently connected"
// *Cause:  Attempt was made to drop a user that is currently logged in.
// *Action: Make sure user is logged off, then repeat command.
01941, 00000, "SEQUENCE keyword expected"
// MERGE: 1917 RENUMBERED TO 1941
// *Cause: keyword missing
// *Action: supply missing keyword
01942, 00000, "IDENTIFIED BY and EXTERNALLY cannot both be specified"
// *Cause:  A user cannot be specified to have and not have a password.
// *Action: Specify only one of the options.
01943, 00000, "IDENTIFIED BY already specified"
// *Cause:  The identified clause has been given twice.
// *Action: Use only one identified by clause.
01944, 00000, "IDENTIFIED EXTERNALLY already specified"
// *Cause:  The identified externaly clause has been given twice.
// *Action: Use only one identified clause.
01945, 00000, "DEFAULT ROLE[S] already specified"
// *Cause:  The default roles clause has been given twice.
// *Action: Use only on default role clause.
01946, 00000, "DEFAULT TABLESPACE already specified"
// *Cause:  The default tablespace clause has been given twice.
// *Action: Use only one default tablespace clause.
01947, 00000, "TEMPORARY TABLESPACE already specified"
// *Cause:  The temporary tablespace clause has been given twice.
// *Action: Use only one temporary tablespace clause.
01948, 00000, "identifier's name length (%s) exceeds maximum (%s)"
// *Cause: A name has been specified that is too long.
//         For example, dbms_session.is_role_enabled() specifies a role name
//         that is too long.
// *Action: Change the application or command to use a correct identifier.
01949, 00000, "ROLE keyword expected"
// *Cause:  The role keyword is required here.
// *Action: Specify the role keyword.
01950, 00000, "no privileges on tablespace '%s'"
// *Cause:  User does not have privileges to allocate an extent in the
//          specified tablespace.
// *Action: Grant the user the appropriate system privileges or grant the user
//          space resource on the tablespace.
01951, 00000,  "ROLE '%s' not granted to '%s'"
// *Cause:  The role you tried to revoke was not granted to the user.
// *Action: Don't try to revoke a privilege which is not granted.
01952, 00000,  "system privileges not granted to '%s'"
// *Cause:  A system privilege you tried to revoke was not granted to the user.
// *Action: Make sure the privileges you are trying to revoke are granted.
01953, 00000,  "command no longer valid, see ALTER USER"
// *Cause:  The syntax for assigning quotas on tablespaces has changed.  The
//          ALTER USER command is now used to perform the functionality
// *Action: Use the alter user command instead.
01954, 00000, "DEFAULT ROLE clause not valid for CREATE USER"
// *Cause:  Default roles cannot be specified for create user.
// *Action: Grant and alter the user's default roles after creating the user.
01955, 00000, "DEFAULT ROLE '%s' not granted to user"
// *Cause:  The user being altered does not have the specified role granted
//          directly to the user.  Note, sub-roles cannot be used in the
//          default role clause.
// *Action: Grant the role to the user.
01956, 00000, "invalid command when OS_ROLES are being used"
// *Cause:  This command cannot be used when the INIT.ORA parameter OS_ROLES
//          is TRUE.
// *Action: Grant the role to the user in the operating system.
01957, 00000, "Keyword MIN or MAX expected, not found"
// *Cause:
// *Action:
01958, 00000, "Must supply an integer for the LAYER option"
// *Cause:
// *Action:
01959, 00000, "Must supply an integer for the OPCODE option"
// *Cause:
// *Action:
01960, 00000, "Invalid dump logfile option"
// *Cause:
// *Action:
01961, 00000, "Invalid dump option"
// *Cause:
// *Action:
01962, 00000, "Must specify a file number or log sequence number"
// *Cause:
// *Action:
01963, 00000, "Must specify a block number"
// *Cause:
// *Action:
01964, 00000, "Must specify a time for the TIME option"
// *Cause:
// *Action:
01965, 00000, "Must specify a PERIOD"
// *Cause:
// *Action:
01967, 00000, "invalid option for CREATE CONTROLFILE"
// *Cause:  An invalid CREATE CONTROLFILE option is present.
// *Action:  Specify only valid CREATE CONTROLFILE options.
01968, 00000, "Only specify RESETLOGS or NORESETLOGS once"
// *Cause:  The keyword RESETLOGS or NORESETLOGS has appeared more than once
// *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
01969, 00000, "You must specify RESETLOGS or NORESETLOGS"
// *Cause:  Missing a RESETLOGS or a NORESETLOGS
// *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
01970, 00000, "You must specify a database name for CREATE CONTROLFILE"
// *Cause:  Missing a database name
// *Action: Retype CREATE CONTROLFILE command with the DATABASE keyword.
01971, 00000, "Illegal ALTER TRACING option"
// *Cause:
// *Action:
01972, 00000, "Must specify a string for ALTER TRACING ENABLE or DISABLE"
// *Cause:
// *Action:
01973, 00000, "Missing change number"
// *Cause: Keyword "CHANGE" found but change number not specified.
// *Action:  Fix command line and resubmit
01974, 00000, "Illegal archive option"
// *Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command
// *Action:
01975, 00000, "Illegal character in change number %s"
// *Cause:
// *Action:
01976, 00000, "Missing change number"
// *Cause:
// *Action:
01977, 00000, "Missing thread number"
// *Cause: Keyword "THREAD" found but thread number not specified.
// *Action:  Fix command line and resubmit
01978, 00000, "Missing sequence number"
// *Cause: Keyword "SEQUENCE" found but sequence number not specified.
// *Action:  Fix command line and resubmit
01979, 00000, "missing or invalid password for role '%s'"
// *Cause:   An attempt was made to enable a role without giving
/            the proper password.
// *Action:  Use the "identified by" clause in set role to specify
//           the correct password.
01980, 00000, "error during OS ROLE initialization"
// *Cause: An OS error occurred while loading a users OS ROLES.
// *Action:  Check the OS error.
01981, 00000, "CASCADE CONSTRAINTS must be specified to perform this revoke"
// *Cause: During this revoke some foreign key contraints will be removed.
//         In order to perform this automatically, CASCADE CONSTRAINTS must
//         be specified.
// *Action:  Remove the constraints or specify CASCADE CONSTRAINTS.
01982, 00000, "invalid auditing option for tables"
// *Cause:  AUDIT or NOAUDIT on a table specifies an auditing option that is
//          not legal for tables.
// *Action: The following options may not be used for tables
//          and should be removed:  REFERENCES, EXECUTE
01983, 00000, "invalid auditing option for DEFAULT"
// *Cause:  AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is
//          not legal for DEFAULT.
// *Action: The following options may not be used for DEFAULT
//          and should be removed:  REFERENCES
01984, 00000, "invalid auditing option for procedures/packages/functions"
// *Cause:  AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is
//          not legal for procedures, packages, or functions.
// *Action: The following options may not be used for procedures, packages,
//          and functions and should be removed:  all but EXECUTE
01985, 00000, "cannot create user as LICENSE_MAX_USERS parameter exceeded"
// *Cause:  Maximum users in the database license limit exceeded.
// *Action: Increase license limit.
01986, 00000, "OPTIMIZER_GOAL is obsolete"
// *Cause:  An obsolete parameter, OPTIMIZER_GOAL, was referenced.
// *Action: Use the OPTIMIZER_MODE parameter.
01987, 00000, "client os username is too long"
// *Cause:  A client's os username is too long for the os logon to succeed.
// *Action: Use a shorter os username.
01988, 00000, "remote os logon is not allowed"
// *Cause:  Remote os login attempted when not allowed.
// *Action: Use a local client, or use the remote_os_authent system parameter
//          to turn on remote os logon.
01989, 00000, "role '%s' not authorized by operating system"
// *Cause:  The os role does not exist, is not granted to you, or you did not
//          provide the correct password.
// *Action: Re-attempt the SET ROLE with a valid os role and password, if
//          necessary.
01990, 00000, "error opening password file '%s'"
// *Cause:
// *Action:
01991, 00000, "invalid password file '%s'"
// *Cause:
// *Action:
01992, 00000, "error closing password file '%s'"
// *Cause:
// *Action:
01993, 00000, "error writing password file '%s'"
// *Cause:
// *Action:
01994, 00000, "GRANT failed: password file missing or disabled"
// *Cause:  The operation failed either because the INIT.ORA parameter 
//          REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the
//          password file was missing.
// *Action: Create the password file using the orapwd tool and set the
//          INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE.
01995, 00000, "error reading password file '%s'"
// *Cause:
// *Action:
01996, 00000, "GRANT failed: password file '%s' is full"
// *Cause:
// *Action:
01997, 00000, "GRANT failed: user '%s' is identified externally"
// *Cause:
// *Action:
01998, 00000, "REVOKE failed: user SYS always has SYSOPER and SYSDBA"
// *Cause:
// *Action:
01999, 00000, "password file cannot be updated in SHARED mode"
// *Cause:  The operation failed because the INIT.ORA parameter
//          REMOTE_LOGIN_PASSWORDFILE was set to SHARED.
// *Action: Set the INIT.ORA parameter to EXCLUSIVE.
/
/ 2000 - 2099 Parse errors continued from 1700 - 1799
/
02000, 00000, "missing %s keyword"
02001, 00000, "user SYS is not permitted to create indexes with freelist groups"
// *Cause: user tried to create an index while running with sys authorization.
// *Action:
02002, 00000, "error while writing to audit trail"
// *Cause:
// *Action:
02003, 00000, "invalid USERENV parameter"
// *Cause:
// *Action:
02004, 00000, "security violation"
// *Cause:  This error code is never returned to a user.   It is used
//    as a value for column, audit_trail.returncode, to signal that a
//    security violation occurred.
// *Action:  None.
02005, 00000, "implicit (-1) length not valid for this bind or define datatype"
// *Cause:
// *Action:
02006, 00000, "invalid packed decimal format string"
// *Cause:
// *Action:
02007, 00000, "can't use ALLOCATE or DEALLOCATE options with REBUILD"
// *Cause: Allocate or deallocate storage and rebuild index are not compatible.
// *Action: Choose one or the other.
02008, 00000, "non-zero scale specified for nonnumeric column"
// *Cause:
// *Action:
02009, 00000, "the size specified for a file must not be zero"
// *Cause:  A value of zero was specified in a SIZE or RESIZE clause
//          of a file specification.
// *Action: Use correct syntax, or, if allowed, omit the SIZE or
//          RESIZE clause.
02010, 00000, "missing host connect string"
// *Cause:
// *Action:
02011, 00000, "duplicate database link name"
// *Cause:
// *Action:
02012, 00000, "missing USING keyword"
// *Cause:
// *Action:
02013, 00000, "missing CONNECT keyword"
// *Cause:
// *Action:
02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc."
// *Cause: An attempt was made to select FOR UPDATE from a view which
//         had not been merged because the view used syntax (for example,
//         DISTINCT or GROUP BY) preventing the merge, or because of
//         initialization file parameter settings.
// *Action: Determine the reason the view will not merge and, if possible,
//          make changes so that it can.
02015, 00000, "cannot select FOR UPDATE from remote table"
// *Cause:
// *Action:
02016, 00000, "cannot use a subquery in a START WITH on a remote database"
// *Cause:
// *Action:
02017, 00000, "integer value required"
// *Cause:
// *Action:
02018, 00000, "database link of same name has an open connection"
// *Cause:
// *Action:
02019, 00000, "connection description for remote database not found"
// *Cause:
// *Action:
02020, 00000, "too many database links in use"
// *Cause:  The current session has exceeded the INIT.ORA open_links maximum.
// *Action: Increase the open_links limit, or free up some open links by
//          committing or rolling back the transaction and canceling open
//          cursors that reference remote databases.
02021, 00000, "DDL operations are not allowed on a remote database"
// *Cause: An attempt was made to use a DDL operation on a remote database.
//         For example, "CREATE TABLE tablename@remotedbname ...".
// *Action: To alter the remote database structure, you must connect to the
//          remote database with the appropriate privileges.
02022, 00000, "remote statement has unoptimized view with remote object"
// *Cause: The local view is unoptimized and contains references to objects
//         at the remote database and the statement must be executed at the
//         remote database.
// *Action: Create a similar view on the remote database and modify the
//          violating view in the SQL statement with the new view@remote.
02023, 00000, "START WITH or CONNECT BY predicate cannot be evaluated by remote data base"
// *Cause:
// *Action:
02024, 00000, "database link not found"
// *Cause: Database link to be dropped is not found in dictionary
// *Action: Correct the database link name
02025, 00000, "all tables in the SQL statement must be at the remote database"
// *Cause: The user's SQL statement references tables from multiple databases.
//         The remote database is not Oracle V7 or above, and can perform
//         updates only if it can reference all tables in the SQL statement.
// *Action:
02026, 00000, "missing LINK keyword"
// *Cause: keyword missing
// *Action: supply missing keyword
02027, 00000, "multi-row UPDATE of LONG column is not supported"
// *Cause:  A bind variable with length greater than 4000 bytes is being
//   used to update a column, and the update statement updates
//   more than one row.
// *Action:  You may only update a single row with such a bind variable.
02028, 00000, "fetching an exact number of rows is not supported by the server"
// *Cause: The server does not support UPIALL, so the fetch of an exact
//         number of rows cannot be emulated on the user side.
// *Action: Connect to a valid server or do not use an exact fetch.
02029, 00000, "missing FILE keyword"
// *Cause: keyword missing
// *Action: supply missing keyword
02030, 00000, "can only select from fixed tables/views"
// *Cause:  An attempt is being made to perform an operation other than
//   a retrieval from a fixed table/view.
// *Action:  You may only select rows from fixed tables/views.
02031, 00000, "no ROWID for fixed tables or for external-organized tables"
// *Cause:  An attempt is being made to access rowid from a fixed
//          table or from a external-organized table.
// *Action:  Do not access ROWID from a fixed table or from a
//           external-organized table.
02032, 00000, "clustered tables cannot be used before the cluster index is built"
// *Cause: User attempted to perform a DML statement on a clustered table
//  for which no cluster index has yet been created.
// *Action:  Create the cluster index.
02033, 00000, "a cluster index for this cluster already exists"
// *Cause: A cluster index already exists for the cluster.
// *Action: None.
02034, 00000, "speed bind not permitted"
// *Cause: Speed bind not allowed with supplied bind variables.  Trapped
//  internally by the system.
// *Action:  none
02035, 00000, "illegal bundled operation combination"
// *Cause: User requested that the UPI bundled execution call perform an
// an illegal combination of operations.
// *Action:  See documentation for legal operation combinations.
02036, 00000, "too many variables to describe with automatic cursor open"
// *Cause: User requested that the UPI bundled execution call perform
// automatic cursor open and close on a describe operation.  There
// were too many select-list items or bind variables to do this.
// *Action:  open and close cursor explicitly
02037, 00000, "uninitialized speed bind storage"
// *Cause: User attempted a UPI bundled execution call containing a
// standalone execute operation without first performing
// a UPI bundled execution call containing a bind operation.
// *Action:  perform a UPI bundled execution call with bind before performing a
// bundled execution call with execute
02038, 00000, "define is not allowed for array type "
// *Cause: User attempted to define a select list variable of type "array".
// Arrays may only serve as host bind variables.
// *Action:
02039, 00000, "bind by value is not allowed for array type "
// *Cause: User attempted to bind an array host variable by value.
// Arrays may only be bound by reference.
// *Action:
/
/ 2040 .. 2099 - Reserved for distributed update
/                (Message range continued at 160)
/
02040, 00000, "remote database %s does not support two-phase commit"
// *Cause: the database was potentially updated but does not support prepare
// to commit (as determined by its logon transaction traits).  The
// transaction was rolled back.
// *Action: Do not attempt to update the remote database unless it is the
// only database updated in one transaction.
02041, 00000, "client database did not begin a transaction"
// *Cause: internal error
// *Action: contact support
02042, 00000, "too many distributed transactions"
// *Cause: the distributed transaction table was full because too many
// distributed transactions were active.
// *Action: Run fewer transactions.  If you are sure you don't have too 
//      many concurrent distributed transactions, this indicates an internal 
//      error and support should be notified.  Instance shutdown/restart 
//      would be a work-around.
02043, 00000, "must end current transaction before executing %s"
// *Cause: a transaction is in progress and one of the following commands
//         commands is issued: COMMIT FORCE, ROLLBACK FORCE, or
//         ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.
// *Action: COMMIT or ROLLBACK the current transaction and resubmit
//          command.
02044, 00000, "transaction manager login denied: transaction in progress"
// *Cause: a remote transaction manager tried to log in while a distributed
//         transaction is in progress.
// *Action: end the current transaction (this is a protocol error from a
//          remote transaction manager)
02045, 00000, "too many local sessions participating in global transaction"
// *Cause: too many sessions at this site for this transaction.
// *Action: use an existing link so another session need not be created.
02046, 00000, "distributed transaction already begun"
// *Cause: internal error or error in external transaction manager.
//         A server session received a begin_tran RPC before finishing
//         with a previous distributed tran.
02047, 00000, "cannot join the distributed transaction in progress"
// *Cause: Either a transaction is in progress against a remote database
//         that does not fully support two phase commit, and an update
//         is attempted on another database, or updates are pending and
//         and an attempt is made to update a different database that
//         does not fully support two phase commit.
// *Action: complete the current transaction and then resubmit the
//          update request.
02048, 00000, "attempt to begin distributed transaction without logging on"
// *Cause: client program must issue a distributed transaction login.
// *Action: contact support.
02049, 00000, "timeout: distributed transaction waiting for lock"
// *Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock.
// *Action: treat as a deadlock
02050, 00000, "transaction %s rolled back, some remote DBs may be in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; remote DBs will automatically re-sync when the
//    failure is repaired.
02051, 00000, "another session or branch in same transaction failed or finalized"
// *Cause: A session at the same site with the same global transaction ID failed.
//         The failure could also be caused by an application error if an attempt
//         was made to update the database while another tightly coupled transaction
//         branch with the same global transaction ID was finalized or aborted.
// *Action: No action necessary as the transaction will be automatically recovered.
//          In the case of an application error, make sure there are no more updates
//          to the database once the transaction manager has started two-phase commit
//          for tightly coupled distributed transaction.
02052, 00000, "remote transaction failure at %s"
// *Cause: error in remote transaction at given DBLINK
// *Action: retry
02053, 00000, "transaction %s committed, some remote DBs may be in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; remote DBs will automatically re-sync when the
//    failure is repaired.
02054, 00000, "transaction %s in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; DBs will automatically re-sync when the
//    failure is repaired.  Monitor pending_trans$ for final outcome.
02055, 00000, "distributed update operation failed; rollback required"
// *Cause: a failure during distributed update operation may not have
//      rolled back all effects of the operation.  Since
//   some sites may be inconsistent, the transaction must roll back to
// a savepoint or entirely
// *Action: rollback to a savepoint or rollback transaction and resubmit
02056, 00000, "2PC: %s: bad two-phase command number %s from %s"
// *Cause: two-phase commit protocol error.
// *Action: recovery of transaction attempted.  Monitor pending_trans$ table to
//      ensure correct resolution.  Contact support.
02057, 00000, "2PC: %s: bad two-phase recovery state number %s from %s"
// *Cause: internal error in two-phase recovery protocol
// *Action: contact support
02058, 00000, "no prepared transaction found with ID %s"
// *Cause: no transaction with local_tran_id or global_tran_id found in the
//         pending_trans$ table in prepared state.
// *Action: check the pending_trans$ table.
02059, 00000, "ORA-2PC-CRASH-TEST-%s in commit comment"
// *Cause: This is a special comment used to test the two phase commit.
// *Action: Don't use this special comment (%s a number 1-10)
02060, 00000, "select for update specified a join of distributed tables"
// *Cause: tables in a join with the for update clause must reside at the
//         same DB.
02061, 00000, "lock table specified list of distributed tables"
// *Cause: tables in a lock table statement must reside at the same DB.
// *Action: issue multiple lock table commands.
02062, 00000, "distributed recovery received DBID %s, expected %s"
// *Cause: a database link at a coordinator no longer points to the expected
//         database.  Link may have been redefined, or a different DB mounted.
// *Action: restore link definition or remote database.
02063, 00000, "preceding %s%s from %s%s"
// *Cause: an Oracle error was received from a remote database link.
// *Action: refer to the preceding error message(s)
02064, 00000, "distributed operation not supported"
// *Cause: One of the following unsupported operations was attempted:
//         1. array execute of a remote update with a subquery that references
//            a dblink, or
//         2. an update of a long column with bind variable and an update of
//            a second column with a subquery that both references a dblink
//            and a bind variable, or
//         3. a commit is issued in a coordinated session from an RPC procedure 
//            call with OUT parameters or function call.
// *Action: simplify remote update statement
02065, 00000, "illegal option for ALTER SYSTEM"
// *Cause: The option specified for ALTER SYSTEM is not supported
// *Action: refer to the user manual for option supported
02066, 00000, "missing or invalid DISPATCHERS text"
// *Cause: A character string literal was expected, but not found, following
//   ALTER SYSTEM SET DISPATCHERS
// *Action: place the string literal containing the dispatcher's specification
//          after ALTER SYSTEM SET DISPATCHERS
02067, 00000, "transaction or savepoint rollback required"
// *Cause: A failure (typically a trigger or stored procedure with multiple
//   remote updates) occurred such that the all-or-nothing execution
//   of a previous Oracle call cannot be guaranteed.
// *Action: rollback to a previous savepoint or rollback the transaction
//    and resubmit.
02068, 00000, "following severe error from %s%s"
// *Cause: A severe error (disconnect, fatal Oracle error) received from
//   the indicated database link.  See following error text.
// *Action: Contact the remote system administrator.
02069, 00000, "global_names parameter must be set to TRUE for this operation"
// *Cause: A remote mapping of the statement is required but cannot be achieved
//         because global_names should be set to TRUE for it to be achieved
// *Action: Issue alter session set global_names = true if possible
02070, 00000, "database %s%s does not support %s in this context"
// *Cause: The remote database does not support the named capability in
//   the context in which it is used.
// *Action: Simplify the SQL statement.
//
02071, 00000, "error initializing capabilities for remote database %s"
// *Cause: Could not load a remote-specified capability table.
// *Action: Contact support for the remote SQL*Connect product.
//
02072, 00000, "distributed database network protocol mismatch"
// *Cause: This should never happen between different PRODUCTION releases of
//   ORACLE, but may happen between alpha and beta releases, for example.
// *Action: Upgrade the older release.
//
02073, 00000, "sequence numbers not supported in remote updates"
// *Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES
//   on remote tables.
// *Action:
02074, 00000, "cannot %s in a distributed transaction"
// *Cause: A commit or rollback was attempted from session other than
//   the parent of a distributed transaction.
// *Action: Only commit or rollback from the parent session.
02075, 00000, "another instance changed state of transaction %s"
// *Cause: A commit force or rollback force was issued from a session
//   in another instance.
// *Action: Check if another Oracle instance is performing recovery of pending
//    transactions. Query DBA_2PC_PENDING to determine the new state
//    of the transaction.
02076, 00000, "sequence not co-located with updated table or long column"
// *Cause: all referenced sequences must be co-located with the table
//   with the long column.
//
02077, 00000, "selects of long columns must be from co-located tables"
// *Cause: if a select returns long columns from multiple tables, all the
//   tables must be co-located
//
02078, 00000, "invalid setting for ALTER SYSTEM FIXED_DATE"
// *Cause:
// *Action:
//
02079, 00000, "cannot join a committing distributed transaction"
// *Cause: Once a transaction branch is prepared, no more new transaction
//         branches are allowed to start, nor is the prepared transaction
//         branch allowed to be joined.
// *Action: Check the application code as this is an XA protocol violation.
//
02080, 00000, "database link is in use"
// *Cause: a transaction is active or a cursor is open on the database link
//  given in the alter session close database link <link> command.
// *Action: commit or rollback, and close all cursors
//
02081, 00000, "database link is not open"
// *Cause: dblink given is not currently open.
//
02082, 00000, "a loopback database link must have a connection qualifier"
// *Cause: An attempt was made to create a database link with the same name 
//  as the current database.
// *Action: a loopback database link needs a trailing qualifier, for example
//  MYDB.EXAMPLE.COM@INST1  - the '@INST1' is the qualifier
//
02083, 00000, "database name has illegal character '%s'"
// *Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$'
//   '.' and '@' characters.
//
02084, 00000, "database name is missing a component"
// *Cause: supplied database name cannot contain a leading '.',
//   trailing '.' or '@', or two '.' or '@' in a row.
//
02085, 00000, "database link %s connects to %s"
// *Cause: a database link connected to a database with a different name.
//  The connection is rejected.
// *Action: create a database link with the same name as the database it
//  connects to, or set global_names=false.
//
02086, 00000, "database (link) name is too long"
// *Cause: database/database link name can have at most 128 characters.
02087, 00000, "object locked by another process in same transaction"
// *Cause: A database link is being used in the cluster database environment
//   that loops back to the same instance.  One session is trying
//         to convert a lock that was obtained by the other session.
// *Action: Get the more restrictive lock first.  For example, if
//          session 1 gets a share lock and session 2 gets an exclusive lock
//          on the same object, get the exclusive lock first.  Or, simply
//          use the same session to access the object.
02088, 00000, "distributed database option not installed"
// *Cause: Remote and distributed updates and transactions are a separately
//         priced option in ORACLE V7.
//
02089, 00000, "COMMIT is not allowed in a subordinate session"
// *Cause: COMMIT was issued in a session that is not the two-phase commit
//         global coordinator.
// *Action: Issue commit at the global coordinator only.
//
02090, 00000, "network error: attempted callback+passthru"
// *Cause: internal error.
//
02091, 00000, "transaction rolled back"
// *Cause: Also see error 2092. If the transaction is aborted at a remote
//         site then you will only see 2091; if aborted at host then you will
//         see 2092 and 2091.
// *Action: Add rollback segment and retry the transaction.
02092, 00000, "out of transaction table slots for distributed transaction"
// *Cause: The transaction is assigned to the system rollback segment and is
//         trying to get into the PREPARED state, but the required number
//         of non-PREPARED slots are not available, hence the transaction
//         is rolled back.
// *Action: Add a rollback segment and retry the transaction.
02093, 00000, "TRANSACTIONS_PER_ROLLBACK_SEGMENT(%s) more than maximum possible(%s)"
// *Cause: Value of parameter specified is greater than allowed on this port.
// *Action: Use default or reduce it to less than max.
02094, 00000, "replication option not installed"
// *Cause: The replication option was not installed at this site. Updatable
//         materialized views, deferred RPCs, and other replication features were,
//         therefore, unavailable.
// *Action: Install the replication option. The replication option is not
//          part of the Oracle Server product and must be purchased
//          separately. Contact an Oracle Sales representative if the
//          replication option needs to be purchased.
02095, 00000, "specified initialization parameter cannot be modified"
// *Cause: The specified initialization parameter is not modifiable
02096, 00000, "specified initialization parameter is not modifiable with this option"
// *Cause: Though the initialization parameter is modifiable, it cannot be
//         modified using the specified command.
// *Action: Check the DBA guide for information about under what scope
//          the parameter may be modified
02097, 00000, "parameter cannot be modified because specified value is invalid"
// *Cause: Though the initialization parameter is modifiable, the modified
//   value is not acceptable to the parameter.
// *Action: Check the DBA guide for range of acceptable values for this
//    parameter.
02098, 00000, "error parsing index-table reference (:I)"
// *Cause: An incorrect index-table (:I) syntax was encountered.
// *Action: This syntax is for oracle internal use only.
02099, 00000, "used for internal purposes, should never be printed"
/
/ MODIFIED
/   shiyer    03/08/11 - Backport shiyer_bug-8498285 from main
/   jjlee     02/14/11 - Backport jjlee_bug-10398972 from main
/   skiyer    11/03/08 - 7298722:add error 03223
/   jiashi    09/04/08 - add 3176
/   shiyer    06/02/08 - Add 3147
/   jiashi    04/01/08 - add ORA-3174, 3175 for ADG SLA
/   jaeblee   10/30/07 - fix bugs 6510941, 4402125
/   jiashi    10/18/07 - add ORA-3172, 3173 for ADG SLA
/   krajaman  06/01/07 - Change 4023 message 
/   mvemulap  06/06/07 - error 4035
/   kigoyal   04/04/07 - add 3150, fix typos
/   shiyer    04/25/07 - add 3146
/   avaliani  04/18/07 - fix typo in cause of ORA-02391
/   nlee      03/13/07 - Add error message 4024.
/   rupsingh  01/17/07 - Add error message 3009
/   sbodagal  11/16/06 - add 4023
/   debanerj  08/09/06 - add 3145
/   rpingte   06/08/06 - add messages 3142-3144
/   jacao     06/01/06 - add message 3160 
/   shiyer    04/05/06 - add new error message for TTC proto errors 
/   gtarora   04/19/06 - nt equipartition event
/   chliang   03/29/06 - add message 3140 and 3141
/   avaliani  03/29/06 - incorporate erros_us feedback
/   sbedarka  11/16/05 - #(4736313) apply 4k limit for xpl pred to txt 
/   mmpandey  11/02/05 - 4708558: make addition of tempfile in error 03284 
/   cmlim     11/09/05 - update action text for ORA-2352 & 2353 
/   yuli      10/31/05 - remove unused error numbers 
/   cmlim     06/28/05 - bug 4373139 - cleanup error handling 
/   chliang   04/25/05 - fix error text for 3135
/   schandra  01/31/05 - remove error 4018 and friends 
/   cmlim     03/18/05 - fix comment: dpapi msgs end w/ 26099, not 26999 
/   chliang   02/03/05 - add message 3135, 3136
/   nmukherj  09/25/04 - added message 3254
/   pbelknap  06/28/04 - plan diff errors 
/   nmukherj  05/12/04 - 
/   desinha   12/07/03 - 2531841: add 04069 
/   abande    10/14/03 - add error message 3134
/   smalathe  08/19/03 - Bug#3051582: Add mesg 3133 
/   pokumar   07/28/03 - add message 4034
/   cmlim     05/22/03 - bug 2885435: update cause/action of ORA-02368
/   jstenois  03/04/03 - 
/   jstenois  03/03/03 - 2775869: add message for bad rows during import
/   cmlim     03/27/03 - add 2368. obsolete 2353.
/   cmlim     02/17/03 - bug 2769696
/   cmlim     02/03/03 - add 2354, 2355... for dpapi stream load/unload error
/   lilin     12/16/02 - Eliminate Thread Number, add 2188
/   aramarao  11/11/02 - Message for disabling modifying of INITRANS for 
/                        hashed clusters
/   cmlim     11/05/02 - add err msgs for dirpath stream load/unload (#2351,...)
/   nwhyte    10/21/02 - Change "Average" to "average" on message 3222 per 
/                        review comments
/   ilam      08/30/02 - Add 2487, 2488
/   porangas  10/17/02 - Fix bug#2607903
/   wyang     09/11/02 - change 2142, 2180 
/   sbedarka  09/16/02 - #(2479110) handle pin deadlock error
/   nwhyte    08/21/02 - Add object growth trend and create table cost to
/                        dbms_space
/   cmlim     07/01/02 - remove obsolete direct loader msgs. 
/                        reserve this range for 2351-2375 for direct path api.
/   bemeng    08/02/02 - add 3252 (initial extent size for LOB segment)
/   phchang   02/11/02 - #1941831: add error 2314
/   smuralid  12/22/01 - eliminate 2312, 2313 etc
/   yuli      10/23/01 - tablespace rename project 
/   smuthuli  08/01/01 - locally managed SYSTEM tablespace
/   yuli      07/26/01 - change oer 2142 and 2180
/   smuthuli  06/07/01 - Change oer 3237
/   weili     06/22/01 - bug 1755749 fix - remove 3232
/   smuthuli  01/12/01 - add 3249
/   vshukla   01/17/01 - Fix error message 2262.
/   gtarora   01/16/01 - add 2348
/   dalpern   11/28/00 - privileges for kga debugger
/   smukkama  10/11/00 - add 3221 (disallow non-std block size temp segments)
/   amanikut  10/04/00 - modify 2321
/   bhirano   09/03/00 - add out-of-memory error for pool growth
/   preilly   08/14/00 - Update description to fix bug 1164753
/   lsheng    07/27/00 - update error message ORA-02204
/   preilly   07/31/00 - Update error message for bug 1164753
/   skaluska  06/23/00 - add 3119, 3132.
/   mjstewar  06/13/00 - OMF
/   bdagevil  04/18/00 - add error msg for memory management
/   nireland  03/20/00 - Amend ORA-3219 message. #1152302
/   rmurthy   03/31/00 - inheritance related changes
/   apadmana  01/06/00 - change SNAPSHOT to MATERIALIZED VIEW
/   skray     12/13/99 - modified alter tracing messages 2480-2489
/   smuthuli  04/28/99 - add 3247
/   lcprice   07/01/99 - 746805 modify 3211 message
/   mjungerm  03/23/99 - fix comment in 04044
/   weiwang   02/02/99 - add schema name to error 4098
/   akruglik  06/30/98 - incorporate Randy's comments
/   akruglik  06/30/98 - define msgs 3238 and 3239                             
/   ansriniv  04/13/98 - add OER(4047) - dbms_shared_pool
/   atsukerm  03/03/98 - add subpartition messages to DBMS_SPACE package.
/   tnbui     12/03/97 - Change error messages for validating a constraint
/   bgoyal    12/17/97 - error 2327 change column to expression
/   bhimatsi  03/03/98 - bitmapped ts - add error messages
/   atsukerm  02/06/98 - add dbms_space_admin errors.
/   mkcyee    11/03/97 - #(568232): add error 3206
/   lcprice   08/19/97 - Merge of bug fix 461293
/   jwlee     08/04/97 - Add error 4018
/   akruglik  07/29/97 - add msgs 3233-3236
/   mluong    06/24/97 - merge from 803
/   nireland  06/24/97 - Add error message 2475. (#324089)
/   anolan    05/21/97 - checkout
/   mjaganna  06/11/97 - Change message 02160
/   mluong    05/27/97 - fix merge problem
/   anolan    05/14/97 - Demo.
/   jbellemo  04/11/97 - remove 2343
/   jbellemo  04/08/97 - undo 2303, add types to 2344
/   thajek    03/24/97 - del 2346, modify 2303, readd 2344
/   rjenkins  03/18/97 - changing 2256
/   usundara  01/03/97 - add error 2311 for bug 434240
/   usundara  12/31/96 - incomplete and mutually-dependent types (add ora-4055)
/   bcchang   12/20/96 - error.msg split
/
/ 2100 .. 2139 - Reserved for precompiler runtime (SQLLIB)
/
02100, 00000, "PCC: out of memory (i.e., could not allocate)"
02101, 00000, "PCC: inconsistent cursor cache (uce/cuc mismatch)"
02102, 00000, "PCC: inconsistent cursor cache (no cuc entry for this uce)"
02103, 00000, "PCC: inconsistent cursor cache (out-of-range cuc ref)"
02104, 00000, "PCC: inconsistent host cache (no cuc available)"
02105, 00000, "PCC: inconsistent cursor cache (no cuc entry in cache)"
02106, 00000, "PCC: inconsistent cursor cache (OraCursor nr is bad)"
02107, 00000, "PCC: this pgm too old for run-time library: please re-PCC it"
02108, 00000, "PCC: invalid descriptor passed to run-time library"
02109, 00000, "PCC: inconsistent host cache (out-of-range sit ref)"
02110, 00000, "PCC: inconsistent host cache (invalid sqi type)"
02111, 00000, "PCC: heap consistency error"
02112, 00000, "PCC: SELECT..INTO returns too many rows"
/
/ 2140 .. 2499 - V6 parser errors continued
/                parser errors continued at 25000
/
02140, 00000, "invalid tablespace name"
// *Cause:  An identifier does not follow ALTER TABLESPACE.
// *Action:  Specify a tablespace name following ALTER TABLESPACE.
02141, 00000, "invalid OFFLINE option"
// *Cause:  An option other than NORMAL or IMMEDIATE follows OFFLINE.
// *Action:  The user must either specify no option following OFFLINE or
//    one of the options NORMAL or IMMEDIATE.
02142, 00000, "missing or invalid ALTER TABLESPACE option"
// *Cause:  A valid option was not present.
// *Action:  Use one of the valid options: add, rename, default, online,
//    offline, read only, read write, begin, end, no, force,
//          retention guarantee and retention noguarantee.
02143, 00000, "invalid STORAGE option"
// *Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or
//  PCTINCREASE was specified in the STORAGE clause.
// *Action: Specify only valid options.
02144, 00000, "no option specified for ALTER CLUSTER"
// *Cause: No ALTER CLUSTER options are specified.
// *Action:  Specify one or more of the following options: pctfree,
//    pctused, size, storage.
02145, 00000, "missing STORAGE option"
// *Cause: No STORAGE options were specified following STORAGE (
// *Action: Specify one or more STORAGE option between the
//   parentheses.
02146, 00000, "SHARED specified multiple times"
// *Cause:  The SHARED option was specified in a CREATE DATABASE
//   statement multiple times.
// *Action:  Only specify the SHARED option once.
02147, 00000, "conflicting SHARED/EXCLUSIVE options"
// *Cause:  Both the SHARED and EXCLUSIVE options were specified in a
//   CREATE DATABASE statement.
// *Action:  Specify SHARED or EXCLUSIVE, but not both.
02148, 00000, "EXCLUSIVE specified multiple times"
// *Cause:  The EXCLUSIVE option was specified in a CREATE DATABASE
//   statement multiple times.
// *Action:  Only specify the EXCLUSIVE option once.
02149, 00000, "Specified partition does not exist"
// *Cause:   Partition not found for the object.
// *Action:  Retry with correct partition name.
02150, 00000, "invalid new tablespace name"
// *Cause:   The new tablespace name specified in ALTER TABLESPACE RENAME TO
//           statement was invalid.
// *Action:  Retry with a valid new tablespace name.
02151, 00000, "invalid tablespace name: %s"
// *Cause:   Oracle cannot create a tablespace whose name starts with
//           '_$deleted$'.
// *Action:  Try a different tablespace name.
02152, 00000, "Invalid ALTER TABLESPACE ... RENAME option"
// *Cause:   An option other than DATAFILE or TO follows by ALTER
//           TABLESPACE ... RENAME.
// *Action:  The user must specify either DATAFILE or TO following ALTER
//           TABLESPACE ... RENAME.
02153, 00000, "invalid VALUES password string"
// *Cause:   An encoded password string does not follow the VALUES clause.
// *Action:  Place a proper encoded password string after the VALUES clause.
02154, 00000, "a tablespace with the name '%s' is found"
// *Cause:   An attempt to rename a tablespace to a new name failed because
//           the new name is already used by some other tablespace.
// *Action:  Retry with a different new name.
02155, 00000, "invalid DEFAULT tablespace identifier"
// *Cause:  An identifier does not follow DEFAULT TABLESPACE.
// *Action:  Place a tablespace name after DEFAULT TABLESPACE.
02156, 00000, "invalid TEMPORARY tablespace identifier"
// *Cause:  An identifier does not follow TEMPORARY TABLESPACE.
// *Action:  Place a tablespace name after TEMPORARY TABLESPACE.
02157, 00000, "no options specified for ALTER USER"
// *Cause:  No options were specified.
// *Action:  Specify at least one ALTER USER option.
02158, 00000, "invalid CREATE INDEX option"
// *Cause:   An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS,
//     MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, 
//           UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.
// *Action:  Choose one of the valid CREATE INDEX options.
02159, 00000, "installed DLM does not support releasable locking mode"
// *Cause:  The parameter file specified gc_* parameters that allow locks
//          to be release by the LCK process when not in use.  This mode
//          requires additional support from the DLM that is not available.
// *Action: Specify configuration parameters that do not require the 
//          additional function.
02160, 00000, "index-organized table can not contain columns of type LONG"
// *Cause: A column of type LONG defined for index-organized table.
// *Action: Do not use columns of type LONG in index-organized tables.
02161, 00000, "invalid value for MAXLOGFILES"
// *Cause:  A number does not follow MAXLOGFILES.
// *Action:  Specify a number after MAXLOGFILES.
02162, 00000, "invalid value for MAXDATAFILES"
// *Cause:  A number does not follow MAXDATAFILES.
// *Action:  Specify a number after MAXDATAFILES.
02163, 00000, "invalid value for FREELIST GROUPS"
// *Cause:  A number does not follow FREELIST GROUPS.
// *Action:  Specify a number after FREELIST GROUPS.
02164, 00000, "DATAFILE clause specified more than once"
// *Cause:  The CREATE DATABASE command contains more than one DATAFILE clause.
// *Action:  Specify at most one DATAFILE clause.
02165, 00000, "invalid option for CREATE DATABASE"
// *Cause:  An invalid CREATE DATABASE option is present.
// *Action:  Specify only valid CREATE DATABASE options.
02166, 00000, "ARCHIVELOG and NOARCHIVELOG specified"
// *Cause:  Both ARCHIVELOG and NOARCHIVELOG are specified in a
//   CREATE DATABASE statement.
// *Action:  Specify at most one of these two options.
02167, 00000, "LOGFILE clause specified more than once"
// *Cause:  The CREATE DATABASE command contains more than one LOGFILE clause.
// *Action:  Specify at most one LOGFILE clause.
02168, 00000, "invalid value for FREELISTS"
// *Cause:  A number does not follow FREELISTS
// *Action:  Specify a number after FREELISTS
02169, 00000, "FREELISTS storage option not allowed"
// *Cause:  The user attempted to specify the FREELISTS storage
//    option. This option may only be specified during
//    create table or create index.
// *Action:  Remove these options and retry the statement.
02170, 00000, "FREELIST GROUPS storage option not allowed"
// *Cause:  The user attempted to specify the FREELIST GROUPS storage
//    option. This option may only be specified during create
//    table and when allow_freelist_groups INIT.ORA is specified.
// *Action:  Remove this option and retry the statement or set the
//           allow_freelist_groups INIT.ORA parameter.
02171, 00000, "invalid value for MAXLOGHISTORY"
// *Cause:  A number does not follow MAXLOGHISTORY
// *Action:  Specify a number after MAXLOGHISTORY
02172, 00000, "The PUBLIC keyword is not appropriate for a disable thread"
// *Cause: The PUBLIC keyword was specified for a disable.
// *Action:  Remove the keyword and resubmit.
02173, 00000, "invalid option for DROP TABLESPACE"
// *Cause:  Either a token other than INCLUDING was found following the
//   tablespace name or some text was found following INCLUDING CONTENTS.
// *Action:  Place nothing or only INCLUDING CONTENTS after the tablespace name.
02174, 00000, "Missing required thread number"
// *Cause:  Must specify thread number after THREAD keyword
// *Action:
02175, 00000, "invalid rollback segment name"
// *Cause:  In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier
//   was not found following ROLLBACK SEGMENT.
// *Action:  Place the segment name following ROLLBACK SEGMENT.
02176, 00000, "invalid option for CREATE ROLLBACK SEGMENT"
// *Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
// *Action:  Specify one of the valid options: TABLESPACE and STORAGE.
02177, 00000, "Missing required group number"
// *Cause:  Must specify group number after GROUP keyword
// *Action:
02178, 00000, "correct syntax is: SET TRANSACTION READ { ONLY | WRITE }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02179, 00000, "valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02180, 00000, "invalid option for CREATE TABLESPACE"
// *Cause: An invalid option appeared.
// *Action:  Specify one of the valid options: DATAFILE, DEFAULT STORAGE,
//    ONLINE, OFFLINE, FORCE, RETENTION.
02181, 00000, "invalid option to ROLLBACK WORK"
// *Cause:  A token other than TO follows ROLLBACK [WORK].
// *Action:  Place nothing or TO SAVEPOINT <name> after ROLLBACK [WORK].
02182, 00000, "savepoint name expected"
// *Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
// *Action: Place a savepoint name following TO [SAVEPOINT].
02183, 00000, "valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02184, 00000, "resource quotas are not allowed in REVOKE"
// *Cause: In a revoke statement, a resource quota was specified.
// *Action: Specify resource privilege without the quota.
02185, 00000, "a token other than WORK follows COMMIT"
// *Cause:  A token other than WORK follows COMMIT.
// *Action:  Place either nothing or WORK after COMMIT.
02186, 00000, "tablespace resource privilege may not appear with other privileges"
// *Cause: An attempt was made to grant or revoke a resource quota in the
//  same statement in which other privileges are granted or revoked.
// *Action:  Use a separate grant or revoke statement for the resource
//    quota privilege.
02187, 00000, "invalid quota specification"
// *Cause: In a grant or revoke statement, the user attempted to grant
//  a tablespace quota above the upper limit.
// *Action:  Grant a smaller tablespace quota.
02188, 00000, "Cannot enable instance publicly"
// *Cause: An attempt was made to publicly enable a thread associated
//         with an instance.
// *Action:Leave out the PUBLIC keyword.
02189, 00000, "ON <tablespace> required"
// *Cause:  In a grant or revoke statement, the user specified a tablespace
//   quota but did not follow it with the ON <tablespace> clause.
// *Action:  Specify the tablespace on which the quota is to be applied
//    with the ON <tablespace> clause.
02190, 00000, "keyword TABLES expected"
// *Cause: The keyword TABLES is expected following DROP CLUSTER <name>
//  INCLUDING.
// *Action:  Place TABLES after INCLUDING.
02191, 00000, "correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT <rbs>"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02192, 00000, "PCTINCREASE not allowed for rollback segment storage clauses"
// *Cause: pctincrease was specified in a create or alter rollback segment 
// *Action: reissue statement without the pctincrease clause
02194, 00000, "event specification syntax error %s (minor error %s) near '%s'"
// *Cause: There is a syntax error in an event specification.
// *Action:  Fix the error.
02195, 00000, "Attempt to create %s object in a %s tablespace"
// *Cause: The object type is inconsistent with a tablespace contents.
// *Action:  Create an object in a different tablespace, or change the user
//           defaults.
02196, 00000, "PERMANENT/TEMPORARY option already specified"
// *Cause:  In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were
//   specified more than once.
02197, 00000, "file list already specified"
// *Cause:  In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was 
//          specified.
// *Action:  Merge the DATAFILE/TEMPFILE clauses into a single clause.
02198, 00000, "ONLINE/OFFLINE option already specified"
// *Cause:  In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were
//   specified more than once.
// *Action:  Specify at most one of ONLINE or OFFLINE.
02199, 00000, "missing DATAFILE/TEMPFILE clause"
// *Cause:  A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
// *Action:  Specify a DATAFILE/TEMPFILE clause.
02200, 00000, "WITH GRANT OPTION not allowed for PUBLIC"
// *Cause:  An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
// *Action:  Remove the WITH GRANT OPTION clause.
02201, 00000, "sequence not allowed here"
// *Cause:  An attempt was made to reference a sequence in a from-list.
// *Action: A sequence can only be referenced in a select-list.
02202, 00000, "no more tables permitted in this cluster"
// *Cause:  An attempt was made to create a table in a cluster which already
//   contains 32 tables.
// *Action:  Up to 32 tables may be stored per cluster.
02203, 00000, "INITIAL storage options not allowed"
// *Cause:  The user attempted to alter the INITIAL
//   storage option of a table, cluster, index, or rollback segment.
//   These options may only be specified when the object is created.
// *Action:  Remove these options and retry the statement.
02204, 00000, "ALTER, INDEX and EXECUTE not allowed for views"
// *Cause:  An attempt was made to grant or revoke an invalid privilege on a view.
// *Action:  Do not attempt to grant or revoke any of ALTER, INDEX, or
//    EXECUTE privileges on views.
02205, 00000, "only SELECT and ALTER privileges are valid for sequences"
// *Cause:  An attempt was made to grant or revoke an invalid privilege on a
//   sequence.
// *Action:  Do not attempt to grant or revoke DELETE, INDEX, INSERT,
//    UPDATE, REFERENCES or EXECUTE privilege on sequences.
02206, 00000, "duplicate INITRANS option specification"
// *Cause: INITRANS is specified more than once.
// *Action:  Specify INITRANS at most once.
02207, 00000, "invalid INITRANS option value"
// *Cause:  The INITRANS value is not an integer between 1 and 255
//   and less than or equal to the MAXTRANS value.
// *Action:  Choose a valid INITRANS value.
02208, 00000, "duplicate MAXTRANS option specification"
// *Cause:  MAXTRANS is specified more than once.
// *Action:  Specify MAXTRANS at most once.
02209, 00000, "invalid MAXTRANS option value"
// *Cause:  The MAXTRANS value is not an integer between 1 and 255
//   and greater than or equal to the INITRANS value.
// *Action:  Choose a valid MAXTRANS value.
02210, 00000, "no options specified for ALTER TABLE"
// *Cause:  No ALTER TABLE option was specified.
// *Action:  Specify at least one alter table option.
02211, 00000, "invalid value for PCTFREE or PCTUSED"
// *Cause:  The specified value for PCTFREE or PCTUSED is not
//   an integer between 0 and 100.
// *Action:  Choose an appropriate value for the option.
02212, 00000, "duplicate PCTFREE option specification"
// *Cause:  PCTFREE option specified more than once.
// *Action:  Specify PCTFREE at most once.
02213, 00000, "duplicate PCTUSED option specification"
// *Cause:  PCTUSED option specified more than once.
// *Action:  Specify PCTUSED at most once.
02214, 00000, "duplicate BACKUP option specification"
// *Cause: The BACKUP option to ALTER TABLE is specified more than once.
// *Action:  Specify the option at most once.
02215, 00000, "duplicate tablespace name clause"
// *Cause: There is more than one TABLESPACE clause in the CREATE TABLE,
//  CREATE INDEX, or CREATE ROLLBACK SEGMENT statement.
// *Action:  Specify at most one TABLESPACE clause.
02216, 00000, "tablespace name expected"
// *Cause:  A tablespace name is not present where required by the
//    syntax for one of the following statements:
//    CREATE/DROP TABLESPACE, CREATE TABLE,
//    CREATE INDEX, or CREATE ROLLBACK SEGMENT.
// *Action:  Specify a tablespace name where required by the syntax.
02217, 00000, "duplicate storage option specification"
// *Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE)
//  is specified more than once.
// *Action:  Specify all storage options at most once.
02218, 00000, "invalid INITIAL storage option value"
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
02219, 00000, "invalid NEXT storage option value"
// *Cause: The specified value must be an integer.
// *Action:  Choose an appropriate integer value.
02220, 00000, "invalid MINEXTENTS storage option value"
// *Cause: The specified value must be a positive integer
//  less than or equal to MAXEXTENTS.
// *Action:  Specify an appropriate value.
02221, 00000, "invalid MAXEXTENTS storage option value"
// *Cause: The specified value must be a positive integer
//  greater than or equal to MINEXTENTS.
// *Action:  Specify an appropriate value.
02222, 00000, "invalid PCTINCREASE storage option value"
// *Cause:  The specified value must be a positive integer.
// *Action:  Specify an appropriate value.
02223, 00000, "invalid OPTIMAL storage option value"
// *Cause: The specified value must be an integer.
// *Action:  Choose an appropriate integer value.
02224, 00000, "EXECUTE privilege not allowed for tables"
// *Cause:  An attempt was made to grant or revoke an invalid privilege on
//          a table.
// *Action:  Do not attempt to grant or revoke EXECUTE privilege on tables.
02225, 00000, "only EXECUTE and DEBUG privileges are valid for procedures"
// *Cause:  An attempt was made to grant or revoke an invalid privilege 
//          on a procedure, function or package.
// *Action:  Do not attempt to grant or revoke any privilege besides EXECUTE
//          or DEBUG on procedures, functions or packages.
02226, 00000, "invalid MAXEXTENTS value (max allowed: %s)"
// *Cause:  The MAXEXTENTS specified is too large for the database 
//          block size. This applies only to SYSTEM rollback segment.
// *Action: Specify a smaller value.
02227, 00000, "invalid cluster name"
// *Cause: A cluster name of the form [ <identifier> . ] <identifier> is
//  expected but not present.
// *Action:  Enter an appropriate cluster name.
02228, 00000, "duplicate SIZE specification"
// *Cause:  The SIZE option is specified more than once.
// *Action:  Specify the SIZE option at most once.
02229, 00000, "invalid SIZE option value"
// *Cause:  The specified value must be an integer number of bytes.
// *Action:  Specify an appropriate value.
02230, 00000, "invalid ALTER CLUSTER option"
// *Cause:  An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
//   STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
// *Action:  Specify only legal options.
02231, 00000, "missing or invalid option to ALTER DATABASE"
// *Cause:  An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG,
//   MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.
// *Action:  Specify only legal options.
02232, 00000, "invalid MOUNT mode"
// *Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword
//  in an ALTER DATABASE statement.
// *Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.
02233, 00000, "invalid CLOSE mode"
// *Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword
//  in an ALTER DATABASE statement.
// *Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.
02234, 00000, "changes to this table are already logged"
// MERGE: 2292 RENUMBERED TO 2234
// *Cause: the log table to be added is a duplicate of another
// *Action: Don't add this change log to the system; check that the
//    replication product's system tables are consistent
02235, 00000, "this table logs changes to another table already"
// MERGE: 2293 RENUMBERED TO 2235
// *Cause: the table to be altered is already a change log for another table
// *Action: Don't log changes to the specified base table to this table; check
//    that the replication product's system tables are consistent
02236, 00000, "invalid file name"
// *Cause:  A character string literal was not used in the filename list
//    of a LOGFILE, DATAFILE, or RENAME clause.
// *Action: Use correct syntax.
02237, 00000, "invalid file size"
// *Cause:  A non-integer value was specified in the SIZE or RESIZE clause. 
// *Action: Use correct syntax.
02238, 00000, "filename lists have different numbers of files"
// *Cause:  In a RENAME clause in ALTER DATABASE or TABLESPACE, the
//   the number of existing filenames does not equal the number of
//   new filenames.
// *Action:  Make sure there is a new filename to correspond to each
//    existing filename.
02239, 00000, "there are objects which reference this sequence"
// MERGE: 2290 RENUMBERED TO 2239
// *Cause: the sequence to be dropped is still referenced
// *Action: Make sure the sequence name is correct, or drop the referencing
//    constraint/object
02240, 00000, "invalid value for OBJNO or TABNO"
// *Cause:  A number does not follow either OBJNO or TABNO.
// *Action:  Specify a number after OBJNO or TABNO.
02241, 00000, "must of form EXTENTS (FILE <n> BLOCK <n> SIZE <n>, ...)"
// *Cause:  bad extent storage clause
// *Action: respecify
02242, 00000, "no options specified for ALTER INDEX"
// *Cause: No options specified.
// *Action:  Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
02243, 00000, "invalid ALTER INDEX or ALTER MATERIALIZED VIEW option"
// *Cause:  An option other than INITRANS, MAXTRANS,or STORAGE is
//       specified in an ALTER INDEX statement or in the USING
//         INDEX clause of an ALTER MATERIALIZED VIEW statement.
// *Action:  Specify only legal options.
02244, 00000, "invalid ALTER ROLLBACK SEGMENT option"
// *Cause:  The STORAGE option is expected but not found.
// *Action:  Specify the STORAGE option.
02245, 00000, "invalid ROLLBACK SEGMENT name"
// *Cause: An identifier was expected, but not found, following
//  ALTER [PUBLIC] ROLLBACK SEGMENT.
// *Action:  Place a rollback segment name following SEGMENT.
02246, 00000, "missing EVENTS text"
// *Cause:  A character string literal was expected, but not found, following
//   ALTER SESSION SET EVENTS.
// *Action:  Place the string literal containing the events text after EVENTS.
02247, 00000, "no option specified for ALTER SESSION"
// *Cause: The option SET EVENTS was expected, but not found, following
//  ALTER SESSION.
// *Action:  Place the SET EVENTS option after ALTER SESSION.
02248, 00000, "invalid option for ALTER SESSION"
// *Cause: Obvious.
// *Action:  see SQL Language Manual for legal options.
02249, 00000, "missing or invalid value for MAXLOGMEMBERS"
// *Cause: A valid number does not follow MAXLOGMEMBERS.  The value specified
//         must be between 1 and the port-specific maximum number of log
//         file members.
// *Action:  Specify a valid number after MAXLOGMEMBERS.
02250, 00000, "missing or invalid constraint name"
// *Cause: The constraint name is missing or invalid.
// *Action: Specify a valid identifier name for the constraint name.
02251, 00000, "subquery not allowed here"
// *Cause: Subquery is not allowed here in the statement.
// *Action: Remove the subquery from the statement.
02252, 00000, "check constraint condition not properly ended"
// *Cause: The specified search condition for the check constraint is not
//  properly ended.
// *Action: End the condition properly.
02253, 00000, "constraint specification not allowed here"
// *Cause: Constraint specification is not allowed here in the statement.
// *Action: Remove the constraint specification from the statement.
02254, 00000, "DEFAULT <expression> not allowed here"
// *Cause: Default value expression is not allowed for the column here in the
//  statement.
// *Action: Remove the default value expression from the statement.
02255, 00000, "obsolete 7.1.5"
// *Cause: Was that defaults must not conflict with not null constraints
// *Action:
02256, 00000, "number of referencing columns must match referenced columns"
// *Cause: The number of columns in the foreign-key referencing list is not
//   equal to the number of columns in the referenced list.
// *Action: Make sure that the referencing columns match the referenced
//          columns.
02257, 00000, "maximum number of columns exceeded"
// *Cause: The number of columns in the key list exceeds the maximum number.
// *Action: Reduce the number columns in the list.
02258, 00000, "duplicate or conflicting NULL and/or NOT NULL specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02259, 00000, "duplicate UNIQUE/PRIMARY KEY specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02260, 00000, "table can have only one primary key"
// *Cause: Self-evident.
// *Action: Remove the extra primary key.
02261, 00000, "such unique or primary key already exists in the table"
// *Cause: Self-evident.
// *Action: Remove the extra key.
02262, 00000, "ORA-%s occurs while type-checking column default value expression"
// *Cause:  New column datatype causes type-checking error for existing column
//    default value expression.
// *Action: Remove the default value expression or don't alter the column
//    datatype.
02263, 00000, "need to specify the datatype for this column"
// *Cause: The required datatype for the column is missing.
// *Action: Specify the required datatype.
02264, 00000, "name already used by an existing constraint"
// *Cause: The specified constraint name has to be unique.
// *Action: Specify a unique constraint name for the constraint.
02265, 00000, "cannot derive the datatype of the referencing column"
// *Cause: The datatype of the referenced column is not defined as yet.
// *Action: Make sure that the datatype of the referenced column is defined
//    before referencing it.
02266, 00000, "unique/primary keys in table referenced by enabled foreign keys"
// *Cause: An attempt was made to truncate a table with unique or 
//         primary keys referenced by foreign keys enabled in another table.
//         Other operations not allowed are dropping/truncating a partition of a
//         partitioned table or an ALTER TABLE EXCHANGE PARTITION.
// *Action: Before performing the above operations the table, disable the 
//          foreign key constraints in other tables. You can see what 
//          constraints are referencing a table by issuing the following 
//          command:
//          SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
02267, 00000, "column type incompatible with referenced column type"
// *Cause: The datatype of the referencing column is incompatible with the
/  datatype of the referenced column.
// *Action: Select a compatible datatype for the referencing column.
02268, 00000, "referenced table does not have a primary key"
// *Cause: The referenced table does not have a primary key.
// *Action: Specify explicitly the referenced table unique key.
02269, 00000, "key column cannot be of LONG datatype"
// *Cause: Self-evident.
// *Action: Change the datatype of the column,
//   or remove the column from the key.
02270, 00000, "no matching unique or primary key for this column-list"
// *Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement 
//         gives a column-list for which there is no matching unique or primary
//         key constraint in the referenced table.
// *Action: Find the correct column names using the ALL_CONS_COLUMNS
//          catalog view
02271, 00000, "table does not have such constraint"
// *Cause: Self-evident.
// *Action: Make sure the specified constraint name is correct.
02272, 00000, "constrained column cannot be of LONG datatype"
// *Cause: Self-evident.
// *Action: Change the datatype of the column,
//   or remove the constraint on the column.
02273, 00000, "this unique/primary key is referenced by some foreign keys"
// *Cause: Self-evident.
// *Action: Remove all references to the key before the key is to be dropped.
02274, 00000, "duplicate referential constraint specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02275, 00000, "such a referential constraint already exists in the table"
// *Cause: Self-evident.
// *Action: Remove the extra constraint.
02276, 00000, "default value type incompatible with column type"
// *Cause: The type of the evaluated default expression is incompatible with
//  the datatype of the column.
// *Action: Change the type of the column, or modify the default expression.
02277, 00000, "invalid sequence name"
// *Cause: The specified sequence name is not a valid identifier name.
// *Action: Specify a valid identifier name for the sequence name.
02278, 00000, "duplicate or conflicting MAXVALUE/NOMAXVALUE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02279, 00000, "duplicate or conflicting MINVALUE/NOMINVALUE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02280, 00000, "duplicate or conflicting CYCLE/NOCYCLE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02281, 00000, "duplicate or conflicting CACHE/NOCACHE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02282, 00000, "duplicate or conflicting ORDER/NOORDER specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02283, 00000, "cannot alter starting sequence number"
// *Cause: Self-evident.
// *Action: Don't alter it.
02284, 00000, "duplicate INCREMENT BY specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02285, 00000, "duplicate START WITH specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02286, 00000, "no options specified for ALTER SEQUENCE"
// *Cause: Self-evident.
// *Action: The statement is meaningless without any options.
02287, 00000, "sequence number not allowed here"
// *Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate
//  here in the statement.
// *Action: Remove the sequence number.
02288, 00000, "invalid OPEN mode"
// *Cause:  A token other than RESETLOGS appears following
//   ALTER DATABASE <name> OPEN.
// *Action:  Either nothing or RESETLOGS should be placed following OPEN.
02289, 00000, "sequence does not exist"
// *Cause: The specified sequence does not exist, or the user does
//   not have the required privilege to perform this operation.
// *Action: Make sure the sequence name is correct, and that you have
//    the right to perform the desired operation on this sequence.
02290, 00000, "check constraint (%s.%s) violated"
// *Cause: The values being inserted do not satisfy the named check 
// constraint.
// *Action: do not insert values that violate the constraint.
02291, 00000,"integrity constraint (%s.%s) violated - parent key not found"
// *Cause: A foreign key value has no matching primary key value.
// *Action: Delete the foreign key or add a matching primary key.
02292, 00000,"integrity constraint (%s.%s) violated - child record found"
// *Cause: attempted to delete a parent key value that had a foreign
// key dependency.
// *Action: delete dependencies first then parent or disable constraint.
02293, 00000,"cannot validate (%s.%s) - check constraint violated"
// *Cause: an alter table operation tried to validate a check constraint to
// a populated table that had nocomplying values.
// *Action: Obvious
02294, 00000,"cannot enable (%s.%s) - constraint changed during validation"
// *Cause: While one DDL statement was attempting to enable this constraint,
//      another DDL changed this same constraint.
// *Action: Try again, with only one DDL changing the constraint this time.
02295, 00000,"found more than one enable/disable clause for constraint"
// *Cause: a create or alter table specified more than one enable and/or
// disable clause for a given constraint.
// *Action: only one enable or disable may be specified for a given 
// constraint.
02296, 00000,"cannot enable (%s.%s) - null values found"
// *Cause: an alter table enable constraint failed because the table 
//      contains values that do not satisfy the constraint.
// *Action: Obvious
02297, 00000,"cannot disable constraint (%s.%s) - dependencies exist"
// *Cause: an alter table disable constraint failed becuase the table has
//      foriegn keys that are dpendent on this constraint.
// *Action: Either disable the foreign key constraints or use disable cascade
02298, 00000,"cannot validate (%s.%s) - parent keys not found"
// *Cause: an alter table validating constraint failed because the table has
// orphaned child records.
// *Action: Obvious
02299, 00000,"cannot validate (%s.%s) - duplicate keys found"
// *Cause: an alter table validating constraint failed because the table has
//      duplicate key values.
// *Action: Obvious
/
/
/        2300 - 2350 Object extensions to SQL
/          - 2310 - 2319  -  Object columns and Object Tables
/          - 2320 - 2329  -  Nested Table columns
/
02300, 00000, "invalid value for OIDGENERATORS"
// *Cause:  A number was not specified for the value of OIDGENERATORS.
// *Action:  Specify a number for OIDGENERATORS.
02301, 00000, "maximum number of OIDGENERATORS is 255"
// *Cause:  A number greater than 255 was specified for the value of
//          OIDGENERATORS.
// *Action: Make sure the number specified for OIDGENERATORS does not exceed
//           255.
02302, 00000, "invalid or missing type name"
// *Cause:  An invalid or missing type name was entered in a statement.
// *Action: Enter a valid type name in the statement and retry the operation.
02303, 00000, "cannot drop or replace a type with type or table dependents"
// *Cause:  An attempt was made to drop or replace a type that has
//          type or table dependents.
// *Action: For DROP TYPE, drop all type(s) and table(s) depending on the
//          type and then retry the operation, or use the FORCE option.
//          For CREATE TYPE, drop all type(s) and table(s) depending on the
//          type and then retry the operation, or drop all table(s) depending
//          on the type and retry with the FORCE option.
02304, 00000, "invalid object identifier literal"
// *Cause:  An attempt was made to enter an object identifier literal for
//          CREATE TYPE that is either:
//    - not a string of 32 hexadecimal characters
//    - an object identifier  that already identifies an existing
//                object
//    - an object identifier different from the original object
//                 identifier already assigned to the type
// *Action: Do not specify the object identifier clause or specify a 32
//          hexadecimal-character object identifier literal that is unique
//          or identical to the originally assigned object identifier. Then
//          retry the operation.
02305, 00000, "only EXECUTE, DEBUG, and UNDER privileges are valid for types"
// *Cause:  An attempt was made to GRANT or REVOKE an invalid privilege (not
//          EXECUTE, DEBUG, or UNDER) on a type.
// *Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on
//          types.
02306, 00000, "cannot create a type that already has valid dependent(s)"
// *Cause:  An attempt was made to create a type that already has some
//    valid dependent(s) (these dependents depend on the fact that
//    the type does not exist).
// *Action: Drop the dependents first before creating the type, or do not
//    create the type.
02307, 00000, "cannot alter with REPLACE option a type that is not valid"
// *Cause:  An attempt was made to ALTER with REPLACE option a type that
//          is not valid.
// *Action: Use the CREATE OR REPLACE TYPE command to modify the type.
02308, 00000, "invalid option %s for object type column"
// *Cause:  An attempt was made to specify an invalid option, such as PACKED
//          or UNPACKED, for the object type column.
// *Action: Remove the invalid option from column specification and retry
//          the operation.
02309, 00000, "atomic NULL violation"
// *Cause:  An attempt was made to acess the attributes of a NULL object
//         instance.
// *Action: Ensure that the object instance is non-NULL before accessing.
02310, 00000, "exceeded maximum number of allowable columns in table"
// *Cause:  The attributes in the object type column exceeded the maximum
//          number of columns allowed in a table.
// *Action: Specify fewer attributes for the object type and retry the
//          operation. 
02311, 00000, "cannot alter with COMPILE option a valid type with type or table dependents"
// *Cause:  An attempt was made to ALTER with COMPILE option a type that is
//          valid and has type or table dependents.
// *Action: No need to perform this operation.
//
02313, 00000, "object type contains non-queryable type %s attribute"
// *Cause:  The specified object type contains a nested attribute whose type
//          is non-queryable.
// *Action: Use an object type with queryable attribute types.
02314, 00000, "illegal use of type constructor"
// *Cause:  The statement contains an illegal use of a type constructor. 
// *Action: Refer to the SQL Reference manual for the correct statement syntax.
02315, 00000, "incorrect number of arguments for default constructor"
// *Cause:  The number of arguments specified for the default constructor
//    doesn't match the number of attributes of the object type.
// *Action: Specify the correct number of arguments for the default
//          constructor and retry the operation.
02320, 00000, "failure in creating storage table for nested table column %s"
// *Cause:  An error occurred while creating the storage table for the
//         specified nested table column.
// *Action: See the messages that follow for more details. If the situation
//          they describe can be corrected, do so; otherwise contact Oracle
//          Support.
02321, 00000, "event for nested table equipartition"
// *Document: NO
// *Cause:
// *Action:
02322, 00000, "failure in accessing storage table of the nested table column"
// *Cause:  An error occured while performing DML on the storage table of the
//          nested table column.
// *Action: If the situation described in the following messages can be
//          corrected, do so; otherwise contact Oracle Support.
02324, 00000, "more than one column in the SELECT list of THE subquery"
// *Cause:  More than one column was selected in the THE subquery.
// *Action: Specify only one column in the SELECT list of the THE subquery and
//          retry the operation.
02327, 00000, "cannot create index on expression with datatype %s"
// *Cause:   An attempt was made to create an index on a non-indexable 
//           expression.
// *Action:  Change the column datatype or do not create the index on an 
//           expression whose datatype is one of  VARRAY, nested table, object,
//           LOB, or  REF.
02329, 00000, "column of datatype %s cannot be unique or a primary key"
// *Cause:   An attempt was made to place a UNIQUE or a PRIMARY KEY constraint
//           on a column of datatype VARRAY, nested table, object, LOB, FILE
//           or REF.
// *Action:  Change the column datatype or remove the constraint. Then retry
//           the operation.
02330, 00000, "datatype specification not allowed"
// *Cause:   An attempt was made to specify the data type in the column
//           constraint specification of an object table.
// *Action:  Remove data type specification and retry the operation.
02331, 00000, "cannot create constraint on column of datatype %s"
// *Cause:   An attempt was made to create a constraint on a column
//           posessing a non-constrainable datatype -- VARRAY, nested table,
//           object, LOB, FILE, or REF.
// *Action:  Change the column datatype, or remove the constraint.
02332, 00000, "cannot create index on attributes of this column"
// *Cause:   An attempt was made to create an index on an attributes of an
//           object type column.
// *Action:  Do not specify the index on the attribute.
02333, 00000, "cannot create constraints on attributes of this column"
// *Cause:   An attempt was made to create a constraint on an attribute of
//           an object type column.
// *Action:  Remove the constraint or change the object type.
02334, 00000, "cannot infer type for column"
// *Cause:   A datatype was not declared for this column (in the CREATE TABLE)
//           and an attempt was made to create a constraint on an attribute of
//           this column.
// *Action:  Declare a datatype for the column. 
02335, 00000, "invalid datatype for cluster column"
// *Cause:  An attempt was made to declare a CLUSTER column of datatype
//           object, REF, nested table, VARRAY, LOB, or FILE.
// *Action: Remove the CLUSTER column or change the datatype of the column. 
02336, 00000, "column attribute cannot be accessed"
// *Cause:   An attempt was made to extract an attribute of an object type
//           column.
// *Action: Change the object type for the column and retry the operation.
02337, 00000, "not an object type column"
// *Cause:  An attempt was made to use dotted notation on a non-ADT column;
//          that is, "a.b.c" where "a" is not an object type.
// *Action: Either change the column type to an object type or do not
//          perform this operation.
02338, 00000, "missing or invalid column constraint specification"
// *Cause:  A column constraint was not specified.
// *Action: Remove the column specification or specify a column constraint.
//          Then retry the operation.
02339, 00000, "invalid column specification"
// *Cause:  An attempt was made to specify the PACKED or UNPACKED keyword
//          for a non-object type column.
// *Action: Remove the PACKED or UNPACKED keyword in the column
//          specification and retry the operation.
02340, 00000, "invalid column specification"
// *Cause:  An attempt was made to specify an UNPACKED column within a
//          packed table.
// *Action: Remove the UNPACKED keyword in the column specification.
02342, 00000, "replacement type has compilation errors"
// *Cause:  The use of the ALTER...REPLACE statement on a valid type caused
//          a compilation error.
// *Action: Use the ALTER...REPLACE statement to replace the type with a valid
//          type which does not cause compilation errors.
02344, 00000, "cannot revoke execute on a type with table dependents"
// *Cause:  An attempt was made to revoke execute on a type that has
//          dependents.
// *Action: Drop all table(s) depending on the type, then retry
//          the operation, or use the FORCE option.
02345, 00000, "cannot create a view with column based on CURSOR operator"
// *Cause:  A CURSOR operator was used as one of the SELECT elements in the
//          subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. 
// *Action: Remove the CURSOR operator and replace it with the CAST operator.
02347, 00000, "cannot grant privileges on columns of an object table"
// *Cause:  An attempt was made to grant privileges on the columns of an
//          object table.
// *Action: 
02348, 00000, "cannot create VARRAY column with embedded LOB"
// *Cause:  An attempt was made to create a column of a VARRAY type which
//          has an embedded LOB attribute. The LOB could be an attribute of
//          a subtype of the declared type of VARRAY's element.
// *Action: Remove offending attribute from type. If it is a subtype attribute
//          then declare the VARRAY column NOT SUBSTITUTABLE.
02349, 00000, "invalid user-defined type - type is incomplete" 
// *Cause:  An attempt was made to use an incomplete type definition as a
//          column or table datatype.
// *Action: Complete the type definition and retry the operation. 
/
/
/
/        2351 - 2375 Directh Path API errors
/          - 2356, 2366, 2371, & 2373: direct loader errors
/          - 2351 - 2355,
/            2357 - 2365,
/            2367 - 2370,
/            2372,
/            2374 - 2375:
/        see also range 2476 - 2479 for Parallel Direct Loader errors
/        and range 26000 - 26099 for additional Direct Path Load errors
/
02351, 00000, "internal error: %s\n"
// *Cause: An unexpected error condition was detected.
// *Action: Make a note of the error number and message and contact 
//          Oracle Support Services.
02352, 00000, "error setting an OCI attribute: %s\n"
// *Cause: An OCI error has occurred.
// *Action: The table or column referenced may not be accessible.  Contact
//          Oracle Support Services if the problem cannot be resolved.
02353, 00000, "error fetching an OCI attribute: %s\n"
// *Cause: An OCI error has occurred.
// *Action: The table or column referenced may not be accessible.  Contact
//          Oracle Support Services if the problem cannot be resolved.
02354, 00000, "error in exporting/importing data\n%s"
// *Cause: An error has occurred in a stream export or import operation.
//         This message will be followed by another message giving more
//         details about this error.
// *Action: See export/import documentation for an explanation of the second
//          error message.
02355, 00000, "error opening file: %s\n"
// *Cause: An attempt to open the specified file for data export/import failed. 
// *Action: Review the error message.  Resolve the problem and retry the
//          the operation.  Contact Oracle Support Services if
//          the problem cannot be resolved.
02356, 00000, "The database is out of space.  The load cannot continue"
// *Cause: The load was discontinued due to space exhaustion in the database.
// *Action: Add space for the specified table.
02357, 00000, "header in file %s may not contain correct information\n"
// *Cause: The header may be corrupted.
// *Action: Contact Oracle Support Services.
02358, 00000, "error in exporting or importing data\n"
// *Cause: An error has occurred in a stream export or import operation.
// *Action: Contact Oracle Support Services.
02359, 00000, "database version in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because
//         its database version was not compatible with the database version
//         in the other files in the DUMPFILE clause.
// *Action: Verify all the files in the DUMPFILE clause are from
//          the same unload operation.
02360, 00000, "fatal error during data export/import initialization\n"
// *Cause: An unexpected error occurred during initialization for data 
//         export/import.
// *Action: Contact Oracle Support Services.
02361, 00000, "error while attempting to allocate %d bytes of memory\n"
// *Cause: An error occurred while trying to allocate memory.  This is likely
//         caused by insufficient memory.
// *Action: Reconnect to the instance and retry the operation.
02362, 00000, "error closing file: %s\n"
// *Cause: An attempt to close the specified file for data export/import failed.
// *Action: Review the error message.  Resolve the problem and retry the 
//          the operation.  Contact Oracle Support Services if
//          the problem cannot be resolved.
02363, 00000, "error reading from file: %s\n"
// *Cause: An attempt to read from the specified file for data export/import 
//         failed.
// *Action: Review the error message.  Resolve the problem and retry the 
//          the operation.  Contact Oracle Support Services if
//          the problem cannot be resolved.
02364, 00000, "error writing to file: %s\n"
// *Cause: An attempt to write to the specified file for data export/import 
//         failed.
// *Action: Review the error message.  Resolve the problem and retry the 
//          the operation.  Contact Oracle Support Services if
/          the problem cannot be resolved.
02365, 00000, "error seeking in file: %s\n"
// *Cause: An attempt to seek to the specified position in file failed.
// *Action: Review the error message.  Resolve the problem and retry the 
//          the operation.  Contact Oracle Support Services if
/          the problem cannot be resolved.
02366, 00000, "The following index(es) on table %s were processed:"
// *Cause: The table had some indexes which were loaded if there were no errors.
// *Action: none.
02367, 00000, "read ended but had expected more data from file %s\n"
// *Cause: A truncated or incomplete file was used for the load operation.
// *Action: Verify unload operation completed successfully and that the
//          files had not been accidentally truncated.
02368, 00000, "the following file is not valid for this load operation\n"
// *Cause: A file could not be used for this load.
//         See the following message for more information.
// *Action: Verify all the files in the DUMPFILE clause are from
//          the same unload operation and that the unload was successful.
02369, 00000, "internal number in header in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because the
//         internal number in the header was not valid.
// *Action: If the dump files were transferred over, verify the
//          transfer operation was done correctly.
02370, 00000, "internal metadata in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because the
//         internal metadata stored in this file does not match the metadata
//         stored in the first file piece set.
// *Action: Verify all the files in the DUMPFILE clause are from
//          the same unload operation.
02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path"
// *Cause: The loader being used is incompatible with this version of the 
// kernel.
// *Action: Upgrade your loader to at least the specified version or use the 
//       conventional path.
02372, 00000, "data for row: %*.*s \n"
// *Cause: A conversion error occurred while loading data into a table.  The
//         message shows values for the field in the row that had 
//         the conversion error.
// *Action: None.  This is only an informational message.
02373, 00000, "Error parsing insert statement for table %s."
// *Cause: self-evident.
// *Action: Check the error given below this one.
02374, 00000, "conversion error loading table %*.*s.%*.*s"
// *Cause: A row could not be loaded into the table because there was a
//         conversion error for one or more columns in a row.
// *Action: See the message that follows for more information about the row
//          that could not be loaded.  To avoid this error, make sure the
//          definition of the table being imported matches the definition of
//          the table being exported.
02375, 0, "conversion error loading table %*.*s.%*.*s partition %*.*s"
// *Cause: A row could not be loaded into the table because there was a
//         conversion error for one or more columns in a row.
// *Action: See the message that follows for more information about the row
//          that could not be loaded.  To avoid this error, make sure the
//          definition of the table being imported matches the definition of
//          the table being exported.
/
/        2376 - 2399 Resource limit errors
/
02376, 00000, "invalid or redundant resource"
//  *Cause:  a create, or alter profile command which names a resource not
// yet defined, or try to specify same resource twice.
//  *Action: define resource first
02377, 00000, "invalid resource limit"
//  *Cause:  specifying limit of 0
//  *Action: specify limit > 0
02378, 00000, "duplicate resource name %s"
//  *Cause:
//  *Action:
02379, 00000, "profile %s already exists"
//  *Cause:  Try to create a profile which already exist
//  *Action:
02380, 00000, "profile %s does not exist"
//  *Cause:  Try to assign a user to a non-existant profile
//  *Action:
02381, 00000, "cannot drop PUBLIC_DEFAULT profile"
//  *Cause:  Try to drop PUBLIC_DEFAULT profile
//  *Action:
02382, 00000, "profile %s has users assigned, cannot drop without CASCADE"
//  *Cause:
//  *Action:
02383, 00000, "illegal cost factor"
//  *Cause:  Negative or UNLIMITED cost for this resourc
//  *Action:
02390, 00000, "exceeded COMPOSITE_LIMIT, you are being logged off"
//  *Cause:
//  *Action:
02391, 00000, "exceeded simultaneous SESSIONS_PER_USER limit"
//  *Cause: An attempt was made to exceed the maximum number of
//          concurrent sessions allowed by the SESSION_PER_USER clause
//          of the user profile.
//  *Action: End one or more concurrent sessions or ask the database
//           administrator to increase the SESSION_PER_USER limit of
//           the user profile.
02392, 00000, "exceeded session limit on CPU usage, you are being logged off"
//  *Cause:
//  *Action:
02393, 00000, "exceeded call limit on CPU usage"
//  *Cause:
//  *Action:
02394, 00000, "exceeded session limit on IO usage, you are being logged off"
//  *Cause:
//  *Action:
02395, 00000, "exceeded call limit on IO usage"
//  *Cause:
//  *Action:
02396, 00000, "exceeded maximum idle time, please connect again"
//  *Cause:  as stated
//  *Action:
02397, 00000, "exceeded PRIVATE_SGA limit, you are being logged off"
//  *Cause:  Only when using TP monitor
//  *Action: expand limit
02398, 00000, "exceeded procedure space usage"
//  *Cause:  Stored procedured used up too much space in SYSTEM Tablespace
//  *Action: Use less stored procedure
02399, 00000, "exceeded maximum connect time, you are being logged off"
//  *Cause:  As stated
//  *Action:
/
/ 2400 - 2479 EXPLAIN facility errors
/
02400, 00000, "explain plan output buffer size limit exceeded"
//  *Cause: Internally this error is raised and caught to handle cases where
//    the plan output exceeds te buffer size. The output is truncated in
//    cases.
//  *Action: This error should never be seen externally.
02401, 00000, "cannot EXPLAIN view owned by another user"
//  *Cause: The view specified in the SQL statement belongs to another user
//    and cannot be explained.
//  *Action: Create a view with the same definition that belongs to
//     current user.
02402, 00000, "PLAN_TABLE not found"
//  *Cause: The table used by EXPLAIN to store row source information does
//    not exist in the current schema.
//  *Action: Create a plan table in the current schema or use the INTO clause
//     of the statement to put the results of the explain command in an
//     existing plan table.
02403, 00000, "plan table does not have correct format"
//   *Cause: The explicit plan table does not have the appropriate field
//     definitions.
//   *Action: Redefine the plan table to have the appropriate field definitions.
02404, 00000, "specified plan table not found"
//   *Cause: The specified plan table does cannot be found.
//   *Action: Create the specified plan table or use an existing plan table.
02405, 00000, "invalid sql plan object provided"
//   *Cause:  The user provided a NULL, empty, or malformed object of type
//            SQL_PLAN_TABLE_TYPE
//   *Action: Provide a new, properly formed object to the function
/
/        2420 - 2429 Schema errors
/
02420, 00000, "missing schema authorization clause"
// *Cause: the AUTHORIZATION clause is missing from a create schema
//         statement.
// *Action: Preceed the schema authorization identifier with the 
//          AUTHORIZATION keyword.
02421, 00000, "missing or invalid schema authorization identifier"
// *Cause: the schema name is missing or is incorrect in an authorization 
//         clause of a create schema statement.
// *Action: If the name is present, it must be the same as the current
//          schema.
02422, 00000, "missing or invalid schema element"
// *Cause: A statement other than a create table, create view, or grant
//         privilege appears in a create schema statement.
// *Action: Self-evident.
02423, 00000, "schema name does not match schema authorization identifier"
// *Cause: a table definition with a schema name prepended to the table
//         name does not match the schema name provided in the authorization
//         clause of a create schema statement.
// *Action: make sure the schema names match.
02424, 00000, "potential circular view references or unknown referenced tables"
// *Cause: the create schema statement contains views that depend on other
//         views in the containing create schema statement or they contain
//         references to unknown tables.
// *Action: create the dependent views in a separate create schema statement 
//          and make sure all referenced tables are either defined in the
//          create schema statement or exist outside the statement.
02425, 00000, "create table failed"
// *Cause: a create table statement failed in the create schema statement.
// *Action: the cause for failure will be presented below this error message.
//          Follow appropriate action(s) as suggested by the subsequent error
//          message.
02426, 00000, "privilege grant failed"
// *Cause: a grant privilege statement failed inthe create schema statement.
// *Action: the cause for failure will be presented below this error message.
//          Follow appropriate action(s) as suggested by the subsequent error
//          message.
02427, 00000, "create view failed"
// *Cause: a create view statement failed in the create schema statement.
// *Action: the cause for failure will be presented below this error message.
//          Follow appropriate action(s) as suggested by the subsequent error
//          message.
02428, 00000, "could not add foreign key reference"
// *Cause: could not add a foreign key reference because of error in 
//         declaration. Either referenced table does not exist or
//         table does not have an unique key.
// *Action: make sure referenced table exists and/or has unique key
02429, 00000, "cannot drop index used for enforcement of unique/primary key"
// *Cause: user attempted to drop an index that is being used as the 
//         enforcement mechanism for unique or primary key.
// *Action: drop the constraint instead of the index.
/
/   2430 -    Enable/Disable Constraint Error Messages - continued
/
02430, 00000, "cannot enable constraint (%s) - no such constraint"
// *Cause: the named constraint does not exist for this table.
// *Action: Obvious
02431, 00000, "cannot disable constraint (%s) - no such constraint"
// *Cause: the named constraint does not exist for this table.
// *Action: Obvious
02432, 00000, "cannot enable primary key - primary key not defined for table"
// *Cause: Attempted to enable a primary key that is not defined for the table.
// *Action: Need to add a primary key definition for the table.
02433, 00000, "cannot disable primary key - primary key not defined for table"
// *Cause: Attempted to disable a primary key tht is not defined for the 
// table.
// *Action: None
02434, 00000, "cannot enable unique(%s) - unique key not defined for table"
// *Cause: attempted to enable a unique key that is not defined for the table.
// *Action: None
02435, 00000, "cannot disable unique(%s) - unique key not defined for table"
// *Cause: attempted to disable a unique key that is not deined for the table.
// *Action: None
02436, 00000, "date or system variable wrongly specified in CHECK constraint"
// *Cause: An attempt was made to use a date constant or system variable,
//         such as USER, in a check constraint that was not completely
//         specified in a CREATE TABLE or ALTER TABLE statement.  For 
//         example, a date was specified without the century.
// *Action: Completely specify the date constant or system variable.
//         Setting the event 10149 allows constraints like "a1 > '10-MAY-96'",
//         which a bug permitted to be created before version 8.
02437, 00000, "cannot validate (%s.%s) - primary key violated"
// *Cause: attempted to validate a primary key with duplicate values or null
//         values.
// *Action: remove the duplicates and null values before enabling a primary 
//      key.
02438, 00000, "Column check constraint cannot reference other columns"
// *Cause: attempted to define a column check constraint that references
//         another column.
// *Action: define it as a table check constriant.
02439, 00000, "Unique index on a deferrable constraint is not allowed"
// *Cause: attempted to enable a deferrable primary key/unique constraint 
//         that has an existing unique index on the constraint columns.
// *Action: Drop the index on the constraint columns or make the constraint
//          not deferrable.
02440, 00000, "Create as select with referential constraints not allowed"
// *Cause:  create table foo (... ref. con. ...) as select ...;
// *Action: Create the table as select, then alter the table to add the
//          constraints afterwards.
02441, 00000, "Cannot drop nonexistent primary key"
// *Cause: alter table drop primary key - primary key does not exist.
// *Action: None
02442, 00000, "Cannot drop nonexistent unique key"
// *Cause: alter table drop unique (<col list>) - unique specification
//         does not exist.
// *Action: make sure column list for unique constraint is correct.
02443, 00000, "Cannot drop constraint  - nonexistent constraint"
// *Cause: alter table drop constraint <constraint_name>
// *Action: make sure you supply correct constraint name.
02444, 00000, "Cannot resolve referenced object in referential constraints"
// *Cause: attempted to define foreign key referencing an object which
//         cannot be resolved to a base table reference
// *Action: referential constraints can only be defined on objects which
//          can be resolve to base table reference
02445, 00000, "Exceptions table not found"
// *Cause: the explicity or implicity declared exceptions table does not
//         exist.
// *Action: Create the table then issue the enable command again.
02446, 00000, "CREATE TABLE ... AS SELECT failed - check constraint violated"
// *Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement
//         when some rows violated one or more CHECK constraints.
// *Action: Do not select rows that violate constraints.
02447, 00000, "cannot defer a constraint that is not deferrable"
// *Cause: An attempt was made to defer a nondeferrable constraint
// *Action: Drop the constraint and create a new one that is deferrable
02448, 00000, "constraint does not exist"
// *Cause: The named constraint does not exist
// *Action: Stop trying to do something with a nonexistant constraint
02449, 00000, "unique/primary keys in table referenced by foreign keys"
// *Cause: An attempt was made to drop a table with unique or 
//         primary keys referenced by foreign keys in another table.
// *Action: Before performing the above operations the table, drop the 
//          foreign key constraints in other tables. You can see what 
//          constraints are referencing a table by issuing the following 
//          command:
//          SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
/
/        2450 - 2475 Parse and execution errors for hashed clusters
/
02450, 00000, "Invalid hash option - missing keyword IS"
// *Cause:  Missing IS keyword.
// *Action: Specify HASH IS option.
02451, 00000, "duplicate HASHKEYS specification"
// *Cause:  The HASHKEYS option is specified more than once.
// *Action: Only specify the HASHKEYS option once.
02452, 00000, "invalid HASHKEYS option value"
// *Cause:  The specified HASHKEYS option must be an integer value.
// *Action: Specify an appropriate value.
02453, 00000, "duplicate HASH IS specification"
// *Cause:  The HASH IS option is specified more than once.
// *Action: only specify the HASH IS option once.
02454, 00000, "Number of hash keys per block (%s) exceeds maximum of %s"
// *Cause:  The SIZE argument is too small.
// *Action: Increase the SIZE argument.
02455, 00000, "The number of cluster key column must be 1"
// *Cause:  When specifing the HASH IS option, the number of key columns
//          must be 1.
// *Action: Either do not specify the HASH IS option or reduce the number
//          of key columns.
02456, 00000, "The HASH IS column specification must be NUMBER(*,0)"
// *Cause:  The column specification must specify an integer.
// *Action: Specify the column definition as type NUMBER(precision, 0).
02457, 00000, "The HASH IS option must specify a valid column"
// *Cause:  The HASH IS column name is not specified in the cluster
//           definition.
// *Action: Specify a valid column name.
02458, 00000, "HASHKEYS must be specified for a HASH CLUSTER"
// *Cause:  The HASHKEYS option must be specified when creating a HASH CLUSTER.
// *Action:  Specify the HASHKEYS option.
02459, 00000, "Hashkey value must be a positive integer"
// *Cause:  The value of the hash key was not a positive number.
// *Action: Specify a positive integer.
02460, 00000, "Inappropriate index operation on a hash cluster"
// *Cause:  An attempt to create a cluster index was issued on a hash cluster.
// *Action: Do not attempt to create such an index. 
02461, 00000, "Inappropriate use of the INDEX option"
// *Cause:  This option is only valid for non hash clusters.
// *Action: Do not specify this option.
02462, 00000, "Duplicate INDEX option specified"
// *Cause:  The INDEX option is specified more than once.
// *Action: Only specify the INDEX option once.
02463, 00000, "Duplicate HASH IS option specified"
// *Cause:  The HASH IS option is specified more than once.
// *Action: Only specify the HASH IS option once.
02464, 00000, "Cluster definition can not be both HASH and INDEX"
// *Cause:  The cluster can either be a hash or indexed cluster - not both.
// *Action: Remove either the HASH IS or INDEX options.
02465, 00000, "Inappropriate use of the HASH IS option"
// *Cause:  This option is only valid for clusters
// *Action: Do not specify this option
02466, 00000, "The SIZE and INITRANS options cannot be altered for HASH CLUSTERS." 
// *Cause:  An attempt was made to change the SIZE and INITRANS options after 
//          the hash cluster  was created. 
// *Action: Do not specify this option. 
02467, 00000, "Column referenced in expression not found in cluster definition"
// *Cause:  A column in the hash is expression was not present in cluster
//          definition.
// *Action: Recreate the cluster and correct the error in hash expression.
02468, 00000, "Constant or system variable wrongly specified in expression"
// *Cause:  A constant or system variable was specified in the hash expression.
// *Action: Recreate the cluster and correct the error in hash expression.
02469, 00000, "Hash expression does not return an Oracle Number."
// *Cause: Result of evaluating hash expression is not an Oracle Number.
// *Action: Recreate the cluster and correct the error in hash expression.
02470, 00000, "TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression."
// *Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions.
// *Action: Recreate the cluster and correct the error in hash expression.
02471, 00000, "SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion."
// *Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s.
// *Action: Recreate the cluster and remove the offending keywords.
02472, 00000, "PL/SQL functions not allowed in hash expressions"
// *Cause: A PL/SQL function was used in the hash expression.
// *Action: Recreate the cluster and remove the PL/SQL function.
02473, 00000, "Error while evaluating the cluster's hash expression."
// *Cause: An error occurred while evaluating the clusters hash expression.
// *Action: Correct the query and retry.
02474, 00000, "Fixed hash area extents used (%s) exceeds maximum allowed (%s)"
// *Cause:  The number of extents required for creating the fixed hash
//          area exceeds the maximum number allowed.
// *Action: Reduce the number of extents required by increasing the extent
//          allocation sizes within the STORAGE clause.
02475, 00000, "maximum cluster chain block count of %s has been exceeded"
// *Cause:  The number of blocks in a cluster chain exceeds the maximum
//          number allowed.
// *Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider
//          suitability of cluster key.
/
/        2476 - 2479 Reserved for Parallel Direct Loader Errors
02476, 00000, "can not create index due to parallel direct load on table"
// *Cause:  A parallel direct load is occurring to the specified table.
// *Action: Retry statement after load is complete.
02477, 00000, "can not perform parallel direct load on object %s"
// *Cause:  A parallel direct load is not possible because an index is
//          is being created on the table.
// *Action: Retry load after index creation is complete.
02478, 00000, "merge into base segment would overflow MAXEXTENTS limit"
// *Cause:  Merge of temporary segment into base segment failed because
//          MAXEXTENTS was larger than the total in the temp and base segments
// *Action: Use a larger value for MAXEXTENTS on the base segment or make the
//          extents in the temporary segments larger
02479, 00000, "error while translating file name for parallel load"
// *Cause:  An invalid file name was specified to load data into.
// *Action: Specify a valid database file.
/
/ 2480 - 2489 Trace facility errors
/
02481, 00000, "Too many processes specified for events (max %s)"
// *Cause: Too many processes specified than allowed per event.
// *Action: Enter fewer processes by using ranges or wildcards if possible.
02482, 00000, "Syntax error in event specification (%s)"
// *Cause: Illegal event string
// *Action: Enter a legal event string
02483, 00000, "Syntax error in process specification (%s)"
// *Cause: Illegal process string
// *Action: Enter a legal process string
02484, 00000, "Invalid _trace_buffers parameter specification (%s)"
// *Cause:  Bad process or size in _trace_buffers INIT.ORA parameter.
// *Action:
02485, 00000, "Invalid _trace_options parameter specification (%s)"
// *Cause:  Bad syntax for _trace_options INIT.ORA parameter.
// *Action:
02486, 00000, "Error in writing trace file %s"
// *Cause:  Error occurred in creating/writing the file.
// *Action: Check file name and make sure it is constructed properly.
//          Also, check permissions for directories.
02487, 00000, "Error in converting trace data"
// *Cause: Incompatible binary trace data was specified.
// *Action: Check the format of the input data.
02488, 00000, "Error encountered when accessing file [%s] for trace conversion"
// *Cause: An attempt was made to open or access the trace file during 
//         a trace conversion.
// *Action: Check the permissions for both input and output files.
//          Also, check the file compatibility for the trace conversion.
/
/ 2490 - 2499 Reserved for Resizeable Datafiles
/
02490, 00000, "missing required file size in RESIZE clause" 
// *Cause:  No value was specified for the RESIZE clause.
// *Action: Use correct syntax.
02491, 00000, "missing required keyword ON or OFF in AUTOEXTEND clause"
// *Cause:  The keyword ON or OFF was not specified for the AUTOEXTEND clause.
// *Action: Use correct syntax.
02492, 00000, "missing required file block increment size in NEXT clause" 
// *Cause: No value was specified for the NEXT clause.
// *Action: Use correct syntax.
02493, 00000, "invalid file increment size in NEXT clause"
// *Cause:  A non-integer value was used for the NEXT clause of the DATAFILE
//          list.
// *Action: Use correct syntax.
02494, 00000, "invalid or missing maximum file size in MAXSIZE clause"
// *Cause: UNLIMITED was not specified, or an invalid integer value was
//         specified, for the MAXSIZE clause in the DATAFILE file list.
//         The MAXSIZE value cannot be smaller than the SIZE value.
// *Action: Use correct syntax.
02495, 00000, "cannot resize file %s, tablespace %s is read only"
// *Cause: An attempt was made to resize a data file in a tablespace that
//         is read only.
// *Action: Change the tablespace to read/write and retry the resize operation.
/
/ 2500 - 2699 Reserved for CTOS-specific errors
/
/ 2700 - 2899 Reserved for UNIX two-task errors
/
02700, 00000, "osnoraenv: error translating ORACLE_SID"
// *Cause:   Two-task driver could not find the value of ORACLE_SID in the
//     environment.
// *Action:  Make sure that the ORACLE_SID environment variable has been
//     properly set and exported.
02701, 00000, "osnoraenv: error translating oracle image name"
// *Cause:   ORACLE_HOME environment variable not set.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//     properly set and exported.
02702, 00000, "osnoraenv: error translating orapop image name"
// *Cause:   ORACLE_HOME environment variable not set.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//     properly set and exported.
02703, 00000, "osnpopipe: pipe creation failed"
// *Cause:   The pipe driver failed to create pipes for communications with
//     the orapop process.
// *Action:  You have probably exceeded the maximum number of open file
//     descriptors per user or the system file table is full.  Note the 
//     operating system error code and contact your system administrator.
02704, 00000, "osndopop: fork failed"
// *Cause:   The two-task driver could not fork orapop.
// *Action:  Verify that there are enough system resources to support another
//     process.  The user or system process limit may have been exceeded, or
//     the amount of free memory or swap space may be temporarily insufficient.
02705, 00000, "osnpol: polling of communication channel failed"
// *Cause:   The pipe driver failed while polling the communications channel.
// *Action:  Contact your customer support representative.
02706, 00000, "osnshs: host name too long"
// *Cause:   The length of your host-string specified by the TWO_TASK 
//     environment variable exceeds the ORACLE system-imposed limit.
// *Action:  Contact your customer support representative.
02707, 00000, "osnacx: cannot allocate context area"
// *Cause:   The invoked Unix two-task driver could not allocate heap space for
//     the context area.
// *Action:  Contact your customer support representative.
02708, 00000, "osnrntab: connect to host failed, unknown ORACLE_SID"
// *Cause:   The invoked Unix two-task driver failed to find an entry in
//     oratab for the sid you supplied.
// *Action:  First, check whether you have read access to oratab, and
//     see if the desired sid is there.  Add an entry to oratab
//     for the desired sid, if necessary.
02709, 00000, "osnpop: pipe creation failed"
// *Cause:   The pipe driver failed to create pipes for two-task communications
//     with the oracle shadow process.
// *Action:  You have probably exceeded the maximum number of open file
//     descriptors per user or the system file table is full.  Note the 
//     operating system error code and contact your system administrator.
02710, 00000, "osnpop: fork failed"
// *Cause:   The pipe driver could not fork the oracle shadow process.
// *Action:  Verify that there are enough system resources to support another
//     process.  The user or system process limit may have been exceeded, or
//     the amount of free memory or swap space may be temporarily insufficient.
02711, 00000, "osnpvalid: write to validation channel failed"
// *Cause:   The pipe driver failed to write to the orapop process.
// *Action:  Contact your customer support representative.
02712, 00000, "osnpop: malloc failed"
// *Cause:   The pipe driver failed to allocate enough heap space for its 
//     context area buffers.
// *Action:  Contact your customer support representative.
02713, 00000, "osnprd: message receive failure"
// *Cause:   The pipe driver failed to read a message from the communications
//     channel.
// *Action:  Contact your customer support representative.
02714, 00000, "osnpwr: message send failure"
// *Cause:   The pipe driver failed to write a message to the communications
//     channel.
// *Action:  Contact your customer support representative.
02715, 00000, "osnpgetbrkmsg: message from host had incorrect message type"
// *Cause:   The pipe driver received a message having an unrecognizable 
//     message type.
// *Action:  Contact your customer support representative.
02716, 00000, "osnpgetdatmsg: message from host had incorrect message type"
// *Cause:   The Pipe driver received a message having an unrecognizable 
//     message type.
// *Action:  Contact your customer support representative.
02717, 00000, "osnpfs: incorrect number of bytes written"
// *Cause:   The Pipe driver sent a message that was apparently successful,
//     but the number of bytes transmitted did not match the number of
//     bytes furnished to the driver.
// *Action:  Contact your customer support representative.
02718, 00000, "osnprs: reset protocol error"
// *Cause:   The two-task driver could not reset the connection.
// *Action:  Contact your customer support representative.
02719, 00000, "osnfop: fork failed"
// *Cause:   The fast driver could not fork the oracle shadow process.
// *Action:  Verify that there are enough system resources to support another
//     process.  The user or system process limit may have been exceeded, or
//     the amount of free memory or swap space may be temporarily insufficient.
02720, 00000, "osnfop: shmat failed"
// *Cause:   When the fast driver was invoked, processes failed to attach to the
//     shared memory buffer. You probably supplied an illegal shared memory
//     attach address, or the system ran out of data space to accomodate the buffer.
// *Action:  Try invoking the Fast driver later, or use the default attach 
//     address.
02721, 00000, "osnseminit: cannot create semaphore set"
// *Cause:   The Fast driver failed to get a semaphore set.
// *Action:  The system-imposed limit on semaphores or semaphore identifiers
//     may have been exceeded.  Read the returned operating system
//     error code and check with your system administrator.
02722, 00000, "osnpui: cannot send break message to orapop"
// *Cause:   The Pipe driver could not send a break message to orapop.
// *Action:  Contact your customer support representative.
02723, 00000, "osnpui: cannot send break signal"
// *Cause:   The Pipe driver could not send a break message to the ORACLE
//     shadow process.
// *Action:  Contact your customer support representative.
02724, 00000, "osnpbr: cannot send break message to orapop"
// *Cause:   The Pipe driver could not send a break message to orapop.
// *Action:  Contact your customer support representative.
02725, 00000, "osnpbr: cannot send break signal"
// *Cause:   The Pipe driver could not send a break message to the ORACLE
//     shadow process.
// *Action:  Kill system call failed. Check errno and contact customer support.
02726, 00000, "osnpop: access error on oracle executable"
// *Cause:   The Pipe driver could not access the oracle executable.
// *Action:  Check the permissions on the ORACLE executable and each
//     component of the ORACLE_HOME/bin path.
02727, 00000, "osnpop: access error on orapop executable"
// *Cause:   The Pipe driver could not access the orapop executable.
// *Action:  Check the permissions on the orapop executable and each
//     component of the ORACLE_HOME/bin path.
02728, 00000, "osnfop: access error on oracle executable"
// *Cause:   The Fast driver could not access the oracle executable.
// *Action:  Check the permissions on the ORACLE executable and each
//     component of the ORACLE_HOME/bin path.
02729, 00000, "osncon: driver not in osntab"
// *Cause:   The driver you have specified is not supported.
// *Action:  Check with your database administrator which drivers are supported.
02730, 00000, "osnrnf: cannot find user logon directory"
// *Cause:   The driver you have specified could not find your logon directory
//     while searching for your local .sqlnet file.
// *Action:  Set and export the HOME environment variable to identify your
//     home directory.  Check with your system administrator to make sure
//     that your uid and home directory are correct in the /etc/passwd file.
02731, 00000, "osnrnf: malloc of buffer failed"
// *Cause:   The specified driver could not find enough heap space to malloc
//     a buffer.
// *Action:  Contact your customer support representative.
02732, 00000, "osnrnf: cannot find a matching database alias"
// *Cause:   Database alias specified was not identified in either
//     $HOME/.sqlnet or /etc/sqlnet.
// *Action:  Create the alias in a file called .sqlnet in your home directory
//     for personal use or ask your system administrator to create the
//     alias in /etc/sqlnet for system-wide use.
02733, 00000, "osnsnf: database string too long"
// *Cause:   While converting a database alias to a database ID, the resulting
//     database ID string exceeded the ORACLE system-imposed limit.
// *Action:  Contact your customer support representative.
02734, 00000, "osnftt: cannot reset shared memory permission"
// *Cause:   The Fast driver was unable to reset shared memory permissions.
// *Action:  Contact your customer support representative.
02735, 00000, "osnfpm: cannot create shared memory segment"
// *Cause:   The Fast driver failed to create a shared memory segment for 
//     two-task communication.
// *Action:  Check whether the system-imposed limit on shared memory 
//     identifiers has already been reached for your system.
02736, 00000, "osnfpm: illegal default shared memory address"
// *Cause:   The Fast driver failed to establish a default shared memory
//      address.
// *Action:  Contact your customer support representative.
02737, 00000, "osnpcl: cannot tell orapop to exit"
// *Cause:   The Pipe driver failed to send orapop the command to exit.
// *Action:  Contact your customer support representative.
02738, 00000, "osnpwrtbrkmsg: incorrect number of bytes written"
// *Cause:   The pipe driver apparently sent an imcomplete break message.
// *Action:  Contact your customer support representative.
02739, 00000, "osncon: host alias is too long"
// *Cause:   The alias used for a sqlnet host is longer than 161 characters.
// *Action:  Use a shorter alias.
02750, 00000, "osnfsmmap: cannot open shared memory file ?/dbs/ftt_<pid>.dbf"
// *Cause:   The Fast driver failed to create a shared memory file for
//     two-task communication.
// *Action:  Check the permissions on the directory ?/dbs
02751, 00000, "osnfsmmap: cannot map shared memory file"
// *Cause:   The Fast driver failed to map a shared memory file for
//     two-task communication.
// *Action:  Contact your customer support representative.
02752, 00000, "osnfsmmap: illegal shared memory address"
// *Cause:   The Fast driver failed to attach shared memory at the expected
//     location.
// *Action:  Contact your customer support representative.
02753, 00000, "osnfsmmap: cannot close shared memory file"
// *Cause:   The Fast driver cannot close the shared memory file.
// *Action:  Contact your customer support representative.
02754, 00000, "osnfsmmap: cannot change shared memory inheritence"
// *Cause:   The Fast driver could not alter the inheritence attributes
//     of the shared memory.
// *Action:  Contact your customer support representative.
02755, 00000, "osnfsmcre: cannot create chared memory file ?/dbs/ftt_<pid>.dbf"
// *Cause:   The Fast driver failed to create a file for shared memory.
// *Action:  Check the permissions on the directory ?/dbs
02756, 00000, "osnfsmnam: name translation failure"
// *Cause:   The Fast driver encountered an error translating the shared
//     memory filename ?/dbs/ftt_<pid>.dbf.
// *Action:  Contact your customer support representative.
02757, 00000, "osnfop: fork_and_bind failed"
// *Cause:   The Fast driver failed to fork a process onto the desired
//     cluster and node number.
// *Action:  Check the desired node number in sercose[0] and cluster ID in
//     sercose[1].  If these seem valid, contact customer support.
/
/        2758 - 2899 Reserved for ORACLE asynchronous I/O.
02758, 00000, "Allocation of internal array failed"
// *Cause:  The package was unable to allocate memory for an array because
//          the system ran out of memory.
// *Action: Either reclaim memory by killing other processes or reboot the
//          machine with more memory.
02759, 00000, "Not enough request descriptors available"
// *Cause:  All of the package's request descriptors are in use performing
//          other requests.
// *Action: Either wait until enough requests are done, or shut the package
//          down and re-initialize it with more request descriptors.
02760, 00000, "Client close of file failed."
// *Cause:  The client was unable to close a file after forking the servers.
// *Action: This is a system problem - contact your System Administrator.
02761, 00000, "File number to be canceled is negative."
// *Cause:  The file number contained with the sfiov structure is less than
//          zero.
// *Action: This may be a programming error. If it is not, contact ORACLE
//          support.
02762, 00000, "file number to be cancelled is greater than the maximum."
// *Cause:  The file number contained with the sfiov structure is greater
//          than the maximum.
// *Action: This may be a programming error. If it is not, contact ORACLE
//          support.
02763, 00000, "Unable to cancel at least one request"
// *Cause:  No requests were found that could be cancelled.
// *Action: This error can occur if all the requests dealing with that file
//          number have already been filled.
02764, 00000, "Invalid package mode"
// *Cause:  The mode of the package can only be parallel or duplex.
// *Action: See sfa.h for the correct values.
02765, 00000, "Invalid maximum number of servers"
// *Cause:  The number of servers given was less than or equal to zero.
// *Action: Use a number greater than zero.
02766, 00000, "Invalid maximum of request descriptors"
// *Cause:  The number of request descriptors was less than or equal to zero.
// *Action: Use a number greater than zero.
02767, 00000, "Less than one request descriptor was allocated per server"
// *Cause:  The package requires that the number of request descriptors
//          be greater than or equal to the number of servers used.
// *Action: Use a higher number
02768, 00000, "Maximum number of files is invalid"
// *Cause:  The maximum number of files to be used by the package was less
//          than or equal to zero.
// *Action: Use a positive number.
02769, 00000, "Setting of handler for SIGTERM failed"
// *Cause:  The package was unable to set up handling by the server for the
//          termination signal. This is an internal error.
// *Action: Contact ORACLE support.
02770, 00000, "Total number of blocks is invalid"
// *Cause:  The total number of blocks to be allocated for use by the package
//          was not greater than zero.
// *Action: Use a positive number.
02771, 00000, "Illegal request time out value"
// *Cause:  The number was not a positive number.
// *Action: Use a positive number.
02772, 00000, "Invalid maximum server idle time"
// *Cause:  The time given was not a positive number.
// *Action: Use a positive number.
02773, 00000, "Invalid maximum client wait time"
// *Cause:  The time given was not a positive number.
// *Action: Use a positive number.
02774, 00000, "Invalid request list latch time out value"
// *Cause:  The time given was not a positive number.
// *Action: Use a positive number.
02775, 00000, "Invalid request done signal"
// *Cause:  The signal number was not a positive number.
// *Action: Use a positive number.
02776, 00000, "Value for request done signal exceeds maximum"
// *Cause:  The value sent to the package for use as the "request done"
//          signal exceeds the maximum allowed by the operating system.
// *Action: 
02777, 00000, "Stat failed on log directory"
// *Cause:  The package was unable to get information about the directory
//          in which the log files are to reside.
// *Action: Check the permissions on the directory or use a different
//          directory name.
02778, 00000, "Name given for the log directory is invalid"
// *Cause:  The name given for the directory in which the logs are to be kept
//          does not correspond to a directory.
// *Action: Use a different name.
02779, 00000, "Stat failed on core dump directory"
// *Cause:  The package was unable to get information about the directory
//          into which the servers are to dump core in the event of an
//          exception.
// *Action: Check the permissions on the directory or use a different
//          directory name.
02780, 00000, "Name given for the core dump directory is invalid"
// *Cause:  The name given for the directory in which the server processes
//          are to dump core in the event of an exception does not correspond
//          to a directory.
// *Action: Use a different name.
02781, 00000, "Invalid value given for the timing wanted flag"
// *Cause:  The value given was not TRUE or FALSE.
// *Action: 
02782, 00000, "Both read and write functions were not specified"
// *Cause:  To ensure that the functions act symmetrically, pointers to both
//          the read and write functions must be given.
// *Action: Either specify both functions or specify neither. The package
//          will supply its own functions.
02783, 00000, "Both post and wait functions were not specified"
// *Cause:  To ensure that the functions act symmetrically, pointers to both
//          the posting and waiting functions must be given.
// *Action: Either specify both functions or specify neither. The package
//          will supply its own functions.
02784, 00000, "Invalid shared memory ID specified"
// *Cause:  The ID of the segment specified for use as the shared buffer
//          region was invalid.
// *Action: Use a different ID, or let the package specify its own.
02785, 00000, "Invalid shared memory buffer size"
// *Cause:  The size given for the shared memory segment to be used as the
//          shared buffer region was less than or equal to zero.
// *Action: Use a positive number.
02786, 00000, "Size needed for shared region is greater than segment size"
// *Cause:  The size of the shared segment that was specified for the
//          shared buffer region is less than the number of bytes required.
//          The first field of the "additional information" field is the
//          size needed. The second is the size of the segment.
// *Action: Use a larger size segment or let the package allocate its own.
02787, 00000, "Unable to allocate memory for segment list"
// *Cause:  The package cannot allocate memory for an internal segment list
//          because the system has run out of memory.
//          The "additional information" field is the amount of memory
//          that the package attempted to allocate.
// *Action: 
02788, 00000, "Unable to find kernel process pointer in async process array"
// *Cause:  Internal error - Contact ORACLE support.
// *Action: 
02789, 00000, "Maximum number of files reached"
// *Cause:  The maximum number of files that can be used for asynchronous
//          I/O has been reached.
// *Action: Shut down the servers and re-initialize the package with a higher
//          number.
02790, 00000, "File name is too long"
// *Cause:  The length of the name of a file that is being opened for
//          asynchronous I/O is longer than the maximum.
//          The "additional information" field is the maximum length.
// *Action: Use a shorter name.
02791, 00000, "Unable to open file for use with asynchronous I/O"
// *Cause:  The package could not open file for some reason.
// *Action: Check the file name.
02792, 00000, "Unable to fstat() a file being used for asynchronous I/O."
// *Cause:  The fstat(2) call on a file being used for asynchronous I/O
//          failed.
// *Action: Check the file name.
02793, 00000, "Close of asynchronous I/O failed."
// *Cause:  The client was unable to close a file being used for asynchronous
//          I/O.
// *Action: Contact ORACLE support - this should not happen.
02794, 00000, "Client unable to get key for shared memory"
// *Cause:  The client was unable to get a key so that it obtain shared
//          memory for use with shared memory.
// *Action: Contact ORACLE support - this is an internal error.
02795, 00000, "Request list is empty"
// *Cause:  The client was signalled by a server that it was done with a
//          request but the "done" list was empty.
// *Action: Internal error - contact ORACLE support.
02796, 00000, "Done request is not in correct state"
// *Cause:  A request is not in the right state.
// *Action: Internal error - contact ORACLE support.
02797, 00000, "No requests available"
// *Cause:  No free request descriptors are available.
// *Action: Wait until some requests are filled and then retry the request,
//          or shutdown the servers and initialize the package with a
//          higher number of requests.
02798, 00000, "Invalid number of requests"
// *Cause:  The number of operations sent to either sfard() or sfawrite()
//          is less than zero.
// *Action: This is a user programming error.
02799, 00000, "Unable to arm signal handler"
// *Cause:  The arming of a signal handler for the "done" signal failed.
// *Action: Internal error - contact ORACLE support.
02800, 00000, "Requests timed out"
// *Cause:  Some of the requests for asynchronous input or output were not
//          serviced in the required amount of time.
// *Action: If the load on the system is high, it is possible that the
//          timeout limit is too low. Reset it with sfainit(). If the server
//          processes are dying due to unexpected signals, this is an
//          internal error, and ORACLE support should be contacted.
02801, 00000, "Operations timed out"
// *Cause:  Some asynchronous operations timed out in kernel mode.
// *Action: Internal error - contact ORACLE support.
02802, 00000, "No idle servers available in parallel mode"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02803, 00000, "Retrieval of current time failed"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02804, 00000, "Allocation of memory failed for log file name"
// *Cause:  The client was unable to allocated a buffer for the name of the
//          log file.
// *Action: Contact your System Administrator.
02805, 00000, "Unable to set handler for SIGTPA"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02806, 00000, "Unable to set handler for SIGALRM"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02807, 00000, "Allocation of memory for I/O vectors failed."
// *Cause:  The client was unable to allocate memory for the array of I/O
//          vectors that the servers are to use.
// *Action: Contact your System Administrator.
02808, 00000, "Allocation of memory of open files array failed."
// *Cause:  The client was unable to allocate memory for an array of flags
//          that the servers are to use.
// *Action: Contact your System Administrator.
02809, 00000, "Jump buffer not valid"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02810, 00000, "Unable to make temporary file name for memory mapped file"
// *Cause:  
// *Action: 
02811, 00000, "Unable to attach shared memory segment"
// *Cause:  
// *Action: 
02812, 00000, "Bad attach address"
// *Cause:  
// *Action: 
02813, 00000, "Unable to make temporary file name in order to get key"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02814, 00000, "Unable to get shared memory"
// *Cause:  Shmget(2) failed.
// *Action: Check the UNIX number. If you are unsure about what it means,
//          contact ORACLE customer support.
02815, 00000, "Unable to attach shared memory"
// *Cause:  Shmat(2) failed.
// *Action: Check the UNIX number. If you are unsure about what it means,
//          contact ORACLE customer support.
02816, 00000, "Unable to kill a process"
// *Cause:  A server did not die after being sent a kill signal.
// *Action: The process may be a runaway - contact ORACLE customer support.
02817, 00000, "Read failed"
// *Cause:  A server could not read a requested amount of data.
// *Action: Check the call to sfard(). An incorrect file descriptor may have
//          been sent to sfard().
//          The number in the "additional information" field is the starting
//          block number of the data segment being read in.
02818, 00000, "Less than the number of blocks requested was read in"
// *Cause:  A server could not read in the request amount of data.
//          The first number in the "additional information" field is the
//          block number being read in. The second is the actual number
//          of bytes that was read in.
// *Action: This is a programming error.
02819, 00000, "Write failed"
// *Cause:  A server was unable to perform a write.
//          The number in the "additional information" field is the starting
//          block number of the data segment being written out.
//          The first number in the "additional information" field is the
//          block number being written out. The second is the actual number
//          of bytes that was written out. The disk may have filled up.
// *Action: Check the UNIX error number.
02820, 00000, "Unable to write the requested number of blocks"
// *Cause:  A server could not write the requested amount of data out to
//          disk. The disk may have run out of space.
// *Action: Check the UNIX error number.
02821, 00000, "Unable to read the requested number of blocks."
// *Cause:  A server could not read the number of blocks that was requested.
//          The end of the file may have been read.
// *Action: Check the file on disk.
02822, 00000, "Invalid block offset"
// *Cause:  A server was unable to seek to the designated block.
// *Action: Check the UNIX error number.
02823, 00000, "Buffer is not aligned."
// *Cause:  The buffer on which an I/O is being done is not on the correct
//          boundary.
// *Action: Check the calling program.
02824, 00000, "Request free list is empty"
// *Cause:  The list from which the package allocates request descriptors is
//          empty because all of the descriptors is in use.
// *Action: Wait until some become free, or initialize the package with
//          a higher number of request descriptors.
02825, 00000, "Request on free list was not free"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02826, 00000, "Illegal block size"
// *Cause:  A negative number was given for the I/O block size to be used by
//          the asynchronous I/O package.
// *Action: This is a programming error - use either a positive number or
//          zero to get the default value.
02827, 00000, "Invalid file number"
// *Cause:  The file number upon which an operation is to done is either
//          less than zero or greater than the maximum number of files than
//          can be open.
// *Action: This is a programming error. Since the calling program should
//          not touch this number, this is a programming error.
02828, 00000, "Segment free list is empty"
// *Cause:  No segments are available to allocated.
// *Action: Free some segments or shut down the package and re-initialize it
//          with a higher number of segments.
02829, 00000, "No segment of the proper size is available"
// *Cause:  No segment of the proper size is ready for use by the caller.
// *Action: Free some segments and try again.
02830, 00000, "Segment could not be split - no free segments available"
// *Cause:  A segment that is larger than that desired could not be split
//          because no free segment was available.
// *Action: Free some segments and try again.
02831, 00000, "Segment deallocation failed - empty segment list"
// *Cause:  The caller attempted to deallocate a segment but the "in use"
//          list was empty. This is a programming error.
// *Action: Check the calling program.
02832, 00000, "Segment deallocation failed - segment not on list"
// *Cause:  The caller attempted to deallocate a segment that was not on the
//          "in use" list. This is a programming error.
// *Action: Check the calling program.
02833, 00000, "Server was unable to close file"
// *Cause:  A server was unable to close a file being used for asynchronous
//          I/O.
// *Action: See the UNIX error number for more information.
02834, 00000, "Server unable to open file"
// *Cause:  The server was unable to open a file for use with asynchronous
//          I/O.
// *Action: Check the UNIX error number for more information.
02835, 00000, "Server unable to send signal to client"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02836, 00000, "Unable to create temporary key file"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02837, 00000, "Unable to unlink temporary file"
// *Cause:  Internal error.
// *Action: Contact ORACLE support.
02838, 00000, "Unable to arm signal handler for the alarm signal"
// *Cause:  The arming of a signal handler for the alarmsignal failed.
// *Action: Internal error - contact ORACLE support.
02839, 00000, "Sync of blocks to disk failed."
// *Cause:  The server was unable to flush its writes out to disk.
// *Action: Check the UNIX error number.
02840, 00000, "Open of log file by client failed"
// *Cause:  The client process was unable to open its log file.
// *Action: Check the UNIX error number for more information.
02841, 00000, "Server died on start up"
// *Cause:  A server exited during its initialization process.
// *Action: Check the servers' logs for more information.
02842, 00000, "Client unable to fork a server"
// *Cause:  The client could not spawn a server. A possible reason is that
//          the operating system has reached its limit on the number of
//          processes that it can spawn.
// *Action: Either reduce the number of servers that are to be used,
//          or reconfigure the operating system so that it can handle more
//          processes.
02843, 00000, "Invalid value for kernel flag"
// *Cause:  An illegal value was given for the kernel flag in the information
//          structure. Only TRUE and FALSE are permitted.
// *Action: This is a programming error - check the calling routine.
02844, 00000, "Invalid value for the leave open flag"
// *Cause:  A value was given for the flag that determines whether a file is
//          to be left open after the client checks it to see if the servers
//          can use it. Only TRUE and FALSE are supported.
// *Action: This is a programming error - check the calling routine.
02845, 00000, "Invalid value for the timing wanted flag"
// *Cause:  A value was given for the flag that indicates that operations are
//          to be timed out. Only TRUE and FALSE are supported.
// *Action: This is a programming error - check the calling routine.
02846, 00000, "Unkillable server"
// *Cause:  A server would not respond to the termination signal.
//          The first number is the number of the server. The second is its
//          UNIX process number.
//          This is an internal problem.
// *Action: This is an operating system problem.
02847, 00000, "Server did not terminate when posted"
// *Cause:  A server did not respond to a posted request to shutdown.
//          The first number is the number of the server. The second is its
//          UNIX process number.
//          This is an internal problem.
// *Action: Contact ORACLE support.
02848, 00000, "Asynchronous I/O package is not running"
// *Cause:  An operation using the asynchronous I/O package was attempted
//          without first initializing the package using sfainit().
// *Action: Call sfainit() before using the package.
02849, 00000, "Read failed because of an error"
// *Cause:  A server could not read the requested amount of data from
//          disk.
// *Action: Check the UNIX error number.
02850, 00000, "File is closed"
// *Cause:  A file upon which an asynchronous I/O operation is to be
//          performed has already been closed by the package.
// *Action: This is a programming error.
02851, 00000, "Request list is empty when it should not be"
// *Cause:  This is an internal problem.
// *Action: Contact ORACLE support.
02852, 00000, "Invalid critical-section time out value"
// *Cause:  The time given was not a positive number.
// *Action: Use a positive number.
02853, 00000, "Invalid server list latch time out value"
// *Cause:  The time given was not a positive number.
// *Action: Use a positive number.
02854, 00000, "Invalid number of request buffers"
// *Cause:  The value given for "db_slave_buffers" in your INIT.ORA file
//          is less than 0.
// *Action: Use a number that is greater than or equal to 0.
002855, 00000, "Number of requests is less than the number of slaves"
// *Cause: The value given for "db_slave_buffers" in your INIT.ORA file
//          is less than the number specified for the number of slaves,
//          "db_slaves."
// *Action: Specify a number that is greater than that given for "db_slaves"
//          Alternatively, specify 0. The kernel will supply the appropriate
//          number.
/        2875 - 2899 Reserved for IBM RS/6000
02875, 00000, "smpini: Unable to get shared memory for PGA"
// *Cause:   Stated in errno.
// *Action:  Resolve the problem.
02876, 00000, "smpini: Unable to attach to shared memory for PGA"
// *Cause:   Stated in errno.
// *Action:  Resolve the problem.
02877, 00000, "smpini: Unable to initialize memory protection"
// *Cause:   The adspcinit program has not been executed.
//  *Action: Execute the adscpinit program as shown in your Installation
//           and Users' Guide.  If the problem persists, try rebooting
//           your computer.
02878, 00000, "sou2o: Variable smpdidini overwritten"
// *Cause:   The variable smpdidini was overwritten, probably by client code.
// *Action:  Verify client code, e.g. Pro*C, for illegal memory access.
//           If the problem occurs outside Single Task operation, contact
//           your customer support representative.
02879, 00000, "sou2o: Could not gain access to protected memory"
//  *Cause:  This is an internal error, note error code in errno.
//  *Action: Report to your customer support representative.  Restarting
//           your application or your computer may cure the problem.
02880, 00000, "smpini: Could not register PGA for protection"
//  *Cause:  This is an internal error, note error code in errno.
//  *Action: Report to your customer support representative.  Restarting
//           your application or your computer may cure the problem.
02881, 00000, "sou2o: Could not revoke access to protected memory"
//  *Cause:  This is an internal error, note error code in errno.
//  *Action: Report to your customer support representative.  Restarting
//           your application or your computer may cure the problem.
02882, 00000, "sou2o: Could not register SGA for protection"
//  *Cause:  This is an internal error, note error code in errno.
//  *Action: Report to your customer support representative.  Restarting
//           your application or your computer may cure the problem.
02899, 00000, "smscre: Cannot create SGA with Extended Shared Memory feature"
//  *Cause:  The environment variable EXTSHM was set before starting oracle.
//  *Action: Unset the environment variable EXTSHM and startup oracle.
/
/        2900 - 2999 Reserved for licensing server errors
/
/ 3000-3099  currently not implemented features
/
03001, 00000, "unimplemented feature"
// *Cause:  This feature is not implemented.
// *Action:  None.
03002, 00000, "operator not implemented"
// *Cause:  This is an internal error.
// *Action:  Contact your customer support representative.
03007, 00000, "obsolete feature"
// *Cause:  User attempted to use a feature which is no longer supported.
// *Action:  None.
03009, 00000, "Incompatible OCI function call"
// *Cause: An incompatible OCI function call was issued for new functionality.
// *Action: Do not use V7 OCI calls for this functionality.


/
/ 3100-3199  two task interface errors
/    some of these can eventually convert to internal ercs
/
03100, 00000, "communication area cannot be allocated; insufficient memory"
// *Cause:
// *Action:
03105, 00000, "internal protocol error"
// *Cause:
// *Action:
03106, 00000, "fatal two-task communication protocol error"
// *Cause:
// *Action:
03107, 00000, "oranet buffer underflow"
// *Cause:
// *Action:
03108, 00000, "oranet: ORACLE does not support this interface version"
// *Cause:
// *Action:
03109, 00000, "oranet buffer overflow"
// *Cause:
// *Action:
03110, 00000, "oranet: ORACLE does not support this SQL version"
// *Cause:
// *Action:
03111, 00000, "break received on communication channel"
// *Cause:
// *Action:
03112, 00000, "a server linked as single-task cannot use SQL*Net"
// Cause: A statement containing a SQL*Net connect string was issued to the
//        single-task server. For example, a database link was used in a
//        SQL statement.
// Action: Do not use SQL*Net connect strings in a single-task environment.
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup. 
//          Also, look in the alert.log file for any errors. Finally, test to 
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.
03114, 00000, "not connected to ORACLE"
// *Cause:
// *Action:
03115, 00000, "unsupported network datatype or representation"
// *Cause:
// *Action:
03116, 00000, "invalid buffer length passed to a conversion routine"
// *Cause:
// *Action:
03117, 00000, "two-task save area overflow"
// *Cause:
// *Action:
03118, 00000, "two-task coroutine has invalid state"
// *Cause:
// *Action:
03119, 00000, "two-task detected inconsistent datatype specification"
// *Cause: There was both a datatype, and an anonymous datatype declaration
//         found.
// *Action:Correct the specification.
03120, 00000, "two-task conversion routine: integer overflow"
// *Cause:
// *Action:
03121, 00000, "no interface driver connected - function not performed"
// *Cause:
// *Action:
03122, 00000, "attempt to close ORACLE-side window on user side"
// *Cause:  This is an internal error.
// *Action:  Contact your customer support representative.
03123, 00000, "operation would block"
// *Cause:  This is a status code that indicates that the operation
//          cannot complete now. 
// *Action: None; this is not an error.  The operation should be retried
//          again for completion. 
03124, 00000, "two-task internal error"
// *Cause:  Internal error.
// *Action: Contact your customer support representative.
03125, 00000, "client-server protocol violation"
// *Cause: The application received a bad escape sequence from the server and
//         may indicate a problem with the client application user code.
// *Action:  Contact your customer support representative.
03126, 00000, "network driver does not support non-blocking operations"
// *Cause: A non-blocking operation was attempted and the network driver
//         does not support non-blocking operations.
// *Action: Use default blocking operations or use a driver supporting 
//          non-blocking operations.
03127, 00000, "no new operations allowed until the active operation ends"
// *Cause: An attempt was made to execute a new operation before the active
//         non-blocking operation completed or a new operation was attempted
//         before all the pieces of a column were inserted or fetched.
// *Action: Execute the new operation after the non-blocking operation 
//          completes. If piecewise binds/defines were done, execute the new
//          operation after all the pieces have been inserted or fetched.
03128, 00000, "connection is in blocking mode"
// *Cause: The OCI test for non-blocking mode on a connection indicates that 
//         the connection is in blocking mode.
// *Action: If non-blocking mode is required use appropriate OCI calls to 
//          change the mode.
03129, 00000, "the next piece to be inserted is required"
// *Cause: The application performed a piecewise bind on a column.
// *Action: Provide the next piece of this bind variable.
03130, 00000, "the buffer for the next piece to be fetched is required"
// *Cause: The application performed a piecewise define on the column.
// *Action: Provide the next buffer for the next piece to be retrieved.
03131, 00000, "an invalid buffer was provided for the next piece"
// *Cause: The application either provided the length of the buffer for the 
//         next piece to be zero or provided a null pointer.
// *Action: Verify if the buffer pointer for the next piece is null or if the 
//          length is zero.
03132, 00000, "two-task default value overflow"
// *Cause:  The default value specified for a record field was too large.
// *Action: Change the default value to fit the field size.
03133, 00000, "piggyback function error"
// *Document: NO
// *Cause: Piggyback function has returned an error. This is an internal
//         error.
// *Action: 
03134, 00000, "Connections to this server version are no longer supported."
// *Cause:  An attempt was made to connect to an Oracle server of older
//          version.
// *Action: Please refer to documentation for more details.
03135, 00000, "connection lost contact"
// *Cause:  1) Server unexpectedly terminated or was forced to terminate.
//          2) Server timed out the connection.
// *Action: 1) Check if the server session was terminated.
//          2) Check if the timeout parameters are set properly in sqlnet.ora.
03136, 00000, "inbound connection timed out"
// *Cause:  Inbound connection was timed out by the server because 
//          user authentication was not completed within the given time 
//          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
// *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
//          2) Configure SQL*NET with a proper inbound connect timeout value
//             if necessary.
03137, 00000, "TTC protocol internal error : [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause:  TTC protocol internal error.
// *Action: Contact Oracle Support Services.
03138, 00000, "Connection terminated due to security policy violation"
// *Cause:  Connection was terminated due to a security policy violation.
// *Action: Contact the Database Administrator
03139, 00000, "This OCI call has been disabled by the DBA"
// *Cause:  The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled.
// *Action: Contact the Database Administrator
/
/       3140 - 3159 Reserved for TTC/NET vector IO
/
03140, 00000, "I/O operation in progress"
// *Cause:  The current I/O operation was not complete. The error is 
//          typically returned from vectored and/or asynchronous I/O calls.
// *Action: Perform the necessary operation to complete or abort the current I/O.
03141, 00000, "I/O request queue full"
// *Cause:  The I/O request queue was full and no more requests could be queued.
// *Action: Perform the proper operations to complete part or all of the current
//          in-progress I/O requests.
03142, 00000, "Session ID: %ld Serial number: %ld"
// *Cause:  Connection was lost for the specified session and serial number.
//          This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03143, 00000, "Process ID: %s Thread ID: %s"
// *Cause:  Connection was lost for the specified process ID and thread ID.
//          This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03144, 00000, "Process ID: %s"
// *Cause:  Connection was lost for the specified process ID.
//          This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03145, 00000, "I/O streaming direction error"
// *Cause:  Attempted to PUT data when GET streaming was in progress or
//          attempted to GET data when PUT streaming was in progress.
// *Action: Complete current stream read or write I/O before attempting 
//          I/O in reverse direction.
03146, 00000, "Invalid buffer length for TTC field"
// *Cause:  A corrupt Two-Task Common (TTC) packet was received.
// *Action: This is a internal protocol error. Contact Oracle Support Services.
03147, 00000, "Missing mandatory TTC field"
// *Cause:  A corrupt Two-Task Common (TTC) packet was received.
// *Action: This is an internal protocol error. Contact Oracle Support 
//          Services.
03149, 00000, "Invalid Oracle error code"
// *Cause:  An invalid Oracle error code was received by the server.
// *Action: This is an internal protocol error. Contact Oracle Support 
//          Services.
03160, 00000, "An invalid client operation was requested by the server"
// *Cause:  You are using an Oracle client application linked with 
//          libraries with lower version than the current server version.
// *Action: Upgrade client libraries to be same as 
//          or higher than the server version.
/     3170 to 3180 reserved for readable physical standby
03170, 00000, "deadlocked on readable physical standby (undo segment %s)"
// *Cause:  A new undo segment was added. A query can occasionally
//          deadlock when issued around the time an undo segment is added 
//          and used immediately on the primary. 
// *Action: Retry the query. Avoid creating new undo segments when using 
//          standby as a regular part of operation.
03171, 00000, "Recovery was terminated during query execution"
// *Cause:  Recovery was terminated. A query can ocassionally
//          deadlock when recovery is terminated because it needs a block 
//          with changes that are made after the point at which recovery 
//          was terminated.
// *Action: Retry the query. Avoid cancelling recovery on standby.
03172, 00000, "STANDBY_MAX_DATA_DELAY of %s seconds exceeded"
// *Cause:  Standby recovery fell behind the STANDBY_MAX_DATA_DELAY
//          requirement.  
// *Action: Tune recovery and retry the query later, or switch to another
//          standby database within the data delay requirement.
03173, 00000, "Standby may not be synced with primary"
// *Cause:  ALTER SESSION SYNC WITH PRIMARY did not work because either the
//          standby was not synchronous or in a data-loss mode with regard
//          to the primary, or the standby recovery was terminated.
// *Action: Make the standby synchronous and no-data-loss with regard
//          to the primary.  Make the standby recovery active. 
03174, 00000, "STANDBY_MAX_DATA_DELAY does not apply to SYS users"
// *Cause:  ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS
//          users.  
// *Action: Issue ALTER SESSION SET STANDBY_MAX_DATA_DELAY for non-SYS users.
03175, 00000, "parameter %s mismatch"
// *Cause:  The value of the %s parameter was not the same in all instances.
// *Action: Check %s in all instances.
03176, 00000, "%s only works on an open physical standby database"
// *Cause:  The database was not an open physical standby database.
// *Action: Issue the command on an open physical standby database.
03177, 00000, "enable read-only violation logging"
// *Cause:
// *Action:
// *Comment: Used for testing only
/
/ 3200 - 3289 Allocate Extent and other Space Management errors
/
03200, 00000, "the segment type specification is invalid"
// *Cause: segment type is not TABLE, INDEX, or CLUSTER
// *Action: use a correct segment type
/
03201, 00000, "the group number specification is invalid"
// *Cause: the freelist group number was either negative or larger than the
//         the number of freelist groups in the segment
// *Action: use a correct group number
/
03202, 00000, "the scan limit specification is invalid"
// *Cause: the scan limit did not have a positive integer value 
//         the number of freelist groups in the segment
// *Action: use a correct scan limit
/
03203, 00000, "concurrent update activity makes space analysis impossible"
// *Cause: high volume of user updates interfere with the space analysis
// *Action: retry the command or lock the underlying objects
/
03204, 00000, "the segment type specification should indicate partitioning"
// *Cause: partition name is specified for the space analysis, but the object
//         type does not indicate parttitioning
// *Action: specify PARTITION in the segment type, if the object is
//          partitioned, otherwise, omit the partition name
/
03205, 00000, "partition name is required when partitioned type is specified"
// *Cause: partition name is not specified for the space analysis, but the 
//         object type indicates parttitioning
// *Action: specify partition name, if the object is partitioned, otherwise, 
//          specify a non-partitioned type
/
03206, 00000, "maximum file size of (%s) blocks in AUTOEXTEND clause is out of range"
// *Cause: The maximum file size for an autoextendable file has 
//         exceeded the maximum number of blocks allowed.
// *Action: Reduce the size and retry.
/    
03207, 00000, "subpartitioned type must be specified for composite object"
// *Cause: partition type is specified for the space analysis, but the 
//         object type indicates composite partitioning
// *Action: specify subpartition name and subpartition type
/
03208, 00000, "partitioned type must be specified for a non-composite object"
// *Cause: subpartition type is specified for the space analysis, but the 
//         object type indicates non-composite partitioning
// *Action: specify partition name and partition type
/
03209, 00000, "DBMS_ADMIN_PACKAGE invalid file/block specification"
// *Cause: The value of file number or block number is outside of limits or
//         inconsistent
// *Action: Fix the file number/block number value
/    
03210, 00000, "DBMS_ADMIN_PACKAGE invalid option specification"
// *Cause: The value of one of the option parameters is incorrect
// *Action: Fix the option value
/    
03211, 00000, "The segment does not exist or is not in a valid state"
// *Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation
//         does not exist or is not in a state appropriate for this operation
// *Action: Fix the segment specification, or put the segment in the 
//          appropriate state.
/
03212, 00000, "Temporary Segment cannot be created in locally-managed tablespace"
// *Cause: Attempt to create a temporary segment for sort/hash/lobs in
//         in permanent tablespace of kind locally-managed
// *Action: Alter temporary tablespace of user to a temporary tablespace
//          or a dictionary-managed permanent tablespace
/
03213, 00000, "Invalid Lob Segment Name for DBMS_SPACE package"
// *Cause: The Lob Segment specified in the DBMS_SPACE operation does not
//         exist.
// *Action: Fix the Segment Specification
/
03214, 00000, "File Size specified is smaller than minimum required"
// *Cause: File Size specified for add/resize datafile/tempfile does not
//         allow for the minimum required of one allocation unit.
// *Action: Increase the specification for file size
/
03215, 00000, "File Size specified for resize is too small "
// *Cause: File Size specified for resize datafile/tempfile causes
//         bitmap control structures to overlap
// *Action: Increase the specification for file size
/
03216, 00000, "Tablespace/Segment Verification cannot proceed"
// *Cause: Corruptions detected during verification whch cannot be dealt with
// *Action: Do manual verification
/
03217, 00000, "invalid option for alter of TEMPORARY TABLESPACE"
// *Cause: invalid option for alter of temporary tablespace was specified
// *Action: Specify one of the valid options: ADD TEMPFILE,
//          TEMPFILE ONLINE, TEMPFILE OFFLINE
/
03218, 00000, "invalid option for CREATE/ALTER TABLESPACE"
// *Cause: invalid option for create/alter tablespace of type locally-managed
// *Action: Specify one of the valid options.
/
03219, 00000, "Tablespace '%s' is dictionary-managed, offline or temporary"
// *Cause: Operation which is only applicable to permanent, online,
//         locally-managed tablespaces is specified for a tablespace which
//         is either dictionary-managed, offline or temporary
// *Action: Reissue operation for a different tablespace, mount the
//          tablespace or do not issue it at all, since it does not apply 
//          for the given tablespace
/    
03220, 00000, "DBMS_ADMIN_PACKAGE required parameter is NULL or missing"
// *Cause: Some of the procedures was called with missing or NULL parameters
// *Action: Specify the missing parameter
/    
03221, 00000, "Temporary tablespaces and temporary segments must have standard block size"
// *Cause: An attempt was made to do one of the following :
//         (1) create a temporary tablespace with a non-standard block
//             size or,
//         (2) alter an existing permanent tablespace of non-standard 
//             block size to a temporary tablespace or,
//         (3) issue a DDL statement that would result in the creation
//             of a temporary segment in a tablespace of non-standard 
//             block size.  
// *Action: (1) If creating a temporary tablespace, do not specify a block
//              size different from the standard block size. 
//          (2) If altering an existing permanent tablespace to a
//              temporary tablespace, ensure that it is of standard block size.
//          (3) Ensure that the user's temporary tablespace is a
//              tablespace having the standard block size. 
/    
03222, 00000, "average row size and row count must be greater than zero"
// *Cause: Either a bad value passed to dbms_space.create_table_cost()
//         or explain plan did not pass through size information.
// *Action: Check the row size parameter in dbms_space.create_table_cost().
//          For explain plan, make sure statistics have been computed
//          for all source tables in the CREATE TABLE AS SELECT statement.
/
03223, 00000, "Bitmap index block addressable limitation reached"
// *Cause:  The limitation of addressability of BMIB (Bitmap Index Block) was 
//          reached for the current blocksize.
// *Action: If the segment size has grown greater than addressability of BMIB 
//          (Bitmap Index Block), do the following:
//          (1) Partition the table.
//          (2) Move the segment to a tablespace having bigger blocksize.
/
03230, 00000, "segment only contains %s blocks of unused space above high water mark"
// *Cause: Attempt to preserve too many blocks. 
// *Action: reduce the KEEP amount.
/
03231, 00000, "the INITIAL extent may not be deallocated"
// *Cause: Attempt to deallocate space from the segment which was truncated
//         prior to the 7.3 release.
// *Action: increase the KEEP amount, or truncate the segment, and reissue
//          the command.
/
03233, 00000, "unable to extend table %s.%s subpartition %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent for table subpartition segment
//          in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//         files to the tablespace indicated.
03234, 00000, "unable to extend index %s.%s subpartition %s by %s in tablespace %s"
// *Cause:  Failed to allocate an extent for index subpartition 
//          segment in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//         files to the tablespace indicated.
03235, 00000, "max # extents (%s) reached in table %s.%s subpartition %s"
// *Cause:  A table subpartition tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params
03236, 00000, "max # extents (%s) reached in index %s.%s subpartition %s"
// *Cause:  An index subpartition tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
//          you must recreate with larger initial, next or pctincrease params.
03237, 00000, "Initial Extent of specified size cannot be allocated in tablespace (%s)"
// *Cause:  Too large a size for an initial extent due to freelist
//          group specification
// *Action: Reduce number of freelist groups specified for segment
03238, 00000, "unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s"  
// *Cause:  An attempt was made to allocate an extent for LOB subpartition  
//          segment in tablespace, but the extent could not be allocated  
//          because there is not enough space in the tablespace indicated.  
// *Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or 
//          more files to the tablespace indicated.  
03239, 00000, "maxextents (%s) reached in LOB segment %s.%s subpartition %s"  
// *Cause:  A LOB subpartition segment tried to extend past maxextents.  
// *Action: If maxextents is less than the system maximum, raise it. 
//          Otherwise, recreate the subpartition with larger INITIAL, NEXT, 
//          or PCTINCREASE parameters. 
/
/  Errors 3240 - 3250 reserved for tablespace migration and bitmaps relocation
/
03240, 00000, "User's temporary tablespace same as tablespace being migrated"
// *Cause:  Users default temporary tablespace must be different from the 
//          tablespace being migrated.
// *Action: alter users default temporary tablespace to be different.
03241, 00000, "Invalid unit size"
// *Cause:  User specified an invalid unit size for the tablespace 
// *Action: Specify the correct unit size. To estimate unit size please 
//          refer to Oracle Server Administrator's Guide.
03242, 00000, "Tablespace migration retried 500 times"
// *Cause:  For migration to complete, temporary segments should not be present
//          in the tablespace at the time of migration. 
// *Action: Avoid migrating the tablespace when there is heavy temporary
//          segment creation going on as with object drops.
03243, 00000, "destination dba overlaps with existing control information"
// *Cause:  Cannot overlap control information during relocation
// *Action: Please chose another destination address
03244, 00000, "No free space found to place the control information"
// *Cause:  During migration of tablespace found no place to put the control
//          information. If during bitmaps relocation, found no space at the 
//          specified destination.
// *Action: If during migration, add more space to the tablespace and retry
//          migration. If during bitmaps relocation, specify a destination
//          address where there is enough free space.
03245, 00000, "Tablespace has to be dictionary managed, online and permanent to be able to migrate"
// *Cause:  Tablespace was not dictionary managed or online or permanent.
// *Action: Make sure the tablespace is online, permanent and dictionary managed
03246, 00000, "Invalid block number specified"
// *Cause:  Control information cannot be placed at the specified dba either
//          because the block number specified is beyond the file end or 
//          the file is not large enough to accomodate the control information
//          at that location
// *Action: specify a correct block number
03247, 00000, "Invalid block number specified"
// *Cause:  Relocation of bitmaps to the said destination will make 
//          the tablespace self descriptive
// *Action: Choose another destination dba.
03248, 00000, "Too much of segment creation activity during migration"
// *Cause:  Temporary segments were attempted to be created during migration
// *Action: The error is signalled after retrying migration for 500 times.
//          Run migration when there is less of segment creation activity is 
//          going on.
03249, 00000, "Uniform size for auto segment space managed tablespace should have atleast %s blocks"
// *Cause:  For the given blocksize, uniform size specified is insufficient
// *Action: Specify larger extent size and retry
03250, 00000, "Cannot mark this segment corrupt"
// *Cause:  This segment cannot be marked corrupt because it contains 
//          data dictionary objects
// *Action: Check the segment information and reissue the command.
03251, 00000, "Cannot issue this command on SYSTEM tablespace "
// *Cause:  It is not permitted to migrate SYSTEM tablespace from locally
//          managed format to dictionary managed format or relocate bitmaps.
// *Action: Check the tablespace name and procedure name 
03252, 00000, "initial extent size not enough for LOB segment"
// *Cause:  Fatblock size of LOB segment is too big to fit into the initial
//          extent.
// *Action: Specify a smaller fatblock size or create the LOB segment in
//          other tablespaces with bigger initial extent size.
03254, 00000, "unable to execute the sql in read only database"
// *Cause:  Unable to create a consistent snapshot of the object in a read
//          only database. Transaction recovery must be performed before opening the
//          database read only.
// *Action:  Open the database read write, allow dead transaction recovery
//           to complete and then open the database read only.
03261, 00000, "the tablespace %s has only one file"
// *Cause:  Dropping file from ts which has a single file
//          extent.
// *Action: Cannot make a tablespace fileless
03262, 00000, "the file is non-empty"
// *Cause:  Trying to drop a non-empty datafile
// *Action: Cannot drop a non empty datafile
03263, 00000, "cannot drop the first file of tablespace %s"
// *Cause:  Trying to drop the first datafile with which ts is created
// *Action: Cannot drop the first datafile with which ts is created
03264, 00000, "cannot drop offline datafile of locally managed tablespace"
// *Cause:  Trying to drop offline datafile in lmts
// *Action: Try to drop file afetr making it online
03274, 00000, "both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified"
// *Cause:  The DEALLOCATE option and the ALLOCATE option are specified in
//          the same command.
// *Action:  Choose one of the options or issue two separate commands.
03275, 00000, "duplicate DEALLOCATE option specification"
// *Cause:  The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX 
//          is specified more than once.
// *Action:  Specify the option at most once.
03276, 00000, "duplicate ALLOCATE EXTENT option specification"
// MERGE: 2376 RENUMBERED TO 3276
// *Cause:  The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX 
//    is specified more than once.
// *Action:  Specify the option at most once.
03277, 00000, "invalid SIZE specified"
// MERGE: 2377 RENUMBERED TO 3277
// *Cause:  The specified value must be an integer.
// *Action:  Choose an appropriate integer value.
03278, 00000, "duplicate ALLOCATE EXTENT option specification"
// MERGE: 2378 RENUMBERED TO 3278
// *Cause:  An option (DATAFILE, SIZE or INSTANCE) was specified more
//    than once.
// *Action:  Specify each option at most once.
03279, 00000, "invalid INSTANCE specified"
// MERGE: 2379 RENUMBERED TO 3279
// *Cause:  The specified value is not recognized as a valid instance name.
// *Action: Use a valid name. 
03280, 00000, "invalid DATAFILE filename specified"
// MERGE: 2380 RENUMBERED TO 3280
// *Cause:  A character string literal is expected, but not found.
// *Action:  Specify filenames using character string literals.
03281, 00000, "invalid ALLOCATE EXTENT option"
// MERGE: 2381 RENUMBERED TO 3281
// *Cause:  An option other than DATAFILE, SIZE or INSTANCE was specified.
// *Action:  Remove invalid option and retry the command.
03282, 00000, "missing ALLOCATE EXTENT option"
// MERGE: 2382 RENUMBERED TO 3282
// *Cause:  No ALLOCATE EXTENT options were specified.
// *Action:  Specified one or more of the following options:
//     DATAFILE, SIZE or INSTANCE.
03283, 00000, "specified datafile %s does not exist"
// MERGE: 2383 RENUMBERED TO 3283
// *Cause:  The datafile does not exist
// *Action:  Retry the option with the correct datafile
03284, 00000, "datafile or tempfile %s is not a member of tablespace %s"
// MERGE: 2384 RENUMBERED TO 3284
// *Cause:  The specified datafile or tempfile did not belong to the 
//          tablespace that the object resides in.
// *Action:  Retry the option with the correct datafile or tempfile.
03286, 00000, "ALLOCATE EXTENT not valid for HASH CLUSTERS"
//  *Cause:  The cluster is a hash cluster, and can not use the
//           allcoate extent option.
//  Action:  
03287, 00000, "invalid FREELIST GROUP specified"
//  *Cause:  The specified FREELIST GROUP number is invalid
//  *Action: Choose a number between 1 and # freelist groups for this object
03288, 00000, "both FREELIST GROUP and INSTANCE parameters may not be specified"
//  *Cause:  Both FREELIST GROUP and INSTANCE were specified in clause
//  *Action: Remove one of the two parameters
03289, 00000, "partition name and segment type do not match"
//  *Cause:  Partition name and segment type specified for space analysis do 
//           not match
//  *Action: Specify type PARTITION if the object is partitioned, specify 
//           SUBPARTITION if the object is composite
/
/        3290 - 3295 Truncate Parse and Execution Errors
/
03290, 00000, "Invalid truncate command - missing CLUSTER or TABLE keyword"
//  *Cause:  Invalid object specification given.
//  *Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE
03291, 00000, "Invalid truncate option - missing STORAGE keyword"
//  *Cause:  Expected STORAGE keyword
//  *Action: Either specify DROP STORAGE or REUSE STORAGE
03292, 00000, "Table to be truncated is part of a cluster"
//  *Cause:  The table being truncated is a member of a cluster.
//  *Action: Either use TRUNCATE CLUSTER or DROP TABLE
03293, 00000, "Cluster to be truncated is a HASH CLUSTER"
//  *Cause:  Only INDEX CLUSTERS can be truncated.
//  *Action: Drop and recreate the HASH CLUSTER instead of using truncate.
/
/ 3296 - 3299 Reserved for Resizeable Datafiles
/
03296, 00000, "cannot resize datafile - file %s not found"
// *Cause:  The specified datafile is not available for resizing.
// *Action: Ensure that the datafile name is valid, and if so, ensure the
//          file is accessible.
03297, 00000, "file contains used data beyond requested RESIZE value"
// *Cause:  Some portion of the file in the region to be trimmed is 
//          currently in use by a database object
// *Action: Drop or move segments containing extents in this region prior to
//          resizing the file, or choose a resize value such that only free
//          space is in the trimmed.
03298, 00000, "cannot shrink datafile - file %s is under hot backup"
// *Cause:  Attempt to shrink a datafile while it is under hot backup.
//          This is not allowed.
// *Action: Retry shrinking the file after the hot backup completes.
03299, 00000, "cannot create dictionary table %s"
// *Cause:  A dictionary table is created upon the first execution of the 
//    command 'alter database datafile autoextend on' for a database.
//    This operation did not succeed. The most probable cause for this
//    is insufficient space in the system tablespace.
// *Action: See action for next error message in error stack.
/
/       3300 - 3499 Reserved for Meiko
/
/ 3500 - 3699 Reserved for Native Macintosh OS-specific errors
/
/ 3700 - 3999 Reserved for DG AOS/VS specific errors
/
/ 4000-4099 invalid parameter errors
/
04000, 00000, "the sum of PCTUSED and PCTFREE cannot exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100
// *Action: create the table/cluster specifying values whose sum is <= 100
04001, 00000, "sequence parameter %s must be an integer"
// *Cause: %s (a sequence parameter) specified was not an integer
// *Action: create the sequence, giving the specified parameter an integer value
04002, 00000, "INCREMENT must be a non-zero integer"
// *Cause: a sequence increment was specified to be zero
// *Action: specify the increment to be a non-zero value
04003, 00000, "sequence parameter %s exceeds maximum size allowed (%s digits)"
// *Cause: %s (a sequencer parameter) had too many digits
// *Action: specify the parameter with the allowed number of digits
04004, 00000, "MINVALUE must be less than MAXVALUE"
// *Cause: MINVALUE was specified to be greater than or equal to MAXVALUE
// *Action: specify a MINVALUE that is less than MAXVALUE
04005, 00000, "INCREMENT must be less than MAXVALUE minus MINVALUE"
// *Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE
// *Action: specify an INCREMENT that is < MAXVALUE-MINVALUE
04006, 00000, "START WITH cannot be less than MINVALUE"
// *Cause: the given starting value is less than MINVALUE
// *Action: make sure that the starting value is >= MINVALUE
04007, 00000, "MINVALUE cannot be made to exceed the current value"
// *Cause: the given MINVALUE would be greater than the current value
// *Action: always make sure that MINVALUE is <= the current value
04008, 00000, "START WITH cannot be more than MAXVALUE"
// *Cause: the starting value would be larger than MAXVALUE
// *Action: make sure that the starting value is less than MAXVALUE
04009, 00000, "MAXVALUE cannot be made to be less than the current value"
// *Cause: the current value exceeds the given MAXVALUE
// *Action: make sure that the new MAXVALUE is larger than the current value
04010, 00000, "the number of values to CACHE must be greater than 1"
// *Cause: the value in the CACHE clause was one
// *Action: specify NOCACHE, or a value larger than one
04011, 00000, "sequence %s must range between %s and %s"
// *Cause: the value specified for one of the sequence parameters exceeds limits
// *Action: specify parameter within these limits
04012, 00000, "object is not a sequence"
// *Cause: the object specified cannot have sequence ddl's performed on it
// *Action: re-enter the statement being careful with the spelling of the name
04013, 00000, "number to CACHE must be less than one cycle"
// *Cause: number to CACHE given is larger than values in a cycle
// *Action: enlarge the cycle, or cache fewer values
04014, 00000, "descending sequences that CYCLE must specify MINVALUE"
// *Cause: sequences that cycle must have their wrap-wrap specified
// *Action: re-create the sequence, specifying its wrap-value
04015, 00000, "ascending sequences that CYCLE must specify MAXVALUE"
// *Cause: sequences that cycle must have their wrap-wrap specified
// *Action: re-create the sequence, specifying its wrap-value
04016, 00000, "sequence %s no longer exists"
// *Cause: sequence was dropped while processing its next value.
// *Action: re-create the sequence
04017, 00000, "invalid value %s (length = %s) for parameter max_dump_file_size"
// *Cause: neither did the string supplied for max_dump_file_size parameter
//   match the "UNLIMITED" string value nor did it represent a base 10
//   integer.
// *Action: reassign a proper value to this parameter.
/
/       4020-4029 Reserved for Library Cache errors
/
04020, 00000, "deadlock detected while trying to lock object %s%s%s%s%s"
// *Cause:  While trying to lock a library object, a deadlock is detected.
// *Action: Retry the operation later.
04021, 00000, "timeout occurred while waiting to lock object %s%s%s%s%s"
// *Cause:  While waiting to lock a library object, a timeout occurred.
// *Action: Retry the operation later.
04022, 00000, "nowait requested, but had to wait to lock dictionary object"
// *Cause:  Had to wait to lock a library object during a nowait request.
// *Action: Retry the operation later.
04023, 00000, "Object %s%s%s%s%s could not be validated or authorized"
// *Cause: A number of attempts were made to validate or authorize an
//         object but failed.
// *Action: Please report this error to Oracle Support Services.
04024, 00000, "self-deadlock detected while trying to mutex pin cursor %s"
// *Cause:  While trying to mutex pin a cursor, a self-deadlock is detected.
// *Action: Retry the operation later.
04025, 00000, "maximum allowed library object lock allocated for %s%s%s%s%s"
// *Cause: Too many active locks for the object has been allocated. This error
//         can be a result of too many cursors kept open per session.
// *Action: Close cursors, reduce session_cached_cursors value.
04027, 00000, "self-deadlock during automatic validation for object %s.%s"
// *Cause:  An attempt was made to validate an invalidated object but it failed
//          because of a self-deadlock.
// *Action: Identify the root cause of the self-deadlock and take corrective
//          action, e.g. compile the invalidated object separately.
04028, 00000, "cannot generate diana for object %s%s%s%s%s"
// *Cause:  Cannot generate diana for an object because of lock conflict.
// *Action: Please report this error to your support representative.
04029, 00000, "error ORA-%s occurred when querying %s%s%s"
// *Cause:  The table or view being queried might be missing.  The error
//          number indicates the error.
// *Action: Fix the error.
/
/       4030-4039 Reserved for Memory Manager errors
/
04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
// *Cause:  Operating system process private memory was exhausted.
// *Action: 
04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
// *Cause:  More shared memory is needed than was allocated in the shared
//          pool or Streams pool.
// *Action: If the shared pool is out of memory, either use the
//          DBMS_SHARED_POOL package to pin large packages,
//          reduce your use of shared memory, or increase the amount of
//          available shared memory by increasing the value of the
//          initialization parameters SHARED_POOL_RESERVED_SIZE and 
//          SHARED_POOL_SIZE.
//          If the large pool is out of memory, increase the initialization
//          parameter LARGE_POOL_SIZE.  
//          If the error is issued from an Oracle Streams or XStream process,
//          increase the initialization parameter STREAMS_POOL_SIZE or increase
//          the capture or apply parameter MAX_SGA_SIZE.
04032, 00000, "pga_aggregate_target must be set before switching to auto mode"
// *Cause:  attempt to set workarea_size_policy to AUTO while  
//    pga_aggregate_target is not specified
// *Action: before setting workarea_size_policy, set pga_aggregate_target
//          to a value representing the total private memory available to 
//          the instance. This total is generally the total physical memory
//          available in the system minus what is needed for the SGA minus
//          what is needed for the operating system (e.g. 500MB)
04033, 00000, "Insufficient memory to grow pool"
// *Cause:  The system had insufficient memory to grow the pool to the 
//          specified size.  
// *Action: Specify a smaller value to grow the pool.
04034, 00000, "unable to shrink pool to specified size"
// *Cause:  The pool could not shrink to the specified size as it could not
//          free memory.
// *Action: Specify a larger value to which to shrink the pool to.
04035, 00000, "unable to allocate %s bytes of shared memory in shared object cache \"%s\" of size \"%s\""
// *Cause:  More shared memory is needed than was allocated in the shared
//          object cache.
// *Action: 
/
/       4040-4059 Reserved for Stored Procedure errors
/
04041, 00000, "package specification must be created first before creating package body"
// *Cause:  Attempt to create a package body before creating its package
//          specification.
// *Action: Create the package specification first before creating the
//          package body.
04042, 00000, "procedure, function, package, or package body does not exist"
// *Cause:  Attempt to access a procedure, function, package, or package body
//          that does not exist.
// *Action: Make sure the name is correct.
04043, 00000, "object %s does not exist"
// *Cause:  An object name was specified that was not recognized by the system.
//          There are several possible causes:
//          - An invalid name for a table, view, sequence, procedure, function,
//          package, or package body was entered. Since the system could not
//          recognize the invalid name, it responded with the message that the
//          named object does not exist.
//          - An attempt was made to rename an index or a cluster, or some
//          other object that cannot be renamed.
// *Action: Check the spelling of the named object and rerun the code. (Valid
//          names of tables, views, functions, etc. can be listed by querying
//          the data dictionary.)
04044, 00000, "procedure, function, package, or type is not allowed here"
// *Cause:  A procedure, function, or package was specified in an
//          inappropriate place in a statement.
// *Action: Make sure the name is correct or remove it.
04045, 00000, "errors during recompilation/revalidation of %s.%s"
// *Cause:  This message indicates the object to which the following
//          errors apply.  The errors occurred during implicit
//          recompilation/revalidation of the object.
// *Action: Check the following errors for more information, and
//          make the necessary corrections to the object.
04046, 00000, "results of compilation are too large to support"
// *Cause:  Attempt to compile and store a large stored procedure that results
//          in compilation data that is too large for the system to support
//          or store.
// *Action: Reduce the size of the store procedure by splitting it into
//          smaller stored procedures.
04047, 00000, "object specified is incompatible with the flag specified"
// *Cause:  The object type implied by the flag does not match the type
//    of object specified.
// *Action: Specify the correct object, or use the appropriate flag
04050, 00000, "invalid or missing procedure, function, or package name"
// *Cause:  The required procedure, function, or package name is invalid
//          or missing.
// *Action: Specify a valid name.
04051, 00000, "user %s cannot use database link %s.%s"
// *Cause:  During forwarding of a remote object access, an attempt was
//          made to use a non-existent database link or one owned by
//          a user other than the logon user or PUBLIC.
// *Action: Change your database link structure so that all indirect remote
//          accesses are done from the same userid that originates the 
//          request.
04052, 00000, "error occurred when looking up remote object %s%s%s%s%s"
// *Cause:  An error occurred when trying to look up a remote object.
// *Action: Fix the error.  Make sure the remote database system has run
//          CATRPC.SQL to create necessary views used for querying or looking up
//          objects stored in the database.
04053, 00000, "error occurred when validating remote object %s%s%s%s%s"
// *Cause:  An error occurred when trying to validate a remote object.
// *Action: Fix the error.  Make sure the remote database system has run
//          CATRPC.SQL to create necessary views used for querying or looking up
//          objects stored in the database.
04054, 00000, "database link %s does not exist"
// *Cause:  During compilation of a PL/SQL block, an attempt was made to use
//          a non-existent database link.
// *Action: Either use a different database link or create the database link.
04055, 00000, "Aborted: \"%s\" formed a non-REF mutually-dependent cycle with \"%s\"."
// *Cause:  This compilation was aborted because the library unit that was
//          compiled would have formed a non-REF mutually-dependent cycle with
//          some other library units.  This happens when an attempt is made to
//          compile types that have attributes of other types that may
//          participate in a cycle with this type.
//          Example:
//             create type t1;
//             create type t2 (a t1);
//             create type t1 (a t2);
// *Action: Break the cycle (possibly by adding a REF or by using another
//          type).
/
/       4060-4069 Reserved for Stored Procedure Execution errors
/
04060, 00000, "insufficient privileges to execute %s"
// *Cause:  Attempt to execute a stored procedure without
//          sufficient privileges.
// *Action: Get necessary privileges.
04061, 00000, "existing state of %s has been invalidated"
// *Cause:  Attempt to resume the execution of a stored procedure using the
//          existing state which has become invalid or inconsistent
//          with the stored procedure because the procedure has been altered
//          or dropped.
// *Action: Try again; this error should have caused the existing state of
//          all packages to be re-initialized.
04062, 00000, "%s of %s has been changed"
// *Cause:  Attempt to execute a stored procedure to serve
//          an RPC stub which specifies a timestamp or signature that is
//          different from the current timestamp/signature of the procedure.
// *Action: Recompile the caller in order to pick up the new timestamp.
04063, 00000, "%s has errors"
// *Cause:  Attempt to execute a stored procedure or use a view that has
//          errors.  For stored procedures, the problem could be syntax errors
//          or references to other, non-existent procedures.  For views,
//          the problem could be a reference in the view's defining query to
//          a non-existent table.
//          Can also be a table which has references to non-existent or
//          inaccessible types.
// *Action: Fix the errors and/or create referenced objects as necessary.
04064, 00000, "not executed, invalidated %s"
// *Cause:  Attempt to execute a stored procedure that has
//          been invalidated.
// *Action: Recompile it.
04065, 00000, "not executed, altered or dropped %s"
// *Cause:  Attempt to execute a stored procedure that has
//          been altered or dropped thus making it not callable from the
//          calling procedure.
// *Action: Recompile its dependents.
04066, 00000, "non-executable object, %s"
// *Cause:  Attempt to execute a non-procedure.
// *Action: Make sure that a correct name is given.
04067, 00000, "not executed, %s does not exist"
// *Cause:  Attempt to execute a non-existent stored procedure.
// *Action: Make sure that a correct name is given.
04068, 00000, "existing state of packages%s%s%s has been discarded"
// *Cause:  One of errors 4060 - 4067 when attempt to execute a stored
//          procedure.
// *Action: Try again after proper re-initialization of any application's
//          state.
04069, 00000, "cannot drop or replace a library with table dependents"
// *Cause:  An attempt was made to drop or replace a library that has 
//          dependents. There could be a table which depends on type which 
//          depends on the library being dropped.
// *Action: Drop all table(s) depending on the type, then retry.
/
/       4070-4099 Reserved for Trigger errors
/
04070, 00000, "invalid trigger name"
// *Cause:  An invalid trigger name was specified.
// *Action: Verify that trigger name is not a reserved keyword.
04071, 00000, "missing BEFORE, AFTER or INSTEAD OF keyword"
// *Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
// *Action: Specify either BEFORE, AFTER or INSTEAD OF.
04072, 00000, "invalid trigger type"
// *Cause:  An invalid trigger type was given.
// *Action: Specify either INSERT, UPDATE or DELETE.
04073, 00000, "column list not valid for this trigger type"
// *Cause:  A column list was specified for a non-update trigger type.
// *Action: Remove the column list.
04074, 00000, "invalid REFERENCING name"
// *Cause:  An invalid name was given in the referencing clause.
// *Action: Verify the referencing name is not a reserved word.
04075, 00000, "invalid trigger action"
// *Cause:  An statement was given for the trigger action.
// *Action: Re-specify the trigger action.
04076, 00000, "invalid NEW or OLD specification"
// *Cause:  An invalid NEW or OLD specification was given for a column.
// *Action: Re-specify the column using the correct NEW or OLD specification.
04077, 00000, "WHEN clause cannot be used with table level triggers"
// *Cause:  The when clause can only be specified for row level triggers.
// *Action: Remove the when clause or specify for each row.
04078, 00000, "OLD and NEW values cannot be identical"
// *Cause:  The referencing clause specifies identical values for NEW and OLD.
// *Action: Re-specify either the OLD or NEW referencing value.
04079, 00000, "invalid trigger specification"
// *Cause:  The create TRIGGER statement is invalid.
// *Action: Check the statement for correct syntax.
04080, 00000, "trigger '%s' does not exist"
// *Cause:  The TRIGGER name is invalid.
// *Action: Check the trigger name.
04081, 00000, "trigger '%s' already exists"
// *Cause:  The TRIGGER name or type already exists.
// *Action: Use a different trigger name or drop the trigger which is of the 
//          same name.
04082, 00000, "NEW or OLD references not allowed in table level triggers"
// *Cause:  The trigger is accessing "new" or "old" values in a table trigger.
// *Action: Remove any new or old references.
04083, 00000, "invalid trigger variable '%*.s'"
// *Cause:  The variable referenced in the trigger body is invalid.
// *Action: See the manual for valid trigger variable types.
04084, 00000, "cannot change NEW values for this trigger type"
// *Cause:  New trigger variables can only be changed in before row
//          insert or update triggers.
// *Action: Change the trigger type or remove the variable reference.
04085, 00000, "cannot change the value of an OLD reference variable"
// *Cause:  Old values can only be read and not changed.
// *Action: Do not attempt to change an old variable.
04086, 00000, "trigger description too long, move comments into triggering code"
// *Cause:  The trigger description is limited to 2000 characters (for 
//          dictionary storage reasons).  The description does not include
//          the text of the "when" clause or the text of the pl/sql code
//          executed for the trigger.  
// *Action: If the trigger description contains a large comment, move that
//          comment into the pl/sql code for the trigger.
04087, 00000, "cannot change the value of ROWID reference variable"
// *Cause:  Rowid's can only be read and not changed.
// *Action: Do not attempt to change an rowid value.
04088, 00000, "error during execution of trigger '%s.%s'"
// *Cause:  A runtime error occurred during execution of a trigger.
// *Action: Check the triggers which were involved in the operation.
04089, 00000, "cannot create triggers on objects owned by SYS"
// *Cause:  An attempt was made to create a trigger on an object owned by SYS.
// *Action: Do not create triggers on objects owned by SYS.
04090, 00000, "'%s' specifies same table, event and trigger time as '%s'"
// *Cause: Trigger is of duplicate event and trigger time. 
// *Action: Combine the triggering information into one trigger which is 
//         fired at the given time.
04091, 00000, "table %s.%s is mutating, trigger/function may not see it"
// *Cause: A trigger (or a user defined plsql function that is referenced in 
//         this statement) attempted to look at (or modify) a table that was 
//         in the middle of being modified by the statement which fired it.
// *Action: Rewrite the trigger (or function) so it does not read that table.
04092, 00000, "cannot %s in a trigger"
// *Cause: A trigger attempted to commit or rollback.
// *Action: Rewrite the trigger so it does not commit or rollback.
04093, 00000, "references to columns of type LONG are not allowed in triggers"
// *Cause: A trigger attempted to reference a long column in the triggering
//         table.
// *Action: Do not reference the long column.
04094, 00000, "table %s.%s is constraining, trigger may not modify it"
// *Cause: A trigger attempted to modify a table that was constraining for
//         some referential constraint of a parent SQL statement.
04095, 00000, "trigger '%s' already exists on another table, cannot replace it"
// *Cause: Cannot replace a trigger which already exists on a different table
//         than the one being replaced.
// *Action: Drop the trigger with the same name and re-create it.
04096, 00000, "trigger '%s' has a WHEN clause which is too large, limit 2K"
// *Cause: A trigger's 'when' clause is limited to 2K for dictionary storage 
//         reasons.  The trigger being created exceeded that size.
// *Action: Use a smaller 'when' clause.  Note, the trigger body could be used
//         to perform the same limiting action as the 'when' clause.
04097, 00000, "DDL conflict while trying to drop or alter a trigger"
// *Cause: An attempt was made to concurrently perform two DDL operations on 
//         a trigger or trigger table.
// *Action: Investigate the new state of the trigger and retry the DDL 
//          operation, if still appropriate.
04098, 00000, "trigger '%s.%s' is invalid and failed re-validation"
// *Cause: A trigger was attempted to be retrieved for execution and was
//         found to be invalid.  This also means that compilation/authorization
//         failed for the trigger.
// *Action: Options are to resolve the compilation/authorization errors,
//         disable the trigger, or drop the trigger.
04099, 00000, "trigger '%s' is valid but not stored in compiled form"
// *Cause: A trigger was attempted to be retrieved for execution and was
//         found to be valid, but not stored.  This may mean the an
//         upgrade was done improperly from a non-stored trigger release.
// *Action: Alter compile the trigger to create the trigger in stored form.
//          Also, you may want to review that a proper upgrade was done.
/
/ MODIFIED
/   mmpandey  05/20/10 - 9714832: modify ADRCI Note detail, per new requirement
/   mmpandey  05/14/10 - 9714832: modify ORA-07445 Cause/Action text
/   sagrawal  11/16/09 - bug 9096821: change action for message 6548
/   jmuller   05/05/08 - XbranchMerge jmuller_bug-6805832 from st_rdbms_10.2
/   jmuller   02/08/08 - Fix bug 6805832: plsql_max_stack_size
/   dalpern   03/25/08 - 6907300: dbms_utility.name_resolve context 0
/   mvemulap  01/10/07 - bug 5727887 fix
/   desinha   08/30/06 - edit 6570 to add purge 
/   jmuller   05/10/06 - Fix bug 5206360: document ORA-6501/6502
/   ssubrama  11/07/05 - bug 4292100 remove 6596 as its no longer in use 
/   jmuller   04/07/05 - Fix bug 4236303: disallow deep copy of LOBs during 
/                        RPC 
/   jmuller   03/16/05 - Fix bug 4185606: flag ref cursor parameters in 
/                        forwarded RPC case 
/   jmuller   02/28/05 - Fix bug 4200773: handle NULL results in sped-up 
/                        STANDARD function calls more cleanly 
/   swhitman  12/22/04 - 3841541:patched Tru64 kernels get proc starttime 
/   wojeil    11/09/04 - add 7405 
/   jmuller   07/02/04 - Fix bug 3711648: parameterize ORA-6500 
/   jmuller   12/09/03 - Fix bug 1284461: name missing unit in 
/                        ORA-6508/BAD_DYN_LINK
/   avaliani  11/14/03 - add 07458-07460 (remove 07457 in 10gr2)
/   sdizdar   10/31/02 - add 7346
/   avaliani  06/19/02 - add 07457
/   mjaeger   06/10/02 - bug 2238718: chg 7247 from sfrfb to Veritas
/   shbose    04/29/02 - 2255071: change message for  ora-6534
/   ssubrama  04/09/02 - bug 2200057 add 6579
/   hbergh    11/05/01 - 1980225: trace file cannot be symlink
/   kmuthukk  07/03/01 - 1720409: rope of debugger/profiler with plsql ncomp
/   mvemulap  03/08/01 - bug 1554027 fix
/   mxyang    02/28/01 - update 6514
/   kumamage  02/15/01 -
/   kumamage  02/08/01 - add message for sftdel
/   arhee     10/26/00 - add new error message for resmgr
/   mxyang    08/11/00 - 6592: CASE not found
/   mvemulap  07/19/00 - native compiler messages
/   asethi    06/23/00 - 6540: pipelined execution of PL/SQL functions
/   arhee     06/19/00 - add mesg for exceeded max est exec time
/   arhee     06/07/00 - fix error mesg 7454
/   arhee     03/28/00 - add error msg 7454
/   hbergh    03/28/00 - 993307: merge Compaq Tru64 message
/   nle       07/22/99 - swap error message number
/   nle       06/29/99 - dynamic returning clause
/   varora    07/06/99 - change 6576 error message
/   nle       06/01/99 - reserve message for runtime
/   nle       05/28/99 - bug 890206
/   astocks   05/25/99 - PL/SQL profiler errors
/   kmuthukk  10/12/98 - raise err for OPEN on non-queries
/   rdecker   09/22/98 - add substitute character to 6502 for sub msgs
/   alui      08/28/98 - Reserved error range 04930-04999 for Digital Unix.
/   arhee     07/23/98 - fix resmgr error msgs
/   arhee     04/13/98 - add dbscheduling messages
/   nikeda    04/07/98 - Add plsql error message for Pro* external procedures
/   kmuthukk  04/07/98 - update purity error
/   rtaranto  04/07/98 - Add 6538 for purity violations
/   rtaranto  04/07/98 - Add errors 6536/6537 for in/out binds
/   kmuthukk  02/24/98 - null dynamic statement
/   mluong    03/20/98 - fix comp error
/   kmuthukk  03/30/98 - pending autonmous transaction rolled back
/   varora    03/28/98 - add duplicate bind error for CALL
/   arhee     03/17/98 - add message for database scheduling
/   kquinn    03/18/98 - Add message 7345
/   jsarma    03/10/98 - Add OER 7451-55
/   varora    02/01/98 - add errors for call method statement
/   agreenbl  10/30/97 - Rename 7302 --> 7305 to match 8.0.x
/   agreenbl  06/27/97 - Remove obsolete sm errors
/   mluong    06/24/97 - merge from 803
/   anolan    05/21/97 - checkout
/   anolan    05/14/97 - Demo.
/   kmuthukk  04/14/97 - restrict access of SR pkgs in triggers (b496997)
/   usundara  12/31/96 - incomplete and mutually-dependent types
/                          o add ora-6545 for pl/sql error handling)
/   bcchang   12/20/96 - error.msg split
/
/
/       Trigger errors continued at 25000-25099
/
/       4100-4499 Reserved for MVS OSD errors
/
/       4500-4899 Reserved for CMS OSD errors
/
/       4900-4929 Reserved for ICL DRS6000
/
/       4930-4999 Reserved for Digital Unix
/
/       5000-5899 Reserved for OEM OSD errors
/
/       5900-5999 Reserved for Wang OSD errors (OEM: GABA)
/
/       6000-6499 Reserved for SQL*Net errors
/
/       NETASY: 6000-6029  SQL*Net ASYNC Driver errors
/
/
/ Digital Unix specific errors (04930 - 04999).
/ This error range is used, starting from release 8.0.6, and 8.1.5.
/ The DEC specific errors 08324-08329 in e7500.msg are now listed here
/ as 04930 - 04935,04940.
/
04930, 00000, "open sequence number failed or initial state is valid"
// *Cause: Either Shared Sequence Number OS component was not installed
//         properly, or an MC hardware failure may have occurred or a
//         previous instance was not shut down properly.
// *Action: Verify that there are no background or foreground Oracle
//          processes from a previous instance on this node using the OS
//          command ps -ef|grep <instance_name>.  Verify that there are no
//          shared memory segments belonging to the user which owns the
//          Oracle installation by isuing the ipcs -b OS command.  If there
//          are shared memory segments or processes still on the system,
//          use svrmgrl to shutdown the instance with the abort option. If
//          the instance is not up, verify that the cluster software and/or
//          the hardware is installed and working.  Log in as superuser and
//          issue the cnxshow command.  Are all of the nodes in the cluster
//          listed?  Are they members of the cluster?  Is the communications
//          between nodes okay?  If the answer to any of these questions is
//          false, contact Digital's customer support organization.
04931, 00000, "unable to set initial sequence number value"
// *Cause: A call to the SSN failed to set the sequence number to its initial
//         value, possibly caused by an MC hardware problem.
// *Action: Verify that the MC hardware is functioning properly.  If it is
//          not, contact Digital's customer support organization.  If it is,
//          contact Oracle support.
04932, 00000, "increment or adjust of sequence number failed"
// *Cause: A call to the SSN failed to increment the sequence number.
// *Action: Verify that the MC hardware is functioning properly.  If it is
//          not, contact Digital's customer support organization.  If it is,
//          contact Oracle support.
04933, 00000, "initial service identifier is non-zero"
// *Cause: A valid service identifier existed before the sequence number
//         service was opened.
// *Action: Verify that the instance is completely shut down.
04934, 00000, "unable to obtain the current sequence number"
// *Cause: A call to the SSN failed to return its current value.
//         Either there are many errors occurring on the MC hardware,
//         or the sequence number has become invalid and cannot be
//         validated.
// *Action: Verify that the MC hardware is functioning properly.  If it
//          is, contact Oracle Support.
04935, 00000, "unable to get/convert SCN recovery lock"
// *Cause: A process has timed out trying to get or convert the SCN
//         recovery lock.  Another process probably has the lock in
//         EX or SHR mode, but is not releasing it.
// *Action: Contact Oracle Support.
04940, 00000, "unsupported optimization of Oracle binary, check alert log for more info"
// *Cause: ORACLE binary has been optimized with unsupported options or
//         a required option has not been used.
// *Action: Check the documentation for a list of supported and required flags
//          for the optimizing utility that you used to optimize ORACLE.
//          Shutdown the instance, optimize ORACLE again with supported
//          combination of options and restart the instance.
04941, 00000, "required operating system patch needs to be applied"
// *Cause: The operating system could not return the start time of a
//         process.
// *Action: Check that the operating system kernel has been patched
//          to return process start time. Apply the required operating
//          system patch and restart the instance.
06000, 00000, "NETASY: port open failure"
// *Cause:  Autologin unable to open port
// *Action: Check log file for OS-specific error code
06001, 00000, "NETASY: port set-up failure"
// *Cause:  Autologin unable to change port attributes
// *Action: Check log file for OS-specific error code
06002, 00000, "NETASY: port read failure"
// *Cause:  Autologin unable to read from port
// *Action: Check log file for OS-specific error code
06003, 00000, "NETASY: port write failure"
// *Cause:  Autologin unable to write to port
// *Action: Check log file for OS-specific error code
06004, 00000, "NETASY: dialogue file open failure"
// *Cause:  Autologin unable to open dialogue file
// *Action: Check connect string for accuracy/typos
06005, 00000, "NETASY: dialogue file read failure"
// *Cause:  Autologin unable to read dialogue file
// *Action: Check log file for OS-specific error code
06006, 00000, "NETASY: dialogue execute failure"
// *Cause:  Expected response never received
// *Action: None
06007, 00000, "NETASY: bad dialogue format"
// *Cause:  Dialogue file contains syntax error
// *Action: Correct the dialogue file
06009, 00000, "NETASY: dialogue filename too long"
// *Cause:  Full file spec for dialogue file exceeds 64 bytes
// *Action: Amend connect string accordingly
06010, 00000, "NETASY: dialogue file too long"
// *Cause:  Dialogue file exceeds 768 bytes in length
// *Action: Simplify dialogue (e.g. remove comments, redundant white space),
//          or split into two and link with "more" command
06011, 00000, "NETASY: dialogue too long"
// *Cause:  One of two:
//            1.  Dialogue contains more than 24 exchange blocks
//            2.  Dialogue send string exceeds 84 bytes in length
// *Action: Simplify dialogue or split into two and link with "more" command
06017, 00000, "NETASY: message receive failure"
// *Cause:  Async driver gets I/O error while doing network read operation
// *Action: Check log file for OS-specific error code and
//          contact your customer support representative.
06018, 00000, "NETASY: message send failure"
// *Cause:  Async driver gets I/O error while doing network write operation
// *Action: Check log file for OS-specific error code and
//          contact your customer support representative.
06019, 00000, "NETASY: invalid login (connect) string"
// *Cause:  Syntax error in login string.
// *Action: Resubmit with correct string.
06020, 00000, "NETASY: initialisation failure"
// *Cause:  Async driver unable to complete initialisation
// *Action: Check log file for OS-specific error code
06021, 00000, "NETASY: connect failed"
// *Cause:  Async driver unable to establish connection with partner
// *Action: Check log file for OS-specific error code
06022, 00000, "NETASY: channel open failure"
// *Cause:  no free channel [should never happen]
// *Action: Contact your customer support representative.
06023, 00000, "NETASY: port open failure"
// *Cause:  Async driver unable to open port
// *Action: Check log file for OS-specific error code
06024, 00000, "NETASY: VTM error"
// *Cause:  Virtual Terminal Manager unable to read/write to port
// *Action: Check log file for OS-specific error code
06025, 00000, "NETASY: Configuration error"
// *Cause:  Async driver genned for server-only, but client service requested
// *Action: Contact your customer support representative.
06026, 00000, "NETASY: port close failure"
// *Cause:  Async driver unable to close port
// *Action: Check log file for OS-specific error code
06027, 00000, "NETASY: channel close failure"
// *Cause:  Async driver unable to close channel
// *Action: Check log file for OS-specific error code
06028, 00000, "NETASY: unable to intialise for logging"
// *Cause:  Async driver unable to initialise for logging I/O
// *Action: Contact your customer support representative.
06029, 00000, "NETASY: port assignment failure"
// *Cause:  Async driver unable to assign port to channel [should never happen]
// *Action: Contact your customer support representative.
/
/       NETDNT: 6030-6049  SQL*Net DECnet Driver errors
/
06030, 00000, "NETDNT: connect failed, unrecognized node name"
// *Cause:  Node name specified in host string is unknown (probably misspelled)
// *Action: Retry with correct node name
06031, 00000, "NETDNT: connect failed, unrecognized object name"
// *Cause:  Host string contains reference to object (which doesn't exist):
//          @d:<node>-<obj> => object is ORDN<obj>;
//              when <node> is VMS, the object is ORDN<obj>.COM
//              when <node> is UNIX, the object is ORDN<obj>
//          @d:<node>::"task=<obj>" => object is <obj>;
//              when <node> is VMS, the object is <obj>.COM
//              when <node> is UNIX, the object is <obj>
// *Action: Retry with correct object name or create the required
//          object on host node
06032, 00000, "NETDNT: connect failed, access control data rejected"
// *Cause:  Host string contains invalid username/password
// *Action: Retry with correct username/password
06033, 00000, "NETDNT: connect failed, partner rejected connection"
// *Cause:  Connection with partner was made but was rejected.
// *Action: Contact your network administrator.
06034, 00000, "NETDNT: connect failed, partner exited unexpectedly"
// *Cause:  Connection with host node was made but partner aborted
// *Action: Make sure object (see 06031, above) is working (for VMS run the
//          command file and make sure that the ORACLE server process starts
//          up); sometimes happens when the network/node is under stress -
//          in this case a retry often works.
06035, 00000, "NETDNT: connect failed, insufficient resources"
// *Cause:  Insufficient system resources are available to complete the
//          connection; for example, all DECnet channels are in use.
// *Action: Contact your network administrator.
06036, 00000, "NETDNT: connect failed, no response from object"
// *Cause:
// *Action:
06037, 00000, "NETDNT: connect failed, node unreachable"
// *Cause:  Host node is down.
// *Action: Contact your network administrator.
06038, 00000, "NETDNT: connect failed, network driver not loaded"
// *Cause:
// *Action:
06039, 00000, "NETDNT: connect failed"
// *Cause:  Connect failed for unexpected reason (see OSD error).
// *Action: Contact your customer support representative.
06040, 00000, "NETDNT: invalid login (connect) string"
// *Cause:  Syntax error in login string.
// *Action: Resubmit with correct string.
06041, 00000, "NETDNT: disconnect failed"
// *Cause:  Driver gets error while doing network close operation
// *Action: Contact your customer support representative.
06042, 00000, "NETDNT: message receive failure"
// *Cause:  Driver gets I/O error while doing network read operation
// *Action: Contact your customer support representative.
06043, 00000, "NETDNT: message send failure"
// *Cause:  Driver gets I/O error while doing network write operation
// *Action: Contact your customer support representative.
06044, 00000, "NETDNT: connect failed, byte count quota exceeded"
// *Cause:  Connect failed because of insufficient byte count quota.
// *Action: Increase byte count quota.
/
/        NETTCP: 06100 - 6149  SQL*Net TCP/IP driver errors
/
/6100-6101  Reserved.
06102, 00000, "NETTCP: cannot allocate context area"
// *Cause:  Insufficient dynamic memory available for connection
//          context area.
// *Action: Contact your customer support representative.
/6103-6104  Reserved.
06105, 00000, "NETTCP: remote host is unknown"
// *Cause:  Host name specified in the login (connect) string is unknown.
// *Action: Check spelling; make sure name is in the TCP/IP HOST file.
06106, 00000, "NETTCP: socket creation failure"
// *Cause:  Process open file quota probably exceeded.
// *Action: Contact your customer support representative.
06107, 00000, "NETTCP: ORACLE network server not found"
// *Cause:  No entry in SERVICES file for ORACLE server.
// *Action: Add ("orasrv") entry to the TCP/IP SERVICES file.
06108, 00000, "NETTCP: connect to host failed"
// *Cause:  Connection attempt to remote host has failed. Probably means
//          that the SQL*Net TCP/IP server on the remote host is not up,
//          or the host itself is not up (check the latter by targeting
//          it with Telnet).
// *Action: Start the SQL*Net TCP/IP server process on the remote host.
06109, 00000, "NETTCP: message receive failure"
// *Cause:  I/O error occurred while attempting network read operation.
// *Action: Contact your customer support representative.
06110, 00000, "NETTCP: message send failure"
// *Cause:  I/O error occurred while attempting network write operation.
// *Action: Contact your customer support representative.
06111, 00000, "NETTCP: disconnect failure"
// *Cause:  Error occurred while closing a socket.
// *Action: Contact your customer support representative.
06112, 00000, "NETTCP: invalid buffer size"
// *Cause:  The buffer size specified in the login string exceeds the
//          allowed maximum (of 4096).
// *Action: Re-submit with valid buffer size.
06113, 00000, "NETTCP: Too many connections"
// *Cause:  The maximum no. of concurrently open connections has been reached.
// *Action: Exit an application with an open connection which is no longer
//          required.
06114, 00000, "NETTCP: SID lookup failure"
// *Cause:  From the remote host's SQL*Net TCP/IP server: the database SID,
//          specified in the login (connect) string, was not recognized.
// *Action: Add the appropriate SID entry to the CONFIG.ORA file on
//          the remote host (and restart the SQL*Net TCP/IP server).
06115, 00000, "NETTCP: unable to create ORACLE logicals"
// *Cause:  The host's SQL*Net TCP/IP server was unable to create the
//          necessary logicals required by the ORACLE server process.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your system administrator.
06116, 00000, "NETTCP: unable to create ORASRV process"
// *Cause:  The host's SQL*Net TCP/IP server was unable to create
//          the ORACLE server process.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your system administrator.
06117, 00000, "NETTCP: unable to create ORASRV: quota exceeded"
// *Cause:  The host's SQL*Net TCP/IP server was unable to create
//          the ORACLE server process because of quota depletion.
// *Action: Increase quota allocations to the SQL*Net TCP/IP
//          server process.
06118, 00000, "NETTCP: unable to complete handshake with ORASRV"
// *Cause:  The ORACLE server process was started but failed to
//          complete its initialization.
// *Action: Contact your customer support representative.
06119, 00000, "NETTCP: spurious client request"
// *Cause:  The host's SQL*Net TCP/IP server was unable to recognize
//          this connection request.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06120, 00000, "NETTCP: network driver not loaded"
// *Cause:  The TCP/IP network driver is not loaded.
// *Action: Check that the TCP/IP driver is loaded correctly.
06121, 00000, "NETTCP: access failure"
// *Cause:  The host's SQL*Net TCP/IP server was unable to test the
//          accessibility of the SID mapping file (specified in
//          CONFIG.ORA) associated with this connection request.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06122, 00000, "NETTCP: setup failure"
// *Cause:  The host's SQL*Net TCP/IP server was unable to set up
//          the appropriate environment to service this connection
//          request.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06123, 00000, "NETTCP: cannot set KEEPALIVE"
// *Cause:  The host's SQL*Net TCP/IP server was unable to set the
//          socket KEEPLIVE option.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06124, 00000, "NETTCP: timeout waiting for ORASRV"
// *Cause:  The ORACLE server process was started but failed to
//          respond after N secs.
// *Action: For heavily loaded systems this is not an uncommon
//          occurrence. Increase the value of N (the default is
//          30) by placing the following entry in the CONFIG.ORA
//          file:
//            SQLNET ORASRV_WAIT = <no. of secs>
//          which will come into effect the next time the SQL*Net
//          TCP/IP server is started.
06125, 00000, "NETTCP: ORASRV exited unexpectedly"
// *Cause:  The ORACLE server process was started but exited unexpectedly.
//          Possible causes:
//            1.  Insufficient quotas to run ORASRV
//            2.  ORACLE is not installed
//          See the ORASRV output file for more details; the file will be
//          in the ORA_SQLNET directory and will have a name of the form:
//            ORA_SRVTnn_<SID>.OUT
// *Action: If appropriate action is not obvious from the ORASRV output
//          file then contact your customer support representative.
06126, 00000, "NETTCP: ORASRV unable to open network connection"
// *Cause:  The ORACLE server process was started but was unable to
//          open the socket passed to it by TCPSRV.
// *Action: Contact your customer support representative.
06127, 00000, "NETTCP: unable to change username"
// *Cause:  The host's SQL*Net TCP/IP server could not establish a
//          PROXY LOGIN connection because the client username
//          is unknown (to the host OS).
// *Action: Create new user account on host.
06128, 00000, "NETTCP: unable to create mailbox"
// *Cause:  The host's SQL*Net TCP/IP server was unable to create a
//          mailbox (needed for IPC communication with the ORACLE
//          server process).
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06129, 00000, "NETTCP: unable to transfer socket ownership to ORASRV"
// *Cause:  The host's SQL*Net TCP/IP server was unable to transfer
//          the network communication handle to the ORACLE server
//          process.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06130, 00000, "NETTCP: host access denied"
// *Cause:  The host's SQL*Net TCP/IP server rejected this connection
//          request because the client node does not have access
//          privilege - as determined by the contents of the Valid
//          Node Table (VNT), a component of the host's CONFIG.ORA.
// *Action: To grant access, add appropriate entry to the host's VNT.
06131, 00000, "NETTCP: user access denied"
// *Cause:  The host's SQL*Net TCP/IP server rejected this connection
//          request because the client user(name) does not have access
//          privilege - as determined by the contents of the Username
//          Mapping Table (UMT), a component of the host's CONFIG.ORA.
// *Action: To grant access, add appropriate entry to the host's UMT.
06132, 00000, "NETTCP: access denied, wrong password"
// *Cause:  The host SQL*Net TCP/IP server rejected this connection
//          request because the client password did not match the host
//          password.
// *Action: To grant access, get passwords in sync.
06133, 00000, "NETTCP: file not found"
// *Cause:  The host's SQL*Net TCP/IP server could not find the SID
//          mapping file (specified in CONFIG.ORA) associated with
//          this connection request.
// *Action: Check CONFIG.ORA for spelling; make correct entry.
06134, 00000, "NETTCP: file access privilege violation"
// *Cause:  The host's SQL*Net TCP/IP server did not have READ/
//          EXECUTE permission for the SID mapping file (specified
//          in CONFIG.ORA) associated with this connection request.
// *Action: Change protection on SID mapping file.
06135, 00000, "NETTCP: connection rejected; server is stopping"
// *Cause:  The host's SQL*Net TCP/IP server rejected this connection
//          request because it is in the process of stopping.
// *Action: Re-start SQL*Net TCP/IP server.
06136, 00000, "NETTCP: error during connection handshake"
// *Cause:  Network I/O failure occurred while communicating with the
//          host's SQL*Net TCP/IP server.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06137, 00000, "NETTCP: error during connection handshake"
// *Cause:  Network I/O failure occurred while communicating with the
//          host's SQL*Net TCP/IP server.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06138, 00000, "NETTCP: error during connection handshake"
// *Cause:  Network I/O failure occurred while communicating with the
//          host's SQL*Net TCP/IP server.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
/6139       Reserved.
06140, 00000, "NETTCP: no such user"
// *Cause:  A proxy login connect attempt failed because the client
//          username has no counterpart on the host.
// *Action:
06141, 00000, "NETTCP: no privilege for user"
// *Cause:  A proxy login connect attempt failed because the
//          SQL*Net TCP/IP server had insufficient privileges
//          to access the proxy account.
// *Action: Change account protection; change server privilges.
06142, 00000, "NETTCP: error getting user information"
// *Cause:  A proxy login connect attempt failed because the
//          SQL*Net TCP/IP server was unable to access the
//          proxy account.
//          See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06143, 00000, "NETTCP: maximum connections exceeded"
// *Cause:  The connect failed because the maximum conncurrent
//          connections supported by the host's SQL*Net TCP/IP
//          server has already been reached.
// *Action: Wait for a short period and re-try.
06144, 00000, "NETTCP: SID (database) is unavailable"
// *Cause:  The database administrator on the host has varied
//          the SID offline.
// *Action: Wait for it to be varied back on-line.
06145, 00000, "NETTCP: unable to start ORASRV: images not installed"
// *Cause:  The host's SQL*Net TCP/IP server was unable to start
//          the ORACLE server process because the ORACLE protected
//          images were not installed.
// *Action: Install the images.
/6146-6149  Reserved.
/
/        TWOTASK: 06200 - 06219  VMS Two-Task driver errors
/
06200, 00000, "TWOTASK: connect failed, can't create mailbox"
// *Cause:
// *Action:
06201, 00000, "TWOTASK: connect failed, can't attach to mailbox"
// *Cause:
// *Action:
06202, 00000, "TWOTASK: connect failed, can't spawn ORASRV process"
// *Cause:
// *Action:
06203, 00000, "TWOTASK: connect failed, handshake failure"
// *Cause:
// *Action:
06204, 00000, "TWOTASK: connect failed, can't access ORASRV2.COM"
// *Cause:
// *Action:
06205, 00000, "TWOTASK: connect failed, can't create logical name"
// *Cause:
// *Action:
06206, 00000, "TWOTASK: message receive failure"
// *Cause:
// *Action:
06207, 00000, "TWOTASK: message send failure"
// *Cause:
// *Action:
06208, 00000, "TWOTASK: invalid login (connect) string"
// *Cause:
// *Action:
06209, 00000, "TWOTASK: connect failed, mailbox already exists"
// *Cause:
// *Action:
06210, 00000, "TWOTASK: connect failed, ORASRV exited unexpectedly"
// *Cause:
// *Action:
06211, 00000, "TWOTASK: connect failed, timeout waiting for ORASRV"
// *Cause:
// *Action:
06212, 00000, "TWOTASK: connect failed, logical name table is full"
// *Cause:
// *Action:
06213, 00000, "TWOTASK: connect failed"
// *Cause:
// *Action:
06214, 00000, "TWOTASK: connect failed, insufficient quotas to create ORASRV"
// *Cause:
// *Action:
06215, 00000, "TWOTASK: connect failed, ORASRV protected image not installed"
// *Cause:
// *Action:
06216, 00000, "TWOTASK: connect failed, can't find ORASRV image file"
// *Cause:
// *Action:
/6217-6219  Reserved.
/
/        NETNTT: 6250 - 6274  SQL*Net nCUBE Two-Task errors
/
06250, 00000, "NETNTT: cannot allocate send and receive buffers"
// *Cause:   Two-task driver could not allocate data buffers.
// *Action:  There is insufficient memory to run your program.  Kill
//           off other processes to free up memory.
06251, 00000, "NETNTT: cannot translate address file name"
// *Cause:   ORACLE_HOME environment variable not set.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//           properly set and exported.
06252, 00000, "NETNTT: cannot open address file"
// *Cause:   The NTT two-task driver could not open a file containing
//           address information.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//           properly set and exported.  Make sure the instance you are
//           attempting to connect to is actually up and running.
06253, 00000, "NETNTT: cannot read arguments from address file"
// *Cause:   The NTT two-task driver could not read addressing information
//           from its addressing file.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//           properly set and exported.  Make sure the instance you are
//           attempting to connect to is actually up and running.
06254, 00000, "NETNTT: cannot share connection to cube"
// *Cause:   The NTT two-task driver could not share a connection to the cube.
// *Action:  Make sure that the ORACLE_HOME environment variable has been
//           properly set and exported.  Make sure the instance you are
//           attempting to connect to is actually up and running.
06255, 00000, "NETNTT: cannot read pid of remote process"
// *Cause:   An error occurred while reading the NTT communications link.
// *Action:  Contact your customer support representative.
06256, 00000, "NETNTT: remote fork failed"
// *Cause:   The Oracle listener process on the cube could not fork off
//           a shadow process.
// *Action:  The instance you are trying to connect to probably doesn't
//           have enough memory to run another shadow process.  Ask someone
//           else to log off, or connect to a different instance.
06257, 00000, "NETNTT:  cannot send command line to shadow process"
// *Cause:   An error occurred while writing the NTT communications link.
// *Action:  Contact your customer support representative.
06258, 00000, "NETNTT: cannot allocate context area"
// *Cause:   Two-task driver could not allocate data buffers.
// *Action:  There is insufficient memory to run your program.  Kill
//           off other processes to free up memory.
06259, 00000, "NETNTT: cannot read from remote process"
// *Cause:   An error occurred while reading the NTT communications link.
// *Action:  Contact your customer support representative.
06260, 00000, "NETNTT: cannot write to remote process"
// *Cause:   An error occurred while writing the NTT communications linke.
// *Action:  Contact your customer support representative.
06261, 00000, "NETNTT: nrange() failed"
// *Cause:   The call to 'nrange()' failed while attempting to establish
//           a connection.
// *Action:  Contact your customer support representative.
06262, 00000, "NETNTT: nfconn() failed"
// *Cause:   The call to 'nfconn()' failed while attempting to establish
//           a connection.
// *Action:  Contact your customer support representative.
06263, 00000, "NETNTT: out of memory in pi_connect"
// *Cause:   Two-task driver could not allocate data buffers.
// *Action:  There is insufficient memory to run your program.  Kill
//           off other processes to free up memory.
06264, 00000, "NETNTT: data protocol error"
// *Cause:   The NTT two-task driver received an unexpected message type."
// *Action:  Contact your customer support representative.
06265, 00000, "NETNTT: break protocol error"
// *Cause:   The NTT two-task driver received an unexpected message type."
// *Action:  Contact your customer support representative.
06266, 00000, "NETNTT: bad write length"
// *Cause:   The NTT two-task driver failed on an internal consistency
//           check.
// *Action:  Contact your customer support representative.
06267, 00000, "NETNTT: bad state"
// *Cause:   The NTT two-task driver failed on an internal consistency
//           check.
// *Action:  Contact your customer support representative.
06268, 00000, "NETNTT: cannot read /etc/oratab"
// *Cause:   The NTT two-task driver could not read configuration information
//           from /etc/oratab.
// *Action:  Make sure /etc/oratab exists and is readable.  This error may
//           occur if the file is incorrectly formatted.  It also may occur
//           if the driver has run out of memory.
/6268-6274   Reserved
/
/        IPA: 6300 - 6323  SQL*Net IPA errors
/
06300, 00000, "IPA: Disconnect failure"
// *Cause:  A fatal error occurred during the disconnect from the server.
//          This was probably caused by inaccessible message queues.
// *Action: If there is no message queue, restart the SQL*Net IPA servers
//          using ipactl. Otherwise contact your customer support
//          representative.
06301, 00000, "IPA: Cannot allocate driver context"
// *Cause:  The memory pool is exhausted.
// *Action: Check the circumstances and try to allocate less memory in your
//          program or adjust the init parameters in your INIT.ORA file and
//          retry.
06302, 00000, "IPA: Cannot connect to remote host"
// *Cause:   The cause may be one of the following:
//           - there is no ADI server defined to reflect a connection to the
//             specified host.
//           - the remote host is not known by the local system.
//           - the ORACLE kernel on the remote host is not generated with the
//             IPA driver
// *Action:  Check sequentially for the above causes and eliminate the actual
//           cause found.
06303, 00000, "IPA: Message send error"
// *Cause:  The SQL*Net IPA driver could not write the message into the
//          message queue.
// *Action: Make sure that the message queue exists and is accessible.
//          If necessary rerun ipactl.
06304, 00000, "IPA: Message receive error"
// *Cause:  The SQL*Net IPA driver could not read a message from the message
//        queue.
// *Action: Make sure that the message queue exists and is accessible.
//          If necessary rerun ipactl.
06305, 00000, "IPA: Illegal message type"
// *Cause:  The communication between user and ORACLE is out of
//          synchronization. This message should not normally be issued.
// *Action: Contact your customer support representative.
06306, 00000, "IPA: Message write length error"
// *Cause:  The IPA driver tried to write a message in the queue that was
//          too big for the queue.
// *Action: Contact your customer support representative.
06307, 00000, "IPA: Cannot reset connection"
// *Cause:  A fatal error occurred during the resetting of the connection.
// *Action: Contact your customer support representative.
06308, 00000, "IPA: No more connections available"
// *Cause:  You have exhausted all your connections.
// *Action: Try again when some of the current users have logged off.
06309, 00000, "IPA: No message queue available"
// *Cause:  The SQL*Net IPA servers have not been started.
// *Action: Run ipactl.
06310, 00000, "IPA: Environment variable(s) not set"
// *Cause:  Environment variable(s) not set correctly.
// *Action: Check and correct.
06311, 00000, "IPA: Maximum number of servers reached"
// *Cause:  Maximum number of servers reached.
// *Action: Shutdown and restart with an increased maximum number of servers.
//          Note that database links consume one server per link. Be sure
//          to start up enough servers to support database links.
06312, 00000, "IPA: Incorrect outgoing service name supplied"
// *Cause:  Incorrect outgoing service name supplied.
// *Action: Check and correct the service name.
06313, 00000, "IPA: Shared memory failed to initialise"
// *Cause:  The shared memory has not been set up correctly.
// *Action: Contact your system manager.
06314, 00000, "IPA: Event set up failure"
// *Cause:  Fatal interprocess communication error.
// *Action: Contact your system manager.
06315, 00000, "IPA: Invalid connect string"
// *Cause:  The connect string is malformed.
// *Action: Check and correct.
06316, 00000, "IPA: Invalid database SID"
// *Cause:  The SID is unknown at the remote side.
// *Action: Either the database does not exist, is not running, or
//          there are no reserved servers for that SID.
06317, 00000, "IPA: Local maximum number of users exceeded"
// *Cause:  The maximum number of simultaneous users of SQL*Net IPA has been
//          exceeded on the local side.
// *Action: Wait for free connections to become available.  If the problem
//          persists, contact your system manager.
06318, 00000, "IPA: Local maximum number of connections exceeded"
// *Cause:  The maximum number of simultaneous connections that SQL*Net IPA
//          can handle to different hosts has been exceeded on the local side.
// *Action: Wait for free connections to become available.  If the problem
//          persists, contact your system manager.
06319, 00000, "IPA: Remote maximum number of users exceeded"
// *Cause:  The maximum number of simultaneous users of SQL*Net IPA has been
//          exceeded on the remote side.
// *Action: Wait for free connections to become available.  If the problem
//          persists, contact your system manager.
06320, 00000, "IPA: Remote maximum number of connections exceeded"
// *Cause:  The maximum number of simultaneous connections that SQL*Net IPA
//          can handle from different hosts has been exceeded on the remote
//          side.
// *Action: Wait for free connections to become available.  If the problem
//          persists, contact your system manager.
06321, 00000, "IPA: Cannot reach the remote side"
// *Cause:  There has been a timeout on an attempt to connect to a remote
//          server the reason for which is most likely to be the remote
//          SQL*Net IPA software is not running. An alternative reason
//          could be that the remote initiator service name is incorrect.
// *Action: Check and start the remote SQL*Net software. Check that it is
//          started with the correct service names supplied.
06322, 00000, "IPA: Fatal shared memory error"
// *Cause:  An internal error has occurred in the shared memory handling.
// *Action: Contact customer support.
06323, 00000, "IPA: Cause event error"
// *Cause:  Fatal interprocess communication error.
// *Action: Contact your system manager.
/
/        NETCMN: 6400 - 6429  SQL*Net CoMmoN errors
/
06400, 00000, "NETCMN: No default host string specified"
// *Cause: There was no default host string specified in the configuration
//         and the user didn't specify any explicit connect string.
// *Action: Either reconfigure the system specifying a default connect string
//          or use an explicit connect string.
06401, 00000, "NETCMN: invalid driver designator"
// *Cause:  The login (connect) string contains an invalid driver designator.
// *Action: Correct the string and re-submit.
06402, 00000, "NETCMN: error receiving break message"
// *Cause:  Error occurred while attempting to read a break message.
// *Action: Contact your customer support representative.
06403, 00000, "Unable to allocate memory."
// *Cause:  System unable to allocate needed virtual memory.
// *Action: Configure more memory, reduce load, or simply try again.
06404, 00000, "NETCMN: invalid login (connect) string"
// *Cause:  Syntax error in login string.
// *Action: Correct string and re-submit.
06405, 00000, "NETCMN: reset protocol error"
// *Cause:  Unable to reset out of break state.
// *Action: Contact your customer support representative.
06406, 00000, "NETCMN: error sending break message"
// *Cause:  Error occurred while attempting to send a break message.
// *Action: Contact your customer support representative.
06407, 00000, "NETCMN: unable to set up break handling environment"
// *Cause:  Error occurred while attempting to set up asynchronous
//          handlers for in-coming, out-of-band break messages.
// *Action: Contact your customer support representative.
06408, 00000, "NETCMN: incorrect message format"
// *Cause:  Message from partner contains bad header.
// *Action: Contact your customer support representative.
/6409-6412  Reserved.
06413, 00000, "Connection not open."
// *Cause:  Unable to establish connection.
// *Action: Use diagnostic procedures to ascertain exact problem.
/6414-6415  Reserved.
06416, 00000, "NETCMN: error on test"
// *Cause:  Error occurred while testing I/O status of the network connection.
// *Action: Contact your customer support representative.
/6417-6429  Reserved.
/6418  Unused
06419, 0000, "NETCMN: server can not start oracle"
// *Cause:  The remote server was unable to start an ORACLE process on
//          behalf of the client.
// *Action: Make sure permissions on the remote ORACLE program are correctly
//          set. Contact your system administrator.
06420, 0000, "NETCMN: SID lookup failure"
// *Cause:  From the remote host's server: the database SID,
//          specified in the login (connect) string, was not recognized.
// *Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file
//          on the remote host (restarting the remote server may be needed).
06421, 0000, "NETCMN: Error detected in the read-in data"
// *Cause:  Error found during recomputation of checksum or CRC.
// *Action: Possible hardware failures of communication nodes.
//          Contact system administrator immediately.
06422, 0000, "NETCMN: Error in sending data"
// *Cause:  Unable to transmit data to remote host.
// *Action: Try reconnect to remote host, and contact your system
//          administrator.
06423, 0000, "NETCMN: Error in receiving  data"
// *Cause:  Unable to receive data from remote host.
// *Action: Try reconnect to remote host, and contact your system
//          administrator.
/
/       6430-6449 Reserved for NCR System 3000
/
06430, 0000, "ssaio: Seals do not match"
// *Cause:  A function was called with an invalid argument.
// *Action: Contact your Oracle Customer Support Representative.
06431, 0000, "ssaio: Invalid Block number"
// *Cause:  The file block number is out of range of the file. The additional
//          information returns the block number.
// *Action: Verify that the block number is correct. Run dbfsize and check if
//          the block number is in that range. Contact your Oracle Customer
//          Support Representative.
06432, 0000, "ssaio: Buffer Not Aligned"
// *Cause:  The I/O buffer was not aligned on a 2K boundary.
// *Action: Contact your Oracle Customer Support Representative.
06433, 0000, "ssaio: LSEEK error, unable to seek to requested block."
// *Cause:  The additional information returns the block number
// *Action: Look up the additional information returned in your operating
//          system reference manual. Verify that the block number is correct.
06434, 0000, "ssaio: read error, unable to read requested block from database file."
// *Cause:  The read system call returned an error.
// *Action: The additional information indicates the block number. Look up
//          the additional information returned in your operating system
//          manual.
06435, 0000, "ssaio: write error, unable to write requested block to database file."
// *Cause:  The write system call returned an error.
// *Action: The additional information indicates the block number. Look up
//          the additional information returned in your operating system
//          manual.
06436, 0000, "ssaio: asynchronous I/O failed due to incorrect parameters."
// *Cause:  The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
//          the additional information returned in your operating system
//          manual.
06437, 0000, "ssaio: the asynchronous write was unable to write to the database file."
// *Cause:  The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
//          the additional information returned in your operating system
//          manual.
06438, 0000, "ssaio: the asynchronous read was unable to read from the database file."
// *Cause:  The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
//          the additional information returned in your operating system
//          manual.
06439, 0000, "ssaio: the asynchronous write returned incorrect number of bytes"
// *Cause:  This write call may have been truncated. The additional
//          information returns the block number and number of bytes.
// *Action: Verify that the block number and the number of bytes written are
//          correct.
06440, 0000, "ssaio: the asynchronous read returned incorrect number of bytes"
// *Cause:  This read call may have been truncated. The additional
//          information returns the block number and number of bytes.
// *Action: Verify that the block number and the number of bytes read are
//          correct.
06441, 0000, "ssvwatev: Incorrect parameter passed to function call"
// *Cause:  Either the ORACLE process id, or wait time or event ID is invalid.
// *Action: The additional information indicates the process id, time and
//          event id.
06442, 0000, "ssvwatev: Failed with unexpected error number."
// *Cause:  Some system problems may exists on your system, please check
//          error logs.
// *Action: The additional information indicates the error number. Look up
//          the additional information returned in your operating system
//          manual.
06443, 0000, "ssvpstev: Incorrect parameter passed to function call"
// *Cause:  An invalid event ID is passed in to this routine.
// *Action: The additional information indicates the event id.
06444, 0000, "ssvpstev: Failed with unexpected error number."
// *Cause:  Some system problems may exist on your system, please check error
//          logs.
// *Action: The additional information indicates the error number. Look up
//          the additional information returned in your operating system
//          manual.
06445, 0000, "ssvpstevrg: Incorrect parameters passed to function call"
// *Cause:  An invalid event id, or the low and high event ID do not exist.
// *Action: The additional information indicates the error number. It also
//          contains the event id, low boundary and high boundary.
06446, 0000, "ssvpstevrg: Failed with unexpected error number."
// *Cause:  Some system problems may exist on your system, please check error
//          logs.
// *Action: The additional information indicates the error number. Look up
//          the additional information returned in your operating system
//          manual.
06447, 0000, "ssvpstp: Incorrect parameter passed to function call"
// *Cause:  Invalid oracle process ID is passed in to this routine.
// *Action: The additional information indicates the process id.
06448, 0000, "ssvpstp: Failed with unexpected error number."
// *Cause:  Some system problems may exists on your system, please check
//          error logs.
// *Action: The additional information indicates the error number. Look up
//          the additional information returned in your operating system
//          manual.
06449, 0000, "The list IO or the sysvendor is not installed."
// *Cause:  ORACLE tries to use the sysvendor interface (INIT.ORA parameter
//          use_sysvendor=true) but the UNIX kernel does not have the ORACLE
//          sysvendor interface linked in.
// *Action: Set use_sysvendor=false in INIT.ORA, if you don't want to use
//          this interface or link the UNIX kernel with this interface so
//          that ORACLE can use it.
/
/       6500-6599 PL/SQL Errors
/
/       6500-6539 are signalled by PL/SQL and owned by PL/SQL's peiexc.h
/       file.  6540-6549 are signalled by PL/SQL and are used for PL/SQL
/       error handling and appear in pcmdef.h.  6550-6599 are used by the
/       RDBMS to signal PL/SQL related errors and do not appear in PL/SQL's
/       peiexc.h file.
/
06500, 00000, "PL/SQL: storage error"
// *Cause: PL/SQL was unable to allocate additional storage.  This message 
//         normally appears with an ORA-4030 or ORA-4031 error which gives 
//         additional information.  Sometimes this error can be caused by 
//         runaway programs. 
// *Action: 1) Ensure there are no issues or bugs in your PL/SQL program which 
//             are causing excessive amounts of memory to be used.
//          2) Programmatically cause unused objects to be freed (e.g. by
//             setting them to NULL).
//          3) Increase the amount of shared or process memory (as appropriate)
//             available to you.
06501, 00000, "PL/SQL: program error"
// *Cause: This is an internal error message. An error has been detected in a
//         PL/SQL program. 
// *Action: Contact Oracle Support Services.
06502, 00000, "PL/SQL: numeric or value error%s"
// *Cause: An arithmetic, numeric, string, conversion, or constraint error
//         occurred. For example, this error occurs if an attempt is made to
//         assign the value NULL to a variable declared NOT NULL, or if an
//         attempt is made to assign an integer larger than 99 to a variable
//         declared NUMBER(2).   
// *Action: Change the data, how it is manipulated, or how it is declared so
//          that values do not violate constraints. 
06503, 00000, "PL/SQL: Function returned without value"
// *Cause: A call to PL/SQL function completed, but no RETURN statement was
//         executed.
// *Action: Rewrite PL/SQL function, making sure that it always returns
//          a value of a proper type.
06504, 00000, "PL/SQL: Return types of Result Set variables or query do not match"
// *Cause: Number and/or types of columns in a query does not match declared
//         return type of a result set  variable, or declared types of two Result
//         Set variables do not match.
// *Action: Change the program statement or declaration. Verify what query the variable
//          actually refers to during execution.
06505, 00000, "PL/SQL: variable requires more than 32767 bytes of contiguous memory"
// *Cause: A PL/SQL variable was declared with a constraint which required more
//         than 32767 bytes of memory.
//         PL/SQL does not currently support allocations of contiguous memory
//         greater than 32767 bytes.
// *Action: Consider reducing the constraint in the variable declaration.
//          If that is not possible, try changing the database or national
//          character set to such, that requires less memory for the same
//          constraint. Note: changing the character set will impact execution
//          of all PL/SQL code.
06508, 00000, "PL/SQL: could not find program unit being called%s"
// *Cause:
// *Action:
06509, 00000, "PL/SQL: ICD vector missing for this package"
// *Cause:
// *Action:
06510, 00000, "PL/SQL: unhandled user-defined exception"
// *Cause:   A user-defined exception was raised by PL/SQL code, but
//           not handled.
// *Action:  Fix the problem causing the exception or write an exception
//           handler for this condition. Or you may need to contact your
//           application administrator or DBA.
06511, 00000, "PL/SQL: cursor already open"
// *Cause:   An attempt was made to open a cursor that was already open.
// *Action:  Close cursor first before reopening.
06512, 00000, "at %sline %s"
// *Cause:   Backtrace message as the stack is unwound by unhandled
//           exceptions.
// *Action:  Fix the problem causing the exception or write an exception
//           handler for this condition. Or you may need to contact your
//           application administrator or DBA.
06513, 00000, "PL/SQL: index for PL/SQL table out of range for host language array"
// *Cause: An attempt is being made to copy a PL/SQL table to a host language
//         array.  But an index in the table is either less than one or
//         greater than the maximum size of the host language array.
//         When copying PL/SQL tables to host language arrays, the table
//         entry at index 1 is placed in the first element of the array, the
//         entry at index 2 is placed in the second element of the array, etc.
//         If an table entry has not been assigned then the corresponding
//         element in the host language array is set to null.
// *Action: Increase size of host language array, or decrease size of PL/SQL
//         table.  Also make sure that you don't use index values less than 1.
//
06514, 00000, "PL/SQL: The remote call cannot be handled by the server"
// *Cause:  The remote call has parameters that are cursor variables or
//          lob variables. This cannot be handled by stored procedures on
//          your server.
// *Action: Avoid using cursor variables or lob variables as parameters for
//          stored procedures on this server or upgrade your server to a
//          version that supports this.
06515, 00000, "PL/SQL: unhandled exception %s"
// *Cause:   An exception was raised by PL/SQL code, but not handled.
//           The exception number is outside the legal range of Oracle
//           errors.
// *Action:  Fix the problem causing the exception or write an exception
//           handler for this condition. Or you may need to contact your
//           application administrator or DBA.
// *Comment: The exception was created via a pragma exception_init with a
//           value larger than MAX_OEN. This capability exists for backward
//           compatibility with V1 PL/SQL.
06516, 00000, "PL/SQL: the Probe packages do not exist or are invalid"
// *Cause:   A Probe operation, probably an attempt to initialize the ORACLE
//           server to debug PL/SQL, could not be completed because the
//           Probe packages were not loaded or have become invalid.
// *Action:  DBA should load the Probe packages. This can be done by running
//           the pbload.sql script supplied with the RDBMS.
// *Comment: catproc.sql should load Probe by default, but it did not do so
//           in releases prior to 7.3.3.
//
06517, 00000, "PL/SQL: Probe error - %s"
// *Cause:   An error occurred while passing a Probe operation to the server
//           for execution.
// *Action:  Refer to the entry for the embedded error message.
// *Comment: The error is most likely a UPI or network problem. The Probe
//           error is just to let the user know how the error arose.
06518, 00000, "PL/SQL: Probe version %s incompatible with version %s"
// *Cause:   The current version of Probe is incompatible with the version on
//           the ORACLE server.
// *Action:  Refer to the documentation to ensure that this degree of
//           compatibility is supported.
// *Comment: This error is not currently expected. It will only occur at a
//           later time if incompatible Probe changes are introduced.
06519, 00000, "active autonomous transaction detected and rolled back"
// *Cause:   Before returning from an autonomous PL/SQL block, all autonomous
//           transactions started within the block must be completed (either
//           committed or rolled back). If not, the active autonomous
//           transaction is implicitly rolled back and this error is raised.
// *Action:  Ensure that before returning from an autonomous PL/SQL block,
//           any active autonomous transactions are explicitly committed
//           or rolled back.
//-----------------------------------------------------------------------
//
// 06520 through 06529 reserved for Foreign function errors
//
//
06520, 00000, "PL/SQL: Error loading external library"
// *Cause:  An error was detected by PL/SQL trying to load the external
//          library dynamically.
// *Action: Check the stacked error (if any) for more details.
//
06521, 00000, "PL/SQL: Error mapping function"
// *Cause:  An error was detected by PL/SQL trying to map the mentioned
//          function dynamically.
// *Action: Check the stacked error (if any) for more details.
//
06522, 00000, "%s"
// *Cause:  ORA-06520 or ORA-065211 could stack this error with
//          a system specific error string.
// *Action: This error string should give the cause for errors
//          ORA-06520 or ORA-065211
//
06523, 00000, "Maximum number of arguments exceeded"
// *Cause:  There is an upper limit on the number of arguments that one
//          can pass to the external function.
// *Action: Check the port specific documentation on how to calculate the
//          upper limit.
//
06524, 00000, "Unsupported option : %s"
// *Cause:  The option specified is an unsupported feature for external procedures.
//
// *Action: Correct the syntax in the external specification
//
06525, 00000, "Length Mismatch for CHAR or RAW data"
// *Cause:  The length specified in the length variable has an illegal
//          value. This can happen if you have requested requested a PL/SQL
//          INOUT, OUT or RETURN raw variable to be passed as a RAW with
//          no corresponding length variable. This error can also happen
//          if there is a mismatch in the length value set in the length
//          variable and the length in the orlvstr or orlraw.
//
// *Action: Correct the external procedure code and set the length variable
//          correctly.
//
06526, 00000, "Unable to load PL/SQL library"
// *Cause:  PL/SQL was unable to instantiate the library referenced by this
//          referenced in the EXTERNAL syntax. This is a serious error and
//          should normally not happen.
//
// *Action: Report this problem to customer support.
//
06527, 00000, "External procedure SQLLIB error: %s"
// *Cause:  An error occurred in sqllib during execution of a Pro* external
//          procedure.
//
// *Action: The message text indicates the actual SQLLIB error that
//          occurred.  Consult the Oracle Error Messages and Codes manual
//          for a complete description of the error message and follow
//          the appropriate action.
//
06528, 00000, "Error executing PL/SQL profiler"
// *Cause:  An error occurred in during execution of a PL/SQL profiler
//          procedure.
//
// *Action: Check the stacked errors for more details.
//
06529, 00000, "Version mismatch - PL/SQL profiler"
// *Cause:  The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not
//          match the version of the code in the server implementing the
//          profiler.
//
// *Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load
//          the correct version of the PL/SQL profiler packages
//
06530, 00000, "Reference to uninitialized composite"
// *Cause:  An object, LOB, or other composite was referenced as a
//          left hand side without having been initialized.
// *Action: Initialize the composite with an appropriate constructor
//          or whole-object assignment.
//
06531, 00000, "Reference to uninitialized collection"
// *Cause:  An element or member function of a nested table or varray
//          was referenced (where an initialized collection is needed)
//          without the collection having been initialized.
// *Action: Initialize the collection with an appropriate constructor
//          or whole-object assignment.
//
06532, 00000, "Subscript outside of limit"
// *Cause:  A subscript was greater than the limit of a varray
//          or non-positive for a varray or nested table.
// *Action: Check the program logic and increase the varray limit
//          if necessary.
//
06533, 00000, "Subscript beyond count"
// *Cause:  An in-limit subscript was greater than the count of a varray
//          or too large for a nested table.
// *Action: Check the program logic and explicitly extend if necessary.
//
06534, 00000, "Cannot access Serially Reusable package %s"
// *Cause:   The program attempted to access a Serially Reusable package in
//           PL/SQL called from SQL context (trigger or otherwise). Such an
//           access is currently unsupported.
// *Action:  Check the program logic and remove any references to Serially Reusable
//           packages (procedure, function or variable references) which might happen
//           in PL/SQL called from  sql context (trigger or otherwise).
//
06535, 00000, "statement string in %s is NULL or 0 length"
// *Cause:   The program attempted to use a dynamic statement string that
//           was either NULL or 0 length.
// *Action:  Check the program logic and ensure that the dynamic statement
//           string is properly initialized.
//
06536, 00000, "IN bind variable bound to an OUT position"
// *Cause:   The program attempted to bind an IN bind variable to a
//           statement that was expecting an OUT bind variable at
//           that position.
// *Action:  Make sure that an OUT or IN OUT bind mode is specified
//           for the bind argument.
//
06537, 00000, "OUT bind variable bound to an IN position"
// *Cause:   The program attempted to bind an OUT bind variable to a
//           statement that was expecting an IN bind variable at
//           that position.
// *Action:  Make sure that an IN or IN OUT bind mode is specified
//           for the bind argument.
//
06538, 00000, "statement violates %s RESTRICT_REFERENCES pragma"
// *Cause:   The program attempted to execute a dynamic statement which
//           does not meet the purity level specified (in the pragma
//           RESTRICT_REFERENCES directive) for the module executing the
//           statement.
// *Action:  Ensure that the dynamic statement meets the purity level
//           specified for the module executing the statement.
//
06539, 00000, "target of OPEN must be a query"
// *Cause:   The program attempted to perform an OPEN cursor operation
//           on a dynamic statement that was not a query.
// *Action:  Ensure that the OPEN cursor operation is done on a
//           dynamic query statement.
//
//--------------------------------------------------------
// 06540 through 06549 reserved for pl/sql error handling
//
06540, 00000, "PL/SQL: compilation error"
// *Cause: A pl/sql compilation error occurred.
//         However, the user generally will not see this error message.
//         Instead, there will be accompanying PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06541, 00000, "PL/SQL: compilation error - compilation aborted"
// *Cause: A pl/sql compilation error occurred and the compilation was aborted;
//         but the compilation unit was written out to the backing store.
//         However, unlike ora-06545, the user generally will not see this error
//         message. Instead, there will be accompanying PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06542, 00000, "PL/SQL: execution error"
//  Currently unused.  Reserved for future use.
//
06543, 00000, "PL/SQL: execution error - execution aborted"
//
//
06544, 00000, "PL/SQL: internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: A pl/sql internal error occurred.
// *Action:Report as a bug; the first argument is the internal error nuber.
//
06545, 00000, "PL/SQL: compilation error - compilation aborted"
// *Cause: A pl/sql compilation error occurred and the compilation was
//         aborted completely without the compilation unit being written
//         out to the backing store.  Unlike ora-06541, the user will always
//         see this error along with the accompaning PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06546, 00000, "DDL statement is executed in an illegal context"
// *Cause: DDL statement is executed dynamically in illegal PL/SQL context.
//         - Dynamic OPEN cursor for a DDL in PL/SQL
//         - Bind variable's used in USING clause to EXECUTE IMMEDIATE a DDL
//         - Define variable's used in INTO clause to EXECUTE IMMEDIATE a DDL
// *Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute
//          the DDL statement.
06547, 00000, "RETURNING clause must be used with INSERT, UPDATE, or DELETE statements"
// *Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute
//         dynamic UPDATE, INSERT, or DELETE statements only.
// *Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE,
//          or DELETE statements only.  For other statements, use USING clause
//          instead.
06548, 00000, "no more rows needed"
// *Cause:   The caller of a pipelined function did not need more rows
//           to be produced by the pipelined function.
// *Action:  Do not catch the NO_DATA_NEEDED exception in an exception handling
//           block.
//
06549, 00000, "PL/SQL: failed to dynamically open shared object (DLL): %s:%s"
// *Cause:   One possible cause might be there are too many DLLs open at the
//           same time.
// *Action:
//
//--------------------------------------------------------
//
06550, 00000, "line %s, column %s:\n%s"
// *Cause:  Usually a PL/SQL compilation error.
// *Action:
06551, 00000, "PL/SQL: Unhandled exception"
// *Cause:
// *Action:
06552, 00000, "PL/SQL: %s"
// *Cause:
// *Action:
06553, 00000, "PLS-%s: %s"
// *Cause:
// *Action:
06554, 00000, "package DBMS_STANDARD must be created before using PL/SQL"
// *Cause:    The DBMS specific extensions to PL/SQL's package "STANDARD"
//            are in package "DBMS_STANDARD".  This package must be
//            created before using PL/SQL.
// *Action:   Create package "DBMS_STANDARD".  The source for this
//            PL/SQL stored package is provided with the distribution.
06555, 00000, "this name is currently reserved for use by user SYS"
// *Cause:    You tried to create a package named "STANDARD",
//            "DBMS_STANDARD" or "DEBUG_IO".  These are currently
//            reserved for use by user SYS.
// *Action:   Choose another name for your package.
06556, 00000, "the pipe is empty, cannot fulfill the unpack_message request"
// *Cause:    There are no more items in the pipe.
// *Action:   Check that the sender and receiver agree on the number and types
//            of items placed on the pipe.
06557, 00000, "null values are not allowed for any parameters to pipe icd's"
// *Cause:    Internal error from the dbms_pipe package.
// *Action:
06558, 00000, "buffer in dbms_pipe package is full.  No more items allowed"
// *Cause:    The pipe buffer size has been exceeded.
// *Action:
06559, 00000, "wrong datatype requested, %s, actual datatype is %s"
// *Cause:    The sender put different datatype on the pipe than that being
//            requested (package 'dbms_pipe').  The numbers are: 6 - number,
//            9 - char, 12 - date.
// *Action:   Check that the sender and receiver agree on the number and types
//            of items placed on the pipe.
06560, 00000, "pos, %s, is negative or larger than the buffer size, %s"
// *Cause:    Internal error from the dbms_pipe package.
// *Action:
06561, 00000, "given statement is not supported by package DBMS_SQL"
// *Cause:  Attempting to parse an unsupported statement using procedure
//          PARSE provided by package DBMS_SQL.
// *Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE,
//          LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported.
06562, 00000, "type of out argument must match type of column or bind variable"
// *Cause:  Attempting to get the value of a column or
//          a bind variable by calling procedure COLUMN_VALUE or
//          VARIABLE_VALUE of package DBMS_SQL but the type of
//          the given out argument where to place the value is different
//          from the type of the column or bind variable that was previously
//          defined by calling procedure DEFINE_COLUMN (for defining a column)
//          or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.
// *Action: Pass in an out argument of the correct type when calling
//          procedure COLUMN_VALUE or VARIABLE_VALUE.  The right
//          type is the type that was provided when defining the column or
//          binding the bind variable.
06563, 00000, "name has too many parts"
// *Cause:  The name to be resolved was specified as one of the following:
//          - With three parts (A.B.C) but the A.B parts resolved to an object
//            that did not expose visible nested procedures; the C part could
//            not be resolved.
//          - With two parts (A.B) and the A part resolved to an object that
//            did not expose visible nested procedures; the B part could not be
//            resolved.
// *Action: Specify the valid name of an object or of a packaged procedure
//          or function without specifying any additional trailing parts.
06564, 00000, "object %s does not exist"
// *Cause:  The named object could not be found.  Either it does not exist
//          or you do not have permission to access it.
// *Action: Create the object or get permission to access it.
06565, 00000, "cannot execute %s from within stored procedure"
// *Cause:  The named procedure cannot be executed from within a stored
//          procedure, function or package.  This function can only be
//          used from pl/sql anonymous blocks.
// *Action: Remove the procedure from the calling stored procedure.
06566, 00000, "invalid number of rows specified"
// *Cause:  An invalid number of rows was specified in a call to the
//          procedure DEFINE_COLUMN in the package DBMS_SQL. For a given
//          parsed statement in a given cursor, all columns must be
//          defined to have the same number of rows, so all the calls
//          to DEFINE_COLUMN must specify the same number of rows.
// *Action: Specify a number that matches that for previously defined
//          columns.
06567, 00000, "invalid number of values specified"
// *Cause:  An invalid number of values to be bound was specified in a
//          call to the procedure BIND_VARIABLE in the package DBMS_SQL.
//          In order to execute a given parsed statement in a given cursor,
//          the same number of values must have been bound for all bind
//          variables, so when EXECUTE is called, the latest calls to
//          BIND_VARIABLE must must have specified the same number of values
//          to be bound for all bind variables.
// *Action: Make sure that the same number of values have been bound for all
//          of the bind variables.
06568, 00000, "obsolete ICD procedure called"
// *Cause:  An obsolete ICD procedure was called by a PL/SQL program.
//          The PL/SQL program was probably written for an eralier release of
//          RDBMS.
// *Action: Make sure that all PL/SQL programs have been upgraded to the latest
//          release of the RDBMS.  This can be accomplished by following
//          upgrade instructions in the README file, or by running
//          the catproc.sql script supplied with the RDBMS.
06569, 00000, "Collection bound by bind_array contains no elements"
// *Cause:  A collection with zero elements was bound to a bind variable
//          in a call to procedure BIND_ARRAY in the package DBMS_SQL.
//          In order to execute a bind of a collection, the collection must
//          contain at least one element.  If no elements are present then
//          at execute time there will be no value for this bind and the
//          statement is meaningless.
// *Action: Fill the collection with the elements you want to bind and
//          try the bind call again.
/
/
06570, 00000, "shared pool object does not exist, cannot be pinned/purged"
// *Cause:  The specified shared pool shared cursor could not be found,
//          therefore it cannot be pinned/purged.
// *Action: Make sure that a correct shared cursor name is given.  Names
//          are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's
//          are an 8 digit hex number from the 'address' column of v$sqlarea,
//          and the D's are a 1 to 10 digit decimal number with an optional
//          leading sign (from the 'hash_value' column)
// *Action: Remove the procedure from the calling stored procedure.
/
/ 6571-6579 Reserved for Plsql functions called from Sql
/
06571, 00000, "Function %s does not guarantee not to update database"
// *Cause:  There are two possible causes for this message:
//          * A SQL statement references a packaged, PL/SQL function
//            that does not contain a pragma that prevents the database
//            from being updated.
//          * A SQL statement references a stand-alone, PL/SQL function
//            that contains an instruction to update the database.
// *Action: If the referenced function is a packaged, PL/SQL function:
//          Recreate the PL/SQL function with the required pragma; be
//          certain to include the 'Write No Database State' (WNDS)
//          argument in the argument list of the pragma.
//          If the referenced function is a stand-alone, PL/SQL function:
//          Do not use the function.
06572, 00000, "Function %s has out arguments"
// *Cause:  A SQL statement references either a packaged, or a stand-alone,
//          PL/SQL function that contains an OUT parameter in its argument
//          list. PL/SQL functions referenced by SQL statements must not
//          contain the OUT parameter.
// *Action: Recreate the PL/SQL function without the OUT parameter in the
//          argument list.
06573, 00000, "Function %s modifies package state, cannot be used here"
// *Cause:  There are two possible causes for this message:
//          * A SQL statement references a packaged, PL/SQL function that
//            does not contain a pragma containing the 'Write no Package
//            State' (WNPS).
//          * A SQL statement references a stand-alone, PL/SQL function
//            that modifies a package state. A stand-alone, PL/SQL function
//            referenced by a SQL statement cannot modify a package state.
// *Action: If the function is a packaged, PL/SQL function: Recreate
//          the function and include a pragma containing the 'Write no
//          Package State' (WNPS).
//          If the function is a stand-alone, PL/SQL function: Delete
//          the function from the SQL statement.
06574, 00000, "Function %s references package state, cannot execute remotely"
// *Cause:  There are two possible causes for this message:
//          * A remote, packaged function or a remote-mapped, local,
//            packaged function that does not contain a pragma with the
//            'Write no Package State' (WNPS) and 'Read no Package State'
//            (RNPS) arguments references a package state.
//          * A remote, stand-alone function or a remote-mapped, local,
//            stand-alone function contains a reference to a package
//            state (reads or writes a package variable).
//          Only local functions that are referenced in a SELECT list, VALUES
//          clause of an INSERT statement, or SET clause of an UPDATE
//          statement can modify a package state.
// *Action: If the function is a packaged function: Recreate the function
//          and include a pragma containing the 'Write no Package State'
//          (WNPS) and 'Read no Package State' (RNPS) arguments.
//          If the function is a stand-alone function: Do not call the
//          function.
06575, 00000, "Package or function %s is in an invalid state"
// *Cause:  A SQL statement references a PL/SQL function that is in an
//          invalid state. Oracle attempted to compile the function, but
//          detected errors.
// *Action: Check the SQL statement and the PL/SQL function for syntax
//          errors or incorrectly assigned, or missing, privileges for a
//          referenced object.
06576, 00000, "not a valid function or procedure name"
// *Cause:  Could not find a function (if an INTO clause was present) or
//          a procedure (if the statement did not have an INTO clause) to
//          call.
// *Action: Change the statement to invoke a function or procedure
06577, 00000, "output parameter not a bind variable"
// *Cause:  The argument corresponding to an IN/OUT or OUT parameter
//          for a function or a procedure or a function return value in
//          a CALL statement must be a bind variable.
// *Action: Change the argument to a bind variable
06578, 00000, "output parameter cannot be a duplicate bind"
// *Cause:  The bind variable corresponding to an IN/OUT or OUT parameter
//          for a function or a procedure or a function return value in a
//          CALL statement cannot be a duplicate bind variable.
// *Action: Change the bind variable to be unique
/
06579, 00000, " Bind variable not big enough to hold the output value"
// *Cause:  The bind variable specified by the user is not large enough to
//          hold the output returned by the function or a procedure.
// *Action: Specify a bind variable of larger size.
/
06580, 00000, "Hash Join ran out of memory while keeping large rows in memory"
// *Cause:  Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE *
//          HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than
//          that, this error will be raised.
// *Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row
//          fits in a slot. HASH_AREA_SIZE may also need to be increaed.
/
/ 6581-6591 Reserved for European OEM Ports (contact: egroenen.nl)
/
06592, 00000, "CASE not found while executing CASE statement"
// *Cause:  A CASE statement must either list all possible cases or have an
//          else clause.
// *Action: Add all missing cases or an else clause.
/
06593, 00000, "%s is not supported with natively compiled PL/SQL modules"
// *Cause:  Specified feature is not yet supported for natively compiled
//          PL/SQL modules yet.
// *Action: Recompile the relevant PL/SQL modules in non-native mode by
//          setting the parameter plsql_compiler_flags to INTERPRETED.
/
06594, 00000, "ICD is unable to compute a result"
// *Document: NO
// *Cause:  This exception is internal to PL/SQL, and should not be seen by 
//          customers.
// *Action: Contact Oracle Support Services.
/
06595, 00000, "REF CURSOR parameters are not supported in forwarded RPC calls"
// *Cause:  An attempt was made to make a forwarded RPC call with a REF CURSOR
//          parameter. 
// *Action: Either call the remote function directly (i.e., not by way of
//          forwarding), or move the remote function to a database where it can
//          be called directly. 
/
06596, 00000, "object cannot be  purged, object is permanently kept in shared pool"
// *Cause:  The specified object was permanently kept, therefore, cannot be 
//          purged.
// *Action: Use DBMS_SHARED_POOL.UNKEEP procedure to unkeep the object and then
//               purge it.
/
06597, 00000, "Failed to increase the session's call stack memory to %s bytes at a depth of %s calls.  (The current maximum is %s bytes.)"
// *Cause:  PL/SQL program execution used more call stack memory than permitted.
// *Action: * Ask your DBA to increase the maximum allowed call stack memory.
//          * Decrease the amount of call stack used by the program.  This may
//            be accomplished by using fewer, smaller local variables, or by
//            limiting the depth of function call nesting.
/
/ 6600-6699 Reserved for more SQL*Net errors
/
/ 6700-6899 Reserved for TLI SQL*NET driver errors
/
/ 6900-6999 Reserved for more SQL*Net errors
/
/
/        6600 - 6622: SQL*Net LU6.2 driver errors
/
06600, 00000, "LU6.2 Driver: SNA software is not loaded"
// *Cause:  The SNA software is not running.
// *Action: Start the SNA software and try again.
06601, 00000, "LU6.2 Driver: Invalid database ID string"
// *Cause:  The database string in the connect was invalid.
// *Action: Provide a valid database string, as defined in documentation.
06602, 00000, "LU6.2 Driver: Error allocating context area"
// *Cause:  Context area failure.
// *Action: Contact your local service representative.
06603, 00000, "LU6.2 Driver: Error allocating memory"
// *Cause:  Operating system refused request for memory.
// *Action: Contact you local service representative.
06604, 00000, "LU6.2 Driver: Unable to allocate session with remote LU"
// *Cause:  Allocate system call failed.
// *Action: Ensure that the SNA software is running and that sessions are free.
//          If this is the case, then check your SNA configuration data for
//          errors.  You may have entered an incorrect parameter.
06605, 00000, "LU6.2 Driver: Unexpected line turnaround"
// *Cause:  SNA software switched from send to receive unexpectedly.
// *Action: Check the SNA configuration data, particularly parameters
//          associated with a session.
06606, 00000, "LU6.2 Driver: Unexpected response from SNA"
// *Cause:  A parameter in an SNA call returned an unexpected value.
// *Action: Attempt to reproduce problem, debug and record the value of the
//          'what' data parameter at the time of error.  Then contact your
//          service representative.
06607, 00000, "LU6.2 Driver: Reset occurred in send state"
// *Cause:  A reset was issued whilst in send state.
// *Action: Check the SNA LOG data, if relevent, for further information.
06608, 00000, "LU6.2 Driver: Reset occurred in receive state"
// *Cause:  A reset was received from the partner whilst in receive
//          state.  This may be because the partner deallocated.
// *Action: Check the SNA LOG data, if relevent, for further information.
/
/ 06609 is not used by the LU6.2 Driver.
/
06610, 00000, "LU6.2 Driver: Failed during deallocation"
// *Cause:  LU6.2 driver was unable to deallocate gracefully.
// *Action: Check the reason for deallocation.  Consult the SNA
//          LOG data.
06611, 00000, "LU6.2 Driver: Request to send error"
// *Cause:
// *Action:
06612, 00000, "LU6.2 Driver: Send data error"
// *Cause:
// *Action:
06613, 00000, "LU6.2 Driver: Receive and wait error"
// *Cause:
// *Action:
06614, 00000, "LU6.2 Driver: Receive Immediate error"
// *Cause:
// *Action:
06615, 00000, "LU6.2 Driver: Send error"
// *Cause:
// *Action:
06616, 00000, "LU6.2 Driver: Attach to LU failed"
// *Cause:  The SQL*Net LU6.2 driver was unable to attach to the
//          LU specified in the connect string, or was unable to
//          attach to the default LU.
// *Action: Check that the LU name specified in the connect string,
//          or the default LU name if no LU was specified, is
//          correctly configured and operational.
06617, 00000, "LU6.2 Driver: Attach to PU failed"
// *Cause:
// *Action:
06618, 00000, "LU6.2 Driver: Activation of subnetwork failed"
// *Cause:
// *Action:
06619, 00000, "LU6.2 Driver: Unable to activate remote partner"
// *Cause:
// *Action:
06620, 00000, "LU6.2 Driver: Invalid remote partner"
// *Cause:
// *Action:
06621, 00000, "LU6.2 Driver: Allocation error"
// *Cause:
// *Action:
06622, 00000, "LU6.2 Driver: Unable to attach to SNA"
// *Cause:  The SQL*Net LU6.2 driver could not attach to the SNA
//          software on your machine.  The most likely cause is that the SNA
//          software is not operational.
// *Action: Check the status of the SNA software, ensure that it is
//          operational and then try again.
/
/ 6700-6899 Reserved for TLI SQL*NET driver errors
/
06700, 00000, "TLI Driver: incorrect message type from host"
// *Cause:  TLI received a message with an unrecognizable message type.
// *Action: Contact your customer support representative.
06701, 00000, "TLI Driver: incorrect number of bytes written"
// *Cause:  TLI sent a message that was apparently successful, but the
//          number of bytes transmitted did not match the number
//          of bytes supplied to the driver.
// *Action: Contact your customer support representative.
06702, 00000, "TLI Driver: cannot allocate context area"
// *Cause:  TLI could not allocate heap space for the context area.
// *Action: Contact your customer support representative.
06703, 00000, "TLI Driver: send break message failed"
// *Cause:  TLI failed to send a break message across the connection.
// *Action: Contact your customer support representative.
06704, 00000, "TLI Driver: receive break message failed"
// *Cause:  TLI failed to receive an expected break message.
// *Action: Contact your customer support representative.
06705, 00000, "TLI Driver: remote node is unknown"
// *Cause:  TLI could not find your remote host information.
// *Action: Make sure you specified the hostname correctly on the command
//          line.  (Also, check your capitalization and spelling.)
06706, 00000, "TLI Driver: service not found"
// *Cause:  TLI could not find service information for the specified service
//          name.
// *Action: If you specified the service name on the command line or with the
//          environment variable TLI_SERVER, make sure you specified it
//          correctly.  If the service name is not in the SERVICES file for
//          your protocol, ask your system adminstrator to add it.
06707, 00000, "TLI Driver: connection failed"
// *Cause:  TLI failed to establish the connection to a SQL*Net TCP/IP server
//          due to an error encountered by the remote server, which has
//          supplied a string describing the remote error.
// *Action: See the SQL*Net TCP/IP User's Guide section "orasrv Messages" for
//          the specific cause and action.
06708, 00000, "TLI Driver: message receive failure"
// *Cause:  TLI encountered an error receiving a message from the communication
//          channel.
// *Action: Contact your customer support representative.
06709, 00000, "TLI Driver: message send failure"
// *Cause:  TLI encountered an error sending a message across the communication
//          channel.
// *Action: Contact your customer support representative.
06710, 00000, "TLI Driver: send interrupt break message failed"
// *Cause:  TLI failed to send a break message while handling an interrupt
//          signal from the user.
// *Action: Contact your customer support representative.
06711, 00000, "TLI Driver: error on bind"
// *Cause:  TLI failed to assign a network address to the communication channel.
// *Action: Contact your customer support representative.
06712, 00000, "TLI Driver: error on accept"
// *Cause:  TLI failed to accept a connection request from the client.
// *Action: Contact your customer support representative.
06713, 00000, "TLI Driver: error on connect"
// *Cause:  TLI failed to connect the client to the remote server.  The network
//          line to the remote host may be down.
// *Action: Use other network login programs to make sure that the remote
//          host is accessible.
06720, 00000, "TLI Driver: SID lookup failure"
// *Cause:  The database SID supplied in the database login string was not
//          recognized by the remote host.
// *Action: Ask your system administrator to add the appropriate SID entry
//          to oratab on the remote host.
06721, 00000, "TLI Driver: spurious client req"
// *Cause:  The remote TLI server received an undefined request.
// *Action: Contact your customer support representative.
06722, 00000, "TLI Driver: connection setup failure"
// *Cause:  The remote TLI server rejected the connection request, and the
//          client was unable to retrieve an error code or message.
// *Action: Contact your customer support representative.
06730, 00000, "TLI Driver: unable to open clone device"
// *Cause:  TLI failed to open the Streams clone device associated with the
//          transport provider.
// *Action: Contact your customer support representative.
06731, 00000, "TLI Driver: cannot alloc t_call"
// *Cause:  TLI cannot allocate space for the client's connection information.
// *Action: Contact your customer support representative.
06732, 00000, "TLI Driver: cannot alloc t_discon"
// *Cause:  TLI cannot allocate space for the client's disconnection
//          information.
// *Action: Contact your customer support representative.
06733, 00000, "TLI Driver: failed to receive disconnect"
// *Cause:  TLI failed to receive an expected disconnection message during
//          connection release.
// *Action: Contact your customer support representative.
06734, 00000, "TLI Driver: cannot connect"
// *Cause:  TLI failed to connect the client to the remote server.
// *Action: Check that the remote TLI server is running.
06735, 00000, "TLI Driver: client failed to close error conn"
// *Cause:  TLI failed to properly close a connection after an error was
//          received.
// *Action: Contact your customer support representative.
06736, 00000, "TLI Driver: server not running"
// *Cause:  TLI timed out while attempting to connect to the remote TLI server.
// *Action: Check that the remote TLI server is running with the status utility
//          for the transport provider you are using.  If it is not, ask
//          your system adminstrator to start it.
06737, 00000, "TLI Driver: connection failed"
// *Cause:  TLI could not establish a connection to the remote TLI server.
// *Action: Check that the remote TLI server is running with the status
//          utility for the transport provider you are using.
06741, 00000, "TLI Driver: unable to open protocol device"
// *Cause:  The TLI server failed to open the Streams device associated with
//          the transport provider.
// *Action: Contact your customer support representative.
06742, 00000, "TLI Driver: cannot alloc t_bind"
// *Cause:  The TLI server cannot allocate space for its requested network
//          address.
// *Action: Contact your customer support representative.
06743, 00000, "TLI Driver: cannot alloc t_bind"
// *Cause:  The TLI server cannot allocate space for its actual network
//          address.
// *Action: Contact your customer support representative.
06744, 00000, "TLI Driver: listener cannot bind"
// *Cause:  The TLI server failed to assign the correct network address on
//          which to listen for connections.
// *Action: Contact your customer support representative.
06745, 00000, "TLI Driver: listener already running"
// *Cause:  The network address on which the TLI server awaits connection
//          requests is in use, possibly because the server is already running.
// *Action: Ensure that the TLI server is not already running.  If it is
//          not running and this error message recurs, contact your customer
//          support representative.
06746, 00000, "TLI Driver: cannot alloc t_call"
// *Cause:  TLI cannot allocate space for the TLI server's connection
//          information.
// *Action: Contact your customer support representative.
06747, 00000, "TLI Driver: error in listen"
// *Cause:  The TLI server encountered an error while listening for
//          connection requests.
// *Action: Contact your customer support representative.
06748, 00000, "TLI Driver: cannot allocate t_discon"
// *Cause:  TLI cannot allocate space for the TLI server's disconnection
//          information.
// *Action: Contact your customer support representative.
06749, 00000, "TLI Driver: option not allowed across network"
// *Cause:  The requested TLI server command must be issued from the same
//          host on which the server is running.
// *Action: Log in to the remote host and try again.
06750, 00000, "TLI Driver: sync failed"
// *Cause:  The ORACLE process started by the TLI server was unable to
//          synchronize its inherited connection.
// *Action: Contact your customer support representative.
06751, 00000, "TLI Driver: bound addresses unequal"
// *Cause:  The osn check server address failed. The bound server address was
//          not the same as the requested binding address.
// *Action: Contact your customer support representative.
06752, 00000, "TLI: error in signal setup"
// *Cause:  A call to sigaction() returned with a system error.
// *Action: Contact your customer support representative.
06753, 00000, "TLI Driver: name-to-address mapping failed"
// *Cause:  For SVR4, the netdir_getbyname() call failed for some
//          unknown reason.
// *Action: Contact your custumer service representative.
06754, 00000, "TLI Driver: unable to get local host address"
// *Cause:  The name of the remote host to connect to was not specified, and
//          the name of the local host cannot be retrieved from the HOSTS file.
// *Action: Contact your system administrator.
06755, 00000, "TLI Driver: cannot close transport endpoint"
// *Cause:  The TLI server was unable to close a connection after passing it
//          to an ORACLE process.
// *Action: Contact your customer support representative.
06756, 00000, "TLI Driver: cannot open oratab"
// *Cause:  The TLI server could not open the file used to define the locations
//          of remotely accessible databases.
// *Action: Ask your system administrator to check that the file exists and
//          has the correct permissions.
06757, 00000, "TLI Driver: server got bad command"
// *Cause:  The TLI server received an invalid command.
// *Action: Contact your customer support representative.
06760, 00000, "TLI Driver: timeout reading orderly release"
// *Cause:  TLI was not able to retreive an expected disconnect message while
//          closing the communication channel.
// *Action: Contact your customer support representative.
06761, 00000, "TLI Driver: error sending orderly release"
// *Cause:  TLI encountered an error sending a disconnect message closing the
//          communication channel.
// *Action: Contact your customer support representative.
06762, 00000, "TLI Driver: error reading orderly release"
// *Cause:  TLI encountered an error receiving an expected disconnect message
//          while closing the communication channel.
// *Action: Contact your customer support representative.
06763, 00000, "TLI Driver: error sending disconnect"
// *Cause:  TLI encountered an error sending a disconnect message closing the
//          communication channel.
// *Action: Contact your customer support representative.
06764, 00000, "TLI Driver: error reading disconnect"
// *Cause:  TLI was not able to retreive an expected disconnect message while
//          closing the communication channel.
// *Action: Contact your customer support representative.
06765, 00000, "TLI Driver: error awaiting orderly release"
// *Cause:  TLI encountered an error awaiting a disconnect message while
//          closing the communication channel.
// *Action: Contact your customer support representative.
06766, 00000, "TLI Driver: close failed during release"
// *Cause:  TLI failed to close the communication channel after receiving
//          a disconnect message.
// *Action: Contact your customer support representative.
06767, 00000, "TLI Driver: alloc failed during release"
// *Cause:  TLI cannot allocate space for disconnection information while
//          closing the communication channel.
// *Action: Contact your customer support representative.
06770, 00000, "TLI Driver: error sending version"
// *Cause:  TLI encountered an error while sending its version information
//          during connection establishment.
// *Action: Contact your customer support representative.
06771, 00000, "TLI Driver: error reading version"
// *Cause:  TLI encountered an error while awaiting the expected version
//          information during connection establishment.
// *Action: Contact your customer support representative.
06772, 00000, "TLI Driver: error sending command"
// *Cause:  TLI encountered an error while sending a command message during
//          connection establishment.
// *Action: Contact your customer support representative.
06773, 00000, "TLI Driver: error reading command"
// *Cause:  TLI encountered an error while awaiting the expected command
//          message during connection establishment.
// *Action: Contact your customer support representative.
06774, 00000, "TLI Driver: error sending break mode"
// *Cause:  TLI encountered an error while sending break-mode message during
//          connection establishment.
// *Action: Contact your customer support representative.
06775, 00000, "TLI Driver: error reading break mode"
// *Cause:  TLI encountered an error while awaiting the expected break-mode
//          message during connection establishment.
// *Action: Contact your customer support representative.
06776, 00000, "TLI Driver: error sending parms"
// *Cause:  TLI encountered an error while sending the connection parameters
//          during connection establishment.
// *Action: Contact your customer support representative.
06777, 00000, "TLI Driver: error reading parms"
// *Cause:  TLI encountered an error while awaiting the expected connection
//          parameter message during connection establishment.
// *Action: Contact your customer support representative.
06778, 00000, "TLI Driver: error sending ccode"
// *Cause:  TLI encountered an error while sending the completion status message
//          during connection establishment.
// *Action: Contact your customer support representative.
06779, 00000, "TLI Driver: error reading ccode"
// *Cause:  TLI encountered an error while awaiting the expected completion
//          status message during connection establishment.
// *Action: Contact your customer support representative.
06780, 00000, "TLI Driver: recv error code failed"
// *Cause:  TLI encountered an error while awaiting an expected error message
//          during connection establishment.
// *Action: Contact your customer support representative.
06781, 00000, "TLI Driver: error reading negotation string"
// *Cause:  TLI encountered an error while awaiting the expected negotiation
//          message during connection establishment.
// *Action: Contact your customer support representative.
06790, 00000, "TLI Driver: poll failed"
// *Cause:  TLI was unable to poll the communication channel for possible
//          incoming messages.
// *Action: Contact your customer support representative.
06791, 00000, "TLI Driver: poll returned error event"
// *Cause:  TLI received an unexpected event while polling the communication
//          channel for possible incoming messages.
// *Action: Contact your customer support representative.
06792, 00000, "TLI Driver: server cannot exec oracle"
// *Cause:  The remote TLI server was unable to start an ORACLE process on
//          behalf of the client.
// *Action: Note the operating system error message or number and contact
//          your system adminstrator.  The permissions on the remote ORACLE
//          program may be set incorrectly.
06793, 00000, "TLI Driver: server cannot create new process"
// *Cause:  The remote TLI server was unable to start an ORACLE process on
//          behalf of the client.
// *Action: Note the operating system error message or number and contact
//          your system adminstrator.  The remote host may be unable to create
//          any new processes due to a full process table.
06794, 00000, "TLI Driver: shadow process could not retrieve protocol info"
// *Cause:  The ORACLE process either failed to allocate memory to store
//          the protocol information record, or the protocol rejected the
//          request for some unknown reason.
// *Action: Contact your customer support representative.
06800, 00000, "TLI Driver: SQL*Net SPX client went away during reconnect"
// *Cause:  The client process was aborted by the system or the user, and
//          was unable to complete the connection establishment with the
//          server listener process.
// *Action: Determine cause of client exit, and reattempt connection.
06801, 00000, "TLI Driver: listen for SPX server reconnect failed"
// *Cause:  An unknown event occurred on the client's listening socket.
// *Action: Contact your customer support representative.
06802, 00000, "TLI Driver: could not open the /etc/netware/yellowpages file"
// *Cause:  The /etc/netware/yellowpages file does not exist, or is not
//          readable by the TLI listener process.
// *Action: Insure the file exists and is readable. Make sure that the