/ $Header: error.txt 29-may-2001.16:18:21 gviswana 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 / 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 " 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 / / 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 / / Adding an error for V6: / 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 / 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. 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" // *Cause: Resource interested is busy. // *Action: Retry if necessary. 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" // *Cause: LOG_FILES initialization parameter value exceeded // *Action: Increase the value of the LOG_FILES initialization parameter and // warm start. The parameter needs to be as large as the highest // number of log files that currently exist rather than just the // count of logs that exist. 00064, 00000, "object is too large to allocate on this O/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, "LOG_FILES is %s but needs to be %s to be compatible" // *Cause: The maximum number of log 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 LOG_FILES initialization parameter to // be compatible. 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 to dump global area as well as // bytes for every pointer; 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: 00099, 00000, "timed out while waiting for resource, potential PDML deadlock" // *Cause: The resource needed by the transaction was busy. The PDML // transaction could not acquire the resource within the specified // amount of time. This indicates potential deadlock involving this // PDML transaction and other transactions currently running in the // system. // *Action: Increase the the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT // parameter; then retry the operation. 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, "dispatching mechanism not configured for network protocol %s" // *Cause: Trying to alter the dispatcher's configuration for a network // protocol that was not specified in the INIT.ORA file. // *Action: Include the network protocol in the system parameter // DISPATCHERS in INIT.ORA and re-start the system. 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. 00111, 00000, "not all servers started because number of servers is limited to %s" // *Cause: An attempt was made to start more servers than the maximum // number specified by the system parameter MAX_SHARED_SERVERS. // *Action: Increase the value of MAX_SHARED_SERVERS in INIT.ORA as needed // or re-issue the ALTER SYSTEM SET SHARED_SERVERS command with // an appropriate number of servers. 00112, 00000, "only created up to %s (maximum specified) dispatchers" // *Cause: An attempt was made to start more dispatchers than the maximum // number specified by the system parameter MAX_DISPATCHERS. // *Action: Increase the value of MAX_DISPATCHERS in INIT.ORA as needed. 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, "value out of range for system parameter SERVICE_NAMES" // *Cause: The specified value of the SHARED_SERVERS parameter is incorrect. // *Action: SHARED_SERVERS must be >= 0 and <= MAX_SHARED_SERVERS. 00118, 00000, "value out of range for system parameter DISPATCHERS" // *Cause: The value of the DISPATCHERS parameter is incorrect. // *Action: The sum of all DISPATCHERS values must be >= 0 and // <= MAX_DISPATCHERS. 00119, 00000, "invalid specification for system parameter MTS_LISTENER_ADDRESS" // *Cause: The syntax for the MTS_LISTENER_ADDRESS parameter is incorrect. // *Action: Refer to the Oracle8 Server Reference Manual for the correct syntax. 00120, 00000, "dispatching mechanism not enabled or installed" // *Cause: Either the dispatching mechanism was not enabled or the // ORACLE executable image was not installed with the dispatching // mechanism. // *Action: Refer to manual on how to enable the dispatching mechanism using // system parameters in the INIT.ORA file. Failing that, consult // your ORACLE representative. 00121, 00000, "SHARED_SERVERS specified without DISPATCHERS" // *Cause: A definition for SHARED_SERVERS was specified in the INIT.ORA file, // but no definition for DISPATCHERS was specified. Without a // value for DISPATCHERS, shared servers will never be used. // *Action: Add a definition for DISPATCHERS in the INIT.ORA file // (or take out the definition for SHARED_SERVERS, if shareds // servers are not being used). 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. 00124, 00000, "DISPATCHERS specified without MAX_SHARED_SERVERS" // *Cause: A definition for DISPATCHERS was specified in the INIT.ORA // file, but MAX_SHARED_SERVERS was specified as zero. // *Action: Specify MAX_SHARED_SERVERS to be greater than zero. 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' / / 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, "autonomous transaction disallowed within distributed transaction" // *Cause: A request was made by the application to start an autonomous // transaction when the application was already in a distributed // transaction. // *Action: Roll back or commit the current distributed transaction first. / / 200 .. 249 controlfile management errors / 00200, 00000, "controlfile could not be created" // *Cause: It was not possible to create the controlfile. // *Action: Check that there is sufficient disk space and no conflicts in // filenames and try to create the controlfile again. 00201, 00000, "controlfile version %s incompatible with ORACLE version %s" // *Cause: The controlfile was created by incompatible software. // *Action: Either restart with a compatible software release or use // CREATE CONTROLFILE to create a new controlfile that is // compatible with this release. 00202, 00000, "controlfile: '%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 controlfiles" // *Cause: The mount ID in the controlfile is not the same as the // mount ID in the controlfile used by the first instance to // mount this database. The controlfiles are for the same database // but they are not the same files. Most likely one instance is using // a backup controlfile. // *Action: Check that the correct controlfiles were specified. 00204, 00000, "error in reading (block %s, # blocks %s) of controlfile" // *Cause: A disk I/O failure was detected on reading the controlfile. // *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 controlfile, check alert log for more info" // *Cause: The system could not find a controlfile of the specified name and // size. // *Action: Check that ALL controlfiles 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 controlfile" // *Cause: A disk I/O failure was detected on writing the controlfile. // *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, "controlfiles are not for the same database" // *Cause: The database ID in the controlfile is not the same as the // database ID in the controlfile used by the first instance to // mount this database. Most likely one of the mounts used the wrong // controlfile or there are two databases with the same name. // *Action: Check that the controlfile is for the correct database and is // not an old version. 00208, 00000, "number of controlfile names exceeds limit of %s" // *Cause: An attempt was made to use more controlfiles than Oracle supports. // *Action: Shut down Oracle. Reduce the number of controlfiles 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 controlfile" // *Cause: Cannot open the controlfile. // *Action: Check to make sure the controlfile exists and is not locked by // some other program. 00211, 00000, "controlfile does not match previous controlfiles" // *Cause: A controlfile was specified that belongs to another database. // *Action: Find and install the correct controlfile. 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 controlfile; old file size %s, %s required" // *Cause: To reuse a controlfile, 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, "controlfile '%s' version %s inconsistent with file '%s' version %s" // *Cause: An inconsistent set of controlfiles, datafiles/logfiles, and redo // files was used. // *Action: Use a consistant set of controlfiles, 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 controlfile" // *Cause: No controlfile is specified or the controlfile specified does // not exist. // *Action: Specify at least one valid controlfile and retry the operation. 00216, 00000, "controlfile could not be resized for migration from 8.0.2" // *Cause: Controlfiles created by release 8.0.2 were missing some records. // These records are automatically added by resizing the contolfile // when attempting to run a later release. The resize failed. // *Action: Look in the alert log for the reason that the resize failed. If it // can be fixed by giving the controlfile more space, then do that. // Otherwise, use the CREATE CONTROLFILE script dumpped to the trace // file to create a new controlfile. 00218, 00000, "block size %s of controlfile does not match DB_BLOCK_SIZE (%s)" // *Cause: The block size as stored in the controlfile 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 controlfile has // either been corrupted or belongs to a different database. // *Action: Restore a good copy of the controlfile. 00219, 00000, "required controlfile size %s exceeds maximum allowable size %s" // *Cause: An invocation of CREATE DATABASE, CREATE CONTROLFILE, // cfileCalcSizeList, or cfileCalcSizeArray was executed specifying // a combination of parameters that would require the controlfile // 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. In the case of // cfileCalcSizeList() or cfileCalcSizeArray(), use a different // combination of record type counts. 00220, 00000, "controlfile not mounted by first instance, check alert log for more info" // *Cause: The specified controlfile has a different mount ID than the // other controlfiles that are being mounted. This means that // the first instance to mount the database did not use this // controlfile. // *Action: Find and install the correct controlfile. 00221, 00000, "error on write to controlfile" // *Cause: An error occurred when writing to one or more of the controlfiles. // *Action: See accompanying messages. 00222, 00000, "operation would reuse name of a currently mounted controlfile" // *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 controlfile. // *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, "controlfile resize attempted with illegal record type (%s)" // *Cause: An attempt was made to expand or shrink the controlfile 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 controlfile differs from actual size %s" // *Cause: The expected size of the controlfile as stored in its // header was different than the actual operating system file size. // This usually indicates that the controlfile was corrupted. // *Action: Restore a good copy of the controlfile. 00226, 00000, "operation disallowed while alternate controlfile open" // *Cause: The attempted operation could not be executed at this time because // this process had an alternate controlfile open for fixed table // access. // *Action: Retry the operation after calling cfileUseCurrent. 00227, 00000, "corrupt block detected in controlfile: (block %s, # blocks %s)" // *Cause: A block header corruption or checksum error was detected on reading // the controlfile. // *Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP // CONTROLFILE command. 00228, 00000, "length of alternate controlfile 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 controlfile enqueue" // *Cause: The attempted operation cannot be executed at this time because // this process currently holds the snapshot controlfile enqueue. // *Action: Retry the operation after calling cfileUseCurrent to release the // snapshot controlfile enqueue. 00230, 00000, "operation disallowed: snapshot controlfile enqueue unavailable" // *Cause: The attempted operation cannot be executed at this time because // another process currently holds the snapshot controlfile enqueue. // *Action: Retry the operation after the concurrent operation that is holding // the snapshot controlfile enqueue terminates. 00231, 00000, "snapshot controlfile has not been named" // *Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot // it was detected that no filename for the snapshot controlfile had // previously been specified. // *Action: Specify a name for the snapshot controlfile by calling // cfileSetSnapshotName. 00232, 00000, "snapshot controlfile is nonexistent, corrupt, or unreadable" // *Cause: The snapshot controlfile 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 controlfile is corrupt or unreadable" // *Cause: The specified copy controlfile 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 controlfile" // *Cause: A snapshot or copy controlfile 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 controlfile using // cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, // respectively. 00235, 00000, "controlfile fixed table inconsistent due to concurrent update" // *Cause: Concurrent update activity on a controlfile caused a query on a // controlfile fixed table to read inconsistent information. // *Action: Retry the operation. 00236, 00000, "snapshot operation disallowed: mounted controlfile is a backup" // *Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, // or cfileUseSnapshot when the currently mounted controlfile is a // backup controlfile. // *Action: Mount a current controlfile and retry the operation. 00237, 00000, "snapshot operation disallowed: controlfile newly created" // *Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently // mounted controlfile that was newly created with CREATE CONTROLFILE // was made. // *Action: Mount a current controlfile 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. / / 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 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 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 " 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, "controlfile out of sync with redo log" // *Cause: The redo log file and controlfile 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 controlfile, 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 number %s is invalid, must be between 1 and %s" // *Cause: An invalid file number was specified. // *Action: Specify a correct datafile 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 TIMEOUT interval" // *Cause: A non-zero integer timeout interval (in minutes) must be // specified after the TIMEOUT keyword. // *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. There is // a limit, set at database creation, on the number of redo // log files (typically 16). // *Action: Use the CREATE CONTROLFILE command with a larger value // for MAXLOGFILES. 00303, 00000, "cannot process Multi-Strand Redo" // *Cause: A redo log containing Multi-Strand Redo has been detected. // The current Oracle release cannot process this format of redo. // *Action: Use a later release that supports Multi-Strand 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 controlfile. 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 controlfile. // 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 controlfile" // *Cause: The controlfile change sequence number in the log file is // greater than the number in the controlfile. This implies that // the wrong controlfile 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 // controlfile change sequence number until it is great enough. // *Action: Use the current controlfile or do backup controlfile recovery to // make the controlfile current. Be sure to follow all restrictions // on doing a backup controlfile 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 controlfile. // *Action: Restore correct file or reset logs. 00342, 00000, "archived log was created before last RESETLOGS" // *Cause: Recovery was given a log that was created before the last // ALTER DATABASE OPEN RESETLOGS command. There should be another // log created since then that contains the correct redo. // *Action: Supply the correct log file. 00343, 00000, "too many errors, log member closed" // *Cause: The maximum number of errors on this log member has been exceeded. // *Action: Correct the underlying problem by referring to the other error // messages found with this one. 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" // *Cause: A log file member no longer is 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 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" // *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, "unable to get default db_block_size" // *Cause: the system was unable to determine the default db_block_size // *Action: see accompanying system specific error. As a workaround, // specify the blocksize in the INIT.ORA file. 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) } // 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. // 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_K_cache_size to zero while there were still online // tablespaces with blocksize 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. // / / 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 // new algorithm. This usually requires making more main storage // available to the recovery process. 00397, 00000, "lost write detected for file %s, block %s" // *Cause: The specified block is missing changes that should have been // written to disk, indicating a lost write by the file i/o subsystem // or volume manager. // *Action: Run diagnostic checks on the i/o subsystem and resolve any errors 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. / / 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. / / 470-480 Detached process death errors (signaled in foreground) / 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. 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 / / 00486-00569 / 00568, 00000, "Maximum number of interrupt handlers exceeded" // *Cause: User specified too many ^c handlers // *Action: Remove some old handlers. / / 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]" // *Cause: This is the generic internal error number for Oracle program // exceptions. This indicates that a process has encountered an // exceptional condition. // *Action: Report as a bug - the first argument is the internal error number 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 is 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 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. 00816, 00000, "error message translation failed" // *Cause: // *Action: / / MODIFIED / msusaira 07/23/01 - modify 1257 error mesg / eyho 07/25/01 - remove obsolete v7 error messages on parallel server / 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, "invalid column name" // *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: // *Action: 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" // *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 [ . ] is // expected but not present. If OIDINDEX clause, index name must be // // *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, "LEVEL, PRIOR, or ROWNUM not allowed here" // *Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location. // *Action: Remove LEVEL, PRIOR, or ROWNUM. 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: // *Action: 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: 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. // *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). 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: 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 controlfile was created. // *Action: Check what error was signaled when the database was first // created or when the controlfile was recreated. Take appropriate // actions to recreate the database or a new controlfile. 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" // *Cause: Trying to roll back to a save point that was never established. // *Action: 01087, 00000, "cannot start up ORACLE - currently logged on" // *Cause: // *Action: Logoff and then issue the STARTUP command. 01088, 00000, "cannot shut down ORACLE while active processes exist" // *Cause: Users are still logged into the instance. // *Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. 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 1260: db file errors / 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 controlfile is not '%s'" // *Cause: The database name in the controlfile does not match your // database name. // *Action: Either find the correct controlfile or change your database name. 01104, 00000, "number of controlfiles (%s) does not equal %s" // *Cause: The number of controlfiles used by this instance disagrees with // the number of controlfiles in an existing instance. // *Action: Check to make sure that all controlfiles 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 // *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 controlfile recovery was done with a controlfile 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 controlfile for adding database // files. // *Action: Resize the controlfile 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 controlfile. See accompanying message for reason. // *Action: Make certain that the db files and controlfiles 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 EXCLUSIVE and not open for this operation" // *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" // *Cause: All the files were found to be offline 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 controlfile // 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. /1148 Reserved 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. 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 in progress may need access to files" // *Cause: Either media recovery or instance recovery is in progress. It may // need the files this operation is being applied to. // *Action: Wait for recovery 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 controlfiles 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 controlfile appears more than once in the control_files p // 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 controlfile, 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 controlfiles themselves are unique. For example, in UNIX // check for a symbolic or a hard link to another controlfile 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 controlfile or a datafile from the system tablespace was // omitted from the create controlfile command previously issued. // *Action: For the former problem you need to recover the database from a // more recent controlfile. For the latter problem, simply recreate the // controlfile 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 controlfile. // *Action: Recreate the controlfile with a larger MAXDATAFILES. 01177, 00000, "data file does not match dictionary - probably old incarnation" // *Cause: When comparing the controlfile 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 CONTROL file command. // The information needed to recreate the file was lost with the // controlfile 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 RESETLOGS, cannot recreate" // *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a // datafile that existed at the last RESETLOGS database open. // *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, "Block size %s in header does not match physical block size %s" // *Cause: A log file member given to CREATE CONTROLFILE is on a physical // device that has a different block size than the device originally // used to create the log. // *Action: Move the file to a device with the correct block size or use the // RESETLOGS option to CREATE CONTROLFILE. 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, "controlfile 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 controlfile. Either the data file // or the controlfile 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 // controlfile. 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 controlfile. 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 controlfile. 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 controlfile. 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 controlfile. 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 controlfile - old controlfile" // *Cause: The controlfile change sequence number in the data file is // greater than the number in the controlfile. This implies that // the wrong controlfile 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 // controlfile change sequence number until it is great enough. // *Action: Use the current controlfile or do backup controlfile recovery to // make the controlfile current. Be sure to follow all restrictions // on doing a backup controlfile 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 controlfile 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 controlfile 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 read only" // *Cause: An attempt to start an online backup found that one of the files is // marked read only. Read only files do not need to be set into // online backup mode. // *Action: Make the backup without the begin backup command. 01233, 00000, "file %s is read only - cannot recover using backup controlfile" // *Cause: An attempt to do media recovery using a backup controlfile 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 // controlfile 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 controlfile // from the time the file was read-write. If the correct controlfile // 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 controlfile by media recovery" // *Cause: Media recovery with a backup controlfile or a controlfile that // was rebuilt, encountered the creation of a datafile that was not // in the controlfile. An entry has been added to the controlfile // 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 // controlfile 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 controlfile is needed to allow the RESETLOGS. // Another backup can be restored and recovered, or a controlfile 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, "may not issue ALTER DATABASE END BACKUP when database is open" // *Cause: ALTER DATABASE END BACKUP was issued while the database was open. // *Action: Either use ALTER DATABASE DATAFILE END BACKUP // to end backup for specific files, or ALTER TABLESPACE // END BACKUP if backup is complete for all files in a tablespace. 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 for a // datafile, logfile or control file. // *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 file %s" // *Cause: An error prevented the file from being deleted. // *Action: Subsequent errors describe the operating system error that // prevented the file deletion. Fix the problem, if possible, and // manually purge the file. 01266, 00000, "Unable to create unique file name" // *Cause: Unable to create a unique file name for an Oracle // managed datafile, logfile, or control 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 or // DB_CREATE_ONLINE_LOG_DEST_n parameter is 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. 01274, 0000, "cannot add datafile '%s' - file could not be created" // *Cause: Automated standby file management was enabled but an added file // could not automatically be created on the standby. // The error from the creation attempt is displayed in another message. // The controlfile file entry for the file will be 'UNNAMEDnnnnn'. // *Action: Temporarily set STANDBY_FILE_MANAGEMENT to MANUAL and use // the ALTER DATABASE CREATE DATAFILE statement to create the // file. Then 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 a file with an Oracle Managed Files file name." // *Cause: An attempt was made to add to the database a datafile, log file, or // control file with an Oracle Managed Files file name. // *Action: Retry the operation with a new file name. / / 1280-1399 LogMiner errors / 01280, 00000, "Fatal LogMiner Error." // *Cause: An internal error has occurred inside LogMiner. // *Action: 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: StartDate may be greater than EndDate. Alternatively, there may // be no logfile that is compatible with the date range specified // with StartDate and EndDate. // *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. // *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, "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. 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. 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 data 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, "time or SCN range not fully contained in the listed logfiles" // *Cause: The input date/SCN range is not fully contained within the // logfiles specified for the session. // *Action: select out of v$logmnr_logs view to check the date or SCN range // covered by the logfiles specified for the LogMiner session, // and reissue the procedure with appropriate date or SCN range. 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, "dictionary %s and the earliest logfile are not SCN-compatible" // *Cause: The dictionary snapshot was taken at a SCN that does not // correspond to the creation SCN of the earliest logfile. // *Action: Get a correct dictionary snapshot. 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, "enabled thread bit vector mismatch between dictionary %s and the earliest logfile" // *Cause: // *Action: 01301, 00000, "dbms_logmnr.USE_COLMAP can only be used with a valid dictionary" // *Cause: dbms_logmnr.USE_COLMAP can only be used with a valid dictionary. // *Action: Specify the dictionary file in dbms_logmnr.start_logmnr(). 01302, 00000, "syntax error in logmnr.opt file" // *Cause: A syntax error was detected in the logmnr.opt file. // *Action: Use correct syntax. 01303, 00000, "schema %s, specified in logmnr.opt file, does not exist" // *Cause: The schema specified does not exist. // *Action: Specify a correct schema or a compatible dictionary file. 01304, 00000, "table %s, schema %s, specified in logmnr.opt file, does not exist" // *Cause: The table specified in the logmnr.opt file does not exist in the // dictionary provided to LogMiner. // *Action: Make sure that the table specified is valid. 01305, 00000, "column %s, specified in logmnr.opt file, does not exist in table %s, schema %s" // *Cause: The column specified in logmnr.opt file does not exist for the // table definition in the dictionary provided for LogMiner. // *Action: Make sure that the column specified is valid. 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. 01318, 00000, "Logminer session not started" // *Cause: Logminer activate session was called before prepare session. // *Action: 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, "SCN range not fully contained in the listed logfiles" // *Cause: The input date/SCN range is not fully contained within the // logfiles specified for the session. // *Action: select out of v$logmnr_logs view to check the date or SCN range // covered by the logfiles specified for the LogMiner session, // and reissue the procedure with appropriate date or SCN range. 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 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: Ensure that init.ora parameters enabling archivelog mode are set. // For example: // log_archive_start=true // log_archive_dest="/vobs/oracle/dbs" // log_archive_format="arch%s.log" // 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 8.2 or greater required to build into the logstream" // *Cause: Compatibility mode set to some value less than 8.2 // *Action: Ensure that init.ora parameter establishing a compatability of // 8.2 or greater is set. For example: // compatible=8.2.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 require build table" // *Cause: The table may be missing, or locked by another user. // *Action: This error should not occur. If it does occur and there is // reason to believe that required tables are missing then // as a last resort the package dbmslmd.sql may be reinstalled. // // Doing so will delete all existing Logminer Dictionary data. 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 file 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. // 01341, 00000, "LogMiner out-of-memory" // *Cause: The logfiles to be analyzed in the current LogMiner session // require more system resources than what is currently available. // *Action: Reduce the number of logfiles to be analyzed for a given // LogMiner session and try again. 01348, 00000, "LogMiner testing event" // *Cause: // *Action: 01349, 00000, "LogMiner tracing event" // *Cause: // *Action: // / / 1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE / 1349-1399 have been reserved for LogMiner / / 1400-1499 SQL execute phase errors / 01400, 00000, "cannot insert NULL into (%s)" // *Cause: // *Action: 01401, 00000, "inserted value too large for column" // *Cause: // *Action: 01402, 00000, "view WITH CHECK OPTION where-clause violation" // *Cause: // *Action: 01403, 00000, "no data found" // *Cause: // *Action: 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: // *Action: 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 allows for this column" // *Cause: // *Action: 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 a join view without a key-preserved table" // *Cause: // *Action: 01446, 00000, "cannot select ROWID from 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 " where 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 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: / / 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 database name was specified in the CREATE/ALTER DATABASE // statement, and no db_name INIT.ORA parameter was specified. // *Action: Either the database name must be given in the // statement or in the db_name INIT.ORA parameter. // Note that the SQLDBA STARTUP command issues an ALTER // DATABASE statement using the database name specified as // part of STARTUP (if any). 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. 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: During ALTER DATABASE, an error occurred while renaming // log or data files. // *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 controlfile // 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 controlfile. // *Action: Specify the name of an existing log file. 01516, 00000, "nonexistent log file, datafile or tempfile '%s'" // *Cause: An attempt was made to use ALTER DATABASE to either // rename a log file or datafile, or change attributes // of a datafile or tempfile. The attempt failed because // the specified file is not known to the database's // control file or is not a type supported for the request. // *Action: Specify the name of an existing file of the correct type. 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 controlfile. // *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 controlfile. // *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 controlfile. // *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" // *Cause: Specified rollback segment already exists. // *Action: Use a different name. 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 data 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. // *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). 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 controlfile, 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. 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, "out of transaction slots in transaction tables" // *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 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 DROP LOGFILE" // *Cause: The list of files supplied to DROP LOGFILE contains at least one // duplicate. // *Action: Remove the duplicate file specification and retry. 01567, 00000, "dropping log %s would leave less than 2 log files in 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 ] 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, "instance locking protocol version %s incompatible with ORACLE version %s" // *Cause: Current software uses incompatible locking protocol. // *Action: Upgrade software used to start up instances so that they use // compatible locking protocol. 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 // controlfile 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 controlfile for backup" // *Cause: An operating system error occurred while attempting to open a // controlfile for backup. // *Action: Check the error stack for more detailed information 01583, 00000, "unable to get block size of controlfile to be backed up" // *Cause: An operating system error occurred while attempting to // get the block size of a controlfile for backup. // *Action: Check the error stack for more detailed information 01584, 00000, "unable to get file size of controlfile to be backed up" // *Cause: An operating system error occurred while attempting to // get the file size of a controlfile 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 controlfile backup. // *Action: Check the error stack for more detailed information 01586, 00000, "unable to open destination file %s for backup" // *Cause: An operating system error occurred while attempting to open a // controlfile for backup. // *Action: Check the error stack for more detailed information 01587, 00000, "error during controlfile 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 controlfile backup. // *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 controlfile 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, "gc_files_to_locks not identical to that of another mounted instance" // *Cause: The gc_files_to_locks parameters were different on two instances. // *Action: Modify the INIT.ORA parameter gc_files_to_locks and restart. 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 controlfile was recreated with the RESETLOGS // option, or the controlfile being used is a backup controlfile. // 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 controlfile. // *Action: Use a thread number that is valid, or resize the thread record // and/or checkpoint progress record sections of the controlfile. 01612, 00000, "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, "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, "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, "thread %s is mounted - cannot disable" // *Cause: Some instance, possibly this one, has allocated the thread for its // use. The thread may not be disabled while in use. // *Action: Shutdown cleanly the instance using the thread. 01616, 00000, "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 controlfile. // *Action: Shutdown the instance, change the INIT.ORA parameter and // startup, or resize the thread record and/or checkpoint progress // record sections of the controlfile. 01618, 00000, "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 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 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. 01640, 00000, "cannot make tablespace read only with active transactions" // *Cause: Attempting to make a tablespace read only while there are active // transactions in the database. All transactions must commit or // rollback to insure that there is no undo for a tablespace before // it can be made read only. This includes in doubt distributed // transactions. // *Action: Prevent any more transactions from being started. Putting the // database in restricted mode usually helps. If there are any in // doubt transactions they must also 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 thread %s" // *Casue: 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 controlfile" // *Cause: An attempt is being made to perform a command that does not make // sense when the controlfile 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 for rollback segment in 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 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 for temp segment in tablespace. // *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 for table segment in tablespace. // *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 for index segment in tablespace. // *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 for cluster segment in tablespace. // *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, "controlfile is not a standby controlfile" // *Cause: Attempting to mount, recover or activate a standby database // without a standby controlfile. // *Action: Create a standby controlfile before attempting to use the database // as a standby database. 01666, 00000, "controlfile 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 controlfile. 01667, 00000, "cannot add any more tablespaces: limit of %s exceeded" // *Cause: There is no more room in the controlfile for adding tablespaces. // *Action: Resize the controlfile 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 controlfile not consistent" // *Cause: Attempting to activate a standby database with a controlfile that // has not been recovered to the same point as the data files. Most // likely the controlfile 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, "controlfile is a backup, cannot make a standby controlfile" // *Cause: The currently mounted controlfile is a backup controlfile, and // attempting to create a controlfile for a standby database. // *Action: Complete any needed recovery and open the database with the // resetlogs option. 01672, 00000, "controlfile may be missing files or have extra ones" // *Cause: Attempting to create a standby controlfile, but the controlfile // was either recently created via CREATE CONTROLFILE or an incomplete // recovery has been done. Thus the datafiles in the controlfile // 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 controlfile after an incomplete // recovery or CREATE CONTROLFILE. Since information from its // header is needed for standby database recovery, we can not // create a standby controlfile. // *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 controlfile 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 must be mounted EXCLUSIVE and not open to activate" // *Cause: An attempt to activate a standby database was made when the // database was not mounted EXCLUSIVE or was already open. // *Action: Mount the database EXCLUSIVE and retry the ACTIVATE command. 01680, 00000, "unable to extend LOB segment by %s in tablespace %s" // *Cause: Failed to allocate an extent for a LOB segment in tablespace. // *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 for index segment in tablespace. // *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 for table segment in tablespace. // *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 for lob segment in tablespace. // *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 for lob segment in tablespace. // *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, "controlfile is not a clone controlfile" // *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 controlfile for a clone. // *Action: Mount without the clone option or use a backup controlfile and // shutdown the other instances before mounting as a clone. 01697, 00000, "controlfile 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 controlfile. 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: // *Action: 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: // *Action: 01723, 00000, "zero-length columns are not allowed" // *Cause: // *Action: 01724, 00000, "floating point precision is out of range (1 to 126)" // *Cause: Self-evident. // *Action: Self-evident. 01725, 00000, "USERENV('COMMITSCN') not allowed here" // *Cause: The function USERNEV('COMMMITSCN') is only allowed as a top-level // expression in the VALUES clause of an INSERT statements, 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 either had no key perserved tables, // had more than one key-preserved table, or the key-preserved // table was an unmerged view or a table from a read-only 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 table's owner name is not allowed" // *Cause: // *Action: 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: // *Action: 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: (+) () 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. / / 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 13" // *Cause: The time zone hour specified was not in the valid range. // *Action: Specify a time zone hour between -12 and 13. 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 %d is invalid" // *Cause: The region id referenced an invalid region. // *Action: Please contact Oracle Customer Support. 01882, 00000, "timezone region %s not found" // *Cause: The specified region name was not found. // *Action: Please contact Oracle Customer Support. 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. 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: UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER // privilege cannot 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, "invalid option for OPTIMIZER_GOAL" // *Cause: An invalid OPTIMIZER_GOAL option is present. // *Action: Check the syntax for OPTIMIZER_GOAL, specify a valid option and // re-execute the statement. 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: cannot add users to public password file" // *Cause: // *Action: 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 mode has changed from '%s' to '%s'" // *Cause: // *Action: / / 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." 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 is full, because too many // distributed transactions are active. // *Action: increase the INIT.ORA "distributed_transactions" or 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 in same transaction failed" // *Cause: a session at the same site with same global transaction ID failed. // *Action: none necessary, transaction automatically recovered. 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 with // OUT parameters. // *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, "no new sessions may join a committing distributed transaction" // *Cause: A call to UPI2BG was issued in a session for a transaction that // has begun to commit in a different branch; that is, a call to // upi2en was issued for a branch of the same transaction in another // session. This can only happen when using an external transaction // manager. // *Action: Contact support. // 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 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: attempt to create a database link with the same name as the // current database. // *Action: a loopback database link needs a trailing qualifier, e.g. // MYDB.DEV.US.ORACLE.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 / 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) / 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 is not present. // *Action: Use one of the valid options: add, rename, default, online, // offline, read only, read write, begin, and end. 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. 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. 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 appears. // *Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, // ONLINE, OFFLINE. 02181, 00000, "invalid option to ROLLBACK WORK" // *Cause: A token other than TO follows ROLLBACK [WORK]. // *Action: Place nothing or TO SAVEPOINT 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. 02189, 00000, "ON required" // *Cause: In a grant or revoke statement, the user specified a tablespace // quota but did not follow it with the ON clause. // *Action: Specify the tablespace on which the quota is to be applied // with the ON clause. 02190, 00000, "keyword TABLES expected" // *Cause: The keyword TABLES is expected following DROP CLUSTER // INCLUDING. // *Action: Place TABLES after INCLUDING. 02191, 00000, "correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT " // *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 [ . ] 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 BLOCK SIZE , ...)" // *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 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 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 dependents. // There could be a substitutable column of a supertype of the type // being dropped. // *Action: Drop all type(s) and table(s) depending on the type, then retry // the operation using the VALIDATE option, or use 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. // //02312, 00000, "cannot create extent table for VALUE ADT" // *Cause: attempt to create extent table for VALUE ADT. // *Action: specify object type when creating extent table. // 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, "cannot create index on object type column or attribute" // *Cause: An attempt was made to create an index on an object type column. // *Cause: attempt to create an index on an object type column // *Action: index can only be created on simple, scalar columns or attributes. 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. //02316, 00000, "incorrect number of attributes in object type column" // *Cause: number of attributes in object type operand doesn't // match number of attributes in object type column to be updated. // *Action: ensure both object type attributes match. //02317, 00000, "invalid operation for object type operands" // *Cause: specified an invalid operation on object type operands // *Action: ensure correct operation to be performed on object type operands. //02318, 00000, "invalid REF function on non-object table" // *Cause: specified REF operator is invalid on a non-object table // *Action: REF operator can only be specified on an object table. //02319, 00000, "invalid column argument to REF operator" // *Cause: specified an invalid REF column argument // *Action: argument to REF operator can only be the object type column of the // object table. // *Action: The argument to a REF operator can only be the object type // column of the object table. 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, "object type's default constructor expected" // *Cause: // *Action: specify an ADT default constructor. 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. //02323, 00000, "fail in %s inner table for column %s" // *Cause: An error occured while performing DML on the nested table column. // *Cause: an error occurs while performing DML on the nested table column. // *Action: If the situation described in the next error on the stack // 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. //02325, 00000, "zero rows returned by THE subquery" // *Cause: THE subquery evaluation returns no rows whereas it is supposed to // return a single row. // *Action: change subquery within THE operator to return exactly one row. //02326, 00000, "missing THE keyword" // *Cause: subquery used to return an inner nested table is enclosed // by THE operator // *Action: Put THE operator around the subquery, e.g. THE(subquery). 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. //02328, 00000, "REF column cannot be specified on VALUE ADT" // *Cause: attempt to create REF column of VALUE ADT // *Action: remove REF specifier from column specification 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. //02341, 00000, "cannot refer to non-queryable type %s in SQL" // *Cause: attempt to refer to an object type attribute that is of a // non-queryable type in SQL // *Action: change attribute type to a SQL-queryable type, or reference // the attribute through a 3GL 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. //02350, 00000, "cannot insert into attributes of a packed typed table" // *Cause: specifying a column list in an insert statement // *Action: drop the column list specification // statement. / / / / 2351 - 2375 Direct Loader errors / see also range 2476 - 2479 for Parallel Direct Loader errors / and range 26000 - 26999 for additional Direct Loader errors / 02351, 00000, "Record %s: Rejected - Error on table %s, column %s" // *Cause: The record indicated caused an oracle error on insert. // *Action: Determine the oracle error and correct the record. 02352, 00000, "Direct path connection must be homogeneous" // *Cause: The user-side to kernel-side connection is heterogenous. // *Action: In versions prior to 8.2, the connection must be between // identical hardware and O/S's. Also, the SQL*Loader and RDBMS // versions must be the same. 02353, 00000, "Multibyte character error" // *Cause: Text specified by POSITION or terminated by newlines is invalid. // *Action: Edit the controlfile or the data file to fix alignment of column. 02354, 00000, "Conversion initialization error occurred on field %s" // *Cause: An error occurred during conversion initialization for a field. // *Action: Internal error. Contact customer supprt. 02355, 00000, "Conversion error occurred on CONSTANT field %s" // *Cause: A CONSTANT field caused an oracle error; all rows will be rejected. // *Action: Determine the oracle error and correct the record. 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, "Packed Decimal conversion error" // *Cause: The column could not be converted from packed decimal to character. // *Action: Check the column and make it conform to packed decimal format. 02358, 00000, "Zoned Decimal conversion error" // *Cause: The column could not be converted from packed decimal to character. // *Action: Check the column and make it conform to packed decimal format. 02359, 00000, "Field in data file exceeded maximum specified length" // *Cause: The field is too long for the specified column. // *Action: Shorten the field so that its length is =< the column length. 02360, 00000, "Column not found before end of logical record (use TRAILING NULLCOLS)" // *Cause: A column started after the end of the logical record had been reached. // *Action: Use the TRAILING NULLCOLS option or supply data for the column. 02361, 00000, "Initial enclosing character not found" // *Cause: The initial enclosing character of an enclosed field was not found. // *Action: Supply the character before the start of the field. 02362, 00000, "Logical record ended - second enclosing character not present" // *Cause: The second enclosing character of an enclosed field was not found. // *Action: Supply the character after the end of the field. 02363, 00000, "No terminator found after TERMINATED and ENCLOSED field" // *Cause: No terminator was found after a terminated and enclosed field. // *Action: Supply the character after the end of the field. 02364, 00000, "Record %s: Discarded - failed all WHEN clauses" // *Cause: The record was not loaded because it failed all tables' WHEN clauses. // *Action: none. 02365, 00000, "Index %s was made Index Unusable due to" // *Cause: The index was not loaded because of the error specified. // *Action: Correct the error, then reload. 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, "Index %s was loaded." // *Cause: The index was loaded. // *Action: none. 02368, 00000, "Record %s: Discarded - all columns null." // *Cause: The record was not loaded because all tables' columns were null. // *Action: none. 02369, 00000, "Warning: Variable length field was truncated." // *Cause: A variable length field was truncated by the end of the logical // record. // *Action: This is just a warning, but since a variable length field has the // length embedded in the data for each row, you may want to check your data. 02370, 00000, "Record %s - Warning on table %s, column %s" // *Cause: The record indicated caused an warning. // *Action: Determine the warning and correct the record if necessary. 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, "Relative start position > absolute field end position." // *Cause: A field specified as POSITION(*+n:y) had its relative start occur // after the absolute position y. // *Action: Check that you are not missing a delimiter and that the values of // n and y are correct. 02373, 00000, "Error parsing insert statement for table %s." // *Cause: self-evident. // *Action: Check the error given below this one. 02374, 00000, "No more slots for read buffer queue." // *Cause: There are no free read buffers. // *Action: Use the READBUFFERS keyword in the loader to increase the number // of read buffers. 02375, 00000, "Record %s: Rejected - Error on table %s" // *Cause: The record indicated caused an ORACLE error on insert. // *Action: Determine the ORACLE error and correct the record. // The offending column(s) are not known. / / 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 prfile. // *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 / 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. / / 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 () - 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 // *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 option is not allow to be altered for HASH CLUSTERS" // *Cause: The SIZE can not be changed once the hash cluster has been // 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. / / 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_.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_.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_.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. 3008, 00000, "parameter COMPATIBLE >= %s needed for %s" // *Cause: An attempt was made to use a feature for a later Oracle version, // than the setting of the initialization parameter, COMPATIBLE. // *Action: Set COMPATIBLE to the value in the message (or higher), and // retry the command, but be aware that this will limit your // downgrade options. / / 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: // *Action: 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. / / 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. / 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. 03232, 00000, "unable to allocate an extent of %s blocks from tablespace %s" // *Cause: An attempt was made to specify a HASH_MULTIBLOCK_IO_COUNT value // that is greater than the tablespace's NEXT value // *Action: Increase the value of NEXT for the tablespace using // ALTER TABLESPACE DEFAULT STORAGE or decrease the value of // HASH_MULTIBLOCK_IO_COUNT. / 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" // *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 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 %s is not a member of tablespace %s" // MERGE: 2384 RENUMBERED TO 3284 // *Cause: The specified datafile does not belong to the tablespace // that the object resides in. // *Action: Retry the option with the correct datafile. 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 / / 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. 04018, 00000, "invalid value %s for parameter _scn_scheme" // *Cause: The value specified for init.ora parameter _scn_scheme // is not recognized as one of the defined schemes. // *Action: reassign a proper value. 04019, 00000, "SCN scheme incompatible with other instances" // *Cause: Either different instances are running incompatible Oracle // releases or different values have been assigned to the // _scn_scheme init.ora parameter on different instances. // *Action: Make sure the _scn_scheme init.ora parameter is set to the // same value on all instances. // / / 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 is 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. 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 has been 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. // *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 // INIT.ORA parameters "shared_pool_reserved_size" and // "shared_pool_size". // If the large pool is out of memory, increase the INIT.ORA // parameter "large_pool_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. / / 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 has occurred when trying to look up a remote object. // *Action: Fix the error. Make sure the remote database system has run // KGLR.SQL to create necessary views used for querying/looking up // objects stored in the database. 04053, 00000, "error occurred when validating remote object %s%s%s%s%s" // *Cause: An error has occurred when trying to validate a remote object. // *Action: Fix the error. Make sure the remote database system has run // KGLR.SQL to create necessary views used for querying/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. / / 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 / 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 . 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. 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:- => object is ORDN; // when is VMS, the object is ORDN.COM // when is UNIX, the object is ORDN // @d:::"task=" => object is ; // when is VMS, the object is .COM // when is UNIX, the object is // *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 = // 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_.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: // *Action: 06501, 00000, "PL/SQL: program error" // *Cause: // *Action: 06502, 00000, "PL/SQL: numeric or value error%s" // *Cause: // *Action: 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" // *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 in the context of a trigger" // *Cause: The program attempted to access a Serially Reusable package in // the context of a trigger. 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 the context of a trigger. // 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 does not need more rows // to be produced by the pipelined function. // *Action: Catch the NO_DATA_NEEDED exception is an exception handling // block. // 06549, 00000, "PL/SQL: failed to dynamically open shared object (DLL): %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, "top level procedure/function specified, cannot have subparts" // *Cause: The name to be resolved was specified with three parts (a.b.c) // but the a.b part resolves to a top level procedure or function // (which don't have nested procedures). This can also happen // with a two-part name, a.b, where a is a synonym for a top // level package or procedure. // *Action: Specify a procedure/function within a package, or a top level // procedure/function. 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" // *Cause: The specified shared pool shared cursor could not be found, // therefore it cannot be pinned. // *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 / 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. / / 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 // server machine's node name, network number, ethernet address, // and listening socket number are encoded in the file. 06803, 00000, "TLI Driver: the IPX device file could not be opened" // *Cause: The /dev/ipx file does not exist, or the driver has not been // installed in the kernel correctly. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06804, 00000, "TLI Driver: could not bind an IPX address at initialization" // *Cause: The IPX driver has not been correctly installed. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06805, 00000, "TLI Driver: could not send datagram SAP packet for SPX" // *Cause: The socket endpoint for sending SAP packet was corrupted for // some unknown reason. // *Action: Contact your customer support representative. 06806, 00000, "TLI Driver: could not complete protocol initialization for SPX" // *Cause: A step in the SPX/IPX protocol initialization failed. // *Action: Check the previous error reported, and follow corrective action. 06807, 00000, "TLI Driver: could not open ethernet device driver file" // *Cause: The file /dev/eth does not exist, or the driver it references // could not be opened. // *Action: The system's real ethernet device file, for example /dev/wd, for // the Western Digital ethernet driver, should be linked to the // file /dev/eth. If this has been done, insure that the ethernet // driver has been installed by completing the TCP/IP installation // on your system, and testing a connection. If problem continues, // contact your customer support representative for a list of // supported ethernet drivers. 06808, 00000, "TLI Driver: could not link IPX and ethernet streams" // *Cause: Either the ethernet driver has not been installed in the system // correctly, or the ethernet driver is not supported. // *Action: Insure that the ethernet driver has been installed by completing // the TCP/IP installation on your system, and testing a connection. // If problem continues, contact your customer support representative // for a list of supported ethernet drivers. 06809, 00000, "TLI Driver: could not clear the IPX ethernet SAP at init" // *Cause: The IPX driver has not been correctly installed. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06810, 00000, "TLI Driver: could not set the IPX ethernet SAP at init" // *Cause: The IPX driver has not been correctly installed. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06811, 00000, "TLI Driver: could not set the IPX network number at init" // *Cause: The IPX driver has not been correctly installed, or the // network number encoded in the /etc/netware/yellowpages file // is invalid. // *Action: The network number in the yellowpages file should match the // four-byte network number of your Novell file server. If this // is configured correctly, reinvoke the Oracle root installation. // If problem continues, contact your customer support representative. 06812, 00000, "TLI Driver: could not read the ethernet driver's node address" // *Cause: The ethernet driver is not installed correctly, or does not // support this operation. // *Action: Contact your customer support representative for a list of // supported ethernet drivers. 06813, 00000, "TLI Driver: the configured ethernet address is incorrect" // *Cause: The node address read from the ethernet driver does not match // the value encoded in the /etc/netware/yellowpages file for this // server. // *Action: Confirm the correct ethernet node address for your LAN card, and // enter this value in the yellowpages file. 06814, 00000, "TLI Driver: the SPX device file could not be opened" // *Cause: The /dev/nspxd file does not exist, or the driver has not been // installed in the kernel correctly. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06815, 00000, "TLI Driver: could not link SPX and IPX streams" // *Cause: The SPX driver has not been correctly installed. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06816, 00000, "TLI Driver: could not set the SPX SAP address" // *Cause: The SPX driver has not been correctly installed. // *Action: Reinvoke the Oracle root installation. If problem continues, // contact your customer support representative. 06817, 00000, "TLI Driver: could not read the Novell network address" // *Cause: The file $ORACLE_HOME/spx/address could not be opened for // reading and writing. // *Action: Make sure ORACLE_HOME is set, and the permissions on // the ORACLE_HOME are read, write. If this file has been // unintentially deleted, run spxctl (net option) to reset // the configured Novell network number for SQL*Net SPX. / / 6900-6999 Reserved for more SQL*Net errors / / 6900-6939 CMX errors / 06900, 00000, "CMX: cannot read tns directory" // *Cause: CMX is not started on your system. // *Action: Install and/or start CMX on your system. 06901, 00000, "CMX: no local name assigned to local application" // *Cause: Local application oracmx has no local name assigned // *Action: Enter unique local name for oracmx in the tns directory 06902, 00000, "CMX: cannot attach to cmx subsystem" // *Cause: ccp-xxxx is not started // *Action: start your ccp software on the communication controller 06903, 00000, "CMX: cannot read transport address of remote application" // *Cause: remote application not entered in tns directory // *Action: enter remote application in tns directory 06904, 00000, "CMX: no transport address available for remote application" // *Cause: no local name assigned to remote application // *Action: assign local name to remote application 06905, 00000, "CMX: connect error" // *Cause: remote partner not listening // *Action: make sure remote node has CMX installed and running // make sure oracmx is running on remote host 06906, 00000, "CMX: cannot get maximum packet size from CMX" // *Cause: internal error in CMX // *Action: contact your customer support representative 06907, 00000, "CMX: error during connect confirmation" // *Cause: remote partner aborted // *Action: contact your customer support representative 06908, 00000, "CMX: error during transfer of ORACLE_SID" // *Cause: remote partner aborted // *Action: contact your customer support representative 06909, 00000, "CMX: error during acknowledge of ORACLE_SID" // *Cause: remote partner aborted // *Action: contact your customer support representative 06910, 00000, "CMX: Cannot start oracle process on remote machine" // *Cause: oracle process not found or wrong mode (should be 4751) // *Action: change /etc/oratab or set mode to 4751 06911, 00000, "CMX: t_event returns ERROR" // *Cause: internal error in CMX // *Action: contact your customer support representative 06912, 00000, "CMX: write error in datarq" // *Cause: internal error in CMX // *Action: contact your customer support representative 06913, 00000, "CMX: error during redirection of connection" // *Cause: oracmx has been stopped, or user process has been aborted // *Action: contact your customer support representative 06914, 00000, "CMX: unexepected event during start of oracle" // *Cause: connect sequence out of sync // *Action: contact your customer support representative 06915, 00000, "CMX: unknown t_event in datarq" // *Cause: internal error in CMX // *Action: contact your customer support representative 06916, 00000, "CMX: error in data read (t_datain)" // *Cause: remote partner aborted // *Action: contact your customer support representative 06917, 00000, "CMX: error in data read (too many bytes read)" // *Cause: internal error in CMX // *Action: contact your customer support representative 06918, 00000, "CMX: T_NOEVENT during wait for read event" // *Cause: internal error in CMX // *Action: contact your customer support representative 06919, 00000, "CMX: error during write request (unknown event)" // *Cause: internal error in CMX // *Action: contact your customer support representative 06920, 00000, "CMX: getbrkmsg illegal datatype" // *Cause: received packets are corrupted // *Action: contact your customer support representative 06921, 00000, "CMX: getdatmsg illegal datatype" // *Cause: received packets are corrupted // *Action: contact your customer support representative 06922, 00000, "CMX: bad write length" // *Cause: internal error in CMX // *Action: contact your customer support representative 06923, 00000, "CMX: illegal break condition" // *Cause: break handling out of sync // *Action: contact your customer support representative 06924, 00000, "CMX: wrong break message length" // *Cause: received packets are corrupted // *Action: contact your customer support representative 06925, 00000, "CMX: disconnect during connect request" // *Cause: partner is not responding // *Action: make sure partner is up and running and reachable 06926, 00000, "CMX: T_ERROR during read data" // *Cause: internal error in CMX // *Action: contact your customer support representative 06927, 00000, "CMX: T_DATAIN received before all data written" // *Cause: internal error in CMX // *Action: contact your customer support representative 06928, 00000, "CMX: wrong ORACLE_SID" // *Cause: ORACLE_SID is not entered in remote oratab // *Action: add ORACLE_SID to remote oratab 06929, 00000, "CMX: error when sending ORACLE_SID" // *Cause: internal error in CMX // *Action: contact your customer support representative 06930, 00000, "CMX: error when checking ORACLE_SID" // *Cause: internal error in CMX // *Action: contact your customer support representative 06931, 00000, "CMX: error during read_properties for server" // *Cause: internal error in CMX // *Action: contact your customer support representative 06932, 00000, "CMX: error in local name" // *Cause: internal error in CMX // *Action: contact your customer support representative 06933, 00000, "CMX: error during attach" // *Cause: internal error in CMX // *Action: contact your customer support representative / // 6950 - 6999 Reserved for SQL*Net Appletalk errors / 06950, 00000, "No error" // *Cause: SQL*Net AppleTalk error codes base. This is not an error. // *Action: None. 06951, 00000, "Operating system call error" // *Cause: AppleTalk API received error in VMS system service. // *Action: Contact Oracle Customer Support representative. 06952, 00000, "Remote end of the communication issued a forward-reset packet. " // *Cause: Peer program may have aborted // *Action: Investigate network problems and try again. 06953, 00000, "Not enough virtual memory" // *Cause: Not enough memory available. // *Action: Check VMS process quotas and/or sysgen parameters 06954, 00000, "Illegal file name" // *Cause: Erroneous file name // *Action: Check path name for server output file, or SQL*Net Appletalk // Logical names and symbols. 06955, 00000, "Number of database servers exceed limit" // *Cause: Too many database connections. // *Action: Check ATKSRV_MAXCONparameter in configuration file. 06956, 00000, "Failed to get local host name" // *Cause: Unable to get Appletalk host name. // *Action: Check Appletalk configuration. 06957, 00000, "No SID is currently available" // *Cause: Incoming SQL*Net connection specified invalid SID name. // *Action: Specify correct SID in connect string and retry. 06958, 00000, "Failed to access configuration file" // *Cause: Unable to access CONFIG.ATK // *Action: Check file protections. 06959, 00000, "Buffer I/O quota is too small" // *Cause: Buffered I/O quota exceeded. // *Action: Increase BIOlm using AUTHORIZE utility and retry. 06960, 00000, "Failed to access log file" // *Cause: SQL*Net Appletalk listener could not create log file. // *Action: Check directory path and protections. 06961, 00000, "Insufficient privilege for attempted operation" // *Cause: // *Action: Check process privileges and retry. / / 6970 - 6989 X.25 Driver Errors / 06970, 00000, "X.25 Driver: remote host is unknown" // *Cause: Host name specified in the login (connect string) is unknown. // *Action: Check spelling; make sure name is in the X.25 HOST file. 06971, 00000, "X.25 Driver: error while receiving data" // *Cause: // *Action: 06972, 00000, "X.25 Driver: error while sending data" // *Cause: // *Action: 06973, 00000, "X.25 Driver: invalid buffer size" // *Cause: The buffer size specified in the login string must be between // 5 and 4096. // *Action: Re-submit with valid buffer size. 06974, 00000, "X.25 Driver: SID lookup failure" // *Cause: From the remote host's SQL*Net X.25 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 X.25 server). 06975, 00000, "X.25 Driver: connect to host failed" // *Cause: Connection attempt to remote host has failed. Probably means // that the SQL*Net X.25 server on the remote host is not up, // or the host itself is not up. // *Action: Start the SQL*Net X.25 server process on the remote host. 06976, 00000, "X.25 Driver: endpoint creation failure" // *Cause: Process open file quota probably exceeded. // *Action: Contact your customer support representative. 06977, 00000, "X.25 Driver: X.25 Level 2 failure" // *Cause: X.25 level 2 is down. X.25 link is not working. // *Action: Run system checks to verify functioning of X.25 software. // Contact your hardware vendor. 06978, 00000, "X.25 Driver: Too many callback tries" // *Cause: Call back address probably same as called address. // *Action: Verify that callback address and called address are different. 06979, 00000, "X.25 Driver: server cannot start oracle" // *Cause: The remote X.25 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. / / 7000-7099 Reserved for SQL*CONNECT/DB2 errors / / 7100-7199 Reserved for SQL*CONNECT/IMS errors / / 7200 - 7499 Reserved for UNIX OSD errors / 07200, 00000, "slsid: oracle_sid not set." // *Cause: The environment variable $(ORACLE_SID) is not set. // *Action: Set ORACLE_SID environment variable. 07201, 00000, "slhom: oracle_home variable not set in environment." // *Cause: $(ORACLE_HOME) environment variable not set. // *Action: Set ORACLE_HOME. 07202, 00000, "sltln: invalid parameter to sltln." // *Cause: The sltln name translation routine was called with invalid // arguments. The input, or output stings were either NULL or 0 length. // *Action: Probable internal oracle error. Contact customer support. 07203, 00000, "sltln: attempt to translate a long environment variable." // *Cause: A string was passed to sltln containing a long environment // variable. sltln accepts environment names of 30 or less characters. // *Action: Shorten environment variable name to less than 30 characters. 07204, 00000, "sltln: name translation failed due to lack of output buffer space." // *Cause: The sltln routine is given a maximum length buffer to expand // the name into. An overflow of this buffer occurred. // *Action: Possible internal error. Check output buffer length stored in // sercose[0]. Pathnames are limited to 255 characters. 07205, 00000, "slgtd: time error, unable to obtain time." // *Cause: Time() system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07206, 00000, "slgtd: gettimeofday error, unable to obtain time." // *Cause: Gettimeofday() system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07207, 00000, "sigpidu: process ID string overflows internal buffer." // *Cause: The sigpidu routine is given a maximum length buffer to hold // process ID string. An overflow of this buffer occurred. // *Action: Internal error. Contact customer support. 07208, 00000, "sfwfb: failed to flush dirty buffers to disk." // *Cause: The fsync system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07209, 00000, "sfofi: file size limit was exceeded." // *Cause: The size of the file to be opened exceeded the OS limit imposed // on this process. // *Action: Run osh to increase the file size limit. 07210, 00000, "slcpu: getrusage error, unable to get cpu time." // *Cause: Getrusage system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07211, 00000, "slgcs: gettimeofday error, unable to get wall clock." // *Cause: Gettimeofday system call returned an error. Possible OS error. // *Action: Check additional information returned in OS reference manual. // Contact customer support. 07212, 00000, "slcpu: times error, unable to get cpu time." // *Cause: times system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07213, 00000, "slgcs: times error, unable to get wall clock." // *Cause: times system call returned an error. Possible OS error. // *Action: Check additional information returned in OS reference manual. // Contact customer support. 07214, 00000, "slgunm: uname error, unable to get system information." // *Cause: uname system call returned an error. Possible OS error. // *Action: Check additional information returned in OS reference manual. // Contact customer support. 07215, 00000, "slsget: getrusage error." // *Cause: Getrusage system call returned an error. Possible OS error. // *Action: Check additional information returned. Look for information in // OS reference. Contact customer support. 07216, 00000, "slghst: gethostname error, unable to get name of current host." // *Cause: gethostname system call returned an error. Possible OS error. // *Action: Check additional information returned in OS reference manual. // Contact customer support. 07217, 00000, "sltln: environment variable cannot be evaluated." // *Cause: getenv call returned a null pointer. // *Action: Set the environment variable and try again. 07218, 00000, "slkhst: could not perform host operation" // *Cause: Unix system() call failed // *Action: Examine system error message 07219, 00000, "slspool: unable to allocate spooler argument buffer." // *Cause: Malloc failed to allocate space to hold spooler arguments. // *Action: Check additional information returned in OS reference manual. // The process may have run out of heap space. Contact customer // support. 07220, 00000, "slspool: wait error." // *Cause: Wait returned an error, when waiting for spool job to complete. // Possible spooler program error. // *Action: Check additional information returned. Refer to OS reference // manual. Contact customer support. 07221, 00000, "slspool: exec error, unable to start spooler program." // *Cause: Exec failed when starting line printer spooler command. Likely // that either the default line printer command, or ORACLE_LPPROG, // is incorrectly set. // *Action: Verify default line printer command and ORACLE_LPPROG are set // correctly. Set ORACLE_LPPROG to working line printer spooler. 07222, 00000, "slspool: line printer spooler command exited with an error." // *Cause: The line printer spooler exited with a non-zero return value. // This probably indicates an error in spooling file. // *Action: Verify that line printer spooler is up. Verify that // ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit // value returned as additional informatin. 07223, 00000, "slspool: fork error, unable to spawn spool process." // *Cause: Fork system call failed to create additional process. // Probable resource limit reached. // *Action: Check additional information returned. Retry operation. // Contact system administrator. 07224, 00000, "sfnfy: failed to obtain file size limit; errno = %s." // *Cause: The ulimit system call returned an error. // *Action: Check errno and contact customer support. 07225, 00000, "sldext: translation error, unable to expand file name." // *Cause: Additional information returned is error returned from sltln. // *Action: Check additional information. 07226, 00000, "rtneco: unable to get terminal mode." // *Cause: The ioctl call returned an error. Possible OS error. // *Action: Check additional information for errno. Contact customer support. 07227, 00000, "rtneco: unable to set noecho mode." // *Cause: The ioctl call returned an error. Possible OS error. // *Action: Check additional information for errno. Contact customer support. 07228, 00000, "rtecho: unable to restore terminal to echo mode." // *Cause: The ioctl call returned an error. Possible OS error. // *Action: Check additional information for errno. Contact customer support. 07229, 0000, "slcpuc: error in getting number of CPUs." // *Cause: error in mpcntl system call // *Action: check errno and contact system administrator 07230, 00000, "slemcr: fopen error, unable to open error file." // *Cause: Fopen failed to open file. // *Action: Try to determine which file was not opened. Check that file // exists and is accessible. 07231, 00000, "slemcc: invalid file handle, seals do not match." // *Cause: Function was called with an invalid argument. The file handle // used was not obtained be slemcr. // *Action: Internal error. Contact customer support. 07232, 00000, "slemcc: fclose error." // *Cause: An error was encountered when closing the file. Possible OS error. // *Action: Contact system administator. 07233, 00000, "slemcw: invalid file handle, seals do not match." // *Cause: Function was called with an invalid file handle. File handle // was not obtained by slemcr. // *Action: Internal error. Contact customer support. 07234, 00000, "slemcw: fseek error." // *Cause: Unable to seek to desired position in file. Possible OS error. // Possible internal error. // *Action: Verify that error message file is intact. Try to regenerate // error message file. Contact customer support. 07235, 00000, "slemcw: fwrite error." // *Cause: Unable to write item to file. Possible OS error. // Possible permissions problem. // *Action: Retry operation. 07236, 00000, "slemop: open error." // *Cause: Unable to open error file. Possible permissions problem. // *Action: Verify permission on error message file. Check additional // information for errno. 07237, 00000, "slemcl: invalid file handle, seals do not match." // *Cause: Function was called with an invalid file handle. Handle was not // obtained by previous call to slemop. // *Action: Internal error. 07238, 00000, "slemcl: close error." // *Cause: Unable to close file. Possible OS error. // *Action: Contact system administator. Check additional information // for errno. 07239, 00000, "slemrd: invalid file handle, seals do not match." // *Cause: Function was called with invalid file handle. Handle was not // obtained by call to slemop. // *Action: Internal error. Contact customer support. 07240, 00000, "slemrd: seek error." // *Cause: Unable to seek to desired position in file. Possible OS error. // *Action: Check that error file is still intact. Verify space on device. // Contact system administrator. Check additional information for // errno. 07241, 00000, "slemrd: read error." // *Cause: Unable to read file. Possible OS error. // *Action: Verify that error file is intact. Regenerate error message file. // Contact customer support. Check additional information for errno. 07242, 00000, "slembfn: translation error, unable to translate error file name." // *Cause: Additional information indicates error returned from sltln. // *Action: Check additional information. 07243, 00000, "supplied buffer not big enough to hold entire line" // *Cause: supplied buffer was not big enough // *Action: Internal error. Contact customer support. Additional information // indicates how big the supplied buffer was. 07244, 00000, "ssfccf: create file failed, file size limit reached." // *Cause: An attempt was made to create a file that exceeds the process's file // size limit. // *Action: Run osh to raise the file size limit. 07245, 00000, "sfccf: unable to lseek and write the last block." // *Cause: An attempt was made to move and write to a bad device address. // *Action: Check errno. Possible lack of space on device. 07246, 00000, "sfofi: open error, unable to open database file." // *Cause: sfofi returns an error. // *Action: This is an oracle internal error. 07247, 00000, "sfrfb: read error, unable to read requested block from database file." // *Cause: sfrfb returns an error. // *Action: This is an oracle internal error. 07248, 00000, "sfwfb: write error, unable to write database block." // *Cause: sfwfb returns an error. // *Action: This is an oracle internal error. 07249, 00000, "slsget: open error, unable to open /proc/pid." // *Cause: open() returns an error. // *Action: Check that /proc has the right permissions. 07250, 00000, "spcre: semget error, unable to get first semaphore set." // *Cause: An error occurred when trying to get first semaphore set. // *Action: Check errno. Verify that system is configured to have semaphores. // Verify that enough semaphores are available. Additional // information indicates how many semaphores were requested. 07251, 00000, "spcre: semget error, could not allocate any semaphores." // *Cause: Semget failed to even allocate a single semaphore. Either they are // all in use or the system is not configured to have any semaphores. // *Action: Check to see if all semaphores are in use. Check to see if // system is configured to have semaphores. Check errno. 07252, 00000, "spcre: semget error, could not allocate semaphores." // *Cause: Semget system call returned an error. Possible resource limit // problem. // *Action: Check errno. Verify that enough semaphores are available in system. // If additional errors occur in destroying the semaphore sets then sercose[0] // will be non-zero. If this occurs, remove the semaphore sets using ipcrm. 07253, 00000, "spdes: semctl error, unable to destroy semaphore set." // *Cause: Semctl system call returned an error. // *Action: Check semaphore sets. May require manual cleanup. Check additional // information returned. Consult OS reference manual. 07254, 00000, "spdcr: translation error while expanding ?/bin/oracle." // *Cause: An error occurred while translating the name of the oracle // executable. // *Action: Check sercose[0] for error returned from sltln. Perhaps // $(ORACLE_HOME) is not set correctly. 07255, 00000, "spini: cannot set up signal handler." // *Cause: System failed to set up signal handler. // *Action: Check errno and sercose[0] for the signal number that failed. 07256, 00000, "sptrap: cannot set up signal handler to catch exceptions." // *Cause: System failed to set up signal handler to catch exceptions. // *Action: Check errno and sercose[0] for the signal number that failed. 07257, 00000, "spdcr: translation error expanding program name." // *Cause: Error ocurred when expanding program name ora_PNAME_@. The result // of this translation is put in argv[0] of oracle process. // *Action: Check error returned by sltln returned in sercose[0]. 07258, 00000, "spdcr: fork error, unable to create process." // *Cause: An error occurred when creating a new process. // *Action: Check errno. Perhaps a system limit on the number of processes // has been exceeded. 07259, 00000, "spdcr: exec error, detached process failed in startup." // *Cause: An oracle detached process died shortly after startup. Wait() // indicated that a child process terminated. // *Action: Check ?/dbs directory for trace or core files. Check errno. 07260, 00000, "spdcr: wait error." // *Cause: Wait system call returned an error. // *Action: Check errno. 07261, 00000, "spdde: kill error, unable to send signal to process." // *Cause: Kill system call returned an error. Possibly an attempt to // destroy an already gone process. // *Action: Check errno. 07262, 00000, "sptpa: sptpa called with invalid process id." // *Cause: This is an internal error. // *Action: This is an oracle internal error. 07263, 00000, "sptpa: kill error." // *Cause: Kill system call returned an error. Possible OS error. // *Action: Check errno. Additional information indicates the process // ID tested. 07264, 00000, "spwat: semop error, unable to decrement semaphore." // *Cause: Semop system call returned an error. Semaphore set may not exist. // *Action: Check errno. Semaphore ID is returned in sercose[0]. Verify // semaphore set exists. A possible cause for this error is that a // "shutdown abort" was done while this process was running. 07265, 00000, "sppst: semop error, unable to increment semaphore." // *Cause: Semop system call returned an error. Semaphore set may not exist. // *Action: Check errno. Semaphore ID is returned in sercose[0]. Check // semaphore set existence. A possible cause for this error is that a // "shutdown abort" was done while this process was running. 07266, 00000, "sppst: invalid process number passed to sppst." // *Cause: Function was passed an invalid oracle process id. // *Action: Internal error. 07267, 00000, "spwat: invalid process number." // *Cause: Function was passed an invalid oracle process id. // *Action: Internal error. Additional information indicates the invalid // process id. 07268, 00000, "szguns: getpwuid error." // *Cause: Getpwuid() could not find an entry in the passwd file for a // user. // *Action: Add an entry for the user in the passwd file. 07269, 00000, "spdcr: detached process died after exec." // *Cause: Detached process succesfully execed, but died shortly thereafter. // Additional information indicates exit code, and termination status. // *Action: Check termination code for information as to why process exited. // Check for core dump or trace file. 07270, 00000, "spalck: setitimer error, unable to set interval timer." // *Cause: An error occurred while trying to set an interval timer. // Probable porting problem. // *Action: Check errno. 07271, 00000, "spwat: invalid oracle process number." // *Cause: Function was called with an invalid oracle process number (0). // *Action: Internal oracle error. 07272, 00000, "spwat: invalid semaphore set id." // *Cause: Semaphore ID fetched from SGA was not initialized to valid // value. Additional information returned is semaphore set index, // and oracle process number. // *Action: Oracle internal error. Check semaphore set index. // Check oracle process number. 07273, 00000, "sppst: invalid semaphore id." // *Cause: Semaphore ID fetched from SGA contained an invalid value. // Additional information returned is semaphore set index, and // oracle process number. // *Action: Oracle internal error. Check semaphore set index. Check oracle // process number. 07274, 00000, "spdcr: access error, access to oracle denied." // *Cause: Unable to access "oracle" program. Verify ?/bin/oracle or // $ORABCKPRG exist, and are executable. // *Action: Check errno returned. 07275, 00000, "unable to send signal to process" // *Cause: The kill system call returned an error. Possibly an attempt to // signal a process which does not exist. // *Action: Check errno. 07276, 00000, "no dba group in /etc/group." // *Cause: A group has not been set up for dba users. // *Action: Contact system administrator. Set up dba group in /etc/group. 07277, 00000, "spdde: illegal pid passed as argument." // *Cause: A 0 pid was passed to spdde. // *Action: Internal error. . 07278, 00000, "splon: ops$username exceeds buffer length." // *Cause: Splon constructed an ops$username logon which exceeded the // alloted buffer space. // *Action: Use a shorter Unix username, or use an oracle username. // Contact customer support. 07279, 00000, "spcre: semget error, unable to get first semaphore set." // *Cause: An error occurred when trying to get first semaphore set. // *Action: Check errno. Verify that system is configured to have semaphores. // Verify that enough semaphores are available. Additional information // indicates how many semaphores were requested. 07280, 00000, "slsget: unable to get process information." // *Cause: The ioctl call returned an error. Possible OS error. // *Action: Check additional information for errno. Contact customer support. 07281, 00000, "slsget: times error, unable to get cpu time." // *Cause: times system call returned an error. Possible OS error. // *Action: Check additional information returned. Contact customer support. 07282, 00000, "sksaprd: string overflow." // *Cause: The internal buffer is not big enough to hold the archive control // string. // *Action: Internal restriction. Try a shorter archive control string. 07283, 00000, "sksaprd: invalid volume size for archive destination." // *Cause: An invalid volume size was specified. // *Action: Specify a valid volume size in archive control string. 07284, 00000, "sksaprd: volume size specification not terminated properly." // *Cause: Some non-numeric text follows the volume size specification. // *Action: Enter a correct archive control string. 07285, 00000, "sksaprd: volume size should not be specified for a disk file." // *Cause: Volume size was specified for a disk file. // *Action: If you are archiving to a disk file, do not specify its volume size. 07286, 00000, "sksagdi: cannot obtain device information." // *Cause: Stat on the log archiving device failed. // *Action: Check the returned OSD error for the reason of failure. 07287, 00000, "sksagdi: unsupported device for log archiving." // *Cause: Log archiving to this device is unsupported. // *Action: Try log archiving to a supported device. 07290, 00000, "sksagdi: specified directory for archiving does not exist." // *Cause: The specified pathname is not a directory. // *Action: Verify that the archive destination directory exists. 07303, 00000, "ksmcsg: illegal database buffer size." // *Cause: The database buffer size must be a multiple of the database block // size, and less than the maximum block size. // *Action: Verify that the db_block_size parameter is correct in INIT.ORA. 07304, 00000, "ksmcsg: illegal redo buffer size." // *Cause: The redo buffer size must be a multiple of machine block size. // *Action: Verify that the log_buffer INIT.ORA parameter is correctly set. 07305, 00000, "ksmcsg: illegal database buffer size." // *Cause: The database buffer size must be a multiple of the extended cache // mapping size for indirect data buffers to be used. // *Action: Verify that the db_block_size parameter is correct in INIT.ORA, or // disable the use_indirect_data_buffers parameter. 07324, 00000, "smpall: malloc error while allocating pga." // *Cause: Malloc library routine returned an error. // *Action: Check errno. Possibly out of swap space. 07327, 00000, "smpdal: attempt to destroy pga when it was not mapped." // *Cause: Smpdal was called when the PGA had not been previously created. // *Action: Internal error. 07339, 00000, "spcre: maximum number of semaphore sets exceeded." // *Cause: The internal buffer is not big enough to hold the number of // semaphore set identifiers requested. // *Action: Reconfigure OS to have more semaphores per set. 07345, 00000, "The datafile name must not contain the string '..'." // *Cause: The specified datafile name contains '..'. // *Action: Correct the datafile name and retry the operation. 07390, 00000, "sftopn: translate error, unable to translate file name." // *Cause: An error occurred while expanding the file name to open. Additional // information returns error generated in translation routine. // *Action: Lookup additional error code for further information. 07391, 00000, "sftopn: fopen error, unable to open text file." // *Cause: Fopen library routine returned an error. // *Action: Verify existence and permissions. 07392, 00000, "sftcls: fclose error, unable to close text file." // *Cause: Fclose library routine returned an error. // *Action: Possible internal oracle error. 07393, 00000, "unable to delete text file" // *Cause: An error occurred while deleting a text file. // *Action: Verify that the file exists and check additional errors. 07394, 00000, "unable to append string to text file" // *Cause: An error occurred while performing a string put operation. // *Action: This is an internal error. Check additional information. 07400, 00000, "slemtr: translated name for the message file is too long." // *Cause: The name for the message file overflows internal buffer. // *Action: Try making the complete path-name of the message file shorter // by reorganizing the directory hierarchy. 07401, 00000, "sptrap: cannot restore user exception handlers." // *Cause: The system failed to restore user exception handlers. // *Action: Check errno and sercose[0] for the signal number that failed. 07402, 00000, "sprst: cannot restore user signal handler." // *Cause: The system failed to restore user signal handlers. // *Action: Check errno and sercose[0] for the signal number that failed. 07403, 00000, "sfanfy: db_writers parameter not valid." // *Cause: The db_writers parameter in INIT.ORA exceeds the // system-dependent maximum or is less than 0. // *Action: Change the db_writers parameter in INIT.ORA. 07404, 00000, "sfareq: Timeout occurred waiting for request to complete." // *Cause: The master database writer timed out waiting for a write or // close to complete. One of the database writers may have // stopped running. // *Action: Check all database writer trace files. Shut down the // database and try to warm start. 07406, 00000, "slbtpd: invalid number." // *Cause: An impossible request for binary to decimal conversion was made. // *Action: This conversion cannot be performed. 07407, 00000, "slbtpd: invalid exponent." // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed. 07408, 00000, "slbtpd: overflow while converting to packed decimal." // *Cause: An impossible request for binary to decimal conversion was made. // *Action: This conversion cannot be performed. 07409, 00000, "slpdtb: invalid packed decimal nibble." // *Cause: An impossible request for decimal to binary conversion was made. // *Action: This conversion cannot be performed. 07410, 00000, "slpdtb: number too large for supplied buffer." // *Cause: An impossible request for decimal to binary conversion was made. // *Action: This conversion cannot be performed. 07411, 00000, "slgfn: full path name too big for supplied buffer." // *Cause: The supplied buffer is not big enough to hold the full path name. // *Action: The construction of the full path name cannot be performed. 07412, 00000, "sfaslv: Error getting entry in asynchronous write array." // *Cause: One of the database writer processes could not locate its // entry in the SGA. // *Action: Contact customer support. 07415, 00000, "slpath: allocation of memory buffer failed." // *Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. // *Action: System has run out of heap space. Additional information // indicates errno. 07416, 00000, "slpath: pathname construction failed; lack of output buffer space." // *Cause: The slpath routine is given a maximum length buffer to expand // the name into. An overflow of this buffer occurred. // *Action: Possible internal error. Check output buffer length stored in // sercose[0] and constructed pathname length in sercose[1]. 07417, 00000, "sfareq: One or more database writers not active." // *Cause: One or more of the database writer processes is no longer // running. // *Action: Check the trace files for the database writers. Shut down // the database and try to warm start. 07418, 00000, "sfareq: Database writer got error in timing function." // *Cause: An error occurred when the database writer called the system // timing function. // *Action: Check the database writer trace file. Shut down database and // try to warm start. 07419, 00000, "sfareq: Database writer got error in timing function." // *Cause: An error occurred when the database writer called the system // timing function. // *Action: Check the database writer trace file. Shut down database and // try to warm start. 07425, 00000, "sdpri: error %s in translating dump file location." // *Cause: An oracle error occurred when translating the location of the // dump file. // *Action: Check the oracle error code. 07426, 00000, "spstp: cannot obtain the location of dbs directory." // *Cause: An oracle error occurred when translating the location of the // dbs directory. // *Action: Check additional information for the error returned from sltln. 07427, 00000, "spstp: cannot change directory to dbs." // *Cause: Chdir system call returned an error. Possible permission problems. // *Action: Check additional information for the OS error code. 07431, 00000, "fork failed" // *Cause: The server process was unable to fork a child 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. 07432, 00000, "unable to perform nested sleep" // *Cause: An attempt was made to make a process sleep when it was // already sleeping. This platform does not support this capability. // *Action: Try the SLEEP command when the process is not sleeping. 07440, 00000, "WMON process terminated with error" // *Cause: The wakeup monitor process died. // *Action: Warm start instance. 07441, 00000, "function address must be aligned on %s byte boundary" // *Cause: An improperly aligned function address was specified. // *Action: Use a properly aligned function address. 07442, 00000, "function address must be in the range %s to %s" // *Cause: An invalid function address was specified. // *Action: Use a valid function address. 07443, 00000, "function %s not found" // *Cause: An invalid function name was specified. // *Action: Use a valid function name. 07444, 00000, "function address %s is not readable" // *Cause: An invalid function name/address was specified. // *Action: Use a valid function name/address. 07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]" // *Cause: An OS exception occurred which should result in the creation of a // core file. This is an internal error. // *Action: Contact your customer support representative. 07446, 00000, "sdnfy: bad value '%s' for parameter %s." // *Cause: The directory specified as the value for the stated parameter could // not be used. // *Action: Make sure the directory you have specified is a valid // directory/file specification. 07447, 00000, "ssarena: usinit failed." // *Cause: Oracle failed to create a shared arena file. // *Action: Use sercerrno field to determine cause of failure. 07448, 00000, "ssarena: maximum number of shared arenas exceeded." // *Cause: Oracle attempted to create more shared arena files than permitted. // *Action: Raise the value for max_arena in INIT.ORA. 07449, 00000, "sc: usnewlock failed." // *Cause: Oracle failed to acquire a shared arena lock. // *Action: Check result code in sercerrno to determine the cause of failure. 07451, 00000, "slskstat: unable to obtain load information." // *Cause: kstat library returned an error. Possible OS failure // *Action: Check result code in sercose[0] for more information. 07452, 00000, "specified resource manager plan does not exist in the data dictionary" // *Cause: User tried to load a resource manager plan that does not exist. // *Action: Use a resource manager plan that exists in the data dictionary. 07453, 00000, "requested resource manager plan schema does not contain OTHER_GROUPS" // *Cause: User tried to load a resource manager plan schema that does not // contain the OTHER_GROUPS group. // *Action: Use a resource manager plan schema that contains the // OTHER_GROUPS group. 07454, 00000, "queue timeout, %s second(s), exceeded" // *Cause: User session queued for longer than maximum specified queue // queue duration time for consumer group. // *Action: Re-submit job at a later time or increase queue timeout. 07455, 00000, "estimated execution time (%s secs), exceeds limit (%s secs)" // *Cause: User attempted to execute an operation whose estimated // execution time exceeds the limit specified for the // consumer group. // *Action: Execute job on behalf of another group, or increase limit. 07456, 00000, "cannot set RESOURCE_MANAGER_PLAN when database is closed" // *Cause: An attempt was made to turn on the Resource Manager when the // database was closed. // *Action: Open the database and try again. 07468, 00000, "spwat: mset error, unable to set semaphore." // *Cause: The mset routine returned an error. Semaphore may not exist. // *Action: Check result code in sercerrno. Semaphore number returned // in sercose[0]. 07469, 00000, "sppst: mclear error, unable to clear semaphore." // *Cause: The mclear routine returned an error. Semaphore may not exist. // *Action: Check result code in sercerrno. Semaphore number returned // in sercose[0]. 07470, 00000, "snclget: cannot get cluster number." // *Cause: The cluster_status system call failed to get status information // for the current cluster. // *Action: Check result code in sercose[0]. Possible operating system // failure. 07471, 00000, "snclrd: name translation error of sgadef.dbf file name." // *Cause: Unable to expand out ?/dbs/sgadef@.dbf file name. // *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. // Check error number returned from sltln in sercose[0]. 07472, 00000, "snclrd: open error when opening sgadef.dbf file." // *Cause: open failed when opening the file ?/dbs/sgadef@.dbf // *Action: Check errno. Possible permission problem. Verify that the // file ?/dbs/sgadef@.dbf exists. 07473, 00000, "snclrd: read error when trying to read sgadef.dbf file." // *Cause: Read had an error when reading sgadef.dbf file. // *Action: Check errno. Verify file exists, and is correct size. 07474, 00000, "snclrd: close error, unable to close sgadef.dbf file." // *Cause: An error occurred in close, while closing the file // "?/dbs/sgadef@.dbf" // *Action: Check errno. Possible operating system error. 07475, 00000, "slsget: cannot get vm statistics." // *Cause: The vm_statistics system call failed to get virtual memory // statistics. // *Action: Check result code in sercerrno. Possible operating system // failure. 07476, 00000, "slsget: cannot get mapped memory statistics." // *Cause: The vm_mapmem system call failed to get mapped memory // statistics. // *Action: Check result code in sercerrno. Possible operating system // failure. 07477, 00000, "scgcmn: lock manager not initialized." // *Cause: Lock manager must be initialized before converting locks. // *Action: Check result code in sercerrno. Possible lock manager failure. 07478, 00000, "scgcmn: cannot get lock status." // *Cause: lm_stat_lock failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07479, 00000, "scgcmn: cannot open or convert lock." // *Cause: lm_open or lm_open_convert failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07480, 00000, "snchmod: cannot change permissions on ?/dbs/sgalm.dbf." // *Cause: When creating an instance, snlmini could not change the // permissions on ?/dbs/sgalm.dbf // *Action: Contact your customer support representative. 07481, 00000, "snlmatt: cannot attach to lock manager instance." // *Cause: lm_attach failed to attach to lock manager instance. // *Action: Check result code in sercerrno. Possible lock manager failure. 07482, 00000, "snlmini: cannot create lock manager instance." // *Cause: lm_create failed to create lock manager instance. // *Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if // it exists, then retry. 07483, 00000, "snlkget: cannot convert(get) lock." // *Cause: lm_convert failed to convert(get) lock. // *Action: Check result code in sercerrno. Possible lock manager failure. 07484, 00000, "snlkput: cannot convert(put) lock." // *Cause: lm_convert failed to put lock value. // *Action: Check result code in sercerrno. Possible lock manager failure. 07485, 00000, "scg_get_inst: cannot open instance number lock." // *Cause: lm_open failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07486, 00000, "scg_get_inst: cannot convert(get) instance number lock." // *Cause: lm_convert failed to get lock value. // *Action: Check result code in sercerrno. Possible lock manager failure. 07487, 00000, "scg_init_lm: cannot create lock manager instance." // *Cause: lm_create failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07488, 00000, "scgrcl: lock manager not initialized." // *Cause: Lock manager must be initialized before releasing locks. // *Action: Check result code in sercerrno. Possible lock manager failure. 07489, 00000, "scgrcl: cannot get lock status." // *Cause: lm_stat_lock failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07490, 00000, "scgrcl: cannot convert lock." // *Cause: lm_convert failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07491, 00000, "scgrcl: cannot cancel lock request." // *Cause: lm_cancel failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07492, 00000, "scgrcl: cannot close lock." // *Cause: lm_close failed during lock release/cancel. // *Action: Check result code in sercerrno. Possible lock manager failure. 07493, 00000, "scgrcl: lock manager error." // *Cause: An error was encountered releasing the lock. // *Action: Check result code in sercerrno. Possible lock manager failure. 07494, 00000, "scgcm: unexpected error." // *Cause: Unknown or unexpected error code. // *Action: Check result code in sercerrno. Possible lock manager failure. 07495, 00000, "spwat: lm_wait failed." // *Cause: lm_wait failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07496, 00000, "sppst: lm_post failed." // *Cause: lm_post failed. // *Action: Check result code in sercerrno. Possible lock manager failure. 07497, 00000, "sdpri: cannot create trace file '%s'; errno = %s." // *Cause: The trace file cannot be created for writing. // *Action: Check if the dump directory exists and whether it is writable. 07498, 00000, "spstp: Unable to open /dev/resched." // *Cause: The rescheduling driver /dev/resched is not found or is // not working properly. // *Action: Check installation of the ORACLE rescheduling driver // in the AIX kernel. 07499, 00000, "spglk: Cannot reschedule." // *Cause: The rescheduling driver /dev/resched is not open. // This is an internal error and should not occur. // *Action: Contact your customer support representative. / / 7500-7999 VMS OSD ERRORS / 07500, 00000, "scglaa: $cantim unexpected return" // *Cause: VMS system service $CANTIM returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07501, 00000, "scgtoa: $deq unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07502, 00000, "scgcmn: $enq unexpected return" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07503, 00000, "scgcmn: $setimr unexpected return" // *Cause: VMS system service $SETIMR returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07504, 00000, "scgcmn: $hiber unexpected return" // *Cause: VMS system service $HIBER returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07505, 00000, "scggt: $enq parent lock unexpected return" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07506, 00000, "scgrl: $deq unexpected return on lockid %s" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07507, 00000, "scgcm: unexpected lock status condition" // *Cause: A global locking system service returned an unexpected value. // *Action: Check for system error message (if any) and refer to // VMS documentation, or contact your customer support // representative. 07508, 00000, "scgfal: $deq all unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07509, 00000, "scgfal: $deq parent lock unexpected return" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07510, 00000, "scgbrm: $getlki unexpected return on lockid %s" // *Cause: VMS system service $GETLKI returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07511, 00000, "sscggtl: $enq unexpected return for master termination lock" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07512, 00000, "sscggtl: $enq unexpected return for client termination lock" // *Cause: VMS system service $ENQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07513, 00000, "sscgctl: $deq unexpected return on cancel of term. lock" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07514, 00000, "scgcan: $deq unexpected return while canceling lock" // *Cause: VMS system service $DEQ returned an unexpected value // *Action: Check for system error message and refer to VMS documentation / 07534, 00000, "scginq: $getlki unexpected return on lockid %s" // *Cause: VMS system service $GETLKI returned an unexpected value // *Action: Check for system error message and refer to VMS documentation 07548, 00000, "sftopn: Maximum number of files already open" // *Cause: Too many test files open // *Action: This is an internal error, please report to Oracle 07549, 00000, "sftopn: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07550, 00000, "sftopn: $CONNECT failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07551, 00000, "sftcls: $CLOSE failure" // *Cause: VMS system service $CLOSE failed // *Action: Examine system error message and refer to VMS documentation 07552, 00000, "sftget: $GET failure" // *Cause: VMS system service $GET failed // *Action: Examine system error message and refer to VMS documentation 07561, 00000, "szprv: $IDTOASC failure" // *Cause: VMS system service $IDTOASC failed // *Action: Examine system error message and refer to VMS documentation 07562, 00000, "sldext: extension must be 3 characters" // *Cause: An extension was found but it is of improper length // *Action: This is an internal error, please report to Oracle 07563, 00000, "sldext: $PARSE failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07564, 00000, "sldext: wildcard in filename or extension" // *Cause: A wildcard was used in the file name // *Action: Reenter the file name completely 07565, 00000, "sldext: $SEARCH failure" // *Cause: VMS system service $SEARCH failed // *Action: Examine system error message and refer to VMS documentation 07568, 00000, "slspool: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07569, 00000, "slspool: $CLOSE failure" // *Cause: VMS system service $CLOSE failed // *Action: Examine system error message and refer to VMS documentation 07570, 00000, "szrfc: $IDTOASC failure" // *Cause: VMS system service $IDTOASC failed // *Action: Examine system error message and refer to VMS documentation 07571, 00000, "szrfc: $FIND_HELD failure" // *Cause: VMS system service $FIND_HELD failed // *Action: Examine system error message and refer to VMS documentation 07572, 00000, "szrfc: insufficient rolename buffer space" // *Cause: An OS role name was too long. // *Action: Re-define the role name to be of correct length. 07573, 00000, "slkhst: could not perform host operation" // *Cause: VMS system service LIB$SPAWN failed // *Action: Examine system error message and refer to VMS documentation 07574, 00000, "szrfc: $GETUAI failure" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07576, 00000, "sspexst: $GETJPIW failure on process ID %s" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07577, 00000, "no such user in authorization file" // *Cause: An attempt was made to set an INTERNAL password (for either DBA // or OPER privilege), but the corresponding VMS account (either // ORA__DBA or ORA__OPER) hasn't been created yet. // *Action: Add a VMS account for ORA__DBA and/or ORA__OPER before // trying to set a password for them. 07578, 00000, "szprv: $FIND_HELD failure" // *Cause: VMS system service $FIND_HELD failed // *Action: Examine system error message and refer to VMS documentation 07579, 00000, "spini: $DCLEXH failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07580, 00000, "spstp: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07581, 00000, "spstp: cannot derive SID from unexpected process name" // *Cause: A background process did not have name of correct form // *Action: If the job name was changed, restore it, otherwise this is // an internal error, please report to Oracle. 07582, 00000, "spstp: ORA_SID has illegal value" // *Cause: The ORA_SID must exist and be less than 6 characters // *Action: Consult the VMS Installation guide for information on setting // the SID. 07584, 00000, "spdcr: invalid value for ORA_sid_(proc_)PQL$_item" // *Cause: A logical name used to set a detached process quota value // has an invalid value (probably non-numeric). // *Action: Examine the values of these logical names, correct the one // in error, and retry. 07585, 00000, "spdcr: $PARSE failure" // *Cause: VMS system service $PARSE failed // *Action: Examine system error message and refer to VMS documentation 07586, 00000, "spdcr: $SEARCH failure" // *Cause: VMS system service $SEARCH failed // *Action: Examine system error message and refer to VMS documentation 07587, 00000, "spdcr: $CREPRC failure" // *Cause: VMS system service $CREPRC failed // *Action: Examine system error message and refer to VMS documentation 07588, 00000, "spdcr: $GETJPIW get image name failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07589, 00000, "spdde: system ID not set" // *Cause: The logical name ORA_SID doesn't translate to a valid value. // *Action: Check the value of ORA_SID in the process that gets the // error, and correct the installation or command procedures // that caused ORA_SID to be set incorrectly. 07590, 00000, "spdde: $DELPRC failure" // *Cause: VMS system service $DELPRC failed // *Action: Examine system error message and refer to VMS documentation 07591, 00000, "spdde: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07592, 00000, "sspgprv: Error obtaining required privileges" // *Cause: While obtaining needed privileges, an error was returned from // SYS$SETPRV. // *Action: This is an internal error. Please report to Oracle 07593, 00000, "ssprprv: Error release privileges" // *Cause: While releasing privileges, an error was returned from SYS$SETPRV. // *Action: This is an internal error. Please report to Oracle 07594, 00000, "spiip: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07595, 00000, "sppid: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07596, 00000, "sptpa: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07597, 00000, "spguns: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07598, 00000, "spwat: $SETIMR failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07599, 00000, "spwat: $SCHDWK failure" // *Cause: VMS system service $SCHDWK failed // *Action: Examine system error message and refer to VMS documentation 07600, 00000, "slkmnm: $GETSYIW failure" // *Cause: VMS system service $GETSYIW failed // *Action: Examine system error message and refer to VMS documentation 07601, 00000, "spguno: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07602, 00000, "spgto: $GETJPIW failure" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07605, 00000, "szprv: $ASCTOID failure" // *Cause: VMS system service $ASCTOID failed // *Action: Examine system error message and refer to VMS documentation 07606, 00000, "szprv: $CHKPRO failure" // *Cause: VMS system service $CHKPRO failed // *Action: Examine system error message and refer to VMS documentation 07607, 00000, "szaud: $SNDOPR failure" // *Cause: VMS system service $SNDOPR failed // *Action: Examine system error message and refer to VMS documentation 07608, 00000, "szprv: $GETUAI failure" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07609, 00000, "szprv: $HASH_PASSWORD failure" // *Cause: VMS system service $HASH_PASSWORD failed // *Action: Examine system error message and refer to VMS documentation 07610, 00000, "$GETJPIW failed in retrieving the user's MAC priviledges" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07612, 00000, "$GETUAI failed in retrieving the user's clearance level" // *Cause: VMS system service $GETUAI failed // *Action: Examine system error message and refer to VMS documentation 07613, 00000, "$GETJPIW failed in retrieving the user's process label" // *Cause: VMS system service $GETJPIW failed // *Action: Examine system error message and refer to VMS documentation 07614, 00000, "$CHANGE_CLASS failed in retrieving the user's process label" // *Cause: VMS system service $CHANGE_CLASS failed // *Action: Examine system error message and refer to SEVMS documentation 07615, 00000, "$CHANGE_CLASS failed in retrieving the specified file label" // *Cause: VMS system service $CHANGE_CLASSS failed // *Action: Examine system error message and refer to SEVMS documentation 07616, 00000, "$CHANGE_CLASS failed in retrieving the specified device label" // *Cause: VMS system service $CHANGE_CLASS failed // *Action: Examine system error message and refer to SEVMS documentation 07617, 00000, "$FORMAT_CLASS failed translating the binary label to a string" // *Cause: VMS system service $FORMAT_CLASS failed because the given binary // classification was not valid. // *Action: Examine system error message and refer to SEVMS documentation 07618, 00000, "$IDTOASC failed translating a secrecy level" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of a secrecy level. // *Action: Define the entry in the rights database which the binary label // you specified references. 07619, 00000, "$IDTOASC failed translating an integrity level" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of an integrity level. // *Action: Define the entry in the rights database which the binary label // you specified references. 07620, 00000, "smscre: illegal database block size" // *Cause: An illegal database block size was specified in the parameter file. // It must be positive, a multiple of 512, and less than the maximum // physical i/o data size. // *Action: Change db_block_size in the parameter file to conform to these // limits. 07621, 00000, "smscre: illegal redo block size" // *Cause: An illegal redo log buffer size was specified in the parameter file. // It must be positive and a multiple of 512. // *Action: Change log_buffer in the parameter file to conform to these limits. 07622, 00000, "smscre: $CREATE failure" // *Cause: While creating the system global area (SGA) backing file, VMS // system service $CREATE failed. // *Action: Examine the system error message and refer to VMS documentation. 07623, 00000, "smscre: $CRMPSC failure" // *Cause: While creating the system global area (SGA), VMS system service // $CRMPSC failed. // *Action: Examine the system error message and refer to VMS documentation. 07624, 00000, "smsdes: $DGBLSC failure" // *Cause: While deleting the system global area (SGA), VMS system service // $DGBLSC failed. // *Action: Examine the system error message and refer to VMS documentation. 07625, 00000, "smsget: $MGBLSC failure" // *Cause: While mapping the system global area (SGA) during logon, VMS // system service $MGBLSC failed. The usual reason is that ORACLE // has not been started up. // *Action: Examine the system error message and refer to VMS documentation. // Start up ORACLE if it is not already started. 07626, 00000, "smsget: sga already mapped" // *Cause: An attempt to map the SGA during logon failed because it was // already mapped. This is an internal error. // *Action: Exit your program and try again, and report this to your // customer support representative. 07627, 00000, "smsfre: $CRETVA failure" // *Cause: While unmapping the system global area (SGA) during logoff, VMS // system service $CRETVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07628, 00000, "smsfre: sga not mapped" // *Cause: An attempt to unmap the SGA during logoff failed because it was // not mapped. This is an internal error. // *Action: Exit your program and try again, and report this to your // customer support representative. 07629, 00000, "smpall: $EXPREG failure" // *Cause: While extending the program global area (PGA), VMS // system service $EXPREG failed. This often happens when the virtual // memory page count quota is exceeded. // *Action: Examine the system error message and refer to VMS documentation. 07630, 00000, "smpdal: $DELTVA failure" // *Cause: While deleting the program global area (PGA) during logoff, VMS // system service $DELTVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07631, 00000, "smcacx: $EXPREG failure" // *Cause: While creating or extending a context area, VMS system service // $EXPREG failed. This often happens when the virtual memory page // count quota is exceeded. // *Action: Examine the system error message and refer to VMS documentation. 07632, 00000, "smsrcx: $DELTVA failure" // *Cause: While deleting a context area, VMS system service $DELTVA failed. // *Action: Examine the system error message and refer to VMS documentation. 07633, 00000, "smsdbp: illegal protection value" // *Cause: The buffer debug function was called with an illegal value. // This is an internal error. // *Action: Contact your customer support representative. 07634, 00000, "smsdbp: $CRETVA failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $CRETVA failed. // *Action: Contact your customer support representative. 07635, 00000, "smsdbp: $SETPRT failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $SETPRT failed. // *Action: Contact your customer support representative. 07636, 00000, "smsdbp: $MGBLSC failure" // *Cause: While attempting to set protection in the database buffer // debug mechanism, VMS system service $MGBLSC failed. // *Action: Contact your customer support representative. 07637, 00000, "smsdbp: buffer protect option not specified when sga created" // *Cause: Trying to change the buffer protect mode when the SGA was not // created with buffer protect debug option. This is an internal error. // *Action: Contact your customer support representative. 07638, 00000, "smsget: SGA pad area not large enough for created SGA" // *Cause: An attempt was made to map an SGA with software in which // the SGA pad area isn't large enough. // *Action: Create a smaller SGA, or relink the software with a larger pad. 07639, 00000, "smscre: SGA pad area not large enough (%s bytes required)" // *Cause: An attempt was made to create an SGA with software in which // the SGA pad area isn't large enough. // *Action: Create a smaller SGA, or relink the software with a larger pad. 07640, 00000, "smsget: SGA not yet valid. Initialization in progress" // *Cause: An attempt was made to map to the SGA while it was being // initialized. // *Action: Wait until initialization is complete, and try again. 07641, 00000, "smscre: Unable to use the system pagefile for the SGA" // *Cause: The system global area (SGA) backing file could not be allocated // using the system pagefile because the system-wide limit on // global pages has been exceeded. // *Action: Either increase the VMS system parameter GBLPAGFIL or use a disk // file as the SGA backing file. 07642, 00000, "smprtset: $CMKRNL failure" // *Cause: While attempting to set the protection of a region of memory, // an error was returned from the $CMKRNL system service. // *Action: Examine the system error message and refer to VMS documentation. 07643, 00000, "smsalo: SMSVAR is invalid" // *Cause: an internal error // *Action: Report this error to ORACLE customer support, provide your // INIT.ORA file. 07645, 00000, "sszfsl: $CHANGE_CLASS failure" // *Cause: While attempting to set the label on a file, SEVMS service // $CHANGE_CLASS failed. // *Action: Examine the system message and refer to SEVMS system documentation. 07646, 00000, "sszfck: $CREATE failure" // *Cause: While attempting to create a file, VMS system service $CREATE // failed. // *Action: Examine the system message and refer to VMS system documentation. 07647, 00000, "sszfck: $OPEN failure" // *Cause: While attempting to reopen a file, VMS system service $OPEN failed. // *Action: Examine the system message and refer to VMS system documentation. 07650, 00000, "sigunc: $GETJPIW failure" // *Cause: While attempting to get the user's terminal device name, // user name, user program name, or process name // during logon, VMS system service $GETJPIW failed. // *Action: Examine the system error message and refer to VMS documentation. 07655, 00000, "slsprom:$TRNLOG failure" // *Cause: While attempting to translate SYS$INPUT during a prompt for // a password, VMS system service $TRNLOG failed. // *Action: Examine the system error message and refer to VMS documentation. 07656, 00000, "slsprom:$GETDVI failure" // *Cause: While attempting to get device characteristics during a prompt // for a password, VMS system service $GETDVI failed. // *Action: Examine the system error message and refer to VMS documentation. 07657, 00000, "slsprom:$ASSIGN failure" // *Cause: While prompting for a password, VMS system service $ASSIGN failed. // *Action: Examine the system error message and refer to VMS documentation. 07658, 00000, "slsprom:$QIOW read failure" // *Cause: While prompting for a password, VMS system service $QIOW failed. // *Action: Examine the system error message and refer to VMS documentation. 07665, 00000, "ssrexhd: recursive exception encountered %s %s %s %s %s %s" // *Cause: A VMS exception occurred while executing in the ORACLE exception // handler. The message includes the signal number, first and second // signal arguments, and exception PC, PSL and R0. This is an // internal error. // *Action: Contact your customer support representative. 07670, 00000, "$IDTOASC failed translating a secrecy category" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of a secrecy category. // *Action: Define the entry in the rights database which the binary label // you specified references. 07671, 00000, "$IDTOASC failed translating an integrity category" // *Cause: VMS system service $IDTOASC failed while looking up the string // representation in the rights database of an integrity category. // *Action: Define the entry in the rights database which the binary label // you specified references. 07672, 00000, "$PARSE_CLASS failed translating the string into a binary label" // *Cause: SEVMS system service $PARSE_CLASS failed because the given // string did not represent a valid classification. // *Action: Examine system error message and refer to SEVMS documentation. 07680, 00000, "sou2os: another call to ORACLE currently executing" // *Cause: A call to the ORACLE shared image entry point occurred from within // the shared image. This is an internal error. // *Action: Contact your customer support representative. 07681, 00000, "sou2os: An error occurred while initializing Oracle" // *Cause: While attempting to set up the dispatch vectors for the shared // image, an error occurred. This is an internal error. // *Action: Contact your customer support representative. 07682, 00000, "sou2os: set kernel dispatch fail err" // *Cause: During ORACLE shared image entry, a dispatch to kernel mode // failed. // *Action: Make sure that your shared image is installed with the CMKRNL // privilege, then contact your customer support representative. 07683, 00000, "sou2os: $SETPRV reset error" // *Cause: During an attempt to restore user privileges at ORACLE shared // image exit, VMS system service $SETPRV failed. This is an // internal error. // *Action: Contact your customer support representative. 07684, 00000, "sou2os: supervisor stack reset error" // *Cause: During an attempt to restore the supervisor-mode stack at // ORACLE shared image exit, VMS system service $SETSTK failed. // This is an internal error. // *Action: Contact your customer support representative. 07685, 00000, "sou2os: supervisor stack set error" // *Cause: During an attempt to set the ORACLE supervisor-mode stack // at ORACLE shared image entry, VMS system service $SETSTK failed. // This is an internal error. // *Action: Contact your customer support representative. / / 7700 - 7720: sksarch errors / 07700, 00000, "sksarch: interrupt received" // *Cause: An interrupt was received while archiving the logs // *Action: Retry operation 07701, 00000, "sksatln: internal exception: output buffer too small" // *Cause: Overflow of buffer for parsing archive control text string // *Action: This is an internal error, please report to Oracle 07702, 00000, "unrecognized device type in archive text" // *Cause: Unrecognized device type in archive text // *Action: This is an internal error, please report to Oracle 07703, 00000, "error in archive text: need '/' after device type" // *Cause: The archive control text in the ARCHIVE command is invalid; // the device type (to indicate a file or tape) must be followed // by a '/'. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07704, 00000, "error in archive text: need ':' after device name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the device name must be followed by a ':'. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07705, 00000, "sksaprs: device name buffer too small" // *Cause: The buffer supplied for the device name is too small. This is // an internal error. // *Action: Contact your customer support representative. 07706, 00000, "error in archive text: need disk file name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the disk file name is missing. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07707, 00000, "error in archive text: need tape label name" // *Cause: The archive control text in the ARCHIVE command is invalid; // the tape label name is missing. // *Action: Refer to the SQLDBA Guide for the proper syntax of the text. 07708, 00000, "sksaprs: tape label name buffer too small" // *Cause: The buffer supplied for the tape label is too small. This is // an internal error. // *Action: Contact your customer support representative. 07709, 00000, "sksaprs: archiving to a remote host is not allowed" // *Cause: The user specified a remote disk for archiving via DECnet. // *Action: Archive to a disk on the local host. 07710, 00000, "sksaprs: file name buffer too small" // *Cause: The buffer supplied for the file name is too small. This is // an internal error. // *Action: Contact your customer support representative. 07713, 00000, "sksamtd: could not mount archival device (SYS$MOUNT failure)" // *Cause: VMS system service SYS$MOUNT failed // *Action: Examine system error message and refer to VMS documentation 07715, 00000, "sksadtd: could not dismount archival device (SYS$DISMNT failure)" // *Cause: VMS system service SYS$DISMNT failed // *Action: Examine system error message and refer to VMS documentation 07716, 00000, "sksachk: invalid device specification for ARCHIVE" // *Cause: VMS system service SYS$GETDVI failed" // *Action: Specify a valid device in ARCHIVE control string 07717, 00000, "sksaalo: error allocating memory" // *Cause: VMS system service LIB$GET_VM failed" // *Action: Examine system error message and refer to VMS documentation 07718, 00000, "sksafre: error freeing memory" // *Cause: VMS system service LIB$FREE_VM failed // *Action: Examine system error message and refer to VMS documentation / / 7721-7729 scg overflow errors / 07721, 00000, "scgcm: not enough OS resource to obtain system enqueue" // *Cause: A call to sys$enq returned an error indicating that the operating // system lacked the resources necessary to create a lock. This is // caused by the messages SS$_EXENQLM or SS$_INSFMEM. // *Action: Free up some of the required resource to allow the creation of the // required lock. / / 7740 - 7760 error message file errors 07740, 00000, "slemop: incorrect handle size (programming error)" // *Cause: structures used for reading error message files do not match // *Action: this is an internal error, please report to Oracle 07741, 00000, "slemop: $OPEN failure" // *Cause: VMS system service $OPEN failed // *Action: Examine system error message and refer to VMS documentation 07742, 00000, "slemop: $CONNECT failure" // *Cause: VMS system service $CONNECT failed // *Action: Examine system error message and refer to VMS documentation 07743, 00000, "slemop: incorrect error file attributes" // *Cause: An error message file is of incorrect format // *Action: Unless an error file has been changed, report this to Oracle 07744, 00000, "slemcl: invalid error message file handle" // *Cause: seal in passed in handle does not match correct value // *Action: this is an internal error, please report to Oracle 07745, 00000, "slemcl: $CLOSE failure" // *Cause: VMS system service $CLOSE failed // *Action: Check system error and refer to VMS documentation 07746, 00000, "slemrd: invalid error message file handle" // *Cause: seal in passed in handle does not match correct value // *Action: this is an internal error, please report to Oracle 07747, 00000, "slemrd: $READ failure" // *Cause: VMS system service $READ failed // *Action: Check system error and refer to VMS documentation 07750, 00000, "slemcr: fopen failure" // *Cause: An attempt to create a message file failed. This is an // internal error. // *Action: Contact your customer support representative. 07751, 00000, "slemcr: malloc failure" // *Cause: An attempt to allocate a cache for a newly-created message // file failed. This is an internal error. // *Action: Contact your customer support representative. 07753, 00000, "slemcf: fseek before write failure" // *Cause: An attempt to seek before writing a message file cache // element failed. This is an internal error. // *Action: Contact your customer support representative. 07754, 00000, "slemcf: fwrite failure" // *Cause: An attempt to write a message file cache element failed. // This is an internal error. // *Action: Contact your customer support representative. 07755, 00000, "slemcf: fseek before read failure" // *Cause: An attempt to seek before reading a message file cache // element failed. This is an internal error. // *Action: Contact your customer support representative. 07756, 00000, "slemcf: fread failure" // *Cause: An attempt to read a message file cache element failed. // This is an internal error. // *Action: Contact your customer support representative. 07757, 00000, "slemcc: invalid handle" // *Cause: The seal in a passed-in handle does not match correct value. // This is an internal error. // *Action: Contact your customer support representative. 07758, 00000, "slemcw: invalid handle" // *Cause: The seal in a passed-in handle does not match correct value. // This is an internal error. // *Action: Contact your customer support representative. 07759, 00000, "slemtr: invalid destination" // *Cause: The destination string provided to the function is too short // This is an internal error. // *Action: Contact your customer support representative. 07760, 00000, "slemtr: $open failure" // *Cause: the $open service failed. This is an internal error // *Action: Contact your customer support representative. 07800, 00000, "slbtpd: invalid number" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07801, 00000, "slbtpd: invalid exponent" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07802, 00000, "slbtpd: overflow while converting to packed decimal" // *Cause: An impossible request for binary to decimal conversion was made // *Action: This conversion cannot be performed 07803, 00000, "slpdtb: invalid packed decimal nibble" // *Cause: An impossible request for decimal to binary conversion was made // *Action: This conversion cannot be performed 07804, 00000, "slpdtb: number too large for supplied buffer" // *Cause: An impossible request for decimal to binary conversion was made // *Action: This conversion cannot be performed / / 7820-7839 SSP error messages / 07820, 0000, "sspscn: SYS$CRELNM failure" // *Cause: An error was returned from the SYS$CRELNM function // *Action: Check system error and refer to VMS documentation 07821, 0000, "sspsdn: SYS$DELLNM failure" // *Cause: An error was returned from the SYS$DELLNM function // *Action: Check system error and refer to VMS documentation 07822, 0000, "sspscm: SYS$CREMBX failure" // *Cause: An error was returned from the SYS$CREMBX function while // trying to create the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07823, 0000, "sspsqr: $QIO failure" // *Cause: An error was returned from $QIO while trying to // queue a read to the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07824, 0000, "sspain: $SETIMR failure" // *Cause: An error was returned from SYS$SETIMR while trying to // queue a process spin-watch timer. // *Action: Check system error and refer to VMS documentation 07825, 0000, "sspsck: $QIO failure at AST level" // *Cause: An error was returned from SYS$QIO while trying to // read the process dump mailbox. // *Action: Check system error and refer to VMS documentation 07826, 0000, "sspscm: SYS$GETDVIW failure" // *Cause: An error was returned from SYS$GETDVIW while trying to // get information about the process dump mailbox. // *Action: Check system error and refer to VMS documentation / / 7840-7859 SLLF error messages / 07840, 0000, "sllfop: LIB$GET_VM failure" // *Cause: An error was returned from LIB$GET_VM while attempting to // allocate memory for an i/o vector. // *Action: Check system error and refer to VMS documentation 07841, 0000, "sllfop: SYS$OPEN failure" // *Cause: An error was returned from SYS$OPEN while attempting to // open the data file for reading // *Action: Check system error and refer to VMS documentation 07842, 0000, "sllfcl: SYS$CLOSE failure" // *Cause: An error was returned from SYS$CLOSE while attempting to // close the input data file // *Action: Check system error and refer to VMS documentation 07843, 0000, "sllfcl: LIB$FREE_VM failure" // *Cause: An error was returned from LIB$FREE_VM while attempting to // free the memory for the i/o vector // *Action: Check system error and refer to VMS documentation 07844, 0000, "sllfop: LIB$GET_VM failure" // *Cause: An error was returned from LIB$GET_VM while attempting to // allocate memory for data and index buffers // *Action: Check system error and refer to VMS documentation 07845, 0000, "sllfcl: LIB$FREE_VM failue" // *Cause: An error was returned from LIB$FREE_VM while attempting to // free memory used by data and index buffers // *Action: Check system error and refer to VMS documentation 07846, 0000, "sllfop: %s byte record too big for %s byte user buffer" // *Cause: The longest record in the file will not fit into the // largest data buffer that can be allocated // *Action: Modify the RMS file to have smaller records 07847, 0000, "sllfop: $CONNECT failure" // *Cause: An error was returned by SYS$CONNECT while attempting // to open the data file // *Action: Check system error and refer to VMS documentation 07848, 0000, "sllfrb: $GET failure" // *Cause: An error was returned by SYS$GET while attempting // to read the data file // *Action: Check system error and refer to VMS documentation 07849, 0000, "sllfsk: $GET failure" // *Cause: An error was returned by SYS$GET while attempting to // skip records in the input file // *Action: Check system error and refer to VMS documentation 07850, 0000, "sllfop: bad option" // *Cause: You are using a bad option to loader // Fixed= is one legal option. Check documentation for others. // *Action: Check documentation 07860, 0000, "osnsoi: error setting up interrupt handler" // *Cause: An error occurred while setting up the control interrupt handler // *Action: This is an internal error. Contact your Oracle representative. / / / 7880 - 7889 Error message for sd / 07880, 0000, "sdopnf: internal error" // *Cause: A list of all files open by this process could not be obtained. // *Action: This is an internal error. Contact your customer support // representative. / / 8000 - 8174 Data layer error messages / 08000, 00000, "maximum number of session sequence lists exceeded" // *Cause: the sequence parent state objects for this session are all used // *Action: an internal error; quit the session and begin a new one 08001, 00000, "maximum number of sequences per session exceeded" // *Cause: the limit on the number of sequences usable by session has been hit // *Action: increase INIT.ORA parameter user_sequences to get more 08002, 00000, "sequence %s.CURRVAL is not yet defined in this session" // *Cause: sequence CURRVAL has been selected before sequence NEXTVAL // *Action: select NEXTVAL from the sequence before selecting CURRVAL 08003, 00000, "sequence %s.NEXTVAL exceeds internal limits" // *Cause: The sequence was created with unsafe values for some of the // parameters. The calculation of NEXTVAL cannot be made because it // exceeds the legal represention size. // *Action: Alter or recreate the sequence number with legal limits. 08004, 00000, "sequence %s.NEXTVAL %s %sVALUE and cannot be instantiated" // *Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE // *Action: alter the sequence so that a new value can be requested 08005, 00000, "specified row does not exist" // *Cause: A row with the given rowid does not exist in any of the tables given // *Action: check the query for misspellings of table names and the rowid 08006, 00000, "specified row no longer exists" // *Cause: the row has been deleted by another user since the operation began // *Action: re-try the operation 08008, 00000, "another instance is mounted with USE_ROW_ENQUEUES = %s" // *Cause: the shared instance being started does not have the same value // for use_row_enqueues as already running instances // *Action: ensure that all instances' INIT.ORA files specify the same value // for the parameter 'use_row_enqueues' 08100, 00000, "index is not valid - see trace file for diagnostics" // *Cause: Validate Index detected an inconsistency in its argument index // *Action: Send trace file to your customer support representative 08101, 00000, "index key does not exist root dba %s, dba %s (%s)" // *Cause: Internal error: possible inconsistency in index // *Action: Send trace file to your customer support representative, along // with information on reproducing the error 08102, 00000, "index key not found, obj# %s, dba %s (%s)" // *Cause: Internal error: possible inconsistency in index // *Action: Send trace file to your customer support representative, along // with information on reproducing the error 08103, 00000, "object no longer exists" // *Cause: the object has been deleted by another user since the operation // began // *Action: 08104, 00000, "this index object %s is being online built or rebuilt" // *Cause: the index is being created or rebuild or waited for recovering // from the online (re)build // *Action: wait the online index build or recovery to complete 08105, 00000, "Oracle event to turn off smon cleanup for online index build" // *Cause: set this event only under the supervision of Oracle development // *Action: debugging only 08106, 00000, "can not create journal table %s.%s" // *Cause: online index builder can not create its journal table // *Action: rename your table in conflict 08108, 00000, "may not build or rebuild this type of index online " // *Cause: only support normal index or IOT top-level index // *Action: change your index type 08109, 00000, "nosort is not a supported option for online index build " // *Cause: may not specify nosort for online index build // *Action: get rid of nosort in the index creation command 08110, 00000, "Oracle event to test SMON cleanup for online index build " // *Cause: Oracle Kernel test only // *Action: Donot set this event(for test only) 08111, 00000, "a partitioned index may not be coalesced as a whole" // *Cause: User attempted to coalesce a partitioned index using // ALTER INDEX COALESCE statement, which is illegal // *Action: Coalesce the index a (sub)partition at a time (using // ALTER INDEX MODIFY (sub)PARTITION COALESCE) 08112, 00000, "a composite partition may not be coalesced as a whole" // *Cause: User attempted to coalesce a composite partition // *Action: Coalesce the index a subpartition at a time (using // ALTER INDEX MODIFY SUBPARTITION COALESCE) 08113, 00000, "composite partition index may not be compressed" // *Cause: User attempted to compress a composite partition index // *Action: create uncompressed composite partition index 08114, 00000, "can not alter a fake index" // *Cause: User attempted to alter a fake index // *Action: drop fake index 08115, 00000, "can not online create/rebuild this index type" // *Cause: User attempted to create index type that online doesnot support // *Action: use offline index create/rebuild command 08116, 00000, "can not acquire dml enough lock(S mode) for online index build" // *Cause: User attempted to create index online without allowing DML Share lock // *Action: allow DML share lock on the base table 08117, 00000, "Index Organized Table operation released its block pin" // *Cause: Block maintenance forced the release of a block pin // *Action: Contact your customer support representative / / / 8175 - 8190 Discrete transaction error messages / 08175, 00000, "discrete transaction restriction violated (%s)" // *Cause: An attempt was made to perform an action that is not currently // supported in a discrete transaction. // *Action: Rollback the transaction, and retry it as a normal transaction. / 08176, 00000, "consistent read failure; rollback data not available" // *Cause: Encountered data changed by an operation that does not generate // rollback data : create index, direct load or discrete transaction. // *Action: In read/write transactions, retry the intended operation. Read // only transactions must be restarted. 08177, 00000, "can't serialize access for this transaction" // *Cause: Encountered data changed by an operation that occurred after // the start of this serializable transaction. // *Action: In read/write transactions, retry the intended operation or // transaction. 08178, 00000, "illegal SERIALIZABLE clause specified for user INTERNAL" // *Cause: Serializable mode is not supported for user INTERNAL. // *Action: Reconnect as another user and retry the SET TRANSACTION // command. 08179, 00000, "concurrency check failed" // *Cause: Encountered data changed by an operation that occurred after // a specific snapshot. This is usually used to indicate that a // particular cached copy of a datablock is stale. This is used // for internal use for now. // *Action: refresh the cached copy of the datablock and retry operation. 08180, 00000, "no snapshot found based on specified time" // *Cause: Could not match the time to an SCN from the mapping table. // *Action: try using a larger time. 08181, 00000, "specified number is not a valid system change number" // *Cause: supplied scn was beyond the bounds of a valid scn. // *Action: use a valid scn. 08182, 00000, "operation not supported while in Flashback mode" // *Cause: user tried to do dml or ddl while in Flashback mode // *Action: disable Flashback and re-attempt the operation 08183, 00000, "Flashback cannot be enabled in the middle of a transaction" // *Cause: user tried to do Flashback in the middle of a transaction // *Action: do a commit 08184, 00000, "attempting to re-enable Flashback while in Flashback mode" // *Cause: as stated above // *Action: disable first before re-enabling 08185, 00000, "Flashback not supported for user SYS" // *Cause: user logged on as SYS // *Action: logon as a different (non SYS) user. 08186, 00000, "invalid timestamp specified" // *Cause: as stated above // *Action: enter a valid timestamp / 8200 - 8399 Reserved for NCUBE OSD errors / /8200 - 8204 Reserved 08205, 00000, "ora_addr: $ORACLE_SID not set in environment" // *Cause: The environment variable ORACLE_SID is not set. // *Action: Set the ORACLE_SID environment variable. 08206, 00000, "ora_addr: cannot translate address file name" // *Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf. // *Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set. 08207, 00000, "ora_addr: cannot open address file" // *Cause: The address file could not be opened. // *Action: Check that ORACLE is up. Check that the file // $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has // correct permissions. 08208, 00000, "ora_addr: cannot read from address file" // *Cause: The address file could not be read. // *Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf // exists and contains a single line of text. 08209, 00000, "scngrs: SCN not yet initialized" // *Cause: The System Commit Number has not yet been initialized. // *Action: Contact your customer support representative. 08210, 00000, "Requested I/O error" // *Cause: Oracle requested that an I/O error be returned for this operation. // *Action: This should not occur in normal Oracle operation. Contact support. / 08230, 00000, "smscre: failed to allocate SGA" // *Cause: The n_core system call failed, maybe due to insufficient memory. // *Action: Specify a smaller number of buffers. Check INIT.ORA parameters. 08231, 00000, "smscre: unable to attach to SGA" // *Cause: The process cannot attach to the SGA. This can happen if either // the listener can't attach, or the process cannot communicate // with the listener. // *Action: Verify that the instance is up and running. Contact your // customer support representative. 08232, 00000, "smsdes: cannot detach from SGA" // *Cause: Probably, the listener process has died. // *Action: Contact your customer support representative. 08233, 00000, "smsdes: cannot unmap SGA" // *Cause: The n_core system call failed while detaching from the SGA. // *Action: Note nCX error returned; contact your customer support // representative. 08234, 00000, "smsget: cannot get instance listener address" // *Cause: The instance listener address cannot be read from the sgadef file. // *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. // Additional information gives error return from ora_addr. 08235, 00000, "smsget: listener not on this node" // *Cause: A process wishing to attach to the SGA is on a different // node from its instance's listener. // *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. // Contact your customer support representative. 08236, 00000, "smsget: cannot share subcube with listener" // *Cause: The n_share call failed, probably because the listener has died. // *Action: Check if the listener is running, and contact your customer // support representative. 08237, 00000, "smsget: SGA region not yet created" // *Cause: Attempting to attach to an SGA which has not yet been created. // *Action: Verify that the instance is running. Contact your customer // support representative. 08238, 00000, "smsfre: cannot detach from SGA" // *Cause: The n_core system call failed while detaching from the SGA. // *Action: Check nCX error, and contact your customer support // representative. /8239 - 8242 Reserved /8252 - 8260 Reserved 08260, 00000, "ora_addr: cannot open nameserver" // *Cause: A process could not connect to the nameserver. // *Action: Make sure the nameserver is up and running. Additional // information gives nameserver's returned status. 08261, 00000, "ora_addr: cannot find name in nameserver" // *Cause: The listener nameserver entry for an instance could not be found. // *Action: Make sure the nameserver is up and running. Additional // information gives nameserver's returned status. /8262 Reserved 08263, 00000, "ora_addr: cannot free listener address" // *Cause: The listener nameserver entry could not be freed // *Action: Additional information gives nameserver's returned status. // Contact your customer support representative. 08264, 00000, "ora_addr: cannot close nameserver" // *Cause: The connection to the nameserver could not be closed. // *Action: Additional information gives nameserver's returned status. // Contact your customer support representative. 08265, 00000, "create_ora_addr: cannot open nameserver" // *Cause: A process could not connect to the nameserver. // *Action: Make sure the nameserver is up and running. Additional // information gives nameserver's returned status. 08266, 00000, "create_ora_addr: cannot register name in nameserver" // *Cause: The listener's addressing information could not be registered. // *Action: Make sure the nameserver is up and running. Additional // information gives nameserver's returned status. 08267, 00000, "destroy_ora_addr: cannot close nameserver" // *Cause: The connection to the nameserver could not be closed. // *Action: Additional information gives nameserver's returned status. // Contact your customer support representative. 08268, 00000, "create_ora_addr: cannot close nameserver" // *Cause: The connection to the nameserver could not be closed. // *Action: Additional information gives nameserver's returned status. // Contact your customer support representative. 08269, 00000, "destroy_ora_addr: cannot destroy name" // *Cause: The listener's addressing information could not be removed. // *Action: Additional information gives nameserver's returned status. // Contact your customer support representative. / 8270 - 8273 Reserved nCUBE archival 08270, 00000, "sksachk: Illegal archival control string" // *Cause: Archive files cannot be created with the given archival control // string. // *Action: Check that the volume exists 08271, 00000, "sksabln: Buffer size not large enough for archive control string" // *Cause: The given archival control string expands into too many characters. // *Action: Reduce archive control string length. / 8273 - reserved nCUBE archival 08274, 00000, "Out of memory for environment variable" // *Cause: There is insufficient memory to return the requested value // *Action: Reduce memory usage and retry. 08275, 00000, "Environment variable unset" // *Cause: The requested environment variable is not set // *Action: Ensure that the variable name requested is correct. 08276, 00000, "No room in nameserver for pid" // *Cause: There is no room to record the pid for a background process // *Action: Shutdown abort and restart the database. 08277, 00000, "Cannot set environment variable" // *Cause: There is insufficient memory to expand the environment. // *Action: Reduce memory usage and retry. 08278, 00000, "Cannot get CPU statistics" // *Cause: Could not retrieve CPU times because n_stat failed. // *Action: Contact customer support. 08308, 00000, "sllfop: Cannot open file" // *Cause: Oracle could not open a file. // *Action: Check the Unix errno returned as additional information. 08309, 00000, "sllfop: Cannot fstat file" // *Cause: Oracle could not obtain information about an open file. // *Action: Check the Unix errno returned as additional information. 08310, 00000, "sllfop: Bad value for recsize" // *Cause: An illegal value for the record size was specified. // *Action: Specify a value for the recsize option that is greater than 0. 08311, 00000, "sllfop: bad value for maxrecsize" // *Cause: An illegal value for the maximum record size was specified. // *Action: Specify a value for the maxrecsize option that is greater // than 0. 08312, 00000, "sllfop: unrecognized processing option" // *Cause: An unrecognized processing option was specified. // *Action: Check the Oracle for nCUBE 2 User's Guide for valid options. 08313, 00000, "sllfop: could not allocate buffers" // *Cause: Memory for the load buffers could not be allocated. // *Action: Reduce the maximum record size. Eliminate any unnecessary // processes on your current node before running SQL*Loader again. 08314, 00000, "sllfcf: Error closing file" // *Cause: An error occurred trying to close a file. // *Action: Check the Unix errno returned as additional information. 08315, 00000, "sllfrb: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. 08316, 00000, "sllfsk: Error seeking in file." // *Cause: The lseek system call returned an error. // *Action: Check the Unix errno returned as additional information. 08317, 00000, "sllfsk: Error seeking in file." // *Cause: The lseek system call returned an error. // *Action: Check the Unix errno returned as additional information. 08318, 00000, "sllfsk: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. 08319, 00000, "sllfsk: Error reading file" // *Cause: An error occurred trying to read from a file. // *Action: Check the Unix errno returned as additional information. / / 8320 - 8329 Reserved for scn.c 08320, 00000, "scnget: Call to scnget before scnset or scnfnd." // *Cause: An internal error // *Action: Contact your customer support representative. 08321, 00000, "scnmin: NOT IMPLEMENTED YET" // *Cause: An internal error // *Action: Contact your customer support representative. 08322, 00000, "scnmin: open/convert of bias lock failed" // *Cause: A call to the lkmgr failed to open and convert the bias lock // *Action: Check to make sure the lkmgr is up. 08323, 00000, "scnmin: close of bias lock failed" // *Cause: A call to the lkmgr failed to close the bias lock // *Action: Check to make sure the lkmgr is up. 08330, 00000, "Printing not supported" // *Cause: An attempt was made to automatically spool a file to the printer // *Action: none 08331, 00000, "Wait operation timed out" // *Cause: Oracle timed out waiting for an event // *Action: Contact your Oracle support representative 08332, 00000, "rollback segment #%s specified not available" // *Cause: (same as 1545) // *Action: (same as 1545). Also, make sure you have created enough rollback // segments for the number of instances you are trying to start. / / 8340-8359 Reserved for nCUBE redo server errors / 08340, 00000, "This command not allowed on nCUBE, only one thread is ever used." // *Cause: An illegal command was executed for the nCUBE platform. // *Action: There is no need to issue this command. 08341, 00000, "On nCUBE, this command can only be executed from instance 1." // *Cause: A command that can only be issued on instance 1 was issued elsewhere. // *Action: Log on to instance 1 and repeat the command. 08342, 00000, "sropen: failed to open a redo server connection" // *Cause: An error occurred trying to connect to the redo server. // *Action: The OS specific error message should tell you what to do. 08343, 00000, "srclose: failed to close a redo server connection" // *Cause: An error occurred trying to close the redo server connection. // *Action: The OS specific error message should tell you what to do. 08344, 00000, "srapp: failed to send redo data to the redo server" // *Cause: An error occurred trying to send redo to the redo server. // *Action: The OS specific error message should tell you what to do. / / 8363 - 8399 Reserved for nCUBE sosd errors (unassigned) / /8362 Reserved / / 8400 UTL_RAW and UTL_PG error and warning messages / / Start UTL_RAW and UTL_PG messages / / / / / CONTENTS: / Generic Base Messages for: / Procedural Gateway for APPC Administration Utility: Release 3.3.0 / / NOTES: / / These messages are include in ORAUS.MSG and translated message files / / rherwadk 04/09/96 - add error message for max_dump_file_size parameter / hasun 04/01/96 - Add message #12028 / aroy 03/14/96 - reserve subrange for lob calls / dchatter 03/13/96 - Fix 24307 error / rxgovind 03/06/96 - add error 22929 / slari 03/05/96 - add kpu error 243xxx / gngai 02/15/96 - PDML: change PDML error 12827 to 12828 / gngai 02/15/96 - PDML: added itl deadlock error / gngai 02/13/96 - PDML: added errors for parallel txns / ashgupta 02/08/96 - Add 12023, 12024 (missing index, missing PK info) / ashgupta 02/08/96 - Add 12022, 12025 (altering snapshot log) / ltan 02/08/96 - add 1687 / akruglik 02/07/96 - add messages for LOGGING/NOLOGGING / akruglik 02/01/96 - add msg 14101 / sdas 02/01/96 - non-key overflow / hasun 01/31/96 - Add 12021: snapshot is corrupt / akruglik 01/31/96 - add msg 14100 / akruglik 01/31/96 - shorten message 14052 / hasun 01/22/96 - Add 12019: master table is a remote object / ssamu 01/22/96 - remove unused error message / jwlee 01/18/96 - tablespace-relative DBAs / hasun 01/17/96 - Add 12018: can not create a complex, pk snapshots / akruglik 01/14/96 - merge up to RDBMS_PTI_SUN4_960112 / akruglik 01/11/96 - get rid of msg 14087 / ashgupta 01/10/96 - Adding error 12017 (alter snapshot) / gswart 01/10/96 - Add event to indicate presence of a debugger / ssamu 01/09/96 - modify partition / ssamu 01/09/96 - support validate INTO / akruglik 01/05/96 - add msg 14052 / hasun 12/29/95 - Add errors for snapshot refresh validation / aho 12/28/95 - duc / gswart 12/27/95 - Proj 2381: add event for detecting redo log errors / ssamu 12/26/95 - alter table exchange partition / akruglik 12/22/95 - merge up to RDBMS_PTI_SUN4_951220 / akruglik 12/22/95 - renumber msgs 14083,4 to 14086,7 to avoid / clashes with the latest PTI version / atsukerm 12/21/95 - tablespace-relative DBAs. / sthakur 12/20/95 - add KOKA errors / jwijaya 12/19/95 - add ranges for object SQL / jhealy 12/15/95 - single partition loads: add new errors / ssamu 12/15/95 - disallow LONG datatype columns in partitioned tables / ssamu 12/15/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm / akruglik 11/28/95 - remove parameter from mesg 14080 / akruglik 11/28/95 - add message 14084 / akruglik 11/27/95 - add messages for ALTER INDEX REBUILD PARTITION proce / aho 11/16/95 - iot / ssamu 11/11/95 - change error message 14074 / slari 11/03/95 - add upi object extension error messages / 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 / msimon 09/26/95 - Add in preliminary version of kdl subsystem / jboonleu 09/20/95 - update error message file with ORI errors / tanguyen 09/15/95 - add 21602: dropping type with dependency / emendez 07/23/95 - cheking RCS rev to stabilize 7-7 / png 12/01/94 - V7.01.06: / 8468 replaces 8421-24 / 8466 replaces 8425-28, 8461 / 8467 replaces 8406-8411, 8438, 8439, 8442 / 8401 replaces 8401-8405 / 8435 revised / 8414 added / cddavis 10/09/94 - deleted comments with kkxg references / cddavis 10/09/94 - header prefixed to us version of pirg msgs / 08401, 00000, "invalid compiler name: %s" // *Cause: An invalid compiler name was passed to a UTL_PG // conversion routine. // *Action: Correct the compiler name parameter in the PL/SQL code // that called the conversion routine. / 08412, 00000, "error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message" // *Cause: The WMSGBSIZ is the maximun size for warning message block, // it is recommanded to be 1024 bytes to 8 kbytes. // *Action: Defined WMSGBLK of size between 1k to 8k bytes and // update the WMSGBSIZ to the sizeof(WMSGBLK). / 08413, 00000, "invalid compiler type in FORMAT parameter at %s" // *Cause: An invalid compiler type is defined in format control block. // The format control block is invalid. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08414, 00000, "error encountered in %s" // *Cause: The function returned an error. // Where may be: // RAW_TO_NUMER // NUMBER_TO_RAW // RAW_TO_NUMBER_FORMAT // NUMBER_TO_RAW_FORMAT // MAKE_NUMBER_TO_RAW_FORMAT // MAKE_RAW_TO_NUMBER_FORMAT // *Action: This message will be preceded by messages providing details // about the error. Check those messages to determine what // action to take. / 08429, 00000, "raw data has invalid digit in display type data" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained invalid data. The picture mask // parameter specified a digit, but the corresponding input // from the raw data did not contain a valid digit. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08430, 00000, "raw data missing leading sign" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no leading sign, but the mask // options parameter specified a leading sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08431, 00000, "raw data missing zero as defined in picture" // *Cause: The picture mask parameter passed to a UTL_PG // RAW_TO_NUMBER conversion routine contained a zero, but // the corresponding input from the raw data was not a zero. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08432, 00000, "raw data has invalid floating point data" // *Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained invalid floating point data. // *Action: Correct the input raw data. / 08433, 00000, "invalid picture type in convert raw to number" // *Cause: The picture mask parameter passed to a UTL_PG // RAW_TO_NUMBER conversion routine contained non-numeric // characters, but the conversion was to a numeric data // type. // *Action: Correct the picture mask parameter. / 08434, 00000, "raw data has invalid trailing sign" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no trailing sign, but the mask // options parameter specified a trailing sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08435, 00000, "PICTURE MASK missing the leading sign when SIGN IS LEADING specified" // *Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER // conversion routine had no leading sign, but the mask // options parameter specified a leading sign. // *Action: Correct the input raw data or the mask options so that // they match. / 08436, 00000, "raw data has invalid sign digit" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine had an invalid sign digit in the // position where the picture mask specified a sign. // *Action: Correct the input raw data or the picture mask so that // they match. / 08437, 00000, "invalid picture type in picture mask" // *Cause: The picture mask parameter passed to a UTL_PG // NUMBER_TO_RAW conversion routine contained non-numeric // characters, but the conversion was to a numeric data // type. // *Action: Correct the picture mask parameter. / 08440, 00000, "raw buffer is too short to hold converted data" // *Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW // conversion routine was not large enough to contain the // results of the conversion based on the picture mask. // *Action: Increase the raw buffer size to the size necessary to // hold the entire result of the conversion. / 08441, 00000, "closed parenthesis missing in picture mask" // *Cause: A closed parenthesis was missing from the picture mask // passed to a UTL_PG conversion routine. // *Action: Correct the picture mask. / 08443, 00000, "syntax error in BLANK WHEN ZERO clause in mask options" // *Cause: A syntax error was found in the BLANK WHEN ZERO clause in // the mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // BLANK ZERO // BLANK ZEROS // BLANK ZEROES // BLANK WHEN ZERO // BLANK WHEN ZEROS // BLANK WHEN ZEROES // *Action: Correct the mask options parameter. / 08444, 00000, "syntax error in JUSTIFIED clause in mask options" // *Cause: A syntax error was found in the JUSTIFIED clause in the // mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // JUST // JUST RIGHT // JUSTIFIED // JUSTIFIED RIGHT // *Action: Correct the mask options parameter. / 08445, 00000, "syntax error in SIGN clause in mask options" // *Cause: A syntax error was found in the SIGN clause in the mask // options parameter passed to a UTL_PG conversion routine. // Valid specifications are: // SIGN LEADING // SIGN LEADING SEPARATE // SIGN LEADING SEPARATE CHARACTER // SIGN TRAILING // SIGN TRAILING SEPARATE // SIGN TRAILING SEPARATE CHARACTER // SIGN IS LEADING // SIGN IS LEADING SEPARATE // SIGN IS LEADING SEPARATE CHARACTER // SIGN IS TRAILING // SIGN IS TRAILING SEPARATE // SIGN IS TRAILING SEPARATE CHARACTER // *Action: Correct the mask options parameter. / 08446, 00000, "syntax error in SYNCHRONIZED clause in mask options" // *Cause: A syntax error was found in the SYNCHRONIZED clause in the // mask options parameter passed to a UTL_PG conversion // routine. Valid specifications are: // SYNC // SYNC LEFT // SYNC RIGHT // SYNCHRONIZED // SYNCHRONIZED LEFT // SYNCHRONIZED RIGHT // *Action: Correct the mask options parameter. / 08447, 00000, "syntax error in USAGE clause in mask options" // *Cause: A syntax error was found in the USAGE clause in the mask // options parameter passed to a UTL_PG conversion routine. // Valid specifications are: // USAGE DISPLAY // USAGE COMP // USAGE COMP-3 // USAGE COMP-4 // USAGE COMPUTATIONAL // USAGE COMPUTATIONAL-3 // USAGE COMPUTATIONAL-4 // USAGE IS DISPLAY // USAGE IS COMP // USAGE IS COMP-3 // USAGE IS COMP-4 // USAGE IS COMPUTATIONAL // USAGE IS COMPUTATIONAL-3 // USAGE IS COMPUTATIONAL-4 // *Action: Correct the mask options parameter. / 08448, 00000, "syntax error in DECIMAL-POINT environment clause" // *Cause: A syntax error was found in the DECIMAL-POINT environment // clause parameter passed to a UTL_PG conversion routine. // Valid specifications are: // DECIMAL-POINT IS COMMA // *Action: Correct the environment clause parameter. / 08449, 00000, "invalid numeric symbol found in picture mask" // *Cause: An invalid numeric symbol was found in the picture mask // parameter passed to a UTL_PG conversion routine. // *Action: Correct the picture mask parameter. / 08450, 00000, "invalid specification of CR in picture mask" // *Cause: The CR suffix was incorrectly specified in the picture mask // parameter passed to a UTL_PG conversion routine. The CR // suffix can only appear at the end of a picture mask. // *Action: Correct the picture mask parameter. / 08451, 00000, "invalid specification of DB in picture mask" // *Cause: The DB suffix was incorrectly specified in the picture mask // parameter passed to a UTL_PG conversion routine. The DB // suffix can only appear at the end of a picture mask. // *Action: Correct the picture mask parameter. / 08452, 00000, "specification of E in picture mask is unsupported" // *Cause: The floating point exponent symbol 'E' was specified in the // picture mask parameter passed to a UTL_PG conversion // routine. The floating point data type is currently not // supported by the UTL_PG conversion routines. // *Action: Correct the picture mask parameter, and the data, if // necessary. / 08453, 00000, "more than one V symbol specified in picture mask" // *Cause: The picture mask passed to a UTL_PG conversion routine // contained more than one decimal point indicator ('V'). // Only one decimal point indicator is allowed in the picture // mask. // *Action: Correct the picture mask parameter. / 08454, 00000, "more than one S symbol specified in picture mask" // *Cause: The picture mask passed to a UTL_PG conversion routine // contained more than one operational sign indicator ('S'). // Only one operational sign indicator is allowed in the // picture mask. // *Action: Correct the picture mask parameter. / 08455, 00000, "syntax error in CURRENCY SIGN environment clause" // *Cause: A syntax error was found in the CURRENCY SIGN environment // clause parameter passed to a UTL_PG conversion routine. // Valid specifications are: // CURRENCY SIGN IS x where x is a valid currency sign // *Action: Correct the environment clause parameter. / 08456, 00000, "no sign in picture mask but SIGN clause in mask options" // *Cause: The picture mask parameter passed to a UTL_PG conversion // routine contained no sign symbol ('S', '+', or '-'), but // the mask options parameter contained a SIGN clause. A sign // symbol is required in the picture mask parameter when the // mask options parameter contains a SIGN clause. // *Action: Correct the picture mask parameter or the mask options // parameter. / 08457, 00000,"syntax error in SEPARATE CHARACTER option of SIGN clause" // *Cause: A syntax error was found in the SEPARATE CHARACTER option // of the SIGN clause in the mask options parameter passed to // a UTL_PG conversion routine. Valid specifications are: // SEPARATE // SEPARATE CHARACTER // *Action: Correct the mask options parameter. / 08458, 00000, "invalid format parameter" // *Cause: The format parameter passed to a UTL_PG conversion routine // was invalid. The format parameter should have been built by // a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or // MAKE_NUMBER_TO_RAW_FORMAT. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08459, 00000, "invalid format parameter length" // *Cause: The format parameter passed to a UTL_PG conversion routine // was not the correct length. Format parameters must be 2048 // bytes in length. // *Action: Check to be sure that the format parameter was built by // MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, // and that it was not accidentally overwritten or modified // by the PL/SQL procedure. / 08460, 00000, "invalid environment clause in environment parameter" // *Cause: The environment parameter passed to a UTL_PG conversion // routine contained an unsupported or invalid environment // clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS // COMMA environment clauses are supported. // *Action: Correct the environment parameter. / 08462, 00000, "raw buffer contains invalid decimal data" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contains invalid decimal data. // *Action: Correct the input data. / 08463, 00000, "overflow converting decimal number to Oracle number" // *Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER // was not large enough to hold the Oracle number resulting // from the input decimal number. // *Action: Be sure that the input decimal number is valid, and besure // that the output variable is large enough to hold the Oracle // number value. / 08464, 00000, "input raw decimal data contains more than 42 digits" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine contained more than 42 digits. This // exceeds the maximum size of an Oracle number. // *Action: Correct the raw input buffer. / 08465, 00000, "input mask contains more than 32 characters" // *Cause: The input mask passed to UTL_PG numeric conversion // routine contained more the 32 characters. // *Action: Correct the mask input buffer. / 08466, 00000, "raw buffer length %s is too short for %s" // *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER // conversion routine was less than %s bytes long, but the // picture mask parameter specified that %s bytes of input data // were to be converted. // *Action: Either the input data is incorrect, or the picture mask // is incorrect. Correct the appropriate item. / 08467, 00000, "error converting Oracle number to %s" // *Cause: An error occurred when converting an Oracle number to a // COBOL of: // DISPLAY // COMP-3 // or character variable. // The Oracle number was not in the correct format. mat. // *Action: Correct the call to the conversion routine. The input // must be a valid Oracle number variable. / 08468, 00000, "mask option %s is not supported" // *Cause: The mask option was passed to a UTL_PG // conversion routine, but is not supported by UTL_PG. // The can be: // USAGE IS POINTER // USAGE IS INDEX // USAGE IS COMP-1 // USAGE IS COMP-2 // POINTER // *Action: Remove the from the mask options parameter // in the PL/SQL call to UTL_PG. / 08498, 00000, "Warning: picture mask '%s' overrides picture mask option 'USAGE IS %s' to 'USAGE IS DISPLAY'" // *Cause: Picture mask USAGE option was overridden by the picture mask. // *Action: This is an informational message only. The message may be // eliminated by changing the USAGE option to match the picture mask. / 08499, 00000, "Warning: picture mask options '%s' ignored by UTL_PG " // *Cause: Picture mask options such as OCCUR, SYNC and others are not // processed by the UTL_PG numeric conversion routines. // *Action: This is an informational message only. The message may be // eliminated by removing the unnecessary picture mask options // from the parameter list passed to the UTL_PG routine. / / / / End UTL_RAW and UTL_PG messages / / / 8401 - 8499 Reserved for APPC Gateway / / 8500 - 8599 Reserved for Protocol Procedural Gateway for / MQ Series / / / / / / / / / 8600 - 8699 Reserved for ??? sql*connnect errors / / 8700 - 8799 Reserved for ??? sql*connnect errors / / 8800 - 8999 Reserved for Tandem sql*connnect errors / / 9000 - 9099 Reserved for TERADATA sql*connnect errors / / 9100 - 9199 Reserved for file-based sql*connnect errors / / 9200 - 9499 Reserved for OS/2 and MSDOS OSD errors / // File I/O errors: 9200 - 9239 / 09200, 00000, "sfccf: error creating file" // *Cause: Could be out of disk space // *Action: See OSD error accompanying this message 09201, 00000, "sfcopy: error copying file" // *Cause: Block sizes may not match // *Action: See OSD error accompanying this message 09202, 00000, "sfifi: error identifying file" // *Cause: db_block_size specified in init.ora could be incorrect // *Action: See OSD error accompanying this message 09203, 00000, "sfofi: error opening file" // *Cause: File attributes may have changed // *Action: See OSD error accompanying this message 09204, 00000, "sfotf: error opening temporary file" // *Cause: Incorrect path may have been specified for the file // *Action: See OSD error accompanying this message 09205, 00000, "sfqio: error reading or writing to disk" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09206, 00000, "sfrfb: error reading from file" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09207, 00000, "sfsrd: error reading from file" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09208, 00000, "sftcls: error closing file" // *Cause: File may have been corrupted // *Action: See OSD error accompanying this message 09209, 00000, "sftget: error reading from file" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09210, 00000, "sftopn: error opening file" // *Cause: Incorrect path may have been specified for the file // *Action: See OSD error accompanying this message 09211, 00000, "sfwfb: error writing to file" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09212, 00000, "sfwfbmt: error writing to file" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09213, 00000, "slgfn: error fabricating file name" // *Cause: Filename may be too long // *Action: See OSD error accompanying this message 09214, 00000, "sfdone: I/O error detected" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09215, 00000, "sfqio: error detected in IOCompletionRoutine" // *Cause: File may have been truncated or corrupted // *Action: See OSD error accompanying this message 09216, 00000, "sdnfy: bad value '%s' for parameter %s" // *Cause: The directory specified as the value for the stated parameter // could not be used. // *Action: Make sure the directory you have specified is a valid // directory/file specification. 09217, 00000, "sfsfs: failed to resize file" // *Cause: Could be out of disk space // *Action: See OSD error accompanying this message 09218, 00000, "sfrfs: failed to refresh file size" // *Cause: File may be corrupted or truncated // *Action: See OSD error accompanying this message / // Memory allocation errors: 9240 - 9259 / 09240, 00000, "smpalo: error allocating PGA memory" // *Cause: Could be out of memory // *Action: See OSD error accompanying this message 09241, 00000, "smsalo: error allocating SGA memory" // *Cause: Could be out of memory // *Action: See OSD error accompanying this message 09242, 00000, "smscre: error creating SGA" // *Action: See OSD error accompanying this message 09243, 00000, "smsget: error attaching to SGA" // *Cause: SGA may not have been created (database not started) // *Action: See OSD error accompanying this message 09244, 00000, "smprset: error setting memory protections" // *Action: See OSD error accompanying this message 09245, 00000, "smcstk: error switching stacks" // *Action: See OSD error accompanying this message 09246, 00000, "sfsmap: unable to map SGA" // *Action: See OSD error accompanying this message 09247, 00000, "smsdes: error destroying the SGA" // *Action: See OSD error accompanying this message / // Process control errors: 9260 - 9269 / 09260, 00000, "sigpidu: error obtaining process id" // *Cause: May be out of resources // *Action: See OSD error accompanying this message 09261, 00000, "spdcr: error creating detached (background) process" // *Cause: Could be out of resources // *Action: See OSD error accompanying this message 09262, 00000, "spdde: error terminating detached (background) process" // *Cause: Could be out of resources // *Action: See OSD error accompanying this message 09263, 00000, "spini: error initializing process" // *Cause: Could be out of memory // *Action: See OSD error accompanying this message 09264, 00000, "sptpa: error flagging process" // *Cause: Could be out of resources // *Action: See OSD error accompanying this message 09265, 00000, "spwat: error temporarily suspending process" // *Cause: Could be out of resources // *Action: See OSD error accompanying this message 09266, 00000, "spawn: error starting an Oracle process" // *Cause: Could be out memory // *Action: See OSD error accompanying this message / // Security errors: 9270 - 9279 / 09270, 00000, "szalloc: error allocating memory for security" // *Cause: Could be out of memory // *Action: See OSD error accompanying this message 09271, 00000, "szlon: error verifying user name" // *Cause: Username may be too long // *Action: See OSD error accompanying this message 09272, 00000, "remote os logon is not allowed" // *Cause: Remote os login attempted when not allowed. // *Action: See OSD error accompanying this message 09273, 00000, "szrfc: error verifying role name" // *Cause: An OS error was returned when verifying the role name. // *Action: See OSD error accompanying this message 09274, 00000, "szrfc: insufficient role name buffer space" // *Cause: An OS role name was too long. // *Action: See OSD error accompanying this message 09275, 00000, "CONNECT INTERNAL is not a valid DBA connection" // *Cause: CONNECT INTERNAL is no longer supported for DBA connections. // *Action: Please try to connect AS SYSDBA or AS SYSOPER. // / // Direct loader errors: 9280 - 9289 / 09280, 00000, "sllfcf: error closing file" // *Cause: File may be corrupted // *Action: See OSD error accompanying this message 09281, 00000, "sllfop: error opening file" // *Cause: Possibly incorrect path specified to the file // *Action: See OSD error accompanying this message 09282, 00000, "sllfrb: error reading records" // *Cause: File could be corrupted // *Action: See OSD error accompanying this message 09283, 00000, "sllfsk: error skipping records" // *Cause: File could be corrupted // *Action: See OSD error accompanying this message 09284, 00000, "sllfop: cannot allocate read buffer" // *Cause: malloc() system call returned an error. The system might have run // out of heap space // *Action: Check additional information for the OS error. 09285, 00000, "sllfop: unrecognizable processing option, incorrect format" // *Cause: Processing option passed is of incorrect format // *Action: Consult your IUG for permissible formats / // Archiving errors: 9290 - 9299 / 09290, 00000, "sksaalo: error allocating memory for archival" // *Cause: Could be out of memory // *Action: See OSD error accompanying this message 09291, 00000, "sksachk: invalid device specified for archive destination" // *Cause: Unable to access directory // *Action: Specify a valid device in ARCHIVE control string 09292, 00000, "sksabln: unable to build archive file name" // *Cause: Bad directory or format specified // *Action: Specify a valid directory in 'log_archive_format' and a valid // format string in 'log_archive_format' in init.ora 09293, 00000, "sksasmo: unable to send message to console" // *Cause: An error was returned while attempting to send a message // to the console operator // *Action: See OSD error accompanying this message / // Windows specific errors: 9300 - 9309 / 09300, 00000, "osncon: unable to connect, DPMI not available" // *Cause: Unable to detect the presence of DPMI // *Action: Restart Windows and retry 09301, 00000, "osncon: local kernel only supported in standard mode" // *Cause: An attempt was made to connect to S: while in enhanced mode // *Action: Restart Windows in standard mode / // Miscellaneous errors: 9310 - 9339 / 09310, 00000, "sclgt: error freeing latch" // *Cause: Internal error // *Action: See OSD error accompanying this message 09311, 00000, "slsleep: error temporarily suspending process" // *Cause: May be out of resources // *Action: See OSD error accompanying this message 09312, 00000, "slspool: error spooling file to printer" // *Cause: Could be out of resources // *Action: See OSD error accompanying this message 09313, 00000, "slsprom: error prompting user" // *Cause: May be out of resources // *Action: See OSD error accompanying this message 09314, 00000, "sltln: error translating logical name" // *Cause: Internal buffer may have overflowed // *Action: See OSD error accompanying this message 09315, 00000, "sql2tt: two-task error translating ORACLE_EXECUTABLE" // *Cause: Internal error // *Action: See OSD error accompanying this message 09316, 00000, "szrpc: unable to verify password for role" // *Cause: OS roles may not be supported for this platform // *Action: See OSD error accompanying this message 09317, 00000, "szprv: insufficient privileges" // *Cause: The password specified is invalid // *Action: See OSD error accompanying this message 09318, 00000, "slkhst: unable to host out to operating system" // *Cause: There might not be enough memory for the command or hosting out // may not be supported on this platform // *Action: See OSD error accompanying this message 09319, 00000, "slgtd: unable to obtain the current date and time" // *Cause: The system time might be set incorrectly // *Action: See OSD error accompanying this message 09320, 00000, "szrfc: unable to obtain the list of valid OS roles" // *Cause: OS roles may not be supported on this platform // *Action: See OSD error accompanying this message 09321, 00000, "slzdtb: unable to convert zoned decimal to binary" // *Cause: internal error // *Action: See OSD error accompanying this message 09322, 00000, "slpdtb: unable to convert packed decimal to binary" // *Cause: internal error // *Action: See OSD error accompanying this message 09330, 00000, "Session terminated internally by Oracle or by an Oracle DBA" // *Cause: A client workstation that is abnormally disconnected would // cause Oracle to terminate that session after about a minute. // This message also appears in the trace file if a shutdown abort // is performed. /9331 - 9335 Reserved 09340, 00000, "Specified ORACLE_SID is either invalid or too long" // *Cause: ORACLE_SID must be at the most 4 alphanumeric characters. 09341, 00000, "scumnt: unable to mount database" // *Cause: Another instance is currently mounting the database 09342, 00000, "Detached process terminated by Oracle during shutdown abort" // *Cause: The user performed a shutdown abort. 09344, 00000, "spsig: error signalling thread" // *Cause: This function may not be implemented. / / // Windows 32-bit Two-Task driver: 9350 - 9359 / 09350, 00000, "Windows 32-bit Two-Task driver unable to allocate context area" // *Cause: See OSD error accompanying this message 09351, 00000, "Windows 32-bit Two-Task driver unable to allocate shared memory" // *Cause: See OSD error accompanying this message 09352, 00000, "Windows 32-bit Two-Task driver unable to spawn new ORACLE task" // *Cause: See OSD error accompanying this message 09353, 00000, "Windows 32-bit Two-Task driver unable to open event semaphore" // *Cause: See OSD error accompanying this message 09354, 00000, "Windows 32-bit Two-Task driver: ORACLE task unexpectedly died" // *Cause: See OSD error accompanying this message / / // Windows 3.1 Two-Task driver: 9360 - 9379 / 09360, 00000, "Windows 3.1 Two-Task driver unable to allocate context area" // *Cause: See OSD error accompanying this message 09361, 00000, "Windows 3.1 Two-Task driver unable to lock context area" // *Cause: See OSD error accompanying this message 09362, 00000, "Windows 3.1 Two-Task driver unable to deallocate context area" // *Cause: See OSD error accompanying this message 09363, 00000, "Windows 3.1 Two-Task driver invalid context area" // *Cause: See OSD error accompanying this message 09364, 00000, "Windows 3.1 Two-Task driver unable to create hidden window" // *Cause: See OSD error accompanying this message 09365, 00000, "Windows 3.1 Two-Task driver unable to destroy hidden window" // *Cause: See OSD error accompanying this message 09366, 00000, "Windows 3.1 Two-Task driver unable to allocate shared memory" // *Cause: See OSD error accompanying this message 09367, 00000, "Windows 3.1 Two-Task driver unable to deallocate shared memory" // *Cause: See OSD error accompanying this message 09368, 00000, "Windows 3.1 Two-Task driver unable to spawn ORACLE" // *Cause: See OSD error accompanying this message 09369, 00000, "Windows 3.1 Two-Task driver bad instance handle" // *Cause: See OSD error accompanying this message 09370, 00000, "Windows 3.1 Two-Task driver ORACLE task timed out" // *Cause: See OSD error accompanying this message / / 9500 - 9699 Reserved for MPE/XL OSD errors / / 9700 - 9999 Reserved for UNIX OSD errors / 09700, 00000, "sclin: maximum number of latches exceeded" // *Cause: ORACLE wants to use more latches then available. // *Action: increase INIT.ORA parameter latch_pages or // decrease the amount of shared memory you are using. 09701, 00000, "scnfy: maximum number of processes exceeded" // *Cause: PROCESSES INIT.ORA parameter exceeded. // *Action: Decrease the PROCESSES parameter and restart. 09702, 00000, "sem_acquire: cannot acquire latch semaphore" // *Cause: The semaphore used for accessing latches could not be seized // *Action: Send trace file to your customer support representative, // along with information on reproducing the error. 09703, 00000, "sem_release: cannot release latch semaphore" // *Cause: The semaphore used for accessing latches could not be released // *Action: Send trace file to your customer support representative, // along with information on reproducing the error. 09704, 00000, "sstascre: ftok error in creating test and set pages." // *Cause: the ftok() library call failed in sstastcre(). // *Action: Verify that tasdef@.dbf file exists. If it does then this is a // possible system failure. Perhaps System V compatibility is not // enabled. 09705, 00000, "spcre: cannot initialize latch semaphore" // *Cause: The semaphore used for accessing latches could not be initialized // *Action: Send trace file to your customer support representative, // along with information on reproducing the error. 09706, 00000, "slsget: get_process_stats error." // *Cause: get_process_stats system call returned an error. Possible OS error. // *Action: Check additional information returned. Look for information in // OS reference. Contact customer support. 09708, 00000, "soacon: failed to bind socket to port." // *Cause: The bind system call failed on the socket. // *Action: Check additional information for OS error. Try connecting again. 09709, 00000, "soacon: failed to accept a connection." // *Cause: The accept system call failed on the socket. // *Action: Check additional information for OS error. Try connecting again. 09710, 00000, "soarcv: buffer overflow." // *Cause: The internal buffer is not big enough to hold the message read. // *Action: Internal error. Contact customer support representative. 09711, 00000, "orasrv: archmon already connected." // *Cause: An existing connection has already been made from archmon to // orasrv. // *Action: Stop trying to connect. 09712, 00000, "orasrv: log archiver already connected." // *Cause: An existing connection has already been made from log archiver to // orasrv. // *Action: Stop trying to connect. 09713, 00000, "Global hardware clock failure caused instance termination." // *Cause: The global hardware clock used to generate the System Change // Number for Oracle has failed. // *Action: Check the global hardware clock. 09714, 00000, "Two Task interface: cannot obtain puname" // *Cause: The TXIPC driver cannot obtain the name of the PU. // (Possible OS error) // *Action: Check if the PUs are named (consistend). 09715, 00000, "orasrv: cannot obtain puname" // *Cause: Orasrv cannot obtain the name of the PU. // (Possible OS error) // *Action: Check if the PUs are named (consistend). 09716, 00000, "kslcll: Unable to fix in-flux lamport latch." // *Cause: One Oracle process died while still holding a lamport latch. // *Action: Exit (kill) all Oracle user processes. Shutdown (abort) and // restart Oracle RDBMS kernel. 09717, 00000, "osnsui: maximum number of user interrupt handlers exceeded." // *Cause: The internal limit on the number of user interrupt handlers has // been exceeded. // *Action: Reduce the number of simulataneous logons or reduce the number // of user interrupt handlers. 09718, 00000, "osnsui: cannot set up user interrupt handler." // *Cause: Malloc() failed to allocate space to hold user interrupt handler. // *Action: Possible memory resource shortage. 09719, 00000, "osncui: invalid handle." // *Cause: The handle passed to osncui is out of the valid range. // *Action: Use a valid handle. / / 09720-09739 reserved for Philips MPX P9x00 / 09740, 00000, "slsget: cannot get virtual memory region statistics." // *Cause: The vm_region system call failed to get virual memory region // statistics. // *Action: Check return code in sercerrno. Possible operating system // failure. 09741, 00000, "spwat: error waiting for a post." // *Cause: Msg_receive system call returned an error. Internal error. // *Action: Check return code in sercerrno. Port name is returned in // sercose[0]. 09742, 00000, "sppst: error during a post." // *Cause: Msg_send system call returned an error. Internal error. // *Action: Check return code in sercerrno. Port name is returned in // sercose[0]. 09743, 00000, "smscre: could not attach shared memory." // *Cause: The mmap or write system call returned an error. Internal error. // *Action: Contact Oracle support. 09744, 00000, "smsget: mmap returned an error." // *Cause: The mmap system call returned an error. Internal error. // *Action: Contact Oracle support. 09745, 00000, "smscre: vm_allocate error, unable to create shared memory." // *Cause: Error in system call vm_allocate. Failed to create SGA as a // single shared memory segment. // *Action: Check result code returned in sercerrno. Verify that the SGA // attach address is valid. 09746, 00000, "smscre: shared memory attach address incorrect." // *Cause: The vm_allocate system call attached the SGA at an incorrect // location. // *Action: Verify that the SGA attach address is valid. 09747, 00000, "pw_detachPorts: server call pws_detach failed." // *Cause: The call pws_detach to (Oracle helper) failed. // *Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. 09748, 00000, "pws_look_up: fork failed" // *Cause: The pws_look_up call could not fork the (Oracle helper) 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. 09749, 00000, "pws_look_up: port lookup failure" // *Cause: The pws_look_up could not find a port to (Oracle helper). // *Action: Make sure the (Oracle helper) server has been started correctly // by pws_look_up, and that the network name server is still running. 09750, 00000, "pw_attachPorts: port_rename failed." // *Cause: The port_rename system call failed; possible internal error. // *Action: Check return code in sercerrno, report to Oracle customer support. 09751, 00000, "pw_attachPorts: server call pws_attach failed." // *Cause: The call pws_attach to (Oracle helper) failed. // *Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. 09752, 00000, "pw_attachPorts: port_allocate failed." // *Cause: The port_allocate system call failed; possible resource exhaustion. // *Action: Check return code in sercerrno, report to Oracle customer support. 09753, 00000, "spwat: invalid process number." // *Cause: Function was passed an invalid oracle process id. // *Action: Internal error. Additional information indicates the invalid // process id. 09754, 00000, "sppst: invalid process number passed to sppst." // *Cause: Function was passed an invalid oracle process id. // *Action: Internal error. Contact Oracle support. 09755, 00000, "osngpn: port allocation failure." // *Cause: The port_allocate system call failed. // *Action: Possible system resource shortage; check the error code in // sercerrno. 09756, 00000, "osnpns: no port in the name server." // *Cause: osnpns could not find the given named port in the name server. // *Action: Check the error code in sercerrno. Make sure the shadow process // and network name server are still running. 09757, 00000, "osnipn: port allocation failure." // *Cause: The port_allocate system call failed. // *Action: Possible system resource shortage; check the error code in // sercerrno. 09758, 00000, "osnipn: could not check port in name server." // *Cause: The netname_check_in call failed. // *Action: Check the error code in sercerrno. Make sure the network name // server is running. 09759, 00000, "osnsbt: bad message received." // *Cause: The msg_receive system call failed, or received a bad message. // *Action: Internal error. Report the error code returned in sercerrno. 09760, 00000, "osnpui: cannot send break message" // *Cause: The Pipe driver could not send a break message to the ORACLE // shadow process break thread. // *Action: Contact your customer support representative. 09761, 00000, "pw_destroyPorts: server call pws_stop_instance failed." // *Cause: The call pws_stop_instance to (Oracle helper) failed. // *Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. 09762, 00000, "sNeXT_instanceName: translation error." // *Cause: A failure was detected while translating the value of ORACLE_SID. // *Action: Make sure ORACLE_SID is defined, and that it is of legal length. 09763, 00000, "osnmpx: send/receive error exchanging Mach ports." // *Cause: The Mach driver failed to exchange port information with the // other side of the connection. Either msg_send (sercose[0] == 1) // or msg_receive (sercose[0] == 2) failed. // *Action: Check return code in sercerrno. Make sure both sides of the // connection are still running. 09764, 00000, "osnmop: access error on oracle executable" // *Cause: The Mach driver could not access the oracle executable. // *Action: Check the permissions on the ORACLE executable and each // component of the ORACLE_HOME/bin path. 09765, 00000, "osnmop: fork failed" // *Cause: The Mach 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. 09766, 00000, "osnmop: buffer allocation failure." // *Cause: The Mach driver failed to allocate enough vm space for its // I/O buffers. // *Action: Decrease the value of buffer_size parameter in the Two-Task // driver hoststring. 09767, 00000, "osnmfs: bad return code from msg_send." // *Cause: The msg_send system call failed while flushing the Mach driver's // send buffer. // *Action: Internal error. Contact your customer support representative. 09768, 00000, "osnmgetmsg: could not read a message" // *Cause: The msg_receive system call returned a failure code while waiting // for a message in the Mach driver. // *Action: Internal error. Contact your customer support representative. 09769, 00000, "osnmbr: cannot send break message" // *Cause: The Mach driver could not send a break message to the ORACLE // shadow process break thread. // *Action: Internal error. Contact your customer support representative. 09770, 00000, "pws_look_up: translation failure." // *Cause: The pws_look_up routine failed to translate the name of the // (Oracle helper) executable. // *Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. // Additional information gives the translation error code. 09771, 00000, "osnmwrtbrkmsg: bad return code from msg_send." // *Cause: The msg_send sytem call failed while sending a Mach driver break. // *Action: Internal error. Contact your customer support representative. 09772, 00000, "osnpmetbrkmsg: message from host had incorrect message type" // *Cause: The Mach driver received a message having an unrecognizable // message type. // *Action: Internal error. Contact your customer support representative. 09773, 00000, "osnmgetdatmsg: message from host had incorrect message type" // *Cause: The Mach driver received a message having an unrecognizable // message type. // *Action: Internal error. Contact your customer support representative. 09774, 00000, "osnmui: cannot send break message" // *Cause: The Mach driver could not send a break message to the ORACLE // shadow process break thread. // *Action: Internal error. Contact your customer support representative. 09775, 00000, "osnmrs: reset protocol error" // *Cause: The Mach two-task driver could not reset the connection. // *Action: Internal error. Contact your customer support representative. 09776, 00000, "pws_look_up: access error on (Oracle helper) executable" // *Cause: The pws_look_up call could not access the (Oracle helper) // executable. // *Action: Check the permissions on the (Oracle helper) executable and each // component of the ORACLE_HOME/bin path. 09777, 00000, "osnpbr: cannot send break message" // *Cause: The pipe driver could not send a break message to the ORACLE // shadow process break thread. // *Action: Internal error. Contact your customer support representative. 09778, 00000, "snynfyport: failure allocating the notify port." // *Cause: The routine failed to allocate or set the task's notify port. // *Action: Possible operating system error. Contact Oracle support. 09779, 00000, "snyGetPort: failure to allocate a port." // *Cause: The port_allocate system call failed; system resources might be // exhausted. // *Action: Possible operating system error. Contact Oracle support. / / 09786-09825 reserved for Loader V2.0 / 09786, 00000, "sllfop: open error, unable to open file." // *Cause: Open system call returned an error. // *Action: Check errno. 09787, 00000, "sllfop: unrecognizable processing option, incorrect format." // *Cause: Processing option passed is of incorrect format. // *Action: Consult your IUG for permissible formats. 09788, 00000, "sllfrb: unable to read file." // *Cause: Read system call returned an error. // *Action: Check errno. Verify file exists. 09789, 00000, "sllfsk: unable to read file." // *Cause: Read system call returned an error. // *Action: Check errno. Verify file exists. 09790, 00000, "sllfcf: unable to close file." // *Cause: Close system call returned an error. // *Action: Check errno. 09791, 00000, "slembdf: translation error, unable to translate error file name." // *Cause: Additional information indicates error returned from sltln. // *Action: Check additional information. 09792, 00000, "sllfop: cannot allocate read buffer." // *Cause: Malloc system call returned an error. The system might have run out // of heap space. // *Action: Check additional information for the OS error. 09793, 00000, "szguns: length of user name is greater than buffer." // *Cause: The length of the name of the user being looked up is longer than // size of the buffer provided by the calling routine. // *Action: This is an internal error. Contact ORACLE customer support. 09794, 00000, "szrbuild: length of role name is greater than buffer." // *Cause: The length of the name of the role being looked up is longer than // size of the buffer provided by the calling routine. // *Action: This is an internal error. Contact ORACLE customer support. 09795, 00000, "szrbuild: malloc of role structure failed." // *Cause: The allocation of memory for an internal structure used to // hold a role descriptor failed. // *Action: Check the UNIX error number for a possible operating system // failure. 09796, 00000, "szrbuild: malloc of role name failed." // *Cause: The allocation of memory for an internal buffer used to hold the // name of a role failed. // *Action: Check the UNIX error number for a possible operating system // failure. 09797, 00000, "Failed to get O/S MAC privileges." // *Cause: The operating system would not allow the retrieval of this // process' privileges. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09798, 00000, "Label comparison failed." // *Cause: The comparison of two binary labels failed. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09799, 00000, "File label retrieval failed." // *Cause: ORACLE was unable to get a label attached to a file. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09800, 00000, "Process sensitivity label retrieval failed." // *Cause: ORACLE was unable to get the sensitivity label for a process. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09801, 00000, "Unable to get user ID from connection" // *Cause: ORACLE was unable to retrieve the user's ID number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09802, 00000, "Conversion of binary label to string failed." // *Cause: ORACLE was unable to convert a binary label to a string. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09803, 00000, "Allocation of string buffer failed." // *Cause: a buffer used to hold the name of the file for which a label was // to be obtained could not be allocated. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. // The number of bytes that ORACLE attempted to allocate is in // the "Additional Information" field. 09804, 00000, "Class conversion from binary to ORACLE failed." // *Cause: ORACLE was unable to convert a class component from binary // format to ORACLE format. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09805, 00000, "conversion of category number to string failed." // *Cause: ORACLE was unable to translate a category number to its // corresponding string representation failed. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. The // category number is contained in the "Additional information" // field. 09806, 00000, "Allocation of label string buffer failed." // *Cause: a temporary buffer used to hold a label could not be allocated. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. // The number of bytes that ORACLE attempted to allocate is in // the "Additional Information" field. 09807, 00000, "Conversion of label from string to binary failed." // *Cause: ORACLE was unable to convert the string representation of a label // to binary format. // *Action: Re-enter a valid label. 09808, 00000, "Could not obtain user clearance." // *Cause: ORACLE was unable to get a user's clearance level. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09809, 00000, "Unable to get user's group ID from connection" // *Cause: ORACLE was unable to retrieve the user's group ID number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09810, 00000, "Unable to get process ID from connection" // *Cause: ORACLE was unable to retrieve the user's process ID number from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE customer support. 09811, 00000, "Unable to initialize package." // *Cause: ORACLE was unable to initialize the library used to obtain // security information. // *Action: This is an internal error. Contact ORACLE support. 09812, 00000, "Unable to get user clearance from connection" // *Cause: ORACLE was unable to retrieve the user's operating system // session clearance from the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE customer support. 09813, 00000, "Unable to get directory status" // *Cause: ORACLE was unable to determine if a directory is multilevel. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09814, 00000, "Unable to expand file name" // *Cause: ORACLE was unable to expand the name of a file that resides // in multilevel directory. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09815, 00000, "File name buffer overflow" // *Cause: The buffer that ORACLE uses to hold the expanded name of a // too small. // *Action: This is an internal error. Contact ORACLE customer support. 09816, 00000, "Unable to set effective privileges" // *Cause: // *Action: This is an internal error. Contact ORACLE support. 09817, 00000, "Write to audit file failed." // *Cause: ORACLE was unable to write an entry to the file used as the // audit trail. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09818, 00000, "Number is too large" // *Cause: ORACLE was unable to convert a component string to a number because // the number is larger than the largest possible value for an // integer. The additional information field specifies the maximum. // *Action: Correct the string and repeat the conversion. 09819, 00000, "Number exceeds maximum legal value" // *Cause: the number specified for a component was greater than the maximum // value allowed for that component. // *Action: Change the component to a value less than the maximum and repeat // the conversion. The maximum component number is contained in the // "Additional information" field. 09820, 00000, "Conversion of class string to numeric representation failed." // *Cause: ORACLE was unable to convert a class string to a number because // all of the characters in the string were not numeric. // *Action: Change the string to be either all numbers or all non-numeric // characters and repeat the conversion. 09821, 00000, "Numeric label is not valid" // *Cause: A label specified in ORACLE numeric format was found not to be // valid. // *Action: Re-enter a valid label. Consult your system's encodings for valid // numeric component values. 09822, 00000, "Translation of audit file name failed." // *Cause: ORACLE was unable to translate the value of the // "audit_trail_dest" initialization parameter. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09823, 00000, "device name is too long" // *Cause: The name of a device was too long to fit into an internal buffer. // The additional information field contains the length of the device // name. // *Action: This is an internal error. Contact ORACLE support. 09824, 0000, "Unable to enable allowmacaccess privilege." // *Cause: ORACLE was not able to turn on allowmacaccess privilege so that it // could do a label comparison. // *Action: Check the UNIX error number. If it indicates that ORACLE does not // have the allowmacaccess privilege, add the allowmacaccess privilege // to the potential privilege set of $ORACLE_HOME/bin/oracle using // chpriv (1M). If the executable already has the allowmacaccess // privilege, contact ORACLE support. 09825, 0000, "Unable to disable allowmacaccess privilege." // *Cause: ORACLE was not able to turn off the allowmacaccess privilege after // doing a label comparison. // *Action: This is an internal error. Contact ORACLE support. 09826, 00000, "SCLIN: cannot initialize atomic latch." // *Cause: System call atomic_op() return error. // *Action: Check additional information in the trace file. 09827, 00000, "SCLGT: atomic latch return unknown error." // *Cause: System call atomic_op() return unexpected error. // *Action: Check additional information in the trace file. 09828, 00000, "SCLFR: atomic latch return error." // *Cause: System call atomic_op() return unexpected error. // *Action: Check additional information in the trace file. 09829, 00000, "pw_createPorts: server call pws_start_instance failed." // *Cause: The call pws_start_instance to (Oracle helper) failed; system // resources might be exhausted. // *Action: Make sure the server is still active. Check the error code // returned in sercerrno, and look for error messages in the // server log file. 09830, 00000, "snyAddPort: failed to perform a remote procedure call." // *Cause: The msg_rpc system call returned an error. // *Action: Internal error. Contact Oracle support. 09831, 00000, "snyStartThread: failed to build the server port set." // *Cause: The routine failed to build a port set on which to listen for // requests. // *Action: Possible operating system failure. Contact Oracle support. 09832, 00000, "infoCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09833, 00000, "addCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09834, 00000, "snyGetPortSet: failed to collect info on a port." // *Cause: The port_status system called failed. // *Action: Possible operating system error. Contact Oracle support. 09835, 00000, "addCallback: callback port is already in a set." // *Cause: The port to be added to the callback list is already in a port set. // *Action: Internal error. Contact Oracle support. 09836, 00000, "addCallback: could not add a port to the callback set." // *Cause: The port_set_add system called failed. // *Action: Possible operating system error. Contact Oracle support. 09837, 00000, "addCallback: could not add allocate a callback link." // *Cause: The malloc library call failed to allocate space for a callback link. // *Action: Possible operating system error. Contact Oracle support. 09838, 00000, "removeCallback: failure removing the callback port." // *Cause: The port port_set_remove system call failed. // *Action: Possible operating system error. Contact Oracle support. 09839, 00000, "removeCallback: callback port is not in the callback set." // *Cause: The port to be removed to the callback list is not in the // callback port set. // *Action: Internal error. Contact Oracle support. 09840, 00000, "soacon: Name translation failure." // *Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@. // *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID // in oratab is correct. 09841, 00000, "soacon: Name translation failure." // *Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@. // *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID // in oratab is correct. 09842, 00000, "soacon: Archmon unable to create named pipe." // *Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@. // *Action: Your current OS login may lack write permission for the // ORACLE_HOME/dbs directory. Only userids in the dba group of a // given instance can run archmon for that ORACLE_SID. Make sure // that the ORACLE_HOME directory is correct in oratab. 09843, 00000, "soacon: Archmon unable to create named pipe." // *Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@. // *Action: Your current OS login may lack write permission for the // ORACLE_HOME/dbs directory. Only userids in the dba group of a // given instance can run archmon for that ORACLE_SID. Make sure // that the ORACLE_HOME directory is correct in oratab. 09844, 00000, "soacon: Archmon unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/mon2arch_@. // *Action: Only the oracle dba can run archmon. Make sure that your // current OS login has owner or group search permission for the // ORACLE_HOME/dbs directory. The max number of open files may have // been exceeded. 09845, 00000, "soacon: Archmon unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/arch2mon_@. // *Action: Only the oracle dba can run archmon. Make sure that your // current OS login has owner or group search permission for the // ORACLE_HOME/dbs directory. The max number of open files may have // been exceeded. 09846, 00000, "soacon: ARCH unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/mon2arch_@. // *Action: Make sure that the OS userid of the currently running database // has search permission for the ORACLE_HOME/dbs directory. The max // number of open files may have been exceeded. 09847, 00000, "soacon: ARCH unable to open named pipe." // *Cause: open() failed to open named pipe ?/dbs/arch2mon_@. // *Action: Make sure that the OS userid of the currently running database // has search permission for the ORACLE_HOME/dbs directory. The max // number of open files may have been exceeded. 09848, 00000, "soawrt: Unable to write to named pipe." // *Cause: // *Action: 09849, 00000, "soarcv: Unable to read from named pipe." // *Cause: // *Action: 09850, 00000, "soacon: Archmon unable to lock named pipe." // *Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@. // *Action: Make sure that archmon is not already active on another terminal // for this ORACLE_SID. Only one archmon session is allowed at a // time for a given instance. 09851, 00000, "soacon: Archmon unable to lock named pipe." // *Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@. // *Action: Make sure that archmon is not already active on another terminal // for this ORACLE_SID. Only one archmon session is allowed at a // time for a given instance. 09853, 00000, "snyRemovePort: bad return code from request." // *Cause: The request to remove a port from the callback set returned a // failure code. // *Action: Possible operating system error. Contact Oracle support. 09854, 00000, "snyPortInfo: bad return code from request." // *Cause: The request to collect info on a port in the callback set returned // a failure code. // *Action: Possible operating system error. Contact Oracle support. 09855, 00000, "removeCallback: bad message format." // *Cause: The routine received an incorrectly formatted request. // *Action: Internal error. Contact Oracle support. 09856, 00000, "smpalo: vm_allocate error while allocating pga." // *Cause: The vm_allocate system call returned an error. // *Action: Check returned error. Possibly out of system resources. 09857, 00000, "smprset: vm_protect error while protecting pga." // *Cause: The vm_protect system call returned an error. // *Action: Internal error. Contact Oracle support. / / 09858-09859 Reserved For NeXT port / / / 09860-09869 Reserved For Oracle Europe / 09870, 00000, "spini: failure initializing maximum number of open files." // *Cause: ulimit system call returned an error. // *Action: Check errno. 09871, 00000, "TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf." // *Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages. // *Action: Check additional return error for more information. 09872, 00000, "TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf." // *Cause: Create() failed when trying to create the tasdef file. // *Action: Verify permissions on $(ORACLE_HOME)/dbs directory. 09873, 00000, "TASDEF_OPEN: open error when opening tasdef@.dbf file." // *Cause: Unable to open tasdef@.dbf file. // *Action: Check errno. Possible permission problem. Verify that // tasdef@.dbf file exists. 09874, 00000, "TASDEF_READ: read error, unable to read tasdef@.dbf file." // *Cause: Read system call returned an error when attempting to read // ?/dbs/tasdef@.dbf. // *Action: Check errno returned. Sgadef file may be corrupted or // incompatible with oracle version. 09875, 00000, "TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file." // *Cause: Write call failed. // *Action: Check errno returned. Possibly out of space on device. 09876, 00000, "TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file." // *Cause: Close system call returned an error. // *Action: Check errno returned. Possible operating system failure. 09877, 00000, "sstascre: shmget error, unable to get a shared memory segment." // *Cause: Error in shmget. // *Action: Check errno returned. Verify that enough shared memory is available // on the system. 09878, 00000, "sstascre/sstasat: shmat error, unable to attach tas write page" // *Cause: Error in shmat. // *Action: Check errno returned.Verify that enough shared memory is available // on the system. 09879, 00000, "sstascre/sstasat: shmat error, unable to attach tas read page" // *Cause: Error in shmat. // *Action: Check errno returned.Verify that enough shared memory is available // on the system. 09880, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas write page" // *Cause: Error in shmdt. // *Action: Check errno returned. 09881, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas read page" // *Cause: Error in shmdt. // *Action: Check errno returned. 09882, 00000, "sstasfre/sstasdel: shmctl error, unable to remove tas shm page" // *Cause: Error in shmctl. // *Action: Check errno returned. 09883, 00000, "Two Task interface: oratab file does not exist" // *Cause: The oratab file does not exist. // *Action: Install oracle before you use it or recreate the oratab file. 09884, 00000, "Two Task interface: SID doens't match current PU" // *Cause: You are trying to start oracle on another PU than you configured // oracle on or there is no entry for this SID in oratab file. // *Action: Start oracle with this SID on its designated PU (see oratab file). // Or install the new database with SID. 09885, 00000, "osnTXtt: cannot create TXIPC channel" // *Cause: The TXIPC 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. 09886, 00000, "osnTXtt: translation error while expanding txipc@.trc." // *Cause: Failure of sltln(txipc@.trc) while creating debug channel. // *Action: Check additional return error for more information. 09887, 00000, "osnTXtt: Failed to create/open debug channel." // *Cause: // *Action: 09888, 00000, "osnTXtt: txipc channel creation failed" // *Cause: The txipc driver failed to create channels 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 // operating system error code and contact your system administrator. 09889, 00000, "osnTXtt: access error on oracle executable" // *Cause: The txipc driver could not access the oracle executable. // *Action: Check the permissions on the ORACLE executable and each // component of the ORACLE_HOME/bin path. 09890, 00000, "osnTXtt: malloc failed" // *Cause: The txipx driver failed to allocate enough heap space for its // context area buffers. // *Action: Contact your customer support representative. 09908, 00000, "slkmnm: gethostname returned error code." // *Cause: The system call gethostname returned an error. // *Action: This is most likely an internal error. Make sure gethostname // is successful in other contexts, and if so contact Oracle support. 09909, 00000, "Malloc of scratch buffer failed." // *Cause: Memory needed for a temporary buffer could not be allocated. // The additional information field contains the number of bytes // that ORACLE attempted to allocate. // *Action: Check the UNIX error number. It is probable that the system has // run out of memory. If there is no error, contact ORACLE support. 09910, 00000, "Unable to find ORACLE password file entry for user." // *Cause: No entry exists for the user in the ORACLE password file. // *Action: Have the database administrator install a password entry by // running orapasswd. 09911, 00000, "Incorrect user password." // *Cause: The password entered by the user was incorrect. // *Action: Enter the correct password. 09912, 00000, "Malloc of name buffer(s) failed." // *Cause: ORACLE was unable to allocate memory for one or both of the buffers // that are used to hold the name of DBA and the operator users. // *Action: Check the UNIX error number. It is probable that the system has // run out of memory. If there is no error, contact ORACLE support. 09913, 00000, "Malloc of dummy name failed." // *Cause: ORACLE was unable to allocate memory for the user name that is to // to be used in the encryption of the user's password. // *Action: Check the UNIX error number. It is probable that the system has // run out of memory. If there is no error, contact ORACLE support. 09914, 00000, "Unable to open the ORACLE password file." // *Cause: ORACLE could not open the password file for reading. // *Action: Check the UNIX error number. If the error number indicates that the // file does not exist, have the database administrator create the // file by running orapasswd. If the error number indicates // insufficient permissions, ask the database administrator to change // the permissions. Otherwise, contact ORACLE customer support. 09915, 00000, "Password encryption failed." // *Cause: ORACLE was unable to encrypt a password. // *Action: This is an internal error - contact ORACLE customer support. 09916, 00000, "Required password was not specified." // *Cause: A user attempted to connect as "internal," but did not specify a // password. // *Action: Connect as internal again and specify a password. 09918, 00000, "Unable to get user privileges from SQL*Net" // *Cause: ORACLE was unable to retrieve the user's privilege set from the // SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09919, 00000, "Unable to set label of dedicated server" // *Cause: ORACLE was unable to set the label of the dedicated to server // to the required value. // *Action: Check the UNIX error number for a possible operating system error. // Also, check the privileges on the oracle executable. It should // have at least "allowmacaccess" privilege. 09920, 00000, "Unable to get sensitivity label from connection" // *Cause: ORACLE was unable to retrieve the user's sensitivity label from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09921, 00000, "Unable to get information label from connection" // *Cause: ORACLE was unable to retrieve the user's information label from // the SQL*Net connection. // *Action: Check the UNIX error number for a possible operating system error. // Also check the "additional information" field for the SQL*Net // error. If there is no error, contact ORACLE support. 09922, 00000, "Can't spawn process - background log directory not created properly" // *Cause: ORACLE was unable to spawn a background process because the // directory that will hold trace files of the background // processes was not created properly. // *Action: Examine the directory pointed to by the initialization // parameter "background_dump_dest". Make sure that all of the // following is true: // 1. The directory exists. // 2. The name indeed points to a directory, and is not a file. // 3. The directory is accessible and writable to the ORACLE user. 09923, 00000, "Can't spawn process - user log directory not created properly" // *Cause: ORACLE was unable to spawn a background process because the // directory that holds the trace files of the dedicated server // processes was not created properly. // *Action: Examine the directory pointed to by the initialization // parameter "user_dump_dest". Make sure that all of the // following is true: // 1. The directory exists. // 2. The name indeed points to a directory, and is not a file. // 3. The directory is accessible and writable to the ORACLE user. 09924, 00000, "Can't spawn process - core dump directory not created properly" // *Cause: ORACLE was unable to spawn a background process because the // directory that holds the core dumps produced by ORACLE processes // in the event of exceptions was not created properly. // *Action: Examine the directory pointed to by the initialization // parameter "core_dump_dest". Make sure that all of the // following is true: // 1. The directory exists. // 2. The name indeed points to a directory, and is not a file. // 3. The directory is accessible and writable to the ORACLE user. 09925, 00000, "Unable to create audit trail file" // *Cause: ORACLE was not able to create the file being used to hold // audit trail records. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09926, 00000, "Unable to set effective privilege set of the server" // *Cause: A dedicated server was unable to set it's own privilege set. // *Action: Check the privileges granted to the ORACLE executable. It must // have at least "allowmacacess" privilege. 09927, 00000, "Unable to set label of server" // *Cause: ORACLE was not able to set the label of a server to a new value. // *Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it // has "allowmacaccess" privilege. 09928, 00000, "Unable to restore the label of server" // *Cause: ORACLE was unable to restore the label of the server to the value // that it had before raising it to database high. // *Action: This is an internal error - contact ORACLE support. 09929, 00000, "GLB of two labels is invalid" // *Cause: The result of a greatest lower bound operation on two labels was // not valid. // *Action: Repeat the operation with two different labels. Consult the // system encoding file for the values of valid labels. 09930, 00000, "LUB of two labels is invalid" // *Cause: The result of a least upper bound operation on two labels was // not valid. // *Action: Repeat the operation with two different labels. Consult the // system encoding file for the values of valid labels. 09931, 00000, "Unable to open ORACLE password file for reading" // *Cause: An attempt to open a password file for reading failed. // *Action: Make sure that the permissions on the file have not been changed // so that the ORACLE user cannot open it. 09932, 00000, "Close of ORACLE password file failed." // *Cause: An attempt to close a password file failed. // *Action: Check the UNIX error number for the specific reason. 09933, 00000, "Deletion of old password file failed." // *Cause: The removal of the old password file failed. // *Action: Check the UNIX error number for the specific reason. 09934, 00000, "Link of current password file to old failed." // *Cause: ORACLE was unable to create a link so that the old password file // could be saved. // *Action: Check the UNIX error number for the specific reason. 09935, 00000, "Unlink of current password file failed." // *Cause: ORACLE was unable to complete the saving of the current password // file. // *Action: Check the UNIX error number for the specific reason. 09936, 00000, "Open of ORACLE password file for write failed." // *Cause: ORACLE was unable to create a password file. // *Action: Check the UNIX error number for the specific reason. 09937, 00000, "Chmod of ORACLE password file failed." // *Cause: ORACLE was unable to change a password file to be readonly. // *Action: Check the UNIX error number for the specific reason. 09938, 00000, "Save of signal handlers failed." // *Cause: ORACLE was unable to save the previous values of selected // signal handlers. // *Action: This is an internal error. Contact ORACLE support. 09939, 00000, "Restoration of signal handlers failed." // *Cause: ORACLE was unable to restore the previous values of selected // signal handlers. // *Action: This is an internal error. Contact ORACLE support. 09940, 00000, "ORACLE password file header is corrupt" // *Cause: The header of one of the password files was not in the format that // ORACLE expected. // *Action: Check the headers of both files. The header should be in the format // "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" // where N is a number. // Remove the corrupt file(s) and re-run "orapasswd". 09941, 00000, "Version of orapasswd or installer is older than file." // *Cause: The version of orapasswd or installer that is being run is older // than that of the ORACLE password file. Since the file version is // only changed when the format is changed, this error means that the // executable is using a different format than that with which the // file was created. // *Action: Run a version of the installer or orapasswd whose version is the // same or later than that of the file. 09942, 00000, "Write of ORACLE password file header failed." // *Cause: The attempt to write out the header of the ORACLE password file // failed. // *Action: Check the operating system error number. It is possible that the // file system became full. 09943, 00000, "Allocation of memory for password list component failed." // *Cause: When it is building a list of password file entries, ORACLE // allocates memory for various components. One of the // allocations failed. // *Action: Check the operating system error number. The system has // probably run out of memory. 09944, 00000, "Password entry is corrupt." // *Cause: An entry in an ORACLE password file was not in the format that // ORACLE expected. // *Action: Removed the corrupt file(s) and re-run "orapasswd." 09945, 00000, "Unable to initialize the audit trail file" // *Cause: ORACLE unable to write header information to the file being // used as the audit trail. // *Action: Check the UNIX error number for a possible operating system error. // If there is no error, contact ORACLE customer support. 09946, 00000, "File name too long for buffer" // *Cause: The buffer that was to be used to hold a file name was // determined to be too short for the generated name. This will // happen if the translated name for either a trace file or an // audit file is longer than the maximum allowed, which on many // ports is 256 characters. // *Action: Use a shorter file name. 09947, 00000, "Unable to allocate connection attributes structure" // *Cause: ORACLE was not able to allocate the memory needed to hold // the attributes of the SQL*Net connection. The "Additional // Information" field holds the number of bytes that ORACLE // attempted to allocate. // *Action: Check the UNIX error number. It is probable that the system has // run out of memory. If there is no error, contact ORACLE // customer support. 09948, 00000, "Process information label retrieval failed." // *Cause: ORACLE was unable to get the information label for a process. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09949, 00000, "Unable to get client operating system privileges" // *Cause: ORACLE was unable to get the operating system privileges for the // client process. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09950, 00000, "Unable to get server operating system privileges" // *Cause: ORACLE was unable to get its privileges from the operating system. // *Action: This is an error that should never happen. Contact ORACLE customer // support. 09951, 00000, "Unable to create file" // *Cause: ORACLE was unable to create a file. // *Action: Check the UNIX error number for a possible operating system // failure. If there is no error, contact ORACLE support. 09952, 00000, "scgcmn: lk_open_convert unexpected return: open failed" // *Cause: The distributed lock manager returned an unexpected value // *Action: Check for system error message and // refer to the distributed lock manager documentation // or contact your customer support representative. 09953, 00000, "scggc: unexpected return of a lock convert" // *Cause: The distributed lock manager returned an unexpected value // *Action: Check for lock manager error message and refer to DLM documentation // refer to the distributed lock manager documentation // or contact your customer support representative. 09954, 00000, "scgcc: unexpected return status to callback of lock close" // *Cause: The distributed lock manager returned an unexpected value // *Action: Check for lock manager error message and refer to DLM documentation // refer to the distributed lock manager documentation // or contact your customer support representative. 09955, 00000, "scgcan: unexpected return status when canceling a lock" // *Cause: DLM system service x returned an unexpected value // *Action: Check for system error message and refer to DLM documentation // refer to the distributed lock manager documentation // or contact your customer support representative. 09956, 00000, "scgcm: unexpected lock status condition" // *Cause: A global locking system service returned an unexpected value. // *Action: Check for system error message (if any) and refer to // refer to the distributed lock manager documentation // or contact your customer support representative. 09957, 00000, "Unable to send termination request to IMON" // *Cause: The attempt to send a termination signal to IMON failed. // *Action: This is an internal error, contact ORACLE support. 09958, 00000, "IMON: two processes with the same ORACLE pid are active" // *Cause: The IMON process was unable to add an entry for a server process // because another active process occupies the slot. // *Action: This is an internal error, contact ORACLE support. 09959, 00000, "IMON: deletion of a process failed." // *Cause: The IMON process was unable to delete a server process from its // process ID array because no entry for the process could be found. // *Action: This is an internal error, contact ORACLE support. 09960, 00000, "Unable to establish signal handler for termination signal" // *Cause: ORACLE was unable to set up a handler for the signal used to // notify it that the instance was shutting down. // *Action: This is an internal error, contact ORACLE support. 09961, 00000, "Unable to restore termination signal handler" // *Cause: ORACLE failed to set the handler for the termination signal to its // previous value. // *Action: This is an internal error, contact ORACLE support. 09962, 00000, "lk_group_create error in scggrc" // *Cause: // *Action: 09963, 00000, "lk_group_attach error in scggra" // *Cause: // *Action: 09964, 00000, "lk_group_detach error in scggrd" // *Cause: // *Action: 09966, 00000, "scumnt: translation error while expanding ?/dbs/lk" // *Cause: Failure of sltln in scumnt // *Action: Check additional return error for more information. 09967, 00000, "scumnt: unable to create or open file" // *Cause: open system call returned an error // *Action: check errno 09968, 00000, "scumnt: unable to lock file" // *Cause: lock file operating system call returned an error // *Action: check errno 09969, 00000, "scurls: unable to close lock file" // *Cause: close system call returned an error // *Action: check errno 09974, 00000, "skxfidini: Error Initializing SDI Channel" // *Cause: The process was unable to initialize the SDI channel properly. // *Action: Correct the operating system error and retry the operation. / 09975, 00000, "kxfspini: Error Initializing SDI Process" // *Cause: The process was unable to attach to the SDI channel. // *Action: Verify that the SDI process specific limits correctly configured. // Correct the operating system error and retry the operation. / 09976, 00000, "skxfqdini: Error Creating Port" // *Cause: The process was unable to create a communications endpoint. // *Action: Verify that the SDI port specific limits correctly configured. // Correct the operating system error and retry the operation. / 09977, 00000, "skxfqhini: Error Connecting" // *Cause: The process was unable to connect to another endpoint. // *Action: Verify that the SDI port specific limits correctly configured. // Check that the other node(s) is part of the cluster and operating // properly. Correct the operating system error and retry the // operation. / 09978, 00000, "skxfqhdel: Error Disconnecting from another endpoint." // *Cause: The process was unable to disconnect cleanly from another endpoint. // *Action: Check that the other node(s) are part of the cluster and operating // properly. Check the instance and processes on the other node(s). // Correct the operating system error and retry the operation. / 09979, 00000, "skxfqhsnd: Error Sending a message to another endpoint" // *Cause: The process was unable to send a message to an existing endpoint. // *Action: Check that the other node(s) are part of the cluster and operating // properly. Check the instance and processes on the other node(s). // Correct the operating system error and retry the operation. / 09980, 00000, "skxfqdrcv: Error Receiving a message from another endpoint" // *Cause: The process encountered an error while trying to receive a message. // *Action: Check that the other node(s) are part of the cluster and operating // properly. Check the instance and processes on the other node(s). // Correct the operating system error and retry the operation. / 09981, 00000, "skxfqdreg: Error Adding a page to the SDI buffer pool" // *Cause: The process was unable to add a page to the SDI buffer pool. // *Action: Correct the operating system error and retry the operation. / 09982, 00000, "skxfqddrg: Error Removing a page from the SDI buffer pool" // *Cause: The process was unable to remove a page to the SDI buffer pool. // *Action: Correct the operating system error and retry the operation. / 09983, 00000, "skxfidsht: Error shutting down SDI channel" // *Cause: The process was unable shut down the SDI channel // *Action: Check the SDI persistent resources using SDI tools. // Verify that all processes exited cleanly and the instance // is safely shut down. Delete any remaining // SDI channel IDs associated with the current instance. / 09984, 00000, "SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist" // *Cause: file does not exist or is not accessible // *Action: Restart the instance to create the SGA definition file. / 09985, 00000, "SGA definition file could not be read" // *Cause: UNIX read() operation failed // *Action: check errno and take appropriate action. / 09986, 00000, "wrong number of bytes read from SGA definition file" // *Cause: Struct skgmsdef size differs from no. of bytes read from SGA file // *Action: Compare the two struct definitions and ensure that they are // identical in size and structure. / 09987, 00000, "unable to attach to SGA in READ-ONLY mode" // *Cause: The instance is not up, or SGA segments are not read-accessible // *Action: Verify that the instance is up and read permissions for the // SGA segments are set. / 09988, 00000, "error while detaching SGA" // *Cause: skgmsdef struct is corrupted and/or segment addresses are modified // *Action: Safely shut down instance and mount SGA segments again. / 09989, 00000, "attempt to use invalid skgmsdef struct pointer" // *Cause: Pointer to skgmsdef struct used without validating it // *Action: Assign a valid address to the skgmsdef struct pointer before // using it. / / Pseudo-error debugging events: / Error codes 10000 .. 10999 are reserved for debug event codes that are / not really errors. / // NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages should // not be translated. 10000, 00000, "controlfile debug event, name 'control_file'" // *Cause: // *Action: 10001, 00000, "controlfile crash event1" // *Cause: // *Action: 10002, 00000, "controlfile crash event2" // *Cause: // *Action: 10003, 00000, "controlfile crash event3" // *Cause: // *Action: 10004, 00000, "controlfile crash event4" // *Cause: // *Action: 10005, 00000, "trace latch operations for debugging" // *Cause: // *Action: 10006, 00000, "testing - block recovery forced" // *Cause: // *Action: 10007, 00000, "log switch debug crash after new log select, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10008, 00000, "log switch debug crash after new log header write, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10009, 00000, "log switch debug crash after old log header write, thread %s" // *Cause: // *Action: level 1 - closed thread only // level 2 - open thread only // level 3 - open or closed thread 10010, 00000, "Begin Transaction" // *Cause: // *Action: 10011, 00000, "End Transaction" // *Cause: // *Action: 10012, 00000, "Abort Transaction" // *Cause: // *Action: 10013, 00000, "Instance Recovery" // *Cause: // *Action: 10014, 00000, "Roll Back to Save Point" // *Cause: // *Action: 10015, 00000, "Undo Segment Recovery" // *Cause: // *Action: 10016, 00000, "Undo Segment extend" // *Cause: // *Action: 10017, 00000, "Undo Segment Wrap" // *Cause: // *Action: 10018, 00000, "Data Segment Create" // *Cause: // *Action: 10019, 00000, "Data Segment Recovery" // *Cause: // *Action: 10020, 00000, "partial link restored to linked list (KSG)" // *Cause: // *Action: 10021, 00000, "latch cleanup for state objects (KSS)" // *Cause: // *Action: 10022, 00000, "trace ktsgsp" // *Cause: // *Action: 10023, 00000, "Create Save Undo Segment" // *Cause: // *Action: 10024, 00000, "Write to Save Undo" // *Cause: // *Action: 10025, 00000, "Extend Save Undo Segment" // *Cause: // *Action: 10026, 00000, "Apply Save Undo" // *Cause: // *Action: 10027, 00000, "latch cleanup for enqueue locks (KSQ)" // *Cause: // *Action: 10028, 00000, "latch cleanup for enqueue resources (KSQ)" // *Cause: // *Action: 10029, 00000, "session logon (KSU)" // *Cause: // *Action: 10030, 00000, "session logoff (KSU)" // *Cause: // *Action: 10031, 00000, "sort debug event (S*)" // *Cause: // *Action: 10032, 00000, "sort statistics (SOR*)" // *Cause: // *Action: 10033, 00000, "sort run information (SRD*/SRS*)" // *Cause: // *Action: /10034, 00000, "access path analysis (APA*)" // *Cause: // *Action: 10035, 00000, "parse SQL statement (OPIPRS)" // *Cause: // *Action: // Level 1+ Print out user SQL statements // Level >3 Print out recursive SQL // Level >5 Print out row cache cached cursor stats 10036, 00000, "create remote row source (QKANET)" // *Cause: // *Action: 10037, 00000, "allocate remote row source (QKARWS)" // *Cause: // *Action: 10038, 00000, "dump row source tree (QBADRV)" // *Cause: // *Action: 10039, 00000, "type checking (OPITCA)" // *Cause: // *Action: 10040, 00000, "dirty cache list" // *Cause: // *Action: 10041, 00000, "dump undo records skipped" // *Cause: // *Action: 10042, 00000, "trap error during undo application" // *Cause: // *Action: 10043, 00000, "check consistency of owner/waiter/converter lists in KSQ" // *Cause: // *Action: 10044, 00000, "free list undo operations" // *Cause: // *Action: 10045, 00000, "free list update operations - ktsrsp, ktsunl" // *Cause: // *Action: 10046, 00000, "enable SQL statement timing" // *Cause: // *Action: 10047, 00000, "trace switching of sessions" // *Cause: // *Action: 10048, 00000, "Undo segment shrink" // *Cause: // *Action: 10049, 00000, "protect library cache memory heaps" // *Cause: // *Action: Use the OS memory protection (if available) to protect library // cache memory heaps that are pinned. 10050, 00000, "sniper trace" // *Cause: // *Action: 10051, 00000, "trace OPI calls" // *Cause: // *Action: 10052, 00000, "don't clean up obj$" // *Cause: // *Action: 10053, 00000, "CBO Enable optimizer trace" // *Cause: // *Action: 10054, 00000, "trace UNDO handling in MLS" // *Cause: // *Action: 10055, 00000, "trace UNDO handing" // *Cause: // *Action: 10056, 00000, "dump analyze stats (kdg)" // *Cause: // *Action: 10057, 00000, "suppress file names in error messages" // *Cause: // *Action: 10058, 00000, "use table scan cost in tab$.spare1" // *Cause: // *Action: 10059, 00000, "simulate error in logfile create/clear" // *Cause: // *Action: 10060, 00000, "CBO Enable predicate dump" // *Cause: // *Action: 10061, 00000, "disable SMON from cleaning temp segment" // *Cause: // *Action: 10062, 00000, "disable usage of OS Roles in osds" // *Cause: // *Action: 10063, 00000, "disable usage of DBA and OPER privileges in osds" // *Cause: // *Action: 10064, 00000, "thread enable debug crash level %s, thread %s" // *Cause: // *Action: level 1 - after new current log header written // level 2 - after current log committed // level 3 - after redo generation complete 10065, 00000, "limit library cache dump information for state object dump" // *Cause: // *Action: level 1 - minimal (only the address of state objects) // level 2 - little more (no object details) // level 3 - normal 10066, 00000, "simulate failure to verify file" // *Cause: // *Action: level is file number to fail verification 10067, 00000, "force redo log checksum errors - block number" // *Cause: // *Action: level is block number to corrupt 10068, 00000, "force redo log checksum errors - file number" // *Cause: // *Action: level is file number to corrupt 10069, 00000, "Trusted Oracle test event" // *Cause: // *Action: Should never be enabled by customers. Used to prevent diffs in // regression testing by making Trusted behave like Oracle in // specific events. // level > 1 - handle 254 column tables without error // level = 20 - implicitly include ROWLABEL in views 10070, 00000, "force datafile checksum errors - block number" // *Cause: // *Action: level is block number to corrupt 10071, 00000, "force datafile checksum errors - file number" // *Cause: // *Action: level is file number to corrupt 10072, 00000, "protect latch recovery memory" // *Cause: // *Action: 10073, 00000, "have PMON dump info before latch cleanup" // *Cause: // *Action: 10074, 00000, "default trace function mask for kst" // *Cause: // *Action: 10075, 00000, "CBO Disable outer-join to regular join conversion" // *Cause: // *Action: 10076, 00000, "CBO Enable cartesian product join costing" // *Cause: // *Action: 10077, 00000, "CBO Disable view-merging optimization for outer-joins" // *Cause: // *Action: 10078, 00000, "CBO Disable constant predicate elimination optimization" // *Cause: // *Action: / 10079, 00000, "trace data sent/received via SQL*Net" // *Cause: // *Action: level 1 - trace network ops to/from client // level 2 - in addition to level 1, dump data // level 4 - trace network ops to/from dblink // level 8 - in addition to level 4, dump data / 10080, 00000, "dump a block on a segment list which cannot be exchanged" // *Cause: // *Action: / At level > 1, dump the block / At level > 5, dump the stack / At level > 10, unlink the block 10081, 00000, "segment High Water Mark has been advanced" // *Cause: // *Action: 10082, 00000, "free list head block is the same as the last block" // *Cause: // *Action: / At level > 1, dump the block / At level > 5, dump the stack 10083, 00000, "a brand new block has been requested from space management" // *Cause: // *Action: 10084, 00000, "free list becomes empty" // *Cause: // *Action: 10085, 00000, "free lists have been merged" // *Cause: // *Action: 10086, 00000, "CBO Enable error if kko and qka disagree on oby sort" // *Cause: // *Action: 10087, 00000, "disable repair of media corrupt data blocks" // *Cause: // *Action: 10088, 00000, "CBO Disable new NOT IN optimization" // *Cause: // *Action: 10089, 00000, "CBO Disable index sorting" // *Cause: // *Action: 10090, 00000, "invoke other events before crash recovery" // *Cause: // *Action: 10091, 00000, "CBO Disable constant predicate merging" // *Cause: // *Action: 10092, 00000, "CBO Disable hash join" // *Cause: // *Action: 10093, 00000, "CBO Enable force hash joins" // *Cause: // *Action: 10094, 00000, "before resizing a data file" // *Document: NO // *Cause: // *Action: 10095, 00000, "dump debugger commands to trace file" // *Cause: // *Action: 10096, 00000, "after the cross instance call when resizing a data file" // *Document: NO // *Cause: // *Action: 10097, 00000, "after generating redo when resizing a data file" // *Document: NO // *Cause: // *Action: 10098, 00000, "after the OS has increased the size of a data file" // *Document: NO // *Cause: // *Action: 10099, 00000, "after updating the file header with the new file size" // *Document: NO // *Cause: // *Action: 10100, 00000, "after the OS has decreased the size of a data file" // *Document: NO // *Cause: // *Action: 10101, 00000, "atomic redo write recovery" // *Cause: // *Action: 10102, 00000, "switch off anti-joins" // *Cause: // *Action: 10103, 00000, "CBO Disable hash join swapping" // *Cause: // *Action: 10104, 00000, "dump hash join statistics to trace file" // *Cause: // *Action: 10105, 00000, "CBO Enable constant pred trans and MPs w WHERE-clause" // *Cause: // *Action: 10106, 00000, "CBO Disable evaluating correlation pred last for NOT IN" // *Cause: // *Action: 10107, 00000, "CBO Always use bitmap index" // *Cause: // *Action: 10108, 00000, "CBO Don't use bitmap index" // *Cause: // *Action: 10109, 00000, "CBO Disable move of negated predicates" // *Cause: // *Action: 10110, 00000, "CBO Try index rowid range scans" // *Cause: // *Action: 10111, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10112, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10113, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10114, 00000, "Bitmap index creation switch" // *Cause: // *Action: 10115, 00000, "CBO Bitmap optimization use maximal expression" // *Cause: // *Action: 10116, 00000, "CBO Bitmap optimization switch" // *Cause: // *Action: 10117, 00000, "CBO Disable new parallel cost model " // *Cause: // *Action: 10118, 00000, "CBO Enable hash join costing " // *Cause: // *Action: 10119, 00000, "QKA Disable GBY sort elimination" // *Cause: // *Action: 10120, 00000, "generate relative file # different from absolute" // *Cause: // *Action: 10121, 00000, "CBO Don't sort bitmap chains" // *Cause: // *Action: 10122, 00000, "Disable transformation of count(col) to count(*)" // *Cause: // *Action: 10123, 00000, "QKA Disable Bitmap And-EQuals" // *Cause: // *Action: 10124, 00000, "Force creation of segmented arrays by kscsAllocate" // *Cause: // *Action: 10125, 00000, "Disable remote sort elimination" // *Cause: // *Action: 10126, 00000, "Debug oracle java xa" // *Cause: // *Action: 10127, 00000, "Disable remote query block operation" // *Cause: // *Action: 10128, 00000, "Dump Partition Pruning Information" // *Cause: // *Action: set this event only under the supervision of Oracle development // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 dump pruning decriptor for each partitioned object // 0x0002 dump partition iterators // 0x0004 dump optimizer decisions about partition-wise join // 0x0008 dump rowid range scan pruning information 10129, 00000, "Alter histogram lookup for remote queries" // *Cause: // *Action: 10130, 00000, "sort disable readaheads" // *Cause: // *Action: 10131, 00000, "use v$sql_plan code path for explain plan" // *Cause: // *Action: set this event only under the supervision of Oracle development 10132, 00000, "dump plan after compilation" // *Cause: // *Action: set this event only under the supervision of Oracle development 10133, 00000, "testing for SQL Memory Management" // *Cause: // *Action: never set this event // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 do not unregister work areas at instance level 10134, 00000, "tracing for SQL Memory Management for session" // *Cause: // *Action: never set this event // // This event can be turned on globally by seting trace name sqlmem_tracing // with the same set of levels with bit one set to 1 // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 Not used (used for global setting) // 0x0002 IMM level register/unregister 10135, 00000, "CBO do not count 0 rows partitions" // *Cause: // *Action: 10136, 00000, "CBO turn off fix for bug 1089848" // *Cause: // *Action: 10137, 00000, "CBO turn off fix for bug 1344111" // *Cause: // *Action: 10138, 00000, "CBO turn off fix for bug 1577003" // *Cause: // *Action: 10139, 00000, "CBO turn off fix for bug 1386119" // *Cause: // *Action: 10140, 00000, "CBO turn off fix for bug 1332980" // *Cause: // *Action: 10141, 00000, "CBO disable additional keys for inlist in bitmap optimization" // *Cause: // *Action: 10142, 00000, "CBO enable dynamic selectivity estimation" // *Cause: // *Action: 10143, 00000, "CBO force dynamic selectivity estimation (if enabled)" // *Cause: // *Action: 10145, 00000, "test auditing network errors" // *Cause: // *Action: 10146, 00000, "enable Oracle TRACE collection" // *Cause: // *Action: 10147, 00000, "enable join push through UNION view" // *Cause: // *Action: 10148, 00000, "Use pre-7.3.3 random generator" // *Cause: // *Action: 10149, 00000, "allow the creation of constraints with illegal date constants" // *Cause: // *Action: 10150, 00000, "import exceptions" // *Cause: // *Action: This should never be set by users. It is used by import to // allow certain commands to succeed, when for normal users they // would fail. An example is to allow grants on invalid views. 10151, 00000, "Force duplicate dependency removal" // *Cause: // *Action: Setting this to level 1 will force the removal of duplicate // dependencies of cursors as stored in the library cache. 10152, 00000, "CBO don't consider function costs in plans" // *Cause: // *Action: 10153, 00000, "Switch to use public synonym if private one does not translate" // *Cause: // *Action: 10154, 00000, "Switch to disallow synonyms in DDL statements" // *Cause: // *Action: 10155, 00000, "CBO disable generation of transitive OR-chains" // *Cause: // *Action: 10156, 00000, "CBO disable index fast full scan" // *Cause: // *Action: 10157, 00000, "CBO disable index access path for in-list" // *Cause: // *Action: 10158, 00000, "CBO preserve predicate order in post-filters" // *Cause: // *Action: 10159, 00000, "CBO disable order-by sort pushdown into domain indexes" // *Cause: // *Action: 10160, 00000, "CBO disable use of join index" // *Cause: // *Action: 10161, 00000, "CBO recursive semi-join on/off-switch" // *Cause: // *Action: 10162, 00000, "CBO join-back elimination on/off-switch" // *Cause: // *Action: 10163, 00000, "CBO join-back elimination on/off-switch" // *Cause: // *Action: 10164, 00000, "CBO disable subquery-adjusted cardinality fix" // *Cause: // *Action: 10165, 00000, "mark session to be aborted during shutdown normal" // *Cause: // *Action: Turn on this event in a session to mark the session as // abortable so that it can be killed during a shutdown normal. // It is provided for the Oracle Enterprise Manager. 10166, 00000, "trace long operation statistics updates" // *Cause: // *Action: 10167, 00000, "CBO use old index MIN/MAX optimization" // *Cause: // *Action: 10168, 00000, "CBO disable single-table predicate predicate generation" // *Cause: // *Action: 10169, 00000, "CBO disable histograms for multi partitions" // *Cause: // *Action: 10170, 00000, "CBO use old bitmap costing" // *Cause: // *Action: 10171, 00000, "CBO disable transitive join predicates" // *Cause: // *Action: 10172, 00000, "CBO force hash join back" // *Cause: // *Action: 10173, 00000, "CBO no constraint-based join-back elimination" // *Cause: // *Action: 10174, 00000, "view join-back elimination switch" // *Cause: // *Action: 10175, 00000, "CBO star transformation switch" // *Cause: // *Action: 10176, 00000, "CBO colocated join switch" // *Cause: // *Action: 10177, 00000, "CBO colocated join switch" // *Cause: // *Action: 10178, 00000, "CBO turn off hash cluster filtering through memcmp" // *Cause: // *Action: 10179, 00000, "CBO turn off transitive predicate replacement" // *Cause: // *Action: 10180, 00000, "temp table transformation print error messages" // *Cause: // *Action: 10181, 00000, "CBO disable multi-column in-list processing" // *Cause: // *Action: 10182, 00000, "CBO disable generation of implied predicates" // *Cause: // *Action: 10183, 00000, "CBO disable cost rounding" // *Cause: // *Action: 10184, 00000, "CBO disable OR-exp if long inlist on bitmap column" // *Cause: // *Action: 10185, 00000, "CBO force index joins" // *Cause: // *Action: 10186, 00000, "CBO disable index join" // *Cause: // *Action: 10187, 00000, "CBO additional index join switch" // *Cause: // *Action: 10188, 00000, "CBO additional index join switch" // *Cause: // *Action: 10189, 00000, "CBO turn off FFS null fix" // *Cause: // *Action: 10190, 00000, "Analyze use old frequency histogram collection and density" // *Cause: // *Action: 10191, 00000, "Avoid conversion of in-lists back to OR-expanded form" // *Cause: // *Action: 10192, 00000, "nopushdown when number of groups exceed number of rows" // *Cause: // *Action: 10193, 00000, "Force repeatable sampling with specified seed" // *Cause: // *Action: 10194, 00000, "CBO disable new LIKE selectivity heuristic" // *Cause: // *Action: 10195, 00000, "CBO don't use check constraints for transitive predicates" // *Cause: // *Action: 10196, 00000, "CBO disable index skip scan" // *Cause: // *Action: 10197, 00000, "CBO force index skip scan" // *Cause: // *Action: 10198, 00000, "check undo record" // *Cause: for Oracle internal event tracing only // *Action: do NOT set this event for customers' database 10199, 00000, "set parameter in session" // *Cause: // *Action: 10200, 00000, "consistent read buffer status" // *Cause: // *Action: 10201, 00000, "consistent read undo application" // *Cause: // *Action: 10202, 00000, "consistent read block header" // *Cause: // *Action: 10203, 00000, "block cleanout" // *Cause: // *Action: 10204, 00000, "signal recursive extend" // *Cause: // *Action: 10205, 00000, "row cache debugging" // *Cause: // *Action: / At level 1, KQR will dump out latch clean-up debugging traces. / At level 2, KQR will dump out bootstrap debugging traces. / At level 3, KQR will invalidate, remove from the cache and put 0xff's / in row cache objects that are not currently locked. 10206, 00000, "transaction table consistent read" // *Cause: // *Action: 10207, 00000, "consistent read transactions' status report" // *Cause: // *Action: 10208, 00000, "consistent read loop check" // *Cause: // *Action: 10209, 00000, "enable simulated error on controlfile" // *Cause: // *Action: / Enables event 10214 to signal an error for a specific file. Level / is the number of the file to enable them for (file number order from / INIT.ORA file). A level greater than the maximum controlfile multiplexing / factor will signal error for all files. 10210, 00000, "check data block integrity" // *Cause: // *Action: 10211, 00000, "check index block integrity" // *Cause: // *Action: 10212, 00000, "check cluster integrity" // *Cause: // *Action: 10213, 00000, "crash after controlfile write" // *Cause: // *Action: 10214, 00000, "simulate write errors on controlfile" // *Cause: // *Action: / A level of 1-9 simulates write errors on physical blocks 1-9. / If level >= 10 every controlfile write will force an error. 10215, 00000, "simulate read errors on controlfile" // *Cause: // *Action: / For errors 10213,10214, and 10215 / level 1 is for header / level 2 is for shared info / level >2 is any other block / No error 10214 will be simulated unless event 10209 is also set to enable / error simulation on that file 10216, 00000, "dump controlfile header" // *Cause: // *Action: 10217, 00000, "debug sequence numbers" // *Cause: // *Action: 10218, 00000, "dump uba of applied undo" // *Cause: // *Action: 10219, 00000, "monitor multi-pass row locking" // *Cause: // *Action: 10220, 00000, "show updates to the transaction table" // *Cause: // *Action: 10221, 00000, "show changes done with undo" // *Cause: // *Action: 10222, 00000, "row cache" // *Cause: // *Action: 10223, 00000, "transaction layer - turn on verification codes" // *Cause: // *Action: 10224, 00000, "index block split/delete trace" // *Cause: // *Action: 10225, 00000, "free/used extent row cache" // *Cause: // *Action: 10226, 00000, "trace CR applications of undo for data operations" // *Cause: // *Action: 10227, 00000, "verify (multi-piece) row structure" // *Cause: // *Action: 10228, 00000, "trace application of redo by kcocbk" // *Cause: // *Action: 10229, 00000, "simulate I/O error against datafiles" // *Cause: // *Action: 10230, 00000, "check redo generation by copying before applying" // *Cause: // *Action: 10231, 00000, "skip corrupted blocks on _table_scans_" // *Cause: // *Action: such blocks are skipped in table scans, and listed in trace files 10232, 00000, "dump corrupted blocks symbolically when kcbgotten" // *Cause: // *Action: puts corrupted block in trace file 10233, 00000, "skip corrupted blocks on index operations" // *Cause: // *Action: skip corrupted data and/or index blocks during index scans. // information is logged to a trace file. 10234, 00000, "trigger event after calling kcrapc to do redo N times" // *Cause: // *Action: creates a file named 'crash' 10235, 00000, "check memory manager internal structures" // *Cause: // *Action: 10236, 00000, "library cache manager" // *Cause: // *Action: 10237, 00000, "simulate ^C (for testing purposes)" // *Cause: // *Action: 10238, 00000, "instantiation manager" // *Cause: // *Action: 10239, 00000, "multi-instance library cache manager" // *Cause: // *Action: 10240, 00000, "dump dba's of blocks that we wait for" // *Cause: // *Action: 10241, 00000, "remote SQL execution tracing/validation" // *Cause: // *Action: // Level > 0 dump SQL generated for remote execution (OPIX) // Level > 1 validate RPCs in SELECT statements 10242, 00000, "suppress OER 2063 (for testing distrib w/o different error log)" // *Cause: // *Action: 10243, 00000, "simulated error for test %s of K2GTAB latch cleanup" // *Cause: levels 1..6 for insert, 7..11 for delete // *Action: 10244, 00000, "make tranids in error msgs print as 0.0.0 (for testing)" // *Cause: also makes "alter system enable distributed recovery" synchronous // *Action: 10245, 00000, "simulate lock conflict error for testing PMON" // *Cause: // *Action: 10246, 00000, "print trace of PMON actions to trace file" // *Cause: // *Action: 10247, 00000, "Turn on scgcmn tracing. (VMS ONLY)" // *Cause: // *Action: / / LEVEL ACTION /--------------------------------------------------------------------------- / >= 1 Print lock name, action, mode, comp ast, bast, timeout, val? / >= 2 print Success code of request (NORMAL, SYNCH, or NOTQUEUED) / >= 3 print Value block / >= 5 Print delta CPU and elapsed times. / >= 100 stack dump at level 100-. 10248, 00000, "turn on tracing for dispatchers" // *Cause: // *Action: 10249, 00000, "turn on tracing for multi-stated servers" // *Cause: // *Action: 10250, 00000, "Trace all allocate and free calls to the topmost SGA heap" // *Cause: // *Action: 10251, 00000, "check consistency of transaction table and undo block" // MERGE: 10235 RENUMBERED TO 10251 // *Cause: // *Action: 10252, 00000, "simulate write error to data file header" // MERGE: 10238 RENUMBERED TO 10252 // *Cause: // *Action: 10253, 00000, "simulate write error to redo log" // MERGE: 10239 RENUMBERED TO 10253 // *Cause: // *Action: 10254, 00000, "trace cross-instance calls" // *Cause: // *Action: 10255, 00000, "pl/sql parse checking" // *Cause: // *Action: sends all dml statements to pl/sql for parse and semantic check 10256, 00000, "turn off shared server load balancing" // *Cause: // *Action: 10257, 00000, "trace shared server load balancing" // *Cause: // *Action: 10258, 00000, "force shared servers to be chosen round-robin" // *Cause: // *Action: 10259, 00000, "get error message text from remote using explicit call" // *Cause: for npigem coverage testing (normally called only for V5 remote) // *Action: 10260, 00000, "Trace calls to SMPRSET (VMS ONLY)" // *Cause: Allow callers to find their own bugs in memory protection // *Action: // Level >=1 (101) : ini,quit (set) do simple trace // Level >=5 (105) : ini,quit (set) dump arglist // Level >=10 (110) : ini,quit (set) dump call stack 10261, 00000, "Limit the size of the PGA heap" // *Cause: the limit is one kilobyte times the level of the event. If the // pga grows bigger than this signal an internal error. // *Action: 10262, 00000, "Don't check for memory leaks" // *Cause: Setting this event to level one causes memory leak checking to // be disabled. Setting this event to any other non-zero number // allows that number to be used as a threshold value when checking // for memory leaks in the PGA, SGA, and UGA heaps. // *Action: 10263, 00000, "Don't free empty PGA heap extents" // *Cause: This is useful for debugging since watchpoints are lost on free // *Action: 10264, 00000, "Collect statistics on context area usage (x$ksmcx)" // *Cause: // *Action: 10265, 00000, "Keep random system generated output out of error messages" // *Cause: so test system files don't diff // *Action: 10266, 00000, "Trace OSD stack usage" // *Cause: Porters should implement this to help them debug // their stack implementations. It should be used in at least // smcstk(). // *Action: 10267, 00000, "Inhibit KSEDMP for testing" // *Cause: Some tests may generate internal or fatal errors on purpose. / This event can limit the size of tracefile produced for such / tests. // *Action: LEVEL used by KSEDMP is one less than level of this event. / 10268, 00000, "Don't do forward coalesce when deleting extents" // *Cause: setting this event keeps kts from coalescing forward at each // extent when dropping a temp segment. // *Action: 10269, 00000, "Don't do coalesces of free space in SMON" // *Cause: setting this event prevents SMON from doing free space coalesces 10270, 00000, "Debug shared cursors" // *Cause: Enables debugging code in shared cursor management modules // *Action: 10271, 00000, "distributed transaction after COLLECT" // *Cause: // *Action: 10272, 00000, "distributed transaction before PREPARE" // *Cause: // *Action: 10273, 00000, "distributed transaction after PREPARE" // *Cause: // *Action: 10274, 00000, "distributed transaction before COMMIT" // *Cause: // *Action: 10275, 00000, "distributed transaction after COMMIT" // *Cause: // *Action: 10276, 00000, "distributed transaction before FORGET" // *Cause: // *Action: 10277, 00000, "Cursor sharing (or not) related event (used for testing)" // *Cause: // *Action: 10278, 00000, "Internal testing" // *Cause: // *Action: 10279, 00000, "Simulate block corruption in kdb4chk" // *Cause: // *Action: 10280, 00000, "Internal testing - segmentation fault during crash recovery" // *Cause: // *Action: 10281, 00000, "maximum time to wait for process creation" // *Cause: used to override the default SPMXWAIT, level = timeout in sec. // *Action: 10282, 00000, "Inhibit signalling of other backgrounds when one dies" // *Cause: Used in KSB // *Action: 10283, 00000, "simulate asynch I/O never completing" // *Cause: Used in KCF, level = absolute file number // *Action: 10284, 00000, "simulate zero/infinite asynch I/O buffering" // *Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green) // *Action: 10285, 00000, "Simulate controlfile header corruption" // *Cause: // *Action: If set, will cause controlfile header verification to fail 10286, 00000, "Simulate controlfile open error" // *Cause: // *Action: If set, will cause the next controlfile open to have an error 10287, 00000, "Simulate archiver error" // *Cause: // *Action: If set, next archive log will generate error 10288, 00000, "Do not check block type in ktrget" // *Cause: // *Action: If set, don't do type check in ktrget. This is a work-around // for databases that have 0 as block type in some data blocks. 10289, 00000, "Do block dumps to trace file in hex rather than fromatted" // *Cause: // *Action: If set, don't do formatted block dumps. This is a work-around // for block dump routines that accvio when given badly corrupted // blocks. It may also be useful for cases where the type is wrong. 10290, 00000, "kdnchk - checkvalid event - not for general purpose use." // *Cause: // *Action: Internal Event - Should not be set unless directed by RDBMS DEV 10291, 00000, "die in tbsdrv to test controlfile undo" // *Cause: // *Action: If this event is set, error OERI(10291) is signalled when // issueing tablespace commands. The controlfile undo should be // applied returning the controlfile to its previous state. 10292, 0000, "dump uet entries on a 1561 from dtsdrv" // *Cause: // *Action: dumps the uet$ entries blocking the drop on a 1561 to tracefile 10293, 0000, "dump debugging information when doing block recovery" // *Cause: // *Action: If this event is set and a block recovery done, then the // RBA range is printed, along with any chang vectors applied. 10294, 0000, "enable PERSISTENT DLM operations on non-compliant systems" // *Cause: // *Action: Allow specification of buffer cache locking that requires // persistant lock resources and recovery operations even though // the lock manager does not support it. ENABLE THIS EVENT FOR // TESTING ONLY. 10295, 00000, "die after file header update durning cf xact" // *Cause: // *Action: If this event is set then some file header updates will // be followed by an error 10295 to abort the command before // the controlfile xact commits. 10296, 00000, "disable ORA-379" // *Cause: // *Action: If this event is set then we will not signal ORA-379 for // buffer cache deadlocks when all buffers in the cache // are pinned. 10297, 00000, "customize dictionary object number cache" // *Cause: // *Action: If this event is set at level 0, or not set then caching // of object numbers will be turned on, using the default size. // If this event is set at level 1 then caching of object // numbers will be turned off. // If this event is set at a level other than 1, then the // level will be used as the (fixed) size of the cache. 10298, 00000, "ksfd i/o tracing" // *Cause: // *Action: If this event is set then ksfd module generates tracing // for each i/o request 10299, 00000, "Trace prefetch tracking decisions made by CKPT" // *Cause: // *Action: If this event is set then the prefetch tracking decisions // made by the CKPT process are traced. The trace output is // written to that process' trace file. 10300, 00000, "disable undo compatibility check at database open" // *Cause: // *Action: If this event is enabled it will be possible to upgrade to a new // software version with an incompatible log format when there may be // undo that needs to be applied. This is intended for upgrades // from releases before 6.0.34.3 when there are tablespaces that are // offline cleanly with no save undo. Those releases did not check the // deferred rollback segments, it was assumed that there was some // undo in the segments and every offline tablespace had one. This // event must only be set if you are ABSOLUTELY SURE the last // shutdown was a shutdown normal with no errors (do it again to be // sure), and that there is no save undo for any of the offline // tablespaces (dump the save undo segment header). 10301, 0000, "Enable LCK timeout table consistency check" // *Cause: // *Action: / / 10302 - 10318 Reserved for internal triggers / 10302, 00000, "trace create or drop internal trigger" // *Document: NO // *Cause: // *Action: 10303, 00000, "trace loading of library cache for internal triggers" // *Document: NO // *Cause: // *Action: 10304, 00000, "trace replication trigger" // *Document: NO // *Cause: // *Action: 10305, 00000, "trace updatable materialized view trigger" // *Document: NO // *Cause: // *Action: 10306, 00000, "trace materialized view log trigger" // *Document: NO // *Cause: // *Action: 10307, 00000, "trace RepCat execution" // *Document: NO // *Cause: // *Action: 10308, 00000, "replication testing event" // *Document: NO // *Cause: // *Action: 10309, 00000, "Trigger Debug event" // *Document: NO // *Cause: // *Action: // *Comment: This event replaces the earlier event number 10250 // which had multiple definitions 10310, 00000, "trace synchronous change table trigger" // *Document: NO // *Cause: // *Action: 10311, 00000, "Disable Flashback Table Timestamp checking" // *Document: NO // *Cause: // *Action: 10312, 00000, "Allow disable to log rows into the mapping table" // *Document: NO // *Cause: // *Action: 10319, 00000, "Trace PGA statistics maintenance" // *Cause: // *Action: set this event only under the supervision of Oracle development // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 dump message in trace file when PGA stats are diverging // 0x0002 trace top-level PGA allocation and deallocation // 0x0004 always check if full/incremental stats are in sync // 0x0080 full recompute every 30 seconds instead of 10 minutes // / 10320, 0000, "Enable data layer (kdtgrs) tracing of space management calls" // *Cause: // *Action: / 10321, 0000, "Datafile header verification debug failure." // *Document: NO // *Cause: // *Action: For testing purposes only. Simulates a datafile header // verification error. / 10323, 0000, "before committing an add datafile command" // *Cause: // *Action: 10324, 0000, "Enable better checking of redo logs errors" // *Cause: // *Action: Raises internal errors when there are redo log errors // *Comment: Raises internal errors when there are redo log errors / / 10325 - 10335 reserved for recovery testing / 10325, 0000, "Trace control file record section expand and shrink operations" // *Document: NO // *Cause: // *Action: trace control file record section expand and shrink operations to // the alert file // 10326, 00000, "clear logfile debug crash at %s, log %s" // *Document: NO // *Cause: // *Action: level 1 - after prepare, before clearing the log members // level 2 - after clearing the log members, before final cf xaction // level 3 - just before clearing member 1 // level 4 - just before clearing member 2 10327, 00000, "simulate ORA-00235 error for testing" // *Document: NO // *Cause: // *Action: // 10328, 00000, "disable first-to-mount split-brain error, for testing" // *Document: NO // *Cause: // *Action: for testing only. // 10329, 00000, "simulate lost write, test detection by two-pass recovery" // *Document: NO // *Cause: // *Action: for testing only. // 10330, 00000, "clear MTTR statistics in checkpoint progress record" // *Document: NO // *Cause: // *Action: clear MTTR statistics in this thread // 10331, 00000, "simulate resilvering during recovery" // *Document: NO // *Cause: // *Action: for testing only. // 10332, 00000, "force ALTER SYSTEM QUIESCE RESTRICTED command to fail" // *Document: NO // *Cause: // *Action: for testing only. // 10336, 00000, "Do remote object transfer using remote SQL" // *Cause: // *Action: // 10337, 00000, "enable padding owner name in slave sql" //*Document: NO //*Cause: owner name is not padded by default in slave sql //*Action: pad owner name during generation of slave sql //*Comment: applicable only for explain plan queries(for testing purposes) / 10340, 00000, "Buffer queues sanity check for corrupted buffers" //*Document: NO //*Cause: //*Action: Check all buffer queues for corrupted buffer every 5 minutes // / reserve events 10341 - 10350 for checkpoints / 10341, 00000, "Simulate out of PGA memory in DBWR during object reuse" // *Cause: // *Action: checks that DBWR can still perform invalidatino // *Comment: only used during testing / 10342, 00000, "Raise unknown exception in ACQ_ADD when checkpointing" // *Cause: // *Action: should cause process to dump trace file and die // *Comment: This event is obsoleted, and can be reused for another test. / 10343, 00000, "Raise an out of memory exception-OER 4031 in ACQ_ADD" // *Cause: // *Action: For Backgrounds, try to handle checkpoint using reserved entries // *Comment: Only enabled during testing / 10344, 00000, "Simulate kghxal returning 0 in ACQ_ADD but no exception" // *Cause: // *Action: For Backgrounds, try to handle checkpoint using reserved entries // *Comment: This event is obsoleted, and can be reused for another test. / 10345, 00000, "validate queue when linking or unlinking a buffer" // *Cause: // *Action: checks low RBA ordering of queue associated with latch // *Comment: Raises an error if low RBA ordering on queue is wrong / 10346, 00000, "check that all buffers for checkpoint have been written" // *Cause: // *Action: Scans the cache to see that all candidate buffers are written // *Comment: Usually only enabled for TESTING since it involves a cache scan / 10347, 00000, "dump active checkpoint entries and checkpoint buffers" // *Cause: // *Action: Prints the checkpoint queue and buffers to the trace file // *Comment: Usually only enabled for TESTING and code coverage / 10348, 00000, "test abnormal termination of process initiating file checkpoint" // *Cause: // *Action: Causes abnormal termination of process starting a file checkpoint // *Comment: Only enabled for TESTING and code coverage / 10349, 00000, "do not allow ckpt to complete" // *Cause: // *Action: disables checkpoint completion // *Comment: only enabled for TESTING / 10350, 00000, "Simulate more than one object & tsn id in object reuse" // *Cause: // *Action: checks that DBWR can service multiple object id's in reuse" // *Comment: only used during testing / / reserve events 10351-10359 for direct asynchronous read path / 10351, 00000, "size of slots" // *Cause: // *Action: sets the size of slots to use // *Comment: a slot is a unit of I/O and this factor controls the size // *Comment: of the IO. / 10352, 00000, "report direct path statistics" // *Cause: // *Action: turns on direct path statistics // *Comment: reports statistics for direct path / 10353, 00000, "number of slots" // *Cause: // *Action: sets a given number of slots to use // *Comment: a slot is a unit of I/O and this factor controls the number // *Comment: of outstanding I/Os. / 10354, 00000, "turn on direct read path for parallel query" // *Cause: // *Action: enable direct read for parallel query / 10355, 00000, "turn on direct read path for scans" // *Cause: // *Action: enable direct async read for scans / 10356, 00000, "turn on hint usage for direct read" // *Cause: // *Action: enables using hint for direct async reads / 10357, 00000, "turn on debug information for direct path" // *Cause: // *Action: turn on debug information for direct path / 10359, 00000, "turn off updates to control file for direct writes" // *Cause: // *Action: Control files won't get updated for direct writes for LOBs // when NOCACHE NOLOGGING is set. The only bad impact that it // can have is that if you are using the recovery manager, // it may affect a warning that says that the user should // back everything up. Now the recovery manager won't know // to tell you that the files that were updated with // unrecoverable events should be backed up. / / reserve events 10360-10364 for debugging DBWR / 10360, 0000, "enable dbwr consistency checking" // *Cause: internal use only // *Action: enables consistency checking of buffers written by // dbwriter and consistency checking of LRU working sets // / / reserve events 10365-10369 for direct asynchronous read path / 10365, 00000, "turn on debug information for adaptive direct reads" // *Cause: // *Action: turn on debug information for adaptive direct reads / / / reserve events for parallel query option. Available range 10370-10374 / 10370, 00000, "parallel query server kill event" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to commit suicide, codes line / 10371, 00000, "disable TQ hint" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: Stops the generation of the TQ hint (for testing purposes) / 10372, 00000, "parallel query server kill event proc" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to commit suicide, codes proc & weapon / 10373, 00000, "parallel query server kill event" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to commit suicide, code count & context / 10374, 00000, "parallel query server interrupt (validate lock value)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to validate its lock value / 10375, 00000, "turn on checks for statistics rollups" // *Cause: // *Action: enables checks for stat rollup in QC // *Comment: verify that the rollup is being done accurately / / 10376, 00000, "turn on table queue statistics" // *Cause: // *Action: enables table queue statistics gathering // *Comment: all instances must be started with this event when used / 10377, 00000, "turn off load balancing" // *Cause: // *Action: turns off default load balancing // *Comment: allocates slaves sequentially from coordinater to (coord - width) / 10378, 00000, "force hard process/range affinity" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only / 10379, 00000, "direct read for rowid range scans (unimplemented)" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only / 10380, 00000, "kxfp latch cleanup testing event" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only--indicates the server to which the latch // cleanup key applies (0 for QC) / 10381, 00000, "kxfp latch cleanup testing event" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing only--the latch cleanup key (the number of the // LCTEST() call on which to kill the process) / 10382, 00000, "parallel query server interrupt (reset)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to clear its buffers and reset itself / 10383, 00000, "auto parallelization testing event" // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: For testing only. Trace level bits can be used in combination: // 1: parallelize every full table scan (kkfd.c) // 2: create every table/cluster parallel (prsc.c) // 4: create every table/cluster cache // 8: create every table/cluster cache partitions (overrides 4) / 10384, 00000, "parallel dataflow scheduler tracing" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: trace level is a bitfield (see kkrp.h) / 10385, 00000, "parallel table scan range sampling method" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level: 0: (default) sample by random rowid // 1: sample by first rows of partition ranges / 10386, 00000, "parallel SQL hash and range statistics" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: print kxfq hash and range statistics / 10387, 00000, "parallel query server interrupt (normal)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group normally / 10388, 00000, "parallel query server interrupt (failure)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group (query // failed) / 10389, 00000, "parallel query server interrupt (cleanup)" // *Cause: internal use only // *Action: this event should never be set externally // *Comment: commands a slave to leave the server group (signaled // by PMON, coordinator died) / 10390, 00000, "Trace parallel query slave execution" // *Cause: // *Action: set this event only under the supervision of Oracle development. // trace level is a bitfield // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 slave-side execution messages // 0x0002 coordinator-side execution messages // 0x0004 slave context state changes // 0x0008 slave rowid range bind variables and xty // // 0x0010 slave fetched rows as enqueued to TQ // 0x0020 coordinator wait reply handling // 0x0040 coordinator wait message buffering // 0x0080 slave dump timing // // 0x0100 coordinator dump timing // 0x0200 slave dump allocation file numbers // 0x0400 terse format for debug dumps // 0x0800 Trace CRI random sampling // // 0x1000 Trace signals // 0x2000 Trace PX granule operations / 10391, 00000, "trace PX granule allocation/assignment" // *Cause: // *Action: set this event only under the supervision of Oracle development // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 dump summary of each object scanned in parallel // 0x0002 full dump of each object except extent map // 0x0004 full dump of each object including extent map // // 0x0010 dump summary of each granule generators // 0x0020 full dump of granule generators except granule instances // 0x0040 full dump of granule generators including granule instances // // 0x0080 dump system info // 0x0100 dump reference object for the query // 0x0200 gives timing in kxfralo // 0x0400 trace affinity module // 0x0800 trace granule allocation during query execution // // 0x1000 trace object flush // 0x2000 internal // *Comment: print details of PQ parallel granule allocation / 10392, 00000, "parallel query debugging bits" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: turn on/off various kxfp features (documentation in kxfp.c) / 10393, 00000, "print parallel query statistics" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: print kxfp statistics after each parallel query / 10394, 00000, "generate a fake load to test adaptive and load balancing" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: generates a fake load for testing purposes / 10395, 00000, "adjust sample size for range table queues" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: use reduced sample size for testing only / 10396, 00000, "circumvent range table queues for queries" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: for testing. uses only hash table queues in queries, with // any output ordering done in the QC. does not avoid range // table queues during index creation. / 10397, 00000, "suppress verbose parallel coordinator error reporting" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: disable the ORA-12801 message when a parallel query // server gets a SQL error, instead report the slave's // actual error as if signaled in the foreground (for // testing, to match sequential log files) / 10398, 00000, "enable timeouts in parallel query threads" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level of this event indicates the number of seconds // before timing out of a kxfpqdeq() call, after which // an internal error will be signaled...for testing so // that test suites don't wedge. / 10399, 00000, "trace buffer allocation" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level indicates verbosity of tracing // Level1: Buffer leak checking // Level2: trace buffer init, chunk alloc, free and recovery // Level3: trace buffer alloc & free / / 10400, 00000, "turn on system state dumps for shutdown debugging" // *Cause: // *Action: Enables debugging code for shutdown problems (e.g., hangs) / 10401, 00000, "turn on IPC (ksxp) debugging" // *Cause: // *Action: Enables debugging code for IPC service layer (ksxp) / 10402, 00000, "turn on IPC (skgxp) debugging" // *Cause: // *Action: Enables debugging code for IPC layer (skgxp) / 10403, 00000, "fake CPU number for default degree of parallelism" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: level of this event indicates the number of CPUs you want to // set to / / reserve events 10404 - 10405 for mirror resilvering testing 10404, 00000, "crash dbwr after write" // *Cause: // *Action: set this event only to test mirror resilvering osds // *Comment: This event causes dbwr to crash after doing a write to // a mirrored datafile. For use in tkbrmrt only. / 10405, 00000, "emulate broken mirrors" // *Cause: // *Action: set this event to cause mirror resilvering on startup // *Comment: This event is set when starting up after a crash caused // by OER(10404). It is used to persuade the recovery layer // that a mirror was broken. / 10406, 00000, "enable datetime TIMESTAMP, INTERVAL datatype creation" // *Cause: // *Action: set this event to enable datetime datatype creation // *Comment: This event is set when the user wants to create // a datetime datatype column. The compatible=8.1.0.0.0 parameter // must also be set. / 10407, 00000, "enable datetime TIME datatype creation" // *Cause: // *Action: set this event to enable datetime datatype creation // *Comment: This event is set when the user wants to create // a datetime datatype column. The compatible=8.1.0.0.0 parameter // must also be set. / 10408, 00000, "disable OLAP builtin window function usage" // *Cause: // *Action: set this event to disable new OLAP builtin window functions // *Comment: This event is set when the user has a name conflict // with one of the OLAP window function names. This setting // disables the builtin functions so that user functions work. / / Events 10410-10412 reserved for KSXP/CGS error simulation 10410, 00000, "trigger simulated communications errors in KSXP" // *Document: NO // *Cause: // *Action: set this event to simulate communications errors to clients // *Comment: This event is set as 0xCIXXNNNN where C is the client id the // the error will be generated to, I is the instance id the error // will be generated for and NNNN is the minimum message sequence // number for instance I. An initial event value of C=0 indicates // dynamic check of event / 10411, 00000, "simulate errors in IMR" // *Document: NO // *Cause: // *Action: set this event to various IMR errors // *Comment: This event is set as 0xEESSAABB where EE is the error type, // SS is the error subtype, and AA and BB are test specific. / 10412, 00000, "trigger simulated errors in CGS/CM interface" // *Document: NO // *Cause: // *Action: set this event to various CGS/CM errors // *Comment: This event is set as 0xEESSAABB where EE is the error type, // SS is the error subtype, and AA and BB are test specific. / / Events 10425-10450 reserved for global enqueue service tracing and debugging 10425, 00000, "enable global enqueue service open event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service open. 10426, 00000, "enable global enqueue service convert event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service convert. 10427, 00000, "enable global enqueue service traffic controller event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service traffic controller. 10428, 00000, "enable tracing of global enqueue service distributed resource" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service distributed resource operations. 10429, 00000, "enable tracing of global enqueue service IPC calls" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service IPC calls. 10430, 00000, "enable tracing of global enqueue service AST calls" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service AST calls. 10431, 00000, "enable verification messages on pi consistency" // *Document: NO // *Cause: // *Action: Send verification messages to check pi consistency 10432, 00000, "enable tracing of global cache service fusion calls" // *Document: NO // *Cause: // *Action: Dump trace for global cache service fusion calls. 10433, 00000, "global enqueue service testing event" // *Document: NO // *Cause: // *Action: // Level: == 6 to return out-of-memory when getting message buffer // Level: == 7 to suspend lmd for a short period of time // Level: == 8 to suspend lms for a short period of time // Level: == 9 to inject out-of-order dlm messages // Level: == 10 to delay direct sends on send proxies and // to force indirect sends on half of the // direct send messages 10434, 00000, "enable tracing of global enqueue service muliple LMS" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service muliple LMS. 10435, 00000, "enable tracing of global enqueue service deadlock detetction" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service deadlock detetction. 10450, 00000, "signal ctrl-c in kdddca (drop column) after n rows" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Set the level number to the number of rows before the error // is signalled. The error will be ORA-1013 (ctrl-c) / 10500, 00000, "turn on traces for SMON" // *Cause: // *Action: // Level: <=5 trace instance recovery // > 5 trace posting of SMON 10501, 00000, "periodically check selected heap" // *Cause: // *Action: // Level: 0x01 PGA // 0x02 SGA // 0x04 UGA // 0x08 current call // 0x10 user call // 0x20 large allocation pool 10510, 00000, "turn off SMON check to offline pending offline rollback segment" // *Cause: // *Action: 10511, 00000, "turn off SMON check to cleanup undo dictionary" // *Cause: // *Action: 10512, 00000, "turn off SMON check to shrink rollback segments" // *Cause: // *Action: 10513, 00000, "turn off wrap source compression" // *Cause: // *Action: Set this event if you do not want source of wrapped PL/SQL // objects to be concatenated and stored multiple lines to a row. // *Comment: This event should be set if you want the source of wrapped // PL/SQL objects to be stored one line per source row. The // new storage method is multiple lines per row, which // improves load and compile performance. 10515, 00000, "turn on event to use physical cleanout" // *Cause: // *Action: 10520, 00000, "recreate package/procedure/view only if definition has changed" // *Cause: // *Action: Set this event only under the supervision of Oracle development // *Comment: Changes behaviour of create or replace package|procedure|view, // comparing the new definition to the old prior to recreating the // object. Creation is skipped if old and new definitions match // (ie. object has not changed). No level number required. 10550, 00000, "signal error during create as select/create index after n rows" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: Set the level number to the number of rows before the error // is signalled. The error will be ORA-1013 (ctrl-c) // / / 10551 -10589 reserved for recoverable media/standby recovery / 10560, 00000, "block type '%s'" // *Cause: Report block type for details of another error. // *Action: See associated error message. 10561, 00000, "block type '%s', data object# %s" // *Cause: Report block type and data object number for details of // another error. // *Action: See associated error message. 10562, 00000, "Error occurred while applying redo to data block (file# %s, block# %s)" // *Cause: See other errors on error stack. // *Action: Investigate why the error occurred and how important is the data // block. Media and standby database recovery usually can continue // if user allows recovery to corrupt this data block. 10563, 00000, "Test recovery had to corrupt data block (file# %s, block# %s) in order to proceed" // *Cause: Test recovery completed. // *Action: No action is needed. Test recovery has ended successfully. // See other messages on error stack for a summary of the result // of the test recovery. 10564, 00000, "tablespace %s" // *Cause: Report tablespace name for details of another error. // *Action: See associated error message. 10565, 00000, "Another test recovery session is active" // *Cause: There can only be one test recovery session at any time. // Another test recovery session is active. // *Action: Wait till the other test recovery session completes. 10566, 00000, "Test recovery has used all the memory it can use" // *Cause: Test recovery tests redo in memory. It can no longer proceed // because it has consumed all the memory it can use. // *Action: No action is needed. Test recovery has ended successfully. // See other messages on error stack for a summary result // of the test recovery. 10567, 00000, "Redo is inconsistent with data block (file# %s, block# %s)" // *Cause: There are two possible causes of this error: (1) A write issued // by Oracle was lost by the underlying OS or storage system. // (2) an Oracle internal error. // *Action: Investigate why the error occurred and how important is the data // block. Media and standby database recovery usually can continue // if user allows recovery to corrupt this data block. 10568, 00000, "Failed to allocate recovery state object: out of SGA memory" // *Cause: out of SGA memory // *Action: Restart the instance. If problem persists, call Oracle support. 10570, 00000, "Test recovery complete" // *Cause: Test recovery completed. // *Action: No action is needed. Test recovery has ended successfully. // See other messages on error stack for a summary result // of the test recovery. 10571, 00000, "Test recovery canceled" // *Cause: User canceled test recovery. // *Action: No action is needed. Test recovery has ended successfully. // See other messages on error stack for a summary of the result // of the test recovery. 10572, 00000, "Test recovery canceled due to errors" // *Cause: See other errors on the error stack. // *Action: See other messages on error stack. It is possible that no // action is needed. See other messages on error stack for a // summary of the result of the test recovery so far. 10573, 00000, "Test recovery tested redo from change %s to %s" // *Cause: This message show the range of test recovery have tested. // *Action: No action is needed. See other messages on error stack. 10574, 00000, "Test recovery did not corrupt any data block" // *Cause: This message summarizes test recovery result. // *Action: No action is needed. See other messages on error stack. 10575, 00000, "Give up restoring recovered datafiles to consistent state: out of memory" // *Cause: There were not enough memory to restore recovered datafiles // to consistent state // *Action: This error is just a warning: You may not be able to open the // database with resetlogs immediately after this error. However, // you may continue media/standby recovery, and that may make the // datafiles recovered consistent again. 10576, 00000, "Give up restoring recovered datafiles to consistent state: some error occurred" // *Cause: See alert file or other errors on the stack for a cause of the // problem. // *Action: This error is just a warning: You may not be able to open the // database with resetlogs immediately after this error. However, // you may continue media/standby recovery, and that may make the // datafiles recovered consistent again. // 10577, 00000, "Can not invoke test recovery for managed standby database recovery" // *Cause: Test recovery option is used for managed standby database recovery. // *Action: Either remove the test recovery option or invoke manual test // standby database recovery. 10578, 00000, "Can not allow corruption for managed standby database recovery" // *Cause: You used the allow corruption option for managed standby database // recovery. // *Action: Either remove the allow corruption option or invoke manual // standby database recovery. 10579, 00000, "Can not modify control file during test recovery" // *Cause: To proceed with recovery, test recovery needs to modify the // control file. But test recovery is not allowed to modify // controlfile. // *Action: No action is needed. Test recovery has ended successfully. // It can only go so far in the redo stream. 10580, 00000, "Can not modify datafile header during test recovery" // *Cause: To proceed with recovery, test recovery needs to modify a // datafile header. But test recovery is not allowed to modify // datafile headers. // *Action: No action is needed. Test recovery has ended successfully. // It can only go so far in the redo stream. 10581, 00000, "Can not modify redo log header during test recovery" // *Cause: To proceed with recovery, test recovery needs to modify a // redo log header. But test recovery is not allowed to modify // redo log headers. // *Action: No action is needed. Test recovery has ended successfully. // It can only go so far in the redo stream. 10582, 00000, "The control file is not a backup control file" // *Cause: User requested backup control file test recovery, but the // control file is not a backup control file. // *Action: Use a backup control file, or do not use USING BACKUP // CONTROLFILE option. 10583, 00000, "Can not recovery file %s renamed as missing during test recovery" // *Cause: One of the files to be recovered is renamed as missing. // *Action: Rename the file to the correct file or offline it. 10584, 00000, "Can not invoke parallel recovery for test recovery" // *Cause: Both test recovery and parallel recovery are requested. // *Action: Drop either one of the two recovery options. 10585, 00000, "Test recovery can not apply redo that may modify control file" // *Cause: Test recovery has encountered a special redo that may modify // control file. // *Action: No action is needed. Test recovery has proceeded successfully // as far as it could from its starting point. 10586, 00000, "Test recovery had to corrupt 1 data block in order to proceed" // *Cause: This message summarizes test recovery result: Oracle may have // to corrupt one block in order to apply the range of redo tested. // *Action: See alert log for details of the problem. 10587, 00000, "Invalid count for ALLOW n CORRUPTION option" // *Cause: The number specified in the ALLOW n CORRUPTION option is too big. // *Action: Use a smaller number. 10588, 00000, "Can only allow 1 corruption for normal media/standby recovery" // *Cause: The number specified in the ALLOW n CORRUPTION option is too big. // *Action: change to allow zero or one corruption. 10589, 00000, "Test recovery had to corrupt %s data blocks in order to proceed" // *Cause: This message summarizes test recovery result: Oracle may have // to corrupt a number of data blocks as specified in the message // in order to apply the range of redo tested. // *Action: See alert log for details of the problems. 10590, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10591, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10592, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10593, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10594, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10595, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10596, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10597, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10598, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development 10599, 00000, "kga (argus debugger) test flags" // *Cause: // *Action: set this event only under the supervision of Oracle development // 10600, 00000, "check cursor frame allocation" // *Cause: // *Action: 10601, 00000, "turn on debugging for cursor_sharing (literal replacement)" // *Cause: // *Action: 10602, 00000, "cause an access violation (for testing purposes)" // *Cause: // *Action: 10603, 00000, "cause an error to occur during truncate (for testing purposes)" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes kdifrb to encounter an error during truncation of a // table with an index. it is for testing purposes only. 10604, 00000, "trace parallel create index" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of parallel create index 10605, 00000, "enable parallel create index by default" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes all create index statement to by default // occur in parallel. it is for testing purposes only. // the level set in the event is the degree of parallelism. // *Comment: enables analysis of parallel create index - query coordinator 10606, 00000, "trace parallel create index" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of parallel create index - kkri slaves 10607, 00000, "trace index rowid partition scan" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of rowid index scan - rix row source, // and puts more trace on errors in range scans 10608, 00000, "trace create bitmap index" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of create bitmap index - kkrb row source 10609, 00000, "trace for array index insertion" // *Cause: // *Action: set this event to turn off the index array operation // *Comment: disable the index array operation 10610, 00000, "trace create index pseudo optimizer" // *Cause: // *Action: set this event only under the supervision of Oracle development 10611, 00000, "causes migration to fail - testing only" // *Cause: // *Action: set this event only under the supervision of Oracle development 10612, 00000, "prints debug information for auto-space managed segments" // *Cause: // *Action: 10613, 00000, "prints debug information for auto-space managed segments" // *Cause: // *Action: 10614, 00000, "Operation not allowed on this segment" // *Cause: This procedure can be used only on segments in // tablespaces with AUTO SEGMENT SPACE MANAGEMENT // *Action: Recheck the segment name and type and re-issue the statement 10615, 00000, "Invalid tablespace type for temporary tablespace" // *Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be // used as a temporary tablespace // *Action: Recheck the tablespace name and re-issue the statement 10616, 00000, "Operation not allowed on this tablespace" // *Cause: Cannot perform the operation on tablespace with AUTO // SEGMENT SPACE MANAGEMENT // *Action: Recheck the tablespace name and re-issue the statement 10617, 00000, "Cannot create rollback segment in this tablespace" // *Cause: Rollback segments cannot be created in tablespaces // with AUTO SEGMENT SPACE MANAGEMENT // *Action: Recheck the tablespace name and re-issue the statement 10618, 00000, "Operation not allowed on this segment" // *Cause: This DBMS_SPACE operation is not permitted on segments in // tablespaces with AUTO SEGMENT SPACE MANAGEMENT // *Action: Recheck the segment name and type and re-issue the statement 10619, 00000, "Avoid assertions when possible" // *Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc) // *Action: Event makes RDBMS skip assertions and patch up datastructures 10620, 00000, "Operation not allowed on this segment" // *Cause: Cannot alter freelist storage parameter for segments in tablespaces // with AUTO SEGMENT SPACE MANAGEMENT // *Action: Recheck the segment name and re-issue the statement 10621, 00000, "data block does not belong to the segment" // *Cause: The specified file number and block number of the data block // does not belong to the segment // *Action: Recheck the segment, file number, block number and re-issue // the statement 10622, 00000, "test/trace online index (re)build" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: facilitates analysis of online index rebuilds 10623, 00000, "Enable Index range scan Prefetch - testing only" // *Cause: // *Action: set this event only under the supervision of Oracle development 10650, 00000, "disable cache-callback optimisation" // *Cause: // *Action: set this event only under the supervision of Oracle development 10651, 00000, "incorrect file number block number specified" // *Cause: The dba specified is not valid // *Action: Check if the dba specified belongs to the segment and is under the // segment HWM and reissue the statement 10666, 00000, "Do not get database enqueue name" // *Cause: // *Action: 10667, 00000, "Cause sppst to check for valid process ids" // *Cause: // *Action: 10690, 00000, "Set shadow process core file dump type (Unix only)" // *Cause: Control core file size for shadow processes // *Action: Level 1: Detach SGA before dumping core // Level 2: Do not produce any core 10691, 00000, "Set background process core file type (Unix only)" // *Cause: Control core file size file for background processes // *Action: Level 1: Detach SGA before dumping core 10700, 00000, "Alter access violation exception handler" // *Cause: Use this event to control what the VMS exception handler // does when it encounters an access violation. // *Action: // Level: >=10 Suspend current process on access violation // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10701, 00000, "Dump direct loader index keys" // *Cause: Dumps index keys at various points in a direct load based on the // value of this event. // *Action: // *Comment: This is bit mask, interpreted as follows: // 0x01: dump all keys as they are being built (use judiciously, // as this generates a lot of data!) // 0x02: dump index keys which cause OER(1), OER(1409), OER(1452) // errors. // 10702, 00000, "Enable histogram data generation" // *Cause: When enabled, histogram entries will be processed when ANALYZE // is used. // *Action: 10703, 00000, "Simulate process death during enqueue get" // *Cause: Use this event to test process death enqueue cleanup by // causing the process to die in a known place getting an enqueue. // *** THIS SHOULD NEVER BE SET EXCEPT FOR TESTING *** // *Action: // *Comment: Level indicates which enqueue operation will cause death: // 1: enqueue get // 2: enqueue convert // 3: enqueue release 10704, 00000, "Print out information about what enqueues are being obtained" // *Cause: When enabled, prints out arguments to calls to ksqcmi and // ksqlrl and the return values. // *Action: Level indicates details: // Level: 1-4: print out basic info for ksqlrl, ksqcmi // 5-9: also print out stuff in callbacks: ksqlac, ksqlop // 10+: also print out time for each line 10705, 00000, "Print Out Tracing information for every I/O done by ODSs" // *Cause: When enabled, prints out tracing info on I/Os to datafiles. // *Action: // Level: >0 Print a trace of every I/O to the database files // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10706, 00000, "Print out information about global enqueue manipulation" // *Cause: When enabled, prints out activity in ksi routines. // *Action: INternal system parameter (_ksi_trace) can be used in addition // to setting this event to limit output information on selected // set of global enqueue server enqueue type(s) // For example: // _ksi_trace = RTXA // output information only for RT and XA lock types. // // *Action: Level indicates details: // 0-4: show args for each main call // 5-9: also indicate callbacks // 10+: also printout time for each line 10707, 00000, "Simulate process death for instance registration" // *Cause: When enabled, process commits suicide to test instance // registration recovery code. // *Action: Level indicates where the process will die 10708, 00000, "Print out Tracing information for skxf multi instance comms" // *Cause: When enabled, prints activity of skxf routines // *Action: Level indicates details: // 1: Print out tracing for each call // 2: Print a line on Entry to every skxf routine // *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** 10709, 00000, "enable parallel instances in create index by default" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: this causes all create index statement to by default // use multiple instances. it is for testing purposes only. // the level set in the event is the number of instances. // *Comment: enables analysis of parallel create index - query coordinator / / 10710 - 10729 are Reserved for BITMAP row sources / 10710, 00000, "trace bitmap index access" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: display the start-rowid, end-rowid of each bitmap segment - kkrbx // row source 10711, 00000, "trace bitmap index merge" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index merge - kkrbu row source 10712, 00000, "trace bitmap index or" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index or - kkrbo row source 10713, 00000, "trace bitmap index and" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index and - kkrba row source 10714, 00000, "trace bitmap index minus" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index minus - kkrbm row source 10715, 00000, "trace bitmap index conversion to rowids" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index merge - kkrbt row source 10716, 00000, "trace bitmap index compress/decompress" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index compression/decompression - // modules kdibc, kdibci, kdibco, kdibc3 / 10717, 00000, "trace bitmap index compaction trace for index creation" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of bitmap index creation - // modules kkrbc / 10718, 00000, "event to disable automatic compaction after index creation" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables isolation of index creation problems. ie compaction // is an optional part of the index creation algorithem which // improves query performance and shrinks index size // modules kkrbc / 10719, 00000, "trace bitmap index dml" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: enables analysis of inserts update and deletes into tables // with bitmap indexes // modules kkrbc / 10720, 00000, "trace db scheduling" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: traces db scheduling / 10721, 00000, "Internal testing - temp table transformation" // *Cause: // *Action: / / 10730 - 10800 general debugging events / 10722, 00000, "set parameters for CPU frequency calculation (debug)" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: changes parameters for CPU frequency calculation / 10723, 00000, "Internal testing - release buffer for buffer cache shrink" // *Cause: // *Action: / 10730, 00000, "trace row level security policy predicates" // *Cause: // *Action: // *Comment: / 10731, 00000, "dump SQL for CURSOR expressions" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: traces SQL statements generated to execute CURSOR expressions / 10740, 00000, "disables fix for bug 598861" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: disables fix for bug 598861. The fix changes slightly the cost // estimations for set queries in views, and thereby // changes query plans from previous versions // modules vop / 10750, 00000, "test rollback segment blksize guessing for index array insert" // *Cause: // *Action: set this event only under the supervision of Oracle development // *Comment: causes internal error to be raised if a transaction // repeatedly (100 times) fails to bind to a rollback segment // because block size is too small. (Default behaviour is to // silently assume the minimum database block size possible after // that many failures). Enable this event only during testing. / 10800, 00000, "disable Smart Disk scan" // *Cause: // *Action: 10801, 00000, "enable Smart Disk trace" // *Cause: // *Action: 10802, 00000, "reserved for Smart Disk" // *Cause: // *Action: 10803, 00000, "write timing statistics on cluster database recovery scan" // *Cause: // *Action: 10804, 00000, "reserved for ksxb" // *Cause: // *Action: 10806, 00000, "Switch to 7.3 mode when detaching sessions" // *Cause: // *Action: 10807, 00000, "Disable user id check when switching to a global transaction" // *Cause: // *Action: / / / 10810 - 10825 Reserved for OLTP / 10810, 00000, "Trace snapshot too old" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10811, 00000, "Trace block cleanouts" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10812, 00000, "Trace Consistent Reads" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. / / 10830 - 10840 Reserved for sort and aggregation row sources / 10830, 00000, "Trace group by sort row source" // *Cause: // *Action: set this event only under the supervision of Oracle development. // trace level is a bitfield // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace adaptive fetch usage // 0x0002 trace exceptions during aggregation // 0x0004 trace use of one comparison for all key columns // 10831, 00000, "Trace group by rollup row source" // *Cause: // *Action: set this event only under the supervision of Oracle development. // trace level is a bitfield // // LEVEL ACTION //--------------------------------------------------------------------------- // 0x0001 trace use of one comparison for all key columns / / 10841 - 10849 Reserved for OCI / 10841, 00000, "Default un-inintialized charact set form to SQLCS_IMPLICIT" // *Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form // *Action: This event sets charset form as SQLCS_IMPLICIT when it is 0 / / 10850 - 10870 Reserved for AQ / 10850, 00000, "Enable time manager tracing" // *Cause: // *Action: 10851, 00000, "Allow Drop command to drop queue tables" // *Cause: re-enable SQL Drop DDL for queue tables. // *Action: last resort to drop queue table if all other options fail. The // user have to manually cleanup AQ's metadata after this operation. 10852, 00000, "Enable dumping of the AQ statistics hash table" // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10853, 00000, "event for AQ statistics latch cleanup testing" // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10856, 00000, "Disable AQ propagator from using streaming" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10857, 00000, "Force AQ propagator to use two-phase commit" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10858, 00000, "Crash the AQ propagator at different stages of commit" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10859, 00000, "Disable updates of message retry count" // *Document: NO // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DISABLING THE RETRY // FEATURE IN THE EVENT THAT IT CAUSES OTHER INTERNAL ERRORS. 10860, 00000, "event for AQ admin disable new name parser" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. // THIS EVENT IS NOT TO BE TURNED ON BY ANY CUSTOMER. DOING SO, // MAY CAUSE AQ DICTIONARY CORRUPTION 10861, 000000, "disable storing extended message properties" // *Document: NO // *Cause: NA // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY TO DISABLE STORING // NEW MESSAGE PROPERTIES SUCH AS SENDER_ID AND ORIGINAL_MESSAGE_ID. // 10862, 00000, "resolve default queue owner to current user in enqueue/dequeue" // *Cause: resolve default queue owner to current user in enqueue/dequeue. // *Action: turn on if client wish to resolve the default queue owner to the // current user. If not turned on, the default queue owner will be // resolved to the login user. 10871, 00000, "Undo bug 1968802" // *Cause: // *Action: 10872, 00000, "Undo bug 1939611" // *Cause: // *Action: / / 10900 - 10924 Reserved for SPACE management / 10900, 00000, "extent manager fault insertion event #%s" // *Cause: causes faults to be generated in instrumented extent code // *Action: this should only be enabled for internal testing / / 10901 - used in 7.3.4 for disabling extent trimming for merge / 10902, 00000, "disable seghdr conversion for ro operation" // *Cause: causes seghdr conversion to be turned off for ro ops(#555856) // *Action: this should be enabled only if determined that bug 555856 // has occured. Table needs to be exported subsequently 10903, 00000, "Force tablespaces to become locally managed" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. 10904, 00000, "Allow locally managed tablespaces to have user allocation" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE. 10905, 00000, "Do cache verification (kcbcxx) on extent allocation" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10906, 00000, "Unable to extend segment after insert direct load" // *Cause: This is a restriction with insert direct load transactions. // *Action: When a segment has been insert direct loaded, avoid DMLs that // could cause more space to be consumed. 10907, 00000, "Trace extent management events" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10908, 00000, "Trace temp tablespace events" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10909, 00000, "Trace free list events" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING. 10924, 00000, "import storage parse error ignore event" // *Cause: causes server to ignore specific error associated with freelists // and freelist groups when parsing // *Action: this should be enabled by import code only / // 10925 - 10974 Reserved for PL/SQL // / 10925, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 237911 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. 10926, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 190119 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. 10927, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 235190 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / 10928, 00000, "trace name context forever" // * Cause: // * Action: Set this event only under the supervision of Oracle Development. // * Comment: This event causes PL/SQL to dump out information to trace files. 10929, 00000, "trace name context forever" // * Cause: When enabled, turns off bugfix 343966 // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / 10930, 00000, "trace name context forever" // * Cause: When enabled, provides V7 behavior for fixed char binds // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / 10931, 00000, "trace name context forever" // * Cause: When enabled, allows normal packages to be compiled with standard // extensions like "" // * Action: Set this event only for a short amount of time. Once the // packages are compiled, this event should be turned off. // Level 1 - Turn the event on // Level > 1 - Turn the event off / 10932, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available only in version 8.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / 10933, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available only in version 8.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / 10934, 00000, "Reserved. Used only in version 7.x." // * Cause: When enabled, disables one or more features or bug fixes // available only in version 7.3. // * Action: DO NOT SET THIS EVENT! // * Comment: This event is not available in version 8.x. It is reserved // in order to allow events added to version 7.x to be merged // easily into version 8.x. / / 10935, 00000, "Reserved. Used only in version 7.x." // * Cause: When enabled, disables one or more features or bug fixes // available only in version 7.x. // * Action: DO NOT SET THIS EVENT! // * Comment: This event is not available in version 8.x. It is reserved // in order to allow events added to version 7.x to be merged // easily into version 8.x. / / 10936, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available in versions 7.x and 8.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / 10937, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available in versions 7.x and 8.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / / 10938, 00000, "trace name context forever" // * Cause: // * Action: When set, this event enables tracing of PL/SQL calls and exceptions. // * Comment: Setting this event could result in some performance slowdown. / / / 10939, 00000, "trace name context forever" // * Cause: // * Action: When set, this event turns on coverage for PL/SQL procedures and // functions. // * Comment: Setting this event could result in some performance slowdown. / / / 10940, 00000, "trace name context forever" // * Cause: Size of the PL/SQL tracing circular buffer, in kilobytes. // * Action: Set this event in concert with the 10938 event and the // _PLSQL_DUMP_BUFFER_EVENTS init.ora parameter, under supervision // of Oracle Support. / / / 10941, 00000, "trace name context forever" // * Cause: When enabled, turns on PL/SQL profiler // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / 10943, 00000, "trace name context forever" // * Cause: When enabled, disables one or more features or bug fixes // available only in version 8.x. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / 10944, 00000, "trace name context forever" // * Cause: When enabled, allows or controls PL/SQL OPT code gen project. // available only in version 8.2+. // * Action: set this event ONLY for development of the OPT project. // This is not for general use or deployment. 10945, 00000, "trace name context forever" // * Cause: When enabled, disables the behaviour change introduced by the fix // for bug 822764, which traps and handles invalidations of packages // whereas the previous behaviour was to use stale invalidated // instantiations of the stateful package body. // * Action: set this event ONLY if necessary - after reading the README for // this release or under supervision of Oracle Support. / / // / 10975 - 10998 Reserved for Replication / / 10975, 00000, "trace execution of parallel propagation" // *Document: NO // *Cause: // *Action: 10976, 00000, "internal package related tracing" // *Document: NO // *Cause: // *Action: / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 trace the execution of sync procedural replication, // error execution, $RP/$RL invocation. // > 1 trace the loading of meta-data into library cache for ip 10977, 00000, "trace event for RepAPI" // *Document: NO // *Cause: N/A. // *Action: Set this event only under the supervision of Oracle development. // *Comment: Not for general purpose use. 10979, 00000, "trace flags for join index implementation" // *Cause: This is an informational message. // *Action: Values are as follows: // LEVEL ACTION //--------------------------------------------------------------------------- // > 1 Dump refresh expressions (SQL) to trace file. // > 999 If a complete refresh is invoked, it will not be performed // but the system will assume that a complete refresh was done, // causing the view to be VALID and updating timestamps. This // should be used only under Oracle Support supervision. / 10980, 00000, "prevent sharing of parsed query during Materialized View query generation" // *Document: NO // *Cause: N/A. // *Action: Set this event only under the supervision of Oracle development. // *Comment: Not for general purpose use. 10981, 00000, "dscn computation-related event in replication" // *Document: NO // *Cause: N/A. // *Action: / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 During replication enqueue for parallel propagation, make each // transaction in a session depend on the transaction that // precedes it in the same session. / / 10982, 00000, "event to turn off CDC-format MV Logs" // *Document: NO // *Cause: N/A. // *Action: / LEVEL ACTION //--------------------------------------------------------------------------- // = 999 Revert to pre-CDC original format MV Logs for all // new MV Logs created. / / 10983, 00000, "event to enable Create_Change_Table debugging" // *Document: NO // *Cause: N/A. // *Action: / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 Echo input parameter values to the trace log. // > 1 Display trigger debug info to the trace log also. / / 10984, 00000, "subquery materialized view-related event" // *Document: NO // *Cause: N/A // *Action: Set this event only under the supervision of Oracle development. // *Comment: Not for general purpose use. / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 A REFRESH FAST subquery MATERIALIZED VIEW which // satisfies the pre 8.2 ORACLE server requirements will be // treated as a many-many subquery MATERIALIZED VIEW. / 10985, 00000, "event for NULL refresh of materialized views" // *Document: NO // *Cause: N/A // *Action: Set this event only under the supervision of Oracle development. // *Comment: Not for general purpose use. / 10986, 00000, "donot use HASH_AJ in refresh" // *Document: NO // *Cause: N/A // *Action: Set this event while doing refresh if the delta snapshot is small // *Comment: Not for general purpose use. / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 Refresh uses NOT EXISTS sub-query instead of HASH_AJ / 10987, 00000, "event for the support of caching table with object feature" // *Document: NO // *Cause: N/A // *Action: Set this event while caching tables with object features. // *Comment: Not for general purpose use. / LEVEL ACTION //--------------------------------------------------------------------------- // > 0 Turn off the checking of object features of a cached table / 10988, 00000, "event to get exclusive lock during materialized view refresh in IAS" // *Document: NO // *Cause: N/A // *Action: Set this event if you want to get exclusive lock on the Updatable MV container table during refresh in IAS // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // > 0 Get exclusive lock on the updatable MV container table during // refresh in IAS / 10989, 00000, "event to internally create statistics MV" // *Document: NO // *Cause: N/A // *Action: The event is internally used to create statsMV // *Comment: Not for general purpose use. // LEVEL ACTION //--------------------------------------------------------------------------- // > 0 / 10999, 00000, "do not get database enqueue name" // *Cause: // *Action: / / 10999 End Pseudo-error debugging events / / 11000 - 11999 Reserved for mvs sql*net errors / / 12000 - 12099 Reserved for table materialized view errors / 12000, 00000, "a materialized view log already exists on table '%s'" // *Cause: // *Action: 12001, 00000, "cannot create log: table '%s' already has a trigger" // *Cause: Materialized view logs are filled by a trigger on the master table. // That trigger cannot be created. // *Action: To create a materialized view log, drop the current trigger on the // master. 12002, 00000, "there is no materialized view log on table \"%s\".\"%s\"" // *Cause: There was no materialized view log on the master table. // *Action: Create a materialized view log on the master table. 12003, 00000, "materialized view \"%s\".\"%s\" does not exist" // *Cause: The materialized view with the given owner and name does not exist. // *Action: Verify inputs and create a materialized view. 12004, 00000, "REFRESH FAST cannot be used for materialized view \"%s\".\"%s\"" // *Cause: The materialized view log does not exist or cannot be used. // *Action: Use just REFRESH, which will reinstantiate the entire table. // If a materialized view log exists and the form of the materialized // view allows the use of a materialized view log, REFRESH FAST will // be available starting the next time the materialized view is // refreshed. 12005, 00000, "may not schedule automatic refresh for times in the past" // *Cause: An attempt was made to schedule an automated materialized view // refresh for a time in the past. // *Action: Choose a time in the future instead. 12006, 00000, "a materialized view with the same user.name already exists" // *Cause: // *Action: 12007, 00000, "materialized view reuse parameters are inconsistent" // *Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. // REUSE command was given inconsistent parameters immediately after // the REUSE. // *Action: Examine the other messages on the stack to find the problem. 12008, 00000, "error in materialized view refresh path" // *Cause: Table SNAP$_ reads rows from the view // MVIEW$_, which is a view on the master table // (the master may be at a remote site). Any // error in this path will cause this error at refresh time. // For fast refreshes, the table .MLOG$_ // is also referenced. // *Action: Examine the other messages on the stack to find the problem. // See if the objects SNAP$_, MVIEW$_, // .@, .MLOG$_@ // still exist. 12009, 00000, "materialized views may not contain long columns" // *Cause: // *Action: 12010, 00000, "cannot create materialized view log on table owned by SYS" // *Cause: An attempt was made to create a materialized view log on the // table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to // create a trigger on the table, but triggers can not be created // on SYS tables. // *Action: Do not create a materialized view log on SYS tables. 12011, 00000, "execution of %s jobs failed" // *Cause: An error was caught in dbms_ijob.run from one or more jobs // which were due to be run. // *Action: Look at the alert log for details on which jobs failed and why. 12012, 00000, "error on auto execute of job %s" // *Cause: An error was caught while doing an automatic execution of a job. // *Action: Look at the accompanying errors for details on why the execute // failed. 12013, 00000, "updatable materialized views must be simple enough to do fast refresh" // *Cause: The updatable materialized view query contained a join, subquery, // union, connect by, order by, or group by caluse. // *Action: Make the materialized view simpler. If a join is really needed, // make multiple simple materialized views then put a view on top of // them. 12014, 00000, "table '%s' does not contain a primary key constraint" // *Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the // WITH PRIMARY KEY option and the master table did not contain // a primary key constraint or the constraint was disabled. // *Action: Reissue the command using only the WITH ROWID option, create a // primary key constraint on the master table, or enable an existing // primary key constraint. 12015, 00000, "cannot create a fast refresh materialized view from a complex query" // *Cause: Neither ROWIDs and nor primary key constraints are supported for // complex queries. // *Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE // option or create a simple materialized view. 12016, 0000, "materialized view does not include all primary key columns" // *Cause: The query that instantiates the materialized view did not include // all of the columns in the master's primary key constraint. // *Action: Include all of the master's primary key columns in the materialized // view query or create a ROWID materialized view. 12017, 0000, "cannot alter primary key mview '%s' to a rowid mview" // *Cause: An attempt was made to convert the primary key of a materialized // view to a ROWID materialized view. // *Action: Conversion of a primary key materialized view to a ROWID // materialized view is not supported. Create a new materialized view // with ROWIDs or drop and recreate the materialized view with ROWIDs. 12018, 0000, "following error encountered during code generation for \"%s\".\"%s\"" // *Cause: The refresh operations for the indicated materialized view could // not be regenerated due to errors. // *Action: Correct the problem indicated in the following error messages and // repeat the operation. 12019, 0000, "master table is a synonym to a remote object" // *Cause: An attempt was made to create a materialized view or a // materialized view log on a remote synonym which is unsupported. // *Action: Do not create a materialized view or materialized view log on a // remote synonym. 12020, 00000, "materialized view %s is not registered" // *Cause: An attempt was made to unregister a materialized view that is not // registered. // *Action: No action required. 12021, 0000, "materialized view \"%s\".\"%s\" is corrupt" // *Cause: The materialized view indicated is no longer valid. // *Action: Contact Oracle Customer Support. 12022, 0000, "materialized view log on \"%s\".\"%s\" already has rowid" // *Cause: Materialized view log on the indicated table already has ROWID // information. // *Action: No action required. 12023, 0000, "missing index on materialized view \"%s\".\"%s\"" // *Cause: The specified ROWID materialized view did not have the required // index on the ROWID column of its underlying table. // *Action: Drop and recreate the materialized view. 12024, 0000, "materialized view log on \"%s\".\"%s\" does not have primary key columns" // *Cause: Materialized view log on the indicated table does not have primary // key information. // *Action: Add primary keys to the materialized view log using the ALTER // MATERIALIZED VIEW command. 12025, 0000, "materialized view log on \"%s\".\"%s\" already has primary keys" // *Cause: Materialized view log on the indicated table already has primary // key columns. // *Action: No action required. 12026, 0000, "invalid filter column detected" // *Cause: One or more of the specified filter columns did not exist or was a // primary key column or a primary key based object identifier. // *Action: Ensure that all specified filter columns exist in the master table // and ensure that primary key columns or primary key based object // identifiers are not included in the list of filter columns. 12027, 0000, "duplicate filter column" // *Cause: One or more of the specified filter columns were already being // recorded in the materialized view log. // *Action: Describe the materialized view log table and reissue the SQL // command with the filter columns that are already being // recorded in the materialized view log. 12028, 0000, "materialized view type is not supported by master site %s" // *Cause: Pre-Oracle8 master sites are not able to support primary key or // subquery materialized views that are able to perform a fast // refresh. // *Action: Create a ROWID materialized view or use a master table from an // Oracle8 site. 12029, 0000, "LOB columns may not be used as filter columns" // *Cause: An attempt was made to use LOB columns as filter columns. // *Action: Remove LOB columns from the filter columns list and retry command. // 12030, 0000, "cannot create a fast refresh materialized view" // *Cause: The materialized view log did not exist or did not log the // information needed by the materialized view to perform a fast // refresh. // *Action: Ensure that the materialized view log exists and logs the necessary // information. // - For ROWID materialized views, the master table's ROWID // must be logged. // - For primary key materialized views, the master table's primary // key columns must be logged. // - For subquery materialized views, the filter columns, primary key, // and ROWID values must be logged. // - For object materialized views, object id must be logged. // 12031, 0000, "cannot use primary key columns from materialized view log on \"%s\".\"%s\"" // *Cause: The materialized view log either did not have primary key columns // logged, or the timestamp associated with the primary key columns // was more recent than the last refresh time. // *Action: A complete refresh is required before the next fast refresh. // Add primary key columns to the materialized view log, if required. // 12032, 0000, "cannot use rowid column from materialized view log on \"%s\".\"%s\"" // *Cause: The materialized view log either does not have ROWID columns // logged, or the timestamp associated with the ROWID columns is // more recent than the last refresh time. // *Action: A complete refresh is required before the next fast refresh. // Add ROWID columns to the materialized view log, if required. // 12033, 0000, "cannot use filter columns from materialized view log on \"%s\".\"%s\"" // *Cause: The materialized view log either did not have filter columns // logged, or the timestamp associated with the filter columns was // more recent than the last refresh time. // *Action: A complete refresh is required before the next fast refresh. // Add filter columns to the materialized view log, if required. // 12034, 0000, "materialized view log on \"%s\".\"%s\" younger than last refresh" // *Cause: The materialized view log was younger than the last refresh. // *Action: A complete refresh is required before the next fast refresh. // 12035, 0000, "could not use materialized view log on \"%s\".\"%s\"" // *Cause: The materialized view log did not exist or could not be used. // *Action: Use just REFRESH, which will reinstantiate the entire table. // If a materialized view log exists and the form of the materialized // view allows the use of a materialized view log, REFRESH FAST will // be available starting the next time the materialized view is // refreshed. // 12036, 0000, "updatable materialized view log is not empty, refresh materialized view" // *Cause: The updatable materialized view log was not empty. The updatable // materialized view log must be empty before an updatable rowid // materialized view can be altered to a primary key materialized // view. // *Action: Ensure that updatable materialized view log is empty by refreshing // the materialized view before converting the updatable ROWID // materialized view to a primary key materialized view. // 12037, 0000, "unknown export format" // *Cause: An attempt was made to import a materialized view exported by an // unknown export version (e.g., from a newer release than the // importing site) // *Action: Re-export the file using a version of export known by the importing // site. // 12038, 00000, "string literal has unexpected length" // *Cause: // *Action: // 12039, 00000, "unable to use local rollback segment \"%s\"" // *Cause: A local rollback segment was specified in the CREATE MATERIALIZED // VIEW command, but automatic refresh parameters were not specified. // Therefore a refresh group was not created to automatically // refresh the materialized view and the local rollback segment can't // be registered for future use. // *Action: Either supply the automatic refresh parameters so that a refresh // group will be created or do not specify a local rollback segment. // 12040, 00000, "master rollback segment option not support by master site %s" // *Cause: An attempt was made to specify master rollback segment in the // current operation. The master site of the current materialized // view does not allow users to specify a rollback segment to be used // for materialized view operations. This feature is only supported // by Oracle8 or later master sites. // *Action: Do not specify a master rollback segment in the current operation // or choose a new master site. // 12041, 00000, "cannot record ROWIDs for index-organized table \"%s\".\"%s\"" // *Cause: Index-organized tables do not have ROWIDs. Therefore a materialized // view log that records the ROWIDs of an index-organized table // could not be created. // *Action: Do not include the WITH ROWID option when using the // CREATE MATERIALIZED VIEW command and do not include the ADD ROWID // option when using the ALTER MATERIALIZED VIEW command if the master // table is index-organized. // 12042, 00000, "cannot alter job_queue_processes in single process mode" // *Cause: An attempt was made to alter job_queue_processes in single process // mode. // *Action: Do not attempt to set job_queue_processes in single process mode. // 12043, 00000, "invalid CREATE MATERIALIZED VIEW option" // *Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement. // *Action: Specify only valid options. // 12044, 00000, "invalid CREATE MATERIALIZED VIEW LOG option" // *Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG // statement. // *Action: Specify only valid options. // 12045, 00000, "invalid ALTER MATERIALIZED VIEW LOG option" // *Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG // statement. // *Action: Specify only valid options. // 12051, 00000, "ON COMMIT attribute is incompatible with other options" // *Cause: ON COMMIT refresh attribute, incompatible with other // refresh options such as automatic periodic refresh, was specified. // *Action: Specify only valid options. // 12052, 00000, "cannot fast refresh materialized view %s.%s" // *Cause: Either ROWIDs of certain tables were missing in the definition or // the inner table of an outer join did not have UNIQUE constraints on // join columns. // *Action: Specify the FORCE or COMPLETE option. If this error is got // during creation, the materialized view definition may have be // changed. Refer to the documentation on materialized views. // 12053, 00000, "this is not a valid nested materialized view" // *Cause: The list of objects in the FROM clause of the definition of this // materialized view had some dependencies upon each other. // *Action: Refer to the documentation to see which types of nesting are valid. // 12054, 00000, "cannot set the ON COMMIT refresh attribute for the materialized view" // *Cause: The materialized view did not satisfy conditions for refresh at // commit time. // *Action: Specify only valid options. // 12055, 00000, "materialized view definition contains cyclic dependencies with existing materialized views" // *Cause: The materialized view query definition introduced a cyclic // dependency with existing materialized view. // *Action: Modify the materialized view query definition. // 12056, 00000, "invalid REFRESH method" // *Cause: The NEVER REFRESH option may not be used under the // following conditions: // * The materialized view is updatable // * The materialized view refreshes ON COMMIT // * Automatic refresh options are specified // *Action: For updatable materialized views, reissue the SQL command using // REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only // materialized views, reissue the SQL command using ON DEMAND. // 12057, 00000, "materialized view \"%s\".\"%s\" is INVALID and must complete refresh" // *Cause: The status of the materialized view was INVALID and an attempt was // made to fast refresh the materialized view. // *Action: Perform a complete refresh of the materialized view. Check the // value of the STATUS column in dba_mviews, all_mviews, or // user_mviews to verify that the materialized view is VALID after // the complete refresh. // 12058, 00000, "materialized view cannot use prebuilt table" // *Cause: An attempt was made to use the prebuilt tables. // *Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED. // 12059, 00000, "prebuilt table \"%s\".\"%s\" does not exist" // *Cause: The specified prebuilt table did not exist. // *Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or // ensure that the prebuilt table exists. // 12060, 00000, "shape of prebuilt table does not match definition query" // *Cause: The number of columns or the type or the length semantics of a // column in the prebuilt table did not match the materialized // view definition query. // *Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or // ensure that the prebuilt table matches the materialized view // definition query. // 12061, 00000, "invalid ALTER MATERIALIZED VIEW option" // *Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement. // *Action: Specify only valid options. // 12062, 00000, "transaction %s received out of sequence from site %s" // *Cause: A transaction from the client site was received out of sequence. // This implies that one or more transactions were missing. // *Action: Ensure that the transaction queue at the client site is valid // and has not been corrupted. // 12063, 00000, "unable to apply transaction from site %s" // *Cause: The current transaction from the client site could not be // applied to the master site. // *Action: Ensure that the client site is still valid and that it has not // been dropped from the master site. // 12064, 00000, "invalid refresh sequence number: %s" // *Cause: The client site was attempting to perform a refresh with an // invalid refresh sequence. // *Action: Perform a complete refresh to synchronize the refresh // sequence number. // 12065, 00000, "unknown refresh group identifier %s" // *Cause: The specified refresh group did not exist at the master site. // *Action: Ensure that the client site is still valid and that it has not // been dropped from the master site. // 12066, 00000, "invalid CREATE MATERIALIZED VIEW command" // *Cause: The Replication API does not support the following options and // types of materialized view: // o ROWID materialized views // o REFRESH ON COMMIT // o ON PREBUILT TABLE // o BUILD DEFERRED // o NEVER REFRESH // o ENABLE QUERY REWRITE // *Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY // KEY and/or remove the invalid options. // 12067, 00000, "empty refresh groups are not allowed" // *Cause: The refresh group being instantiated did not contain any // materialized views. // *Action: Modify the template to include at least one materialized view. // 12068, 00000, "updatable mview log for mview \"%s\".\"%s\" does not exist" // *Cause: The updatable materialized view was missing the updatable // materialized view log required to track updates made to the // materialized view. // *Action: Create the updatable materialized view log. // 12069, 00000, "invalid object for offline instantiation" // *Cause: Only materialized views can be offline instantiated. The object // being offline instantiated was not a valid materialized view. // *Action: Remove the object from the template or replace the object // with a valid materialized view. // 12070, 00000, "cannot offline instantiate materialized view \"%s\".\"%s\"" // *Cause: Offline instantiation does not support materialized views using the // following options: // o ON PREBUILT TABLE // o BUILD DEFERRED // *Action: Remove the invalid options. // 12071, 00000, "definition query of \"%s\".\"%s\" is invalid for offline instantiation" // *Cause: Offline instantiation requires materialized view definition queries // to observe the following constraints: // o The database link that will be used by the materialized view site // to connect to the master site must be included with each master // table referenced in the query. // o All master tables referenced must be located at the local site. // References to other sites are not allowed. // *Action: Modify the materialized view definition query. // 12072, 00000, "updatable materialized view log data for \"%s\".\"%s\" cannot be created" // *Cause: The updatable materialized view was missing the updatable // materialized view log required to track updates made // to the materialized view. // *Action: Create an updatable materialized view log. // 12073, 00000, "request cannot be processed" // *Cause: An out-of-sequence request was made and it cannot be processed. // *Action: Try again with a valid request. // 12074, 00000, "invalid memory address" // *Cause: An attempt was made to access an invalid memory region. // *Action: Reconnect and try the command again. // 12075, 00000, "invalid object or field" // *Cause: An attempt was made to access an invalid field or object in the // Java Virtual Memory. // *Action: Retry the request. // 12076, 00000, "invalid threshold value" // *Cause: The result set threshold or LOB threshold value is not supported. // *Action: Specify a threshold value below 64K. // 12077, 00000, "temporary updatable materialized view log does not exist" // *Cause: Temporary updatable materialized view log was not created or was // dropped. // *Action: Re-create the temporary updatable materialized view log. // Warning: This will cause a complete refresh of the materialized // view. // 12078, 00000, "fast refresh of refresh group ID %s failed" // *Cause: Refresh result set sent through client method REFRESH_REQ_RESULT // returned an unknown value. // *Action: Re-issue the refresh request. // 12079, 00000, "materialized view options require COMPATIBLE parameter to be %s or greater" // *Cause: The following materialized view options require 8.1 or higher // compatibility setting: // o ON COMMIT // o ON PREBUILT TABLE // o BUILD DEFERRED // o NEVER REFRESH // o ENABLE QUERY REWRITE // // The following materialized view options require 8.2 or higher // compatibility setting: // o materialized views with user-defined types // *Action: Shut down and restart with an appropriate compatibility setting. // 12081, 00000, "update operation not allowed on table \"%s\".\"%s\"" // *Cause: An attempt was made to update a read-only materialized view. // *Action: No action required. Only Oracle is allowed to update a // read-only materialized view. // 12082, 00000, "\"%s\".\"%s\" cannot be index organized" // *Cause: An attempt was made to create an index-organized // materialized aggregate view or an index-organized // updatable ROWID materialized view. This is not // supported. // *Action: Try to create the materialized view without the // index organization clause. 12083, 00000, "must use DROP MATERIALIZED VIEW to drop \"%s\".\"%s\"" // *Cause: An attempt was made to drop a materialized view using // a command other than DROP MATERIALIZED VIEW. // *Action: Use the DROP MATERIALIZED VIEW command. // 12084, 00000, "must use ALTER MATERIALIZED VIEW to alter \"%s\".\"%s\"" // *Cause: An attempt was made to alter a materialized view using // a command other than ALTER MATERIALIZED VIEW. // *Action: Use the ALTER MATERIALIZED VIEW command. 12085, 0000, "materialized view log on \"%s\".\"%s\" already has object id" // *Cause: Materialized view log on the indicated table already has object // id information. // *Action: No action required. // 12086, 00000, "table \"%s\".\"%s\" is not an object table" // *Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the // WITH OBJECT ID option and the master table is not an object // table. // *Action: Either specify the name of an object table, or remove the WITH // OBJECT ID clause. // 12087, 00000, "online redefinition not allowed on tables owned by \"%s\"" // *Cause: An attempt was made to online redefine a table owned by // SYS or SYSTEM. // *Action: Do not attempt to online redefine a table owned by SYS or SYSTEM. // 12088, 00000, "cannot online redefine table \"%s\".\"%s\" with unsupported datatype" // *Cause: An attempt was made to online redefine a table containing // a LONG column, an ADT column, or a FILE column. // *Action: Do not attempt to online redefine a table containing a LONG column, // an ADT column, or a FILE column. // 12089, 00000, "cannot online redefine table \"%s\".\"%s\" with no primary key" // *Cause: An attempt was made to online redefine a table that does not have // a primary key defined on it. // *Action: Do not attempt to online redefine a table that does not have a // primary key defined on it. 12090, 00000, "cannot online redefine table \"%s\".\"%s\"" // *Cause: An attempt was made to online redefine a table that is either a // clustered table, AQ table, temporary table, or IOT overflow table. // *Action: Do not attempt to online redefine a table that is a // clustered table, AQ table, temporary table, or IOT overflow table. // 12091, 00000, "cannot online redefine table \"%s\".\"%s\" with materialized views" // *Cause: An attempt was made to online redefine a table that had // materialized views defined on it or had a materialized view log // defined on it or is a master. // *Action: Drop all materialized views and materialized view logs before // attempting to online redefine the table. // 12092, 00000, "cannot online redefine replicated table \"%s\".\"%s\"" // *Cause: An attempt was made to online redefine a table that is either a // materialized view or a replicated table. // *Action: Do not attempt to online redefine a table that is either a // materialized view or a replicated table. // 12093, 00000, "invalid interim table \"%s\".\"%s\"" // *Cause: The table is not the interim table of the corresponding table // to be online redefined. // *Action: Pass in the valid interim table. // 12094, 00000, "error during online redefinition" // *Cause: There was an error during the online redefinition process. // *Action: Abort the online redefinition process. // 12096, 00000, "error in materialized view log on \"%s\".\"%s\"" // *Cause: There was an error originating from this materialized view log. // One possible cause is that schema redefinition has occurred // on the master table and one or more columns in the log is now // a different type than corresponding master column(s). Another // possible cause is that there is a problem accessing the // underlying materialized view log table. // *Action: Check further error messages in stack for more detail about // the cause. If there has been schema redefinition, drop the // materialized view log and recreate it. // 12097, 00000, "changes in the master tables during refresh, try refresh again" // *Cause: There are some changes (i.e., conventional DML, direct load, // partition maintenance operation) in the master tables during // materialized view refresh. // *Action: Refresh the affected materialized views again. // /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / 12100 - 12299 Reserved for Net8 errors / / / Copyright (c) 1991, 1996, 1997 by the Oracle Corporation. All rights reserved. / / / $Header: net12150.msg 06-aug-97.15:13:07 tmlee Exp $ / / / NAME / net12150.msg - NETwork external message file starting from 12150 - / U.S. english version / / / FUNCTION / Network error message file, American English version. / / / NOTES / Only external errors are to be put into this file. Internal / messages are to put into netius.msg. / / This file, along with netius.msg and net12500.msg, forms tnsus.msg. As a / result, the errors in this file may not overlap with the errors in / those files. Otherwise, errors will result when generating tnsus.msb. / / 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 get / away with longer message text. / / / '/' at beginning-of-line for comments. / '//' at beginning-of-line for *Cause: and *Action: fields. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////// Please maintain this map ////////////////////// / // 00001 - 04200 See netius.msg / . / . / 12150 - 12195 Reserved for OSN (Not to be used by TNS) / 12196 - 12285 NR errors reportable by OSN (returned by nricall()) / 12286 - 12499 ---(Reserved)--- / 12500 - 12699 See net12500.msg / . / . / . / /////////////////////////// Please maintain this map ////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / / / / OWNER / Network and Management Products - Server Technologies / / MODIFIED / tmlee 08/06/97 - modify 12204 / rwessman 03/16/97 - split from netus.msg to correct bug in building / oraus.msg. / 12150, 00000, "TNS:unable to send data" // *Cause: Unable to send data. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12151, 00000, "TNS:received bad packet type from network layer" // *Cause: Internal error. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12152, 00000, "TNS:unable to send break message" // *Cause: Unable to send break message. Connection probably disconnected. // *Action: Re-establish connection. If the error is persistent, turn // on tracing and reexecute the operation. / 12153, 00000, "TNS:not connected" // *Cause: Not currently connected to a remote host. // *Action: Re-establish connection. / 12154, 00000, "TNS:could not resolve service name" // *Cause: The service name specified is not defined correctly in the // TNSNAMES.ORA file. // *Action: Make the following checks and correct the error: // - Verify that a TNSNAMES.ORA file exists and is in the proper // place and accessible. See the operating system specific manual // for details on the required name and location. // - Check to see that the service name exists in one of the // TNSNAMES.ORA files and add it if necessary. // - Make sure there are no syntax errors anywhere in the file. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See // Chapter 4 in the SQL*Net V2 Administrator's Guide. If // possible, regenerate the configuration files using the Oracle // Network Manager. / 12155, 00000, "TNS:received bad datatype in NSWMARKER packet" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12156, 00000, "TNS:tried to reset line from incorrect state" // *Cause: Internal error during break handling. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12157, 00000, "TNS:internal network communication error" // *Cause: Internal error during network communication. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12158, 00000, "TNS:could not initialize parameter subsystem" // *Cause: Unable to locate parameter file. // *Action: Verify that a valid parameter file exists, and is readable. / 12159, 00000, "TNS:trace file not writeable" // *Cause: The trace file to be generated is not writeable by this user. // *Action: If the user does not have write permissions in the directory // to which the trace file will be written, contact the DBA to get the // proper permissions or use TRACE_DIRECTORY_CLIENT in SQLNET.ORA // to specify a directory the user can write to. / 12160, 00000, "TNS:internal error: Bad error number" // *Cause: Corrupt error reporting subsystem. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12161, 00000, "TNS:internal error: partial data received" // *Cause: The connection may be terminated. // *Action: Reconnect and try again. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12162, 00000, "TNS:service name is incorrectly specified" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is incorrectly specified. // *Action: Make sure there are no syntax errors in the connect descriptor. // Particularly look for unmatched parentheses or stray characters. // Any error in a TNSNAMES.ORA file makes it unusable. See Chapter 4 // in the SQL*Net V2 Administrator's Guide. / 12163, 00000, "TNS:connect descriptor is too long" // *Cause: The connect descriptor corresponding to the service name in // TNSNAMES.ORA is too long. // *Action: The maximum length for a connect descriptor is 512 bytes and this // limit has been exceeded. Use a smaller connect descriptor. If this is not // possible, contact Worldwide Customer Support. / 12164, 00000, "TNS:Sqlnet.fdf file not present" // *Cause: The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin. // *Action: The sqlnet.fdf file is required for Oracle Tracing to occur. // Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or // turn off tracing in your ORA file. / 12165, 00000, "TNS:Trying to write trace file into swap space." // *Cause: Oracle Trace doesn't allow writing trace information into your // swap space. // *Action: Oracle Trace cannot write trace information into swap space // so either disable tracing or redirect trace files to be written to another // area of your disk. / 12166, 00000, "TNS:Client can not connect to HO agent." // *Cause: NVstring contained DESCRIPTION/HO. // *Action: Call HO agent from integrating server. / 12168, 00000, "TNS:Unable to contact Directory Server." // *Cause: Configured to use LDAP based Directory Server. // *Action: Bring the Directory Server up or change configuration to LOCAL. / / This line is an OSN Magic Cookie. Don't eat it. Last OSN error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12196 - 12285 NR errors reportable to OSN. / 12196, 00000, "TNS:received an error from TNS" // *Cause: The navigation layer received an error from TNS. // *Action: See the error log file for the specific TNS error. / 12197, 00000, "TNS:keyword-value resolution error" // *Cause: The navigation layer received an error while trying to look up a // value for a keyword. // *Action: Check the syntax of the connect descriptor. / 12198, 00000, "TNS:could not find path to destination" // *Cause: Could not navigate a path through Interchanges to the destination. // This error occurs if an invalid community is in the address string, or // the address includes a protocol that is not available or the // TNSNAV.ORA file does not have a correct CMANAGER address specified or // the Interchange is down. // *Action: Assure that Interchanges necessary to get to the desired // destination are up and have available capacity for an additional // connection. Also check that the correct community and protocol have been // specified in the CMANAGER address used. / 12200, 00000, "TNS:could not allocate memory" // *Cause: Out of memory on machine. // *Action: Reconfigure machine to have more storage or run fewer applications // while the Interchange is running. / 12201, 00000, "TNS:encountered too small a connection buffer" // *Cause: TNS connection buffer supplied by the application was too small // to retrieve the data sent back. // *Action: Supply a larger connection buffer. If problem persists, call // Worldwide Customer Support. / 12202, 00000, "TNS:internal navigation error" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12203, 00000, "TNS:unable to connect to destination" // *Cause: Invalid TNS address supplied or destination is not listening. // This error can also occur because of underlying network transport // problems. // *Action: Verify that the service name you entered on the command line // was correct. Ensure that the listener is running at the remote node and // that the ADDRESS parameters specified in TNSNAMES.ORA are correct. // Finally, check that all Interchanges needed to make the connection are // up and running. / 12204, 00000, "TNS:received data refused from an application" // *Cause: The application using the Interchange or Connection Manager // refused the connection at the listener. // *Action: Make sure that the application listener at the destination is // functioning correctly. If it is and the problem persists, contact // Worldwide Customer Support. / 12205, 00000, "TNS:could not get failed addresses" // *Cause: Internal navigation error. // *Action: Not normally visible to the user. For further details contact // Worldwide Customer Support. / 12206, 00000, "TNS:received a TNS error during navigation" // *Cause: Internal navigation error because of an unexpected TNS error. // *Action: Look at the log file to find the TNS error. If necessary, turn // on tracing and repeat the operation. / 12207, 00000, "TNS:unable to perform navigation" // *Cause: Improperly configured navigation file TNSNAV.ORA. // *Action: Check the syntax of the TNSNAV.ORA file on the application`s // machine,and verify that it lists the correct communities. / 12208, 00000, "TNS:could not find the TNSNAV.ORA file" // *Cause: Either the ORACLE environment is not set up correctly, or the // TNSNAV.ORA file is not present. // *Action: Ensure that the ORACLE environment is set up appropriately // on your platform and that a TNSNAV.ORA file is present. / 12209, 00000, "TNS:encountered uninitialized global" // *Cause: Application calling navigation routine has not properly configured // the global variables. There are no TNSNAV.ORA files available, or they // are defective. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Worldwide Customer Support. / 12210, 00000, "TNS:error in finding Navigator data" // *Cause: Application calling navigation routine has not properly configured // the TNSNAV.ORA file. // *Action: Check the syntax of the TNSNAV.ORA file. / 12211, 00000, "TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA" // *Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. // *Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. / 12212, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have a CMANAGER_NAME specified. // *Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS // binding. Use of the Oracle Network Manager should eliminate this // error. / 12213, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA" // *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file // does not have an ADDRESS specified. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12214, 00000, "TNS:missing local communities entry in TNSNAV.ORA" // *Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. // *Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA // file. / 12215, 00000, "TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA" // *Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. // entry. // *Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA // / 12216, 00000, "TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA" // *Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's // TNSNAV.ORA file is improperly entered. // *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. / 12217, 00000, "TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA" // *Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or // addresses specified are wrong, or the intended Connection Managers are // unavailable. // *Action: Check the PREFERRED_CMANAGERS entries in the client's // TNSNAV.ORA file and correct them or talk with your network administrator // to determine if the specified Connection Managers are available. // Verify that the Interchangess are active by using the INTCTL STATUS // command. / 12218, 00000, "TNS:unacceptable network configuration data" // *Cause: Poorly formed network configuration data. For example, a // PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the // client's TNSNAV.ORA file. Or an Interchange downtime parameter // (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. // *Action: Check the entries in TNSNAV.ORA and the Interchange // configuration files and correct them. If necessary, talk with your // network administrator to determine if the specified Interchanges // (Connection Managers) are available and properly configured. // Use the Oracle Network Manager to generate the configuration files // if necessary. / 12219, 00000, "TNS:missing community name from address in ADDRESS_LIST" // *Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it // that have no COMMUNITY component and others that do have a COMMUNITY // component. // *Action: Check that in the connect descriptors you are using either // all the ADDRESSes have a COMMUNITY component or all do not. / / All succeeding errors are a remap of NS erros in NR / 12221, 00000, "TNS:illegal ADDRESS parameters" // *Cause: An illegal set of protocol adapter parameters was specified. In // some cases, this error is returned when a connection cannot be made to the // protocol transport. // *Action: Verify that the destination can be reached using the specified // protocol. Check the parameters within the ADDRESS section of // TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the // Oracle operating system specific documentation for your platform. // Protocols that resolve names at the transport layer (such as DECnet object // names) are vulnerable to this error if not properly configured or names are // misspelled. / 12222, 00000, "TNS:no such protocol adapter" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12223, 00000, "TNS:internal limit restriction exceeded" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try. / 12224, 00000, "TNS:no listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12225, 00000, "TNS:destination host unreachable" // *Cause: Contact can not be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 12226, 00000, "TNS:operating system resource quota exceeded" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 12227, 00000, "TNS:syntax error" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. / 12228, 00000, "TNS:protocol adapter not loadable" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter is // missing or one of its supporting libraries is missing then this error is // returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will include the name of the shared library (or DLL) that // could not be loaded. / 12229, 00000, "TNS:Interchange has no more free connections" // *Cause: One or more Interchanges along the path to the destination // desired has no more free connections available to be used for this // call. // *Action: Try again later when the Interchanges are less busy, or contact // your network administrator to have him determine which interchange it is, // and increase the number of connections available on that interchange. / 12230, 00000, "TNS:Severe Network error ocurred in making this connection" // *Cause: This error is reported by an interchange which fails to make // contact with the destination due to a physical network error while calling // a destination. // *Action: Try again later when the network service may have been fixed // or report the problem to your Network Administrator so that he may fix // the problem. / 12231, 00000, "TNS:No connection possible to destination" // *Cause: This error is reported by an interchange which fails to find a // possible connection along the path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12232, 00000, "TNS:No path available to destination" // *Cause: This error is reported by an interchange which fails to find a // possible path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12233, 00000, "TNS:Failure to accept a connection" // *Cause: This error is reported by an interchange which fails to accept // a connection due to a redirect failure. // *Action: Report the problem to your Network Administrator so that he may // isolate the interchange problem. / 12234, 00000, "TNS:Redirect to destination" // *Cause: This error is reported by an interchange which determines that this // interchange is not the right gateway and needs to redirect the connection // to another gateway along the path to the destination. // *Action: None. / 12235, 00000, "TNS:Failure to redirect to destination" // *Cause: This error is reported by an interchange which fails to redirect // a connection to another interchange along the path to the destination. // *Action: Report the problem to your Network Administrator so that he may // fix the problem. / 12236, 00000, "TNS:protocol adapter not loaded" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter has not // been loaded, then this error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that has // not been loaded. / / This line is an OSN Magic Cookie. Don't eat it. Last NR error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// / 12300 - 12399 Reserved for Multiple Mounts / / Begin error messages for Multiple Mounts / 12315, 00000, "database link type is invalid for the ALTER DATABASE statement" // *Cause: The database link name you specified on the ALTER DATABASE // statement is not an ROM: link. You must specify an ROM: link // when using the ALTER DATABASE statement to mount or open a // secondary database. // *Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to // the database you want to mount or open. If a valid ROM: link does // not exist, create one using the CREATE DATABASE LINK // command. See the Trusted ORACLE RDBMS Guide to Security Features // for more information about creating database links using // the ROM: link type. 12316, 00000, "syntax error in database link's connect string" // *Cause: The connect string in the CREATE DATABASE LINK statement // has a syntactical error. // *Action: Drop the database link and recreate it using valid syntax. See // the SQL Language Reference Manual for more information about the // connect string portion of the CREATE DATABASE LINK // statement. 12317, 00000, "logon to database (link name %s) denied" // *Cause: There are several possible causes for this error. First, you can // get this error if your username (and password, if you are using // database instead of operating system authentication) in the // secondary database are not identical // to your username (and password) in the primary database. Second, // you can get this error if your username in the secondary database // is invalid (has not been created). Third, // you can get this error if the username/password combination // specified in the connect string of the database link definition // is invalid (either not created or has an invalid password). // *Action: In the first case, ensure that the secondary database contains // a username (and password, if you are using database authentication) // identical to the one you are using in the primary // database. In general, you should always use operating system // authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS // Guide to Security Features for more information about the // advantages of OS authentication). // In the second case, ensure that your username in the // secondary database has been created. // In the third case, ensure that the username specified in the // connect string has been created in the secondary database. 12318, 00000, "database (link name %s) is already mounted" // *Cause: You are attempting to mount a secondary database that has already // been mounted by your instance. // *Action: The database is already mounted, so you need not take additional // action to mount it. To establish access, use the // ALTER DATABASE OPEN command to open the database. 12319, 00000, "database (link name %s) is already open" // *Cause: You are attempting to open a secondary database that is already // open. // *Action: The database is open and you need not take additional action // to establish access. 12321, 00000, "database (link name %s) is not open and AUTO_MOUNTING=FALSE" // *Cause: The secondary database that your instance is attempting to mount // is not open and automatic mounting has not been enabled. // *Action: Manually mount and open the secondary database using // ALTER DATABASE with the OPEN and MOUNT options. // Alternately, to allow your instance to automatically mount and // open secondary databases, set the AUTO_MOUNTING parameter in the // parameter file to TRUE. 12322, 00000, "unable to mount database (link name %s)" // *Cause: This message should be accompanied by additional error messages // that indicate the cause of the problem. // *Action: Follow the steps outlined in the accompanying error messages to // resolve the problem. 12323, 00000, "unable to open database (link name %s)" // *Cause: This message should be accompanied by additional error messages // that indicate the cause of the problem. // *Action: Follow the steps outlined in the accompanying error messages to // resolve the problem. 12324, 00000, "cannot use the ROM: link type on a private database link" // *Cause: You can only specify the ROM: link type on a public, not a // private, database link. // *Action: Determine if there is an existing public database link to the // secondary database. If not, and if you wish to establish public // access to the secondary database, create a public database link to // the secondary database using the CREATE DATABASE LINK // command. 12326, 00000, "database %s is closing immediately; no operations are permitted" // *Cause: The database you attempted to access is closing, so your // operation has been terminated. // *Action: Wait until the database has been reopened, or contact the // database adminstrator. 12329, 00000, "database %s is closed; no operations are permitted" // *Cause: The database you attempted to access is closed, so your // operation has been terminated. // *Action: Wait until the database is reopened, or contact the database // administrator. 12333, 00000, "database (link name %s) is not mounted" // *Cause: You attempted to open a database that has not been mounted. // *Action: Mount the database with the ALTER DATABASE MOUNT // command, then re-attempt to open the database. 12334, 00000, "database (link name %s) is still open" // *Cause: You attempted to dismount a database that is still open. // *Action: Close the database with the ALTER DATABASE CLOSE // command, then re-attempt to dismount the database. 12335, 00000, "database (link name %s) is not open" // *Cause: You attempted to close a database that is not open. // *Action: The database is closed; you can proceed with dismounting it. 12336, 00000, "cannot login to database (link name %s) " // *Cause: You are tyring to login while another user is mounting or // dismounting the same database. // *Action: Check to see if the database is in the middle of being // mounted or opened and try your login again once the database is // accessible. 12341, 00000, "maximum number of open mounts exceeded" // *Cause: The number specified on the OPEN_MOUNTS parameter in the parameter // file exceeds the maximum allowed (255). // *Action: Change the value of this parameter so that it reflects the actual // number of possible open mounts to secondary databases. This must // be less than 255. 12342, 00000, "open mounts exceeds limit set on the OPEN_MOUNTS parameter" // *Cause: The number of currently open mounts exceeds the value you // specified on the OPEN_MOUNTS parameter. // *Action: Increase the value of the OPEN_MOUNTS parameter so that it // accommodates the maximum possible number of open mounts to // secondary databases. 12345, 00000, "user %s lacks CREATE SESSION privilege in database link (linkname %s)" // *Cause: There are several possible causes for this message: // First, you will get this message if your username in the // second database specified was not granted the // CREATE SESSION system privilege. // Second, you will get this message if the username specified // in the connect string of the database link definition was // not granted the CREATE SESSION system privilege. // *Action: The action you take depends upon the cause of the message: // In the first case, ensure that your username in the secondary // database was granted the CREATE SESSION system privilege. // In the second case, ensure the username specified in the // connect string of the database link definition was granted // the CREATE SESSION system privilege in the secondary database. 12350, 00000, "database link being dropped is still mounted" // *Cause: An attempt was made to drop a ROM: database link that was still // mounted and/or opened. // *Action: Close and dismount the database and then re-issue the drop // statement. 12351, 00000, "cannot create view using a remote object which has a remote object reference" // *Cause: You tried to create a view which references a remote object // which, in turn, references an object on another database. Since // the view that you tried to create references a remote object, // that object cannot reference an object on another database. // *Action: Choose a different object to reference in your view or change // the remote object so that it does not reference another database. 12352, 00000, "object %s.%s@%s is invalid" // *Cause: An attempt was made to reference (compile against) an object // of a secondary database but the object is invalid and the system // cannot validate or recompile it because it is in a secondary // database. // *Action: Manually recompile the invalid object in the secondary database. 12353, 00000, "secondary stored object cannot reference remote object" // *Cause: You tried to either select from a remote view or execute a remote // procedure which references an object on another database. Since // the remote view or procedure is on a secondary database, an // additional reference to another database cannot be done. // *Action: Choose a different object to reference or change the remote // view or procedure so that it does not reference another database. 12354, 00000, "secondary object being dropped" // *Cause: You tried to access a object (for example, a table or view) // on a secondary database that was in the process of being // dropped. // *Action: Repeat the operation. If you receive this message again, try to // access the object from the secondary database. If you receive // an internal error or a trace file, contact Oracle WorldWide // Technical Support. / Copyright (c) Oracle Corporation 1999, 2000. All Rights Reserved. / / NAME / lbacus.msg / DESCRIPTION / Error messages for Oracle Label Security / Label Based Access Control Framework / NOTES / Language : American / Character set : US7ASCII / MODIFIED / gmurphy 02/06/01 - use Oracle Label Security in comments / rsripada 06/07/00 - update from 8.1.7 / rburns 08/04/99 - cleanup for RDBMS checkin / rburns 07/31/99 - merge Rita's edits and add rest of messages / rburns 07/27/99 - add comparison errors / shwong 07/27/99 - remove 00000, 00000 / shwong 07/22/99 - fix errors / rburns 07/13/99 - Add messages for PL/SQL functions / rburns 06/24/99 - add ADMIN errors / rburns 06/21/99 - add policy name error / cchui 06/08/99 - Modify datatype error, add event errors / cchui 05/14/99 - Add LBAC new messages for datatypes and events / rburns 04/08/99 - use 12400 to 12499 for now / rburns 03/01/99 - created / 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) 12400, 00000, "invalid argument to facility error handling" // *Cause: An argument to a facility error handling function exceeded // a maximum limit or referred to an invalid product/facility. // *Action: Specify a valid facility error handling parameter value. / Policy Error Codes 12401, 00000, "invalid label string: %s" // *Cause: The policy could not convert the label string to a valid // internal label. // *Action: Correct the syntax of the label string. 12402, 00000, "invalid format string: %s" // *Cause: The format string is not supported by the policy. // *Action: Correct the syntax of the format string. 12403, 00000, "invalid internal label" // *Cause: An internal label could not be converted to a valid label for the // policy. // *Action: Analyze any additional messages on the error stack // and consult the policy documentation. 12404, 00000, "invalid privilege string: %s" // *Cause: The policy could not interpret the privilege string. // *Action: Specify a privilege string that is supported by the policy. 12405, 00000, "invalid label list" // *Cause: The policy determined that the label list was invalid // for its intended use. // *Action: Check the policy constraints on the specific list // of labels. 12406, 00000, "unauthorized SQL statement for policy %s" // *Cause: The policy did not authorize the database session to // perform the requested SQL statement. // *Action: Grant the user or program unit the necessary policy // privilege or additional authorizations. 12407, 00000, "unauthorized operation for policy %s" // *Cause: The policy did not authorize the database session to // perform the requested operation. // *Action: Grant the user or program unit the necessary policy // privilege or additional authorizations. 12408, 00000, "unsupported operation: %s" // *Cause: The specified policy does not support the requested // operation. // *Action: Consult the policy documentation to determine the // supported access mediation operations. 12409, 00000, "policy startup failure for %s policy" // *Cause: The policy encountered an error during startup processing; // access to the data protected by the policy is prohibited. // *Action: Check the alert log for additional information, correct the // policy error, and restart the instance. 12410, 00000, "internal policy error for policy: %s\n Error: %s" // *Cause: The policy enforcement encountered an internal error. // *Action: Consult the policy documentation for details. / General LBAC error messages 12411, 00000, "invalid label value" // *Cause: The specified label value does not exist. // *Action: Check the data dictionary views for the policy to identify // valid labels. 12412, 00000, "policy package %s is not installed" // *Cause: The policy package does not exist in the database. // *Action: Check that the policy package name is correct or install the // required policy package. 12413, 00000, "labels do not belong to the same policy" // *Cause: The labels being compared belong to different policies. // *Action: Only compare labels that belong to the same policy. 12414, 00000, "internal LBAC error: %s\n Error: %s" // *Cause: An internal label policy framework error occurred. // *Action: Contact Oracle Customer Support. 12415, 00000, "A column of another datatype exists on the specified table" // *Cause: The datatype of the column present in the table is different // from the datatype set for the policy column. // *Action: Drop the column on the table or change the datatype for // policy column. 12416, 00000, "policy %s not found" // *Cause: The specified policy does not exist in the database. // *Action: Enter the correct policy name or create the policy. 12417, 00000, "database object \"%s\" not found" // *Cause: The specified object was not in the database. // *Action: Enter the correct name for the database object. 12418, 00000, "user %s not found" // *Cause: The specified user does not exist in the database. // *Action: Correct the user name or create the user. 12419, 00000, "null binary label value" // *Cause: A null value was provided for a binary label operation. // *Action: Provide a valid binary label for the operation. 12420, 00000, "required procedures and functions not in policy package \"%s\"" // *Cause: The policy package did not contain all of the procedures and // functions necessary to enforce the policy. // *Action: Consult the label framework documentation for a list of // required procedures and functions for a policy package. 12421, 00000, "different size binary labels" // *Cause: The label sizes for the binary label operation were not equal. // *Action: Provide binary labels with the same lengths for the operation. 12422, 00000, "max policies exceeded" // *Cause: You tried to create a new policy, but the maximum number of // policies for the instance had already been created. // *Action: Increase the size of the MAX_LABEL_POLICIES initialization // parameter and restart the server. 12423, 00000, "invalid position specified" // *Cause: The position specified for a binary label operation was invalid. // *Action: Provide a position that is within the label size limits. 12424, 00000, "length exceeds binary label size" // *Cause: The length specified for a binary label operation exceeded the // the size of the binary label. // *Action: Provide a bit or byte length that is within the label size limits. 12425, 00000, "cannot apply policies or set authorizations for system schemas" // *Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS // schema or to set user labels/privileges for the SYS, SYSTEM, or // LBACSYS user. // *Action: Apply policies and set authorizations only for non-system users. 12426, 00000, "invalid audit option" // *Cause: The option specified was not a valid audit option for // the specified policy. // *Action: Enter a correct audit option. 12427, 00000, "invalid input value for %s parameter" // *Cause: An input parameter was specified incorrectly. // *Action: Correct the parameter value. 12428, 00000, "" // *Cause: // *Action: 12429, 00000, "label list range exceeded" // *Cause: The specified index value was not between 1 and 6. // *Action: Correct the index value for the label list operation. 12430, 00000, "invalid privilege number" // *Cause: The specified privilege number was not between 1 and 32. // *Action: Correct the privilege number. 12431, 00000, "invalid audit action" // *Cause: The specified audit action was not a valid audit action. // *Action: Correct the audit action number. 12432, 00000, "LBAC error: %s" // *Cause: LBAC enforcement resulted in an error. // *Action: Correct the problem identified in the error message. 12433, 00000, "create trigger failed, policy not applied" // *Cause: The policy could not be applied due to errors during the // creation of a DML trigger. // *Action: Correct the SQL syntax of the label function specification. 12434, 00000, "invalid audit type: %s" // *Cause: The audit type must be BY ACCESS or BY SESSION. // *Action: Correct the audit type value. 12435, 00000, "invalid audit success: %s" // *Cause: The audit success parameter must be SUCCESSFUL or // NOT SUCCESSFUL. // *Action: Correct the audit success value. 12436, 00000, "no policy options specified" // *Cause: A NULL option string was specified, but no default schema or // policy option string was found. // *Action: Enter a valid option string, or alter the schema or policy to have // a valid default option string. 12437, 00000, "invalid policy option: %s" // *Cause: A value that was not a valid policy option was entered. // *Action: Correct the policy option value. 12438, 00000, "repeated policy option: %s" // *Cause: A policy option was entered more than once in the option string. // *Action: Remove the duplicate policy option value. 12439, 00000, "invalid combination of policy options" // *Cause: A set of contradictory policy options was entered. // *Action: Provide a set of compatible policy options. 12440, 00000, "insufficient authorization for the SYSDBA package" // *Cause: The use of the SYSDBA package requires the LBAC_DBA role. // *Action: Grant the LBAC_DBA role to the database user. 12441, 00000, "policy %s already exists" // *Cause: You tried to create a policy with the same name as an existing one. // *Action: Use a different name or drop the existing policy. 12442, 00000, "policy column \"%s\" already used by an existing policy" // *Cause: You tried to create a policy with the same policy column // name as an existing policy. // *Action: Use a different name for the policy column or drop the // existing policy. 12443, 00000, "policy not applied to some tables in schema" // *Cause: You applied a policy to a schema, and some of the tables in the // schema already had the policy applied. // *Action: No action necessary; the policy was applied to the remaining // tables. 12444, 00000, "policy already applied to table" // *Cause: You tried to apply a policy to a table that was already protected // by the policy. // *Action: To change the policy options, predicate, or label function, // remove the policy from the table and re-apply it. 12445, 00000, "cannot change HIDDEN property of column" // *Cause: You tried to specify a different HIDE option for a table // with an existing policy column. // *Action: Drop the column from the table and reapply the policy with the new // HIDE option. 12446, 00000, "Insufficient authorization for administration of policy %s" // *Cause: You tried to perform an administrative function for a policy, but // you have not been granted the _DBA role. // *Action: Grant the user the _DBA role for the specified policy. 12447, 00000, "policy role already exists for policy %s" // *Cause: The role named _DBA already exists. // *Action: Correct the policy name or delete the existing policy. 12448, 00000, "policy %s not applied to schema %s" // *Cause: You tried to alter a schema policy that was not applied. // *Action: Correct the policy name or schema name. 12449, 00000, "Labels specified for user must be of type USER" // *Cause: You tried to set labels for a user, but the labels in the list // were not all designated as USER labels. // *Action: Alter the labels to be USER labels. 12450, 00000, "LOB datatype disabled in LBAC initialization file" // *Cause: You tried to specify a LOB datatype for a column or attribute, // but the use of the LOB datatype has been disabled. // *Action: Change the LBAC initialization file to allow the creation // of LOB columns and attributes. 12451, 00000, "label not designated as USER or DATA" // *Cause: A label is either a DATA label, a USER label, or both DATA and // USER. // *Action: Enter TRUE for at least DATA or USER. 12452, 00000, "label tag %s already exists" // *Cause: The label tag value you entered is already in use for another // label. // *Action: Enter a different value for the label tag. 12453, 00000, "label %s already exists" // *Cause: The label value you entered already exists. // *Action: No action necessary; alter the label to change its tag or type. 12454, 00000, "label %s does not exist for policy %s" // *Cause: The label tag or value you entered did not identify a label // for the policy. // *Action: Enter a label value or tag that is in use by the policy. / SA policy messages (saus.msg) start at 12461 to 12475 / MLS policy messages (mlsus.msg) start at 12476 to 12499 / (and can be re-used if necessary for additional LBAC or SA errors) / Copyright (c) Oracle Corporation 2000. All Rights Reserved. / / NAME / saus.msg / DESCRIPTION / Error messages for Oracle Label Security / Oracle Secure Access Policy 12455-12465 / NOTES / Language : American / Character set : US7ASCII / MODIFIED / rburns 04/25/99 - created / 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) 12461, 00000, "undefined level %s for policy %s" // *Cause: The specified level is not defined for the policy. // *Action: Correct the level identifier value. 12462, 00000, "undefined compartment %s for policy %s" // *Cause: The specified compartment is not defined for the policy. // *Action: Correct the compartment identifier value. 12463, 00000, "undefined group %s for policy %s" // *Cause: The specified group is not defined for the policy. // *Action: Correct the group identifier value. 12464, 00000, "invalid characters in label component %s" // *Cause: Label components can contain only alphanumeric characters, blanks, // and underscores. // *Action: Correct syntax of the label component. 12465, 00000, "Not authorized for write on specified groups or compartments" // *Cause: You included groups or compartments that are not in the user's // list of groups and compartments authorized for write access. // *Action: Enter only groups and compartments that are authorized for write. 12466, 00000, "default level is greater than the user's maximum" // *Cause: The default level cannot be greater than the user's maximum. // *Action: Enter an authorized level. 12467, 00000, "minimum label can contain a level only" // *Cause: You included compartments or groups in the minimum label. // *Action: Enter only an authorized minimum level as the label. 12468, 00000, "max write level does not equal max read level" // *Cause: The level in the max write label must equal the // level in the max read label. // *Action: Enter max read and max write labels with the same level component. 12469, 00000, "no user levels found for user %s and policy %s" // *Cause: No levels have been specified for the user. // *Action: Enter the maximum and minimum labels for the user. 12470, 00000, "NULL or invalid user label: %s" // *Cause: The label entered is NULL or not within the user's authorizations. // *Action: Enter the authorized labels for the user. / MLS policy adaptor messages (mlsus.msg) start at 12499 and work backwards / Copyright (c) Oracle Corporation 1999, 2000. All Rights Reserved. / / NAME / mlscus.msg / DESCRIPTION / Error messages for Oracle Label Security / MLS Policy Package - not released / NOTES / Language : American / Character set : US7ASCII / MODIFIED / rburns 09/01/99 - add mls-specific messages for DML / rburns 08/20/99 - add error messages / rburns 08/04/99 - cleanup for RDBMS checkin / rburns 07/31/99 - merge Ritas edits and add rest of messages / shwong 07/27/99 - remove 00000, 00000 / rburns 06/24/99 - Add messages / shwong 06/08/99 - typo / shwong 05/28/99 - additional error messages / rburns 05/19/99 - Add more error messages / rburns 03/15/99 - created / 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) 12476, 00000, "least upper bound resulted in an invalid OS label" // *Cause: You tried to do an operation that generated a least upper bound // (LUB) label which is not a valid label on your operating system. // *Action: Consult your OS label management documentation for information // on invalid label generation. 12477, 00000, "greatest lower bound resulted in an invalid OS label" // *Cause: You tried to do an operation that generated a greatest lower // bound (GLB) label which is not a valid label on your operating // system. // *Action: Consult your OS label management documentation for information // on invalid label generation. 12479, 00000, "file label %s must equal DBHIGH %s" // *Cause: A database file had an OS label that did not match // DBHIGH. Either DBHIGH was altered or the OS file // was relabeled. // *Action: Relabel the file so that its label matches DBHIGH, or // alter DBHIGH so that it matches the label on the file. 12480, 00000, "specified clearance labels not within the effective clearance" // *Cause: You specified a clearance range that was not within your // authorized clearance; you can only specify clearance ranges // that are within your clearance. // *Action: Specify clearance labels that are within your own clearance // range. 12481, 00000, "effective label not within program unit clearance range" // *Cause: The effective label when the program unit was invoked was // not within the range authorized for the program unit. // *Action: Modify the program unit clearance range or invoke the program // unit from a session with an authorized effective clearance. 12482, 00000, "internal MLS error: %s\n Error: %s" // *Cause: An internal MLS policy error occurred. // *Action: Contact Oracle Customer Support. 12483, 00000, "label not in OS system accreditation range" // *Cause: The specified label is above the OS maximum label or // below the OS minimum label. // *Action: Use a label that is within the accreditation range for the // host OS. 12484, 00000, "invalid OS label" // *Cause: The specified label does not exist in the OS host's label // definition file. // *Action: Use the OS label management tools to define the label. 12485, 00000, "new effective label not within effective clearance" // *Cause: You attempted to enter a value for an effective label that // did not dominate the effective min label or was not dominated // by the effective max label. // *Action: Enter a value between the min and the max labels. 12486, 00000, "effective max labels and min labels cannot be changed" // *Cause: You attempted to enter a value for an effective min label // or effective max label, but these labels cannot be changed. // *Action: Enter NULL values for the effective minimum and maximum labels. 12487, 00000, "clearance labels not between DBHIGH and DBLOW" // *Cause: You attempted to enter a value for a clearance label that was // not dominated by DBHIGH or did not dominate DBLOW. // *Action: Enter clearance label values between DBHIGH and DBLOW. 12488, 00000, "maximum label does not dominate minimum label" // *Cause: You attempted to enter a value for a clearance label that did not // preserve the dominance relationship between the minimum and // maximum labels. // *Action: Enter label values that preserves the dominance relationship // between the minimum and maximum. 12489, 00000, "default label not within clearance range" // *Cause: You attempted to enter a value for a default label that did not // dominate the minimum clearance or was not dominated by the // maximum clearance. // *Action: Enter a default label value within the clearance range. 12490, 00000, "DBHIGH cannot be lowered" // *Cause: You attempted to enter a value for DBHIGH that did not // dominate the existing value of DBHIGH. // *Action: Enter a value for DBHIGH that dominates the old value. 12491, 00000, "DBHIGH value does not dominate DBLOW" // *Cause: You attempted to enter a value for DBHIGH that did not // dominate DBLOW. // *Action: Enter a value for DBHIGH that dominates DBLOW. 12492, 00000, "DBLOW cannot be changed" // *Cause: You attempted to change the value of DBLOW after it had been // set to any initial value. DBLOW can only be set once after // initial database creation. // *Action: To change DBLOW, you have to create a new database, // set DBLOW to the new value, and import your data into the new // database. 12493, 00000, "invalid MLS binary label" // *Cause: The MLS binary label contained an invalid value, was not the // correct size, or contained a level, category, or release // category that was not enabled. // *Action: Check the DBA_MLS_LABELS view for the valid MLS labels. 12494, 00000, "cannot insert or delete a level, category, or release category" // *Cause: You attempted to insert or delete a level, category, or // release category definition. // *Action: If the label definition is no longer valid, change its name to // one that identifies it as invalid. When any labels are converted // to character strings, the new label definition will be used. 12495, 00000, "cannot disable an enabled level, category, or release category" // *Cause: You attempted to disable a level, category, or release category // that had previously been enabled. An enabled label definition // may be exist in some database label, so cannot be disabled. // *Action: If the label definition is no longer valid, change its name to // one that identifies it as invalid. When any labels are converted // to character strings, the new label definition will be used. 12496, 00000, "cannot change existing level, category, or release numbers" // *Cause: You attempted to change the number assigned to level, category // or releasability category. // *Action: Change the character string representations, not the numbers. 12497, 00000, "maximum combined categories exceeds %s" // *Cause: The maximum number of descriptive categories plus release // categories supported by the MLS policy was exceeded. // *Action: Enter numbers that do not add up to more than the maximum. / Used to check if add/drop column on object table should be allowed in atb.c 12498, 00000, "" // *Cause: // *Action: / Used in kztins() for RLS test suite to work ok. 12499, 00000, "" // *Cause: // *Action: / Copyright (c) 1991, 1996, 1997, 1998, 1999, 2000, 2001 by the Oracle Corporation. All rights reserved. / / / $Header: net12500.msg 05-apr-2001.10:37:13 rachacos Exp $ / / / NAME / net12500.msg - NETwork external message file starting from 12500 - / U.S. english version / / / FUNCTION / Network error message file, American English version. / / / NOTES / Only external errors are to be put into this file. Internal / messages are to put into netius.msg. / / This file, along with netius.msg and net12150.msg, forms tnsus.msg. As a / result, the errors in this file may not overlap with the errors in / those files. Otherwise, errors will result when generating tnsus.msb. / / 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 get / away with longer message text. / / / '/' at beginning-of-line for comments. / '//' at beginning-of-line for *Cause: and *Action: fields. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////// Please maintain this map ////////////////////// / // 00001 - 04200 See netius.msg / . / . / 12150 - 12285 See net12150.msg / 12286 - 12499 ---(Reserved)--- / 12500 - 12530 NSG errors reportable by OSN (returned in cndo). / 12531 - 12629 NS (and NT errors reported as NS errors) reportable by OSN / 12630 - 12699 NA errors (returned by native services) / . / . / . / /////////////////////////// Please maintain this map ////////////////////// /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / / / / OWNER / Network and Management Products - Server Technologies / / MODIFIED / rachacos 04/04/01 - Define message for 12602 (NSECPLIMIT). / ppovinec 02/08/01 - Net8 --> Oracle Net rename. / ppovinec 07/18/00 - Listener's 8.2 error messages. / tclarke 02/25/00 - umcomment lost messages for oerr / ppovinec 07/16/99 - Make 12510 more meaningful. / vle 04/29/99 - fix misspelling / emalasky 11/10/98 - add catch-all handler error / emalasky 11/04/98 - add new direct handoff failure error / skanjila 09/04/98 - Add NAE Double Encryption Error Message. / emalasky 04/05/98 - add 8.1 service naming messsages / emalasky 12/09/97 - add NSG messages / emalasky 05/07/97 - 12505: no args, better cause / emalasky 05/01/97 - rollback 12505 / smckinle 04/21/97 - Change 12505 to take an SID parameter. / rwessman 03/19/97 - Eliminated references to Secure Network Services. It / rwessman 03/09/97 - split from netus.msg to correct bug in building / oraus.msg. / / / 12500 - 12530 Reserved for NSG errors reportable to OSN. / / tnslsnr errors... 12500, 00000, "TNS:listener failed to start a dedicated server process" // *Cause: The process of starting up a dedicated server process failed. // The executable could not be found or the environment may be set up // incorrectly. // *Action: Turn on tracing at the ADMIN level and reexecute the operation. // Verify that the ORACLE Server executable is present and has execute // permissions enabled. Ensure that the ORACLE environment is specified // correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being // called may not be installed on the local hard drive. Please check that // the correct Protocol Adapter are successfully linked. // If error persists, contact Oracle Customer Support. / 12501, 00000, "TNS:listener failed to spawn process" // *Cause: The listener failed to start the program specified. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the alias of the program started by listener in the system // LISTENER.ORA file. Make sure the program exists and the arguments are // correct. // Do not include in error manual. / 12502, 00000, "TNS:listener received no CONNECT_DATA from client" // *Cause: No CONNECT_DATA was passed to the listener. // *Action: Check that the service name resolved from TNSNAMES.ORA has // the CONNECT_DATA component of the connect descriptor. / 12504, 00000, "TNS:listener was not given the SID in CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: Check that the connect descriptor corresponding to the service // name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. / 12505, 00000, "TNS:listener could not resolve SID given in connect descriptor" // *Cause: The SID in the CONNECT_DATA was not found in the listener's tables. // *Action: Check to make sure that the SID specified is correct. // The SIDs that are currently registered with the listener can be obtained by // typing "LSNRCTL SERVICES ". These SIDs correspond to // SID_NAMEs in TNSNAMES.ORA, or db_names in INIT.ORA. // *Comment: This error will be returned if the database instance has not // registered with the listener; the instance may need to be started. / 12506, 00000, "TNS:listener was not given the ALIAS in CONNECT_DATA" // *Cause: The SID was missing from the CONNECT_DATA. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the command line or name-address mappings for the // ALIAS component of the CONNECT_DATA. // Do not include in error manual. / 12507, 00000, "TNS:listener could not resolve ALIAS given" // *Cause: The ALIAS in CONNECT_DATA was not found in the system // TNSNAMES.ORA file. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check to make sure that the ALIAS specified is correct. // Do not include in error manual. / 12508, 00000, "TNS:listener could not resolve the COMMAND given" // *Cause: The COMMAND given to listener is not supported. // *Action: This is not seen in normal use of SQL*Net. // *Comment: Check the COMMAND given to listener. This error is probably // caused by incompatible SQL*Net versions. // Do not include in error manual. / 12509, 00000, "TNS:listener failed to redirect client to service handler" // *Cause: The dispatcher terminated unexpectedly // *Action: Attempt to connect again and if the same error occurs, // contact the DBA to check the state of the dispatchers for this SID. // If the problem persists, turn on tracing in the listener to determine // the TNS error caused by the redirect. / 12510, 00000, "TNS:database temporarily lacks resources to handle the request" // *Cause: The dispatchers appear to be busy handling other requests. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers and/or dispatchers' limit on // number of connections/sessions that they can accept. / 12511, 00000, "TNS:service handler found but it is not accepting connections" // *Cause: The dispatchers notified the listener that they temporarily // do not accept new connections. // *Action: Attempt the connection again. If error persists, contact the DBA // to check the state of the dispatchers and/or ask him to increase the number // of dispatchers. / 12512, 00000, "TNS:service handler found but it has not registered a redirect address" // *Cause: The dispatcher just came up and has not had time yet to register // the address that a client should be redirected to. // *Action: Attempt the connection again. If error persists, ask // the DBA to increase the number of dispatchers. / 12513, 00000, "TNS:service handler found but it has registered for a different protocol" // *Cause: The dispatchers registered for this service are connected to // the listener by way of a different network protocol than that of the client. // *Action: Contact the DBA to register a dispatcher on your protocol. / 12514, 00000, "TNS:listener could not resolve SERVICE_NAME given in connect descriptor" // *Cause: The SERVICE_NAME in the CONNECT_DATA was not found in // the listener's tables. // *Action: Check to make sure that the SERVICE_NAME specified is correct. // *Comment: This error will be returned if the (database) service has not been // registered with the listener; a database instance that is part of this // service may need to be started or configured properly. / 12515, 00000, "TNS:listener could not find a handler for this presentation" // *Cause: None of the listener's known service handlers are registered // as supporting the presentation protocol required by the connecting client. // *Action: Check that the destination service is configured to accept the // presentation protocol. / 12516, 00000, "TNS:listener could not find available handler with matching protocol stack" // *Cause: None of the known and available service handlers for the given // SERVICE_NAME support the client's protocol stack: transport, session, // and presentation protocols. // *Action: Check to make sure that the service handlers (e.g. dispatchers) // for the given SERVICE_NAME are registered with the listener, are accepting // connections, and that they are properly configured to support the desired // protocols. / 12517, 00000, "TNS:listener could not find service handler supporting direct handoff" // *Cause: None of the known service handlers are registered as supporting // direct handoff as required for this client connection. // *Action: Check that the instance(s) are configured properly for direct // handoff, and are versions of Oracle that support direct handoff. / 12518, 00000, "TNS:listener could not hand off client connection" // *Cause: The process of handing off a client connection to another process // failed. // *Action: Turn on listener tracing and re-execute the operation. Verify // that the listener and database instance are properly configured for // direct handoff. If problem persists, call Oracle Support. // *Comment: The problem can be worked around by configuring dispatcher(s) // to specifically handle the desired presentation(s), and connecting // directly to the dispatcher, bypassing the listener. / 12519, 00000, "TNS:no appropriate service handler found" // *Cause: The listener could not find any available service handlers that // are appropriate for the client connection. // *Action: Run "lsnrctl services" to ensure that the instance(s) have // registered with the listener, and are accepting connections. / 12520, 00000, "TNS:listener could not find available handler for requested type of server" // *Cause: None of the known and available service handlers for requested type // of server (dedicated or shared) are appropriate for the client connection. // *Action: Run "lsnrctl services" to ensure that the instance(s) have // registered with the listener and that the appropriate handlers are // accepting connections. / 12521, 00000, "TNS:listener could not resolve INSTANCE_NAME given in connect descriptor" // *Cause: The INSTANCE_NAME in the CONNECT_DATA was not found in // the listener's tables for the specified SERVICE_NAME. // *Action: Check to make sure that the INSTANCE_NAME specified is correct. // *Comment: This error will be returned if the database instance has not // registered with the listener or it has registered under different service; // the instance may need to be started. / 12522, 00000, "TNS:listener could not find available instance with given INSTANCE_ROLE" // *Cause: There are not any available and appropriate database instances // registered with the listener, that are part of the service identified by // SERVICE_NAME given in the connect descriptor and that have the specified // INSTANCE_ROLE (and INSTANCE_NAME, if specified). // *Action: Check to make sure that the INSTANCE_ROLE specified is correct. // Run "lsnrctl services" to ensure that the instance(s) have registered with // the listener and that they are ready to accept connections. / 12523, 00000, "TNS:listener could not find instance appropriate for the client connection" // *Cause: The listener could not find any available (database) instances, // that are appropriate for the client connection. // *Action: Run "lsnrctl services" to ensure that the instance(s) are // registered with the listener, and have status READY. / 12524, 00000, "TNS:listener could not resolve HANDLER_NAME given in connect descriptor" // *Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener's // tables for the specified SERVICE_NAME and INSTANCE_NAME. // *Action: Check to make sure that the HANDLER_NAME specified is correct. // *Comment: This error will be returned if the database instance and/or its // service handlers have not been registered with the listener or they have // been registered for different service; the instance may need to be started. / / This line is an OSN Magic Cookie. Don't eat it. Last NSG error in 2.0.9. / / //////////////////////////////////////////////////////////////////// / / 12531 - 12629 ns errors reportable to osn: / / 12531 - 15609 ns primary errors / 12610 - 12629 ns secondary errors / / A primary may (optionally) be qualified by a secondary / error. For example: 12531 ("invalid argument") might / be qualified by 12617 ("bad 'what' value"). / 12531, 00000, "TNS:cannot allocate memory" // *Cause: Sufficient memory could not be allocated to perform the desired // activity. // *Action: Either free some resource for TNS, or add more memory to the // machine. For further details, turn on tracing and reexecute the operation. / 12532, 00000, "TNS:invalid argument" // *Cause: An internal function received an invalid parameter. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12533, 00000, "TNS:illegal ADDRESS parameters" // *Cause: An illegal set of protocol adapter parameters was specified. In // some cases, this error is returned when a connection cannot be made to the // protocol transport. // *Action: Verify that the destination can be reached using the specified // protocol. Check the parameters within the ADDRESS section of // TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the // Oracle operating system specific documentation for your platform. // Protocols that resolve names at the transport layer (such as DECnet object // names) are vulnerable to this error if not properly configured or names are // misspelled. / 12534, 00000, "TNS:operation not supported" // *Cause: An internal function received a request to perform an // operation that is not supported (on this machine). // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12535, 00000, "TNS:operation timed out" // *Cause: The requested connection could not be completed within the timeout // period specified by the CONNECT_TIMEOUT parameter in listener.ora. This // error arises from the tnslsnr. // *Action: Either reconfigure CONNECT_TIMEOUT to be 0, which means // wait indefinitely, or reconfigure CONNECT_TIMEOUT to be some higher // value. Or, if the timeout is unacceptably long, turn on tracing // for further information. / 12536, 00000, "TNS:operation would block" // *Cause: An internal operation did not commence because to do so would // block the current process and the user has requested that operations be // non-blocking. // *Action: None needed; this is an information message. / 12537, 00000, "TNS:connection closed" // *Cause: "End of file" condition has been reached; partner has disconnected. // *Action: None needed; this is an information message. / 12538, 00000, "TNS:no such protocol adapter" // *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" // keyword-value pair in a TNS address) is unknown. If the supplied address // is typographically correct then the protocol adaptor is not installed. // *Action: Install the protocol adapter or correct typographically error, // as appropriate. Note: if the supplied address was derived from // resolving the service name, check the address in the appropriate file // (TNSNAMES.ORA, LISTENER.ORA or TNSNET.ORA). / 12539, 00000, "TNS:buffer over- or under-flow" // *Cause: Buffer too small for incoming data or too large for outgoing data. // *Action: This restriction (which is associated with CONNECT DATA) is not // normally visible to the user. For further details, turn on tracing and // reexecute the operation; contact Oracle Customer Support. / 12540, 00000, "TNS:internal limit restriction exceeded" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try. / 12541, 00000, "TNS:no listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12542, 00000, "TNS:address already in use" // *Cause: Specified listener address is already being used. // *Action: Start your listener with a unique address. / 12543, 00000, "TNS:destination host unreachable" // *Cause: Contact can not be made with remote party. // *Action: Make sure the network driver is functioning and the network is up. / 12544, 00000, "TNS:contexts have different wait/test functions" // *Cause: Two protocol adapters have conflicting wait/test functions. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12545, 00000, "Connect failed because target host or object does not exist" // *Cause: The address specified is not valid, or the program being // connected to does not exist. // *Action: Ensure the ADDRESS parameters have been entered correctly; the // most likely incorrect parameter is the node name. Ensure that the // executable for the server exists (perhaps "oracle" is missing.) // If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the // host name to a numeric IP address and try again. / 12546, 00000, "TNS:permission denied" // *Cause: User has insufficient privileges to perform the requested operation. // *Action: Acquire necessary privileges and try again. / 12547, 00000, "TNS:lost contact" // *Cause: Partner has unexpectedly gone away, usually during process // startup. // *Action: Investigate partner application for abnormal termination. On an // Interchange, this can happen if the machine is overloaded. / 12548, 00000, "TNS:incomplete read or write" // *Cause: A data send or receive failed. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12549, 00000, "TNS:operating system resource quota exceeded" // *Cause: The current user has exceeded the allotted resource assigned in the // operating system. // *Action: Acquire more operating system resource, or perform a different // function. / 12550, 00000, "TNS:syntax error" // *Cause: The supplied connect descriptor contains illegal syntax. // *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. / 12551, 00000, "TNS:missing keyword" // *Cause: The supplied connect descriptor is missing one or more TNS // keywords. // *Action: Check the syntax, and ensure all required keywords are present. / 12552, 00000, "TNS:operation was interrupted" // *Cause: An internal operation was interrupted and could not complete. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12554, 00000, "TNS:current operation is still in progress" // *Cause: An internal operation is still in progress. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12555, 00000, "TNS:permission denied" // *Cause: User has insufficient privileges to perform the requested operation. // *Action: Acquire necessary privileges and try again. / 12556, 00000, "TNS:no caller" // *Cause: TNS detected an incoming connect request but there was no caller. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12557, 00000, "TNS:protocol adapter not loadable" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter is // missing or one of its supporting libraries is missing then this error is // returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will include the name of the shared library (or DLL) that // could not be loaded. / 12558, 00000, "TNS:protocol adapter not loaded" // *Cause: On some platforms (such as OS/2) protocol adapters are loaded at // run-time. If the shared library (or DLL) for the protocol adapter has not // been loaded, then this error is returned. // *Action: For further details, turn on tracing and reexecute the operation. // The trace file will have the name of the shared library (or DLL) that has // not been loaded. / 12560, 00000, "TNS:protocol adapter error" // *Cause: A generic protocol adapter error occurred. // *Action: Check addresses used for proper protocol specification. Before // reporting this error, look at the error stack and check for lower level // transport errors.For further details, turn on tracing and reexecute the // operation. Turn off tracing when the operation is complete. / 12561, 00000, "TNS:unknown error" // *Cause: A generic protocol error occurred. // *Action: For further details, turn on tracing and reexecute the operation. / 12562, 00000, "TNS:bad global handle" // *Cause: Internal error - bad 'gbh' agrument passed to TNS from caller. // System may have been linked with old libraries. // *Action: Not normally visible to the user, contact Oracle Customer // Support. / 12564, 00000, "TNS:connection refused" // *Cause: The connect request was denied by the remote user (or TNS software). // *Action: Not normally visible to the user. For further details, turn on // tracing and reexecute the operation. / 12566, 00000, "TNS:protocol error" // *Cause: An unexpected TNS protocol error has occurred. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 12569, 00000, "TNS:packet checksum failure" // *Cause: The data received is not the same as the data sent. // *Action: Attempt the transaction again. If the error is persistent, turn // on tracing and reexecute the operation. / 12570, 00000, "TNS:packet reader failure" // *Cause: An error occurred during a data receive. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12571, 00000, "TNS:packet writer failure" // *Cause: An error occurred during a data send. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12574, 00000, "TNS:redirection denied" // *Cause: The connect request failed because it would have required // redirection and the caller has requested no redirections. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12582, 00000, "TNS:invalid operation" // *Cause: An internal function received an invalid request. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12583, 00000, "TNS:no reader" // *Cause: A send operation has been requested but partner has already // disconnected. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12585, 00000, "TNS:data truncation" // *Cause: A receive operation has completed with insufficient data // to satisfy the user's request. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12589, 00000, "TNS:connection not bequeathable" // *Cause: An attempt to hand-off a connection from one process to another // has failed because the protocol provider does not support it. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12590, 00000, "TNS:no I/O buffer" // *Cause: An attempt to perform an I/O operation failed because no buffer // was available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12591, 00000, "TNS:event signal failure" // *Cause: The TNS software is unable to signal an event occurrence. // *Action: For further details, turn on tracing and reexecute the operation. // If error persists, contact Oracle Customer Support. / 12592, 00000, "TNS:bad packet" // *Cause: An ill-formed packet has been detected by the TNS software. // *Action: For further details, turn on tracing and reexecute the // operation. If error persists, contact Oracle Customer Support. / 12593, 00000, "TNS:no registered connection" // *Cause: An attempt to solicit network event activity has failed because // no connections are registered for event notification. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12595, 00000, "TNS:no confirmation" // *Cause: TNS is unable to get requested confirmation acknowledgement from // remote partner. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12596, 00000, "TNS:internal inconsistency" // *Cause: TNS has detected an internal inconsistency. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12597, 00000, "TNS:connect descriptor already in use" // *Cause: Internal error - illegal use of connect descriptor. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12598, 00000, "TNS:banner registration failed" // *Cause: The registration of a product banner with the Oracle server failed. // *Action: This is an error which is not normally visible externally. Enable // tracing and attempt to repeat the error. If it occurs // again, contact Oracle Customer Support. / 12599, 00000, "TNS:cryptographic checksum mismatch" // *Cause: The data received is not the same as the data sent. // *Action: Attempt the transaction again. If error persists, check // (and correct) the integrity of your physical connection. / 12600, 00000, "TNS: string open failed" // *Cause: The creation of a string in ORACLE NLS format failed. // *Action: This is an internal error, enable tracing and attempt to repeat the // error. If it occurs again, contact Oracle Customer Support. / 12601, 00000, "TNS:information flags check failed" // *Cause: The TNS information flags set by the process prior to connection // negotiation were not present after the negotiation was // finished. // *Action: This is an internal error. Enable tracing and attempt to repeat the // error. If it occurs again, contact Oracle Customer // Support. / 12602, 00000, "TNS: Connection Pooling limit reached" // *Cause: The operation failed because maximum active current connections has // been reached. It may not be a real error when the Connection // Pooling feature is enabled. It is possible that the application // later re-issues the operation and successfully grabs the connection // pool slot and proceeds. // *Action: This is an internal error. Enable tracing and attempt to repeat the // error. If it occurs again, contact Oracle Customer // Support. / / 12610 - 12629 ns secondary errors / 12611, 00000, "TNS:operation is not portable" // *Cause: Attempted operation is not portable. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12612, 00000, "TNS:connection is busy" // *Cause: Attempted operation failed because it conflicts with an on-going // action or status of the connection. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12615, 00000, "TNS:preempt error" // *Cause: A request to service an event failed because no event notification // has yet been posted. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12616, 00000, "TNS:no event signals" // *Cause: The TNS software is unable to enable event signals. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / /12617, 00000, "TNS:bad 'what' type" // *Cause: The operation failed because the type of data specified is unknown. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. Iferror persists, contact // Oracle Customer Support. / 12618, 00000, "TNS:versions are incompatible" // *Cause: The two machines are running incompatible versions of TNS. // *Action: Check the version numbers, and upgrade the machine with the // smaller one. / 12619, 00000, "TNS:unable to grant requested service" // *Cause: The connect request failed because requested service could not be // provided by the local TNS software. // *Action: If appropriate, reexecute with reduced service requirements. / 12620, 00000, "TNS:requested characteristic not available" // *Cause: The connect request failed because a requested transport // characteristic could not be supported by the remote TNS software. // *Action: If appropriate, reexecute with reduced requirements. / 12622, 00000, "TNS:event notifications are not homogeneous" // *Cause: An attempt to register a connection for event notification failed // because the event notification type conflicts with existing registrations. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12623, 00000, "TNS:operation is illegal in this state" // *Cause: Connection is half-duplex and a full-duplex operation was // attempted. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation. If error persists, contact // Oracle Customer Support. / 12624, 00000, "TNS:connection is already registered" // *Cause: An attempt to register a connection for event notification failed // because the connection is already registered. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12625, 00000, "TNS:missing argument" // *Cause: An operation failed because an argument was missing" // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12626, 00000, "TNS:bad event type" // *Cause: An attempt to register a connection for event notification failed // because the event type is unknown. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12628, 00000, "TNS:no event callbacks" // *Cause: An attempt to register a connection for event notification failed // because asynchronous callbacks are not available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / 12629, 00000, "TNS:no event test" // *Cause: An attempt to register a connection for event notification failed // because the ability to test for events is not available. // *Action: Not normally visible to the user. For further details, turn // on tracing and reexecute the operation and contact Oracle Customer // Support. / / 12630 - 12699 Reserved for NA errors. / 12630, 00000, "Native service operation not supported" // *Cause: An operation requested by a user is not supported by the native // services component. // *Action: This may be an internal error if the operation should have been // supported. / 12631, 00000, "Username retrieval failed" // *Cause: The authentication service failed to retrieve the name of a user. // *Action: Enable tracing to determine which routine is failing. / 12632, 00000, "Role fetch failed" // *Cause: The authentication service failed to retrieve one of the user's // roles. // *Action: Enable tracing to determine which routine is failing. / 12633, 00000, "No shared authentication services" // *Cause: The list of authentication services specified by the user does not // match those supported by the process. // *Action: Either specify another list or relink the executable with the // desired services. / 12634, 00000, "Memory allocation failed" // *Cause: Process was unable to allocate memory. // *Action: Terminate other processes in order to reclaim needed memory. / 12635, 00000, "No authentication adapters available" // *Cause: The executable was not linked with any authentication service // adapters but the sqlnet.ora parameter that determines whether or // not authentication is required was set to true. // *Action: Either disable the parameter or relink the executable with service // adapters. / 12636, 00000, "Packet send failed" // *Cause: A process was unable to send a packet to another process. // Possible causes are: // 1. The other process was terminated. // 2. The machine on which the other process is running went down. // 3. Some other communications error occurred. // *Action: If the cause is not obvious, contact Oracle Customer Support. / 12637, 00000, "Packet receive failed" // *Cause: A process was unable to receive a packet from another process. // Possible causes are: // 1. The other process was terminated. // 2. The machine on which the other process is running went down. // 3. Some other communications error occurred. // *Action: If the cause is not obvious, contact Oracle Customer Support. / 12638, 00000, "Credential retrieval failed" // *Cause: The authentication service failed to retrieve the credentials of a // user. // *Action: Enable tracing to determine the exact error. / 12639, 00000, "Authentication service negotiation failed" // *Cause: No match was found between the types of authentication services // that the client supports and those that the server is using. // *Action: Possible solutions: // 1. Change the entry in sqlnet.ora that determines which services // are to be used. // 2. Relink the client with at least one of the authentication // service adapters that the server supports. // 3. Relink the server with at least one of the authentication // service adapters that the client supports. // 4. Disable authentication on both the client and server. / 12640, 00000, "Authentication adapter initialization failed" // *Cause: The function specified in the authentication table entry for the // service failed. // *Action: Enable tracing to determine the exact error. / 12641, 00000, "Authentication service failed to initialize" // *Cause: The authentication service failed during initialization. // *Action: Enable tracing to determine the exact error. / 12642, 00000, "No session key" // *Cause: A process has no session key associated with it because the // authentication service being used does not use one. // *Action: If a session key is required, use another authentication service. / 12643, 00000, "Client received internal error from server" // *Cause: The client process received an error from the server that indicated // that an internal SQL*Net native services error had occurred. // *Action: Enable tracing on both processes and attempt to recreate the // problem. If successful in recreating the problem, contact Oracle // Customer Support. / 12644, 00000, "Authentication service initialization failed" // *Cause: The routine called to initialize the authentication adapter failed. // *Action: Enable tracing to determine the exact error. A likely cause is that // memory is exhausted. / 12645, 00000, "Parameter does not exist." // *Cause: A sqlnet.ora parameter from which a value was needed does not // exist. // *Action: Set the parameter in the parameter file. / 12646, 00000, "Invalid value specified for boolean parameter" // *Cause: The value specified for a parameter was set to a value other than // true/false or on/off. // *Action: Correct the value of the parameter. / 12647, 00000, "Authentication required" // *Cause: The parameter that controls whether authentication is required was // set to true, but the executable does not have an // authentication service linked in. // *Action: Either re-link the executable with an authentication service // adapter or disable the parameter. / 12648, 00000, "Encryption or data integrity algorithm list empty" // *Cause: A SQL*Net list-of-algorithms parameter was empty, e.g. // "()". // *Action: Change the list to contain the name of at least one // installed algorithm, or remove the list entirely if every // installed algorithm is acceptable. / 12649, 00000, "Unknown encryption or data integrity algorithm" // *Cause: A SQL*Net list-of-algorithms parameter included an // algorithm name that was not recognized. // *Action: Either remove that algorithm name, correct it if it was // misspelled, or install the driver for the missing // algorithm. / 12650, 00000, "No common encryption or data integrity algorithm" // *Cause: The client and server have no algorithm in common for // either encryption or data integrity or both. // *Action: Choose sets of algorithms that overlap. In other words, // add one of the client's algorithm choices to the server's // list or vice versa. / 12651, 00000, "Encryption or data integrity algorithm unacceptable" // *Cause: The algorithm the server chose to use for encryption or // data integrity was not one of the choices acceptable to // the client. This is either the result of an internal // error, of a network data transmission error, or of // deliberate tampering with the transmitted data. // *Action: For further details, turn on tracing, re-execute the // operation, and contact Oracle Customer Support. / 12652, 00000, "String truncated" // *Cause: Not enough memory was allocated for a string so it had to be // trucated // *Action: If it is OK that the string is truncated, then it is not an // error. Otherwise, call the routine that reported the error // again with a larger string buffer. / 12653, 00000, "Authentication control function failed" // *Cause: The control function utilized by the authentication service driver // failed. // *Action: Enable tracing to determine the exact error. / 12654, 00000, "Authentication conversion failed" // *Cause: The authentication service was unable to convert the credentials // of a user from the format specific to the format into the // ORACLE format. // *Action: Enable tracing to determine the exact error. / 12655, 00000, "Password check failed" // *Cause: The authentication service being used was unable to verify the // provided password. // *Action: Enable tracing to determine the exact error. / 12656, 00000, "Cryptographic checksum mismatch" // *Cause: The cryptographic checksum received with a packet of // incoming data didn't match the checksum computed by the // receiving end. This indicates that the packet was // tampered with or otherwise corrupted in transit. // *Action: Look for sources of data corruption, perhaps including // deliberate tampering. / 12657, 00000, "No algorithms installed" // *Cause: The near side of the connection required the use of a // service (either encryption or checksumming) when no // algorithms for that service were installed. // *Action: Remove the "ON" requirement for that service. / 12658, 00000, "ANO service required but TNS version is incompatible" // *Cause: A client process that is running an earlier version of TNS // attempted toconnect but the connection failed because the server // process required that an ANO service (authentication, encryption, // etc.) be used. // *Action: Relink the calling executable and retry the connection or eliminate // the requirement that the service be used on the server side. / 12659, 00000, "Error received from other process" // *Cause: An error was received by one or more services from the process on // the other side of the connection. // *Action: Enable tracing to determine the exact error(s). // The error(s) is (are) not returned directly because an error // generated by a server may not make sense on the client side and // vice-versa. / 12660, 00000, "Encryption or crypto-checksumming parameters incompatible" // *Cause: One side of the connection specified "REQUIRED" for encryption // or crypto-checksumming, while the other side specified "REJECTED". // *Action: Change the "REQUIRED" side to "REQUESTED" if the // you want encryption or crypto-checksumming to be optional, or // change the "REJECTED" side to "ACCEPTED" if you do not // want the service to be optional. / 12661, 00000, "Protocol authentication to be used" // *Cause: The SQL*Net authentication service has determined that the SQL*Net // transport protocol in use is to be utilized to authenticate a // user's identity. // *Action: This error is used solely to communicate information between the // authentication service and the SQL*Net session layer and should not // be visible to the user. // If the error is seen, contact Oracle customer support. / 12662, 00000, "proxy ticket retrieval failed" // *Cause: The authentication adapter used by SQL*Net failed to retrieve the // credentials needed to authenticate a database link. // *Action: Enable tracing to determine the exact error. / 12663, 00000, "Services required by client not available on the server" // *Cause: Service(s) that was (were) required by the client process were not // available on the server process. // *Action: Configure the server with the services required by the client (best // solution) or delete the requirement from the configuration // file of the client (least secure). / 12664, 00000, "Services required by server not available on the client" // *Cause: Service(s) that was (were) required by the server process were not // available on the client process. // *Action: Configure the client with the services required by the server (best // solution) or delete the requirement from the configuration // file of the server (least secure). / 12665, 00000, "NLS string open failed" // *Cause: A native service was unable to make a string available for use by // the National Language Support component. // *Action: Make sure the National Language Support component has been // properly. If it has, enable tracing and report the problem // to Customer Support. / 12666, 00000, "Dedicated server: outbound transport protocol different from inbound" // *Cause: The protocol specified for an externally-identified outbound // connection from a dedicated server (database link) was not the same // as that used for the inbound connection. It is not possible for // SQL*Net to authenticate a proxy connection that uses a protocol // that is different from that which was used for the connection to // the dedicated server. // *Action: Specify the same protocol in the SQL*Net connect string or alias // for the outbound connection as that used for the inbound // connection / 12667, 00000, "Shared server: outbound transport protocol different from inbound" // *Cause: The protocol specified for an externally-identified outbound // connection from a shared server (database link) was not the same as // as that used for the inbound connection. It is not possible for // SQL*Net to authenticate a proxy connection that uses a protocol // that is different from that which was used for the connection to // the shared server. // *Action: Specify the same protocol in the SQL*Net connect string or alias // for the outbound connection as that used for the inbound // connection / 12668, 00000, "Dedicated server: outbound protocol does not support proxies" // *Cause: The protocol specified to perform an externally-identified proxy // connection (database link) from a dedicated server does // not support proxy connections. // *Action: Specify a protocol in the SQL*Net connect string or alias used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in SQL*Net, the protocol used for // the proxy connection must the same as that used for the // connection from the client to the server. / 12669, 00000, "Shared server: outbound protocol does not support proxies" // *Cause: The protocol specified to perform an externally-identified proxy // connection (database link) from a shared server does not support // proxy connections. // *Action: Specify a protocol in the SQL*Net connect string or alias used for // the connection that does support externally-authenticated proxy // connections. // NOTE: Because of a limitation in SQL*Net, the protocol used for // the proxy connection must the same as that used for the // connection from the client to the server. / 12670, 00000, "Incorrect role password" // *Cause: A password supplied for a role could not be validated by the // authentication service. // *Action: Supply the correct password. / 12671, 00000, "Shared server: adapter failed to save context" // *Cause: The adapter for the authentication service failed when it tried to // save the data needed for proxy connections (database // links) through the multi-threaded server. // *Action: Enable tracing to determine the exact error. Contact Oracle // Customer Support if the reason is not obvious. / 12672, 00000, "Database logon failure" // *Cause: The authentication service adapter in use encountered an error // it attempted to validate the logon attempt of a user. // *Action: Enable tracing to determine the exact error encountered by the // adapter. / 12673, 00000, "Dedicated server: context not saved" // *Cause: A connection was marked as being a proxy connection (database link) // from a dedicated server but no inbound context was present. // *Action: This error should not normally be visible to the user. Contact // Oracle Customer Support. / 12674, 00000, "Shared server: proxy context not saved" // *Cause: A connection was marked as being a proxy connection (database link) // from a shared server but no inbound context was present. // *Action: This error should not normally be visible to the user. Contact // Oracle Customer Support. / 12675, 00000, "External user name not available yet" // *Cause: The authentication service in use was not able to return the // external name of a user of the ORACLE server because it is not // available to the service yet. // *Action: This is just an informational message and should not normally be // visible to the user. If the error does appear, contact Oracle // Customer Support. / 12676, 00000, "Server received internal error from client" // *Cause: The server process received an error from the client which // indicated that an internal SQL*Net native services error had // occurred. // *Action: Enable tracing on both processes and attempt to recreate the // problem. If the problem recurs, contact Oracle Customer // Support. / 12677, 00000, "Authentication service not supported by database link" // *Cause: The authentication service used by the proxy process (database // link) was unable to find the adapter being used by the client // in its list of authentication mechanisms. // *Action: Specify an authentication adapter that is shared by the client and // the server being used for the database link. / 12678, 00000, "Authentication disabled but required" // *Cause: The configuration parameters that control whether SQL*Net // authentication is disabled or required were both set to TRUE. // *Action: Set one or both of the parameters to FALSE. / 12679, 00000, "Native services disabled by other process but required" // *Cause: The remote process has disabled native services but the local // process requires them. // *Action: Enable native services on the remote process or disable them // locally. / 12680, 00000, "Native services disabled but required" // *Cause: The process has disabled native services but at least one service // is required. // *Action: Enable native services or change the configuration file so that // none of the available services are required. / 12681, 00000, "Login failed: the SecurID card does not have a pincode yet" // *Cause: The SecurID card that is used to logon to Oracle, does not have // a pincode assigned to it. // *Action: Use one of the programs supplied by Security Dynamics to assign // a pincode to the card. / 12682, 00000, "Login failed: the SecurID card is in next PRN mode" // *Cause: The SecurID card and the SecurID server are out of sync and the // server requires the next cardcode to resynchronize the card. // *Action: Use one of the programs supplied by Security Dynamics to // resynchronize the SecurID card. / 12683, 00000, "encryption/crypto-checksumming: no Diffie-Hellman seed" // *Cause: The "sqlnet.crypto_seed" parameter is missing from the // SQLNET.ORA parameters file for SQL*Net. // *Action: Add this line to SQLNET.ORA: // sqlnet.crypto_seed = "randomly-chosen text" / 12684, 00000, "encryption/crypto-checksumming: Diffie-Hellman seed too small" // *Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA // parameter file for SQL*Net is too small. // *Action: Add more randomly-chosen text to it, perhaps using Network // Manager. / 12685, 00000, "Native service required remotely but disabled locally" // *Cause: A native service is required by the remote process but native // services have been disabled locally. // *Action: Enable native services locally or change the configuration // parameters on the remote host so that no native services are // required. / 12686, 00000, "Invalid command specified for a service" // *Cause: An operation which does not exist was specified for a native // service. // *Action: This is a programming error and should not normally be visible to // the user. If the error does appear, contact Oracle Customer // Support. / 12687, 00000, "Database link failed: credentials expired" // *Cause: The credentials that are used to authenticate the user for the // requested database link have expired. // *Action: Renew your credentials. Refer to the documentation specific for // your Network Authentication Adapter on how to do this. / 12688, 00000, "Login failed: the SecurID server rejected the new pincode" // *Cause: There are a number of reasons why the SecurID server would refuse // a pincode: // - The user might not have permission to make up his own pincode. // - The pincode was either too short or too long. Valid pincodes // consist of minimal four, but no more than eight characters. // - The pincode contains any non alpha-numeric characters. // *Action: Reexecute the operation and make sure to use a pincode that // satisfies the above requirements. If the problem persists, turn // on tracing at the Oracle Server side of the connection and // examine the trace file for the exact error. / 12689, 00000, "Server Authentication required, but not supported" // *Cause: Server Authentication is required for this connection, but not // supported by both sides of the connection. // *Action: Make sure both sides of the connection have the correct version of // Advanced Networking Option, and that the Authentication Adapter // supports Server Authentication. / 12690, 00000, "Server Authentication failed, login cancelled" // *Cause: Server Authentication is required, but the server's credentials // were found invalid by the client. // *Action: Make sure that the server has a valid set of credentials. Refer to // your authentication adapter specific documentation on how to do // this. / 12696, 00000, "Double Encryption Turned On, login disallowed" // *Cause: The user is using a Secure Protocol Adapter that has Encryption // turned ON as well as ANO Encryption. // *Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption // if possible. Refer to Oracle Advanced Security Administrator's // Guide on how to do this. / 12699, 00000, "Native service internal error" // *Cause: An internal error occurred in the native services component. // *Action: Enable tracing to determine the exact error. Contact Oracle // Customer Support. / / / This line is an OSN Magic Cookie. Don't eat it. / All new error messages up to 12699 ___MUST___ be placed in this file / above and before and preceding the preceding Magic Cookie line. / / This line is an OSN Magic Cookie. Don't eat it. Last NS error in 2.0.9. / / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12700 - 12999: Reserved. / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / /////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////// / / 12700 - 12799 Reserved for NLS / 12700, 00000, "invalid NLS parameter value (%s)" // *Cause: An invalid or unknown NLS configuration parameter was specified. // *Action: 12701, 00000, "CREATE DATABASE character set is not known" // *Cause: The character set specified when creating the database is unknown. // *Action: 12702, 00000, "invalid NLS parameter string used in SQL function" // *Cause: An unknown parameter name or invalid value is specified in a NLS // parameter string. // *Action: 12703, 00000, "this character set conversion is not supported" // *Cause: The requested conversion between two character sets in the CONVERT // function is not implemented // *Action: 12704, 00000, "character set mismatch" // *Cause: One of the following: // - The string operands(other than an nlsparams argument) to an // operator or built-in function do not have the same character // set. // - An nlsparams operand is not in the database character set. // - String data with character set other than the database character // set is passed to a built-in function not expecting it. // - The second argument to CHR() or CSCONVERT() is not CHAR_CS or // NCHAR_CS. // - A string expression in the VALUES clause of an INSERT statement, // or the SET clause of an UPDATE statement, does not have the // same character set as the column into which the value would // be inserted. // - A value provided in a DEFAULT clause when creating a table does // not have the same character set as declared for the column. // - An argument to a PL/SQL function does not conform to the // character set requirements of the corresponding parameter. // *Action: 12705, 00000, "invalid or unknown NLS parameter value specified" // *Cause: The NLS parameter value specified in an alter session statement // is not valid or not implemented. // *Action: 12706, 00000, "this CREATE DATABASE character set is not allowed" // *Cause: It is not allowed to create a database on a native ASCII-based // machine using an EBCDIC-based character set, and vice versa. // *Action: 12707, 00000, "error while getting create database NLS parameter %s" // *Cause: Internal error // *Action: 12708, 00000, "error while loading create database NLS parameter %s" // *Cause: Internal error // *Action: 12709, 00000, "error while loading create database character set" // *Cause: Internal error // *Action: 12710, 00000, "CREATE CONTROLFILE character set is not known" // *Cause: The character set specified when creating the controlfile is unknown. // *Action: 12711, 00000, "this CREATE CONTROLFILE character set is not allowed" // *Cause: It is not allowed to create a controlfile on a native ASCII-based // machine using an EBCDIC-based character set, and vice versa. 12712, 00000, "new character set must be a superset of old character set" // *Cause: When you ALTER DATABASE ... CHARACTER SET, the new // character set must be a superset of the old character set. // For example, WE8ISO8859P1 is not a superset of the WE8DEC. // *Action: Specify a superset character set. 12713, 00000, "Character data loss in NCHAR/CHAR conversion" // *Cause: When character set conversion happens between CHAR and NCHAR // either implicitly or explicitly, some characters are lost // due to no mapping characters in the destination character set. // *Action: Make sure all the characters can be mapped to destination // character set or set NLS_NCHAR_CONV_EXCP to be FALSE. 12714, 00000, "invalid national character set specified" // *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national // character set // *Action: Ensure that the specified national character set is valid 12715, 00000, "invalid character set specified" // *Cause: The character set specified is not allowed for this operation // or is invalid // *Action: Ensure that the specified character set is valid 12716, 00000, "Cannot ALTER DATABASE CHARACTER SET when CLOB data exists" // *Cause: CLOB data changes representation to Unicode when converting to a // multibyte character set and must be migrated // *Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated // by methods such as import/export 12717, 00000, "Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists" // *Cause: NCLOB data changes representation to Unicode when converting to a // multibyte character set and must be migrated // *Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated // by methods such as import/export 12718, 00000, "operation requires connection as SYS" // *Cause: This command can only be run when connecting as SYS // *Action: Connect as SYS to run this command 12719, 00000, "operation requires database is in RESTRICTED mode" // *Cause: This command can only be run when the database is in RESTRICTED mode // *Action: Ensure that the system is in RESTRICTED mode 12720, 00000, "operation requires database is in EXCLUSIVE mode" // *Cause: This command can only be run when the database is in EXCLUSIVE mode // *Action: Ensure that the system is in EXCLUSIVE mode 12721, 00000, "operation cannot execute when other sessions are active" // *Cause: This command can only be run when there are no other sessions active // *Action: Ensure there are no other connections to the database / / 12800 - 12899 Reserved for Parallel Query/Index Creation / / 12800, 00000, "system appears too busy for parallel query execution" // *Cause: load on system is too high to perform parallel queries. // *Action: re-execute serially or wait until system load is reduced. / 12801, 00000, "error signaled in parallel query server %s" // *Cause: A parallel query server reached an exception condition. // *Action: Check the following error message for the cause, and consult // your error manual for the appropriate action. // *Comment: This error can be turned off with event 10397, in which // case the server's actual error is signaled instead. / 12802, 00000, "parallel query server lost contact with coordinator" // *Cause: A parallel query server lost contact with the foreground // (coordinator) process/thread. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12803, 00000, "parallel query server lost contact with another server" // *Cause: A parallel query server lost contact with another server. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12804, 00000, "parallel query server appears to have died" // *Cause: Cannot find process information for a parallel query // server thread. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. / 12805, 00000, "parallel query server died unexpectedly" // *Cause: A parallel query server died unexpectedly, PMON cleaning // up the process. // *Action: Check your system for anomalies and reissue the statement. // If this error persists, contact your customer service // representative. See trace file for more details. / 12806, 00000, "could not get background process to hold enqueue" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact your customer service representative. / 12807, 00000, "process queue could not receive parallel query message" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // contact your customer service representative. / 12808, 00000, "cannot set %s_INSTANCES greater than number of instances %s" // *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES // using the ALTER SYSTEM command to a value larger than the number // of available instances. // *Action: See the accompanying message for the current allowable // maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES // to ALL. / 12809, 00000, "cannot set %s_INSTANCES when mounted in exclusive mode" // *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES // using the ALTER SYSTEM command while the database was mounted // in exclusive mode. // *Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless // running Oracle Real Application Clusters mounted in // CLUSTER_DATABASE mode. / 12810, 00000, "PARALLEL_MAX_SERVERS must be less than or equal to %s" // *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter // to a value higher than the maximum allowed by the system. // *Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to // the maximum specified in the accompanying message and retry. / 12811, 00000, "PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, %s" // *Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter // to a value higher than PARALLEL_MAX_SERVERS. // *Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to // PARALLEL_MAX_SERVERS (indicated in the accompanying message) // and retry. / 12812, 00000, "only one PARALLEL or NOPARALLEL clause may be specified" // *Cause: PARALLEL was specified more than once, NOPARALLEL was specified // more than once, or both PARALLEL and NOPARALLEL were specified // in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or // CLUSTER statement, or in a RECOVER command. // *Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and // reissue the statement. / 12813, 00000, "value for PARALLEL or DEGREE must be greater than 0" // *Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, // CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement. // *Action: Specify a degree of parallelism greater than 0 or specify // default parallelism using PARALLEL with no degree or using // DEGREE DEFAULT within a PARALLEL clause. / 12814, 00000, "only one CACHE or NOCACHE clause may be specified" // *Cause: CACHE was specified more than once, NOCACHE was specified more // than once, or both CACHE and NOCACHE were specified in a // CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER // statement. // *Action: Remove all but one of the CACHE or NOCACHE clauses and // reissue the statement. / 12815, 00000, "value for INSTANCES must be greater than 0" // *Cause: PARALLEL parameter specifying number of instances must // be a positive integer or DEFAULT // *Action: specify a positive integer or DEFAULT for INSTANCES // if parallelism across instances is desired. / 12816, 00000, "parallel create index fastpath operation" // *Cause: // *Action: set this event only under the supervision Oracle development // *Comment: this event permits fastpath index creation. it merges // sub-index in a quick but suboptimal fashion wrto space usage. // Level: the level indicates the number of rows in a branch block // that we are willing to copy before attempting fastpath operation. / 12817, 00000, "parallel query option must be enabled" // *Cause: A parallel query option feature has been invoked but this option // has not been enabled. // *Action: Enable the parallel query option. / 12818, 00000, "invalid option in PARALLEL clause" // *Cause: an unrecognized option was used within a PARALLEL clause. // *Action: specify any combination of DEGREE { | DEFAULT } and // INSTANCES { | DEFAULT } within the PARALLEL clause. / 12819, 00000, "missing options in PARALLEL clause" // *Cause: PARALLEL clause cannot be empty. // *Action: specify any combination of DEGREE { | DEFAULT } and // INSTANCES { | DEFAULT } within the PARALLEL clause. / 12820, 00000, "invalid value for DEGREE" // *Cause: invalid value for DEGREE was specified within a PARALLEL // clause. // *Action: specify a positive integer or DEFAULT for the DEGREE // option within a PARALLEL clause. / 12821, 00000, "invalid value for INSTANCES" // *Cause: invalid value for INSTANCES was specified within a PARALLEL // clause. // *Action: specify a positive integer or DEFAULT for the INSTANCES // option within a PARALLEL clause. / 12822, 00000, "duplicate option in PARALLEL clause" // *Cause: DEGREE or INSTANCES was specified more than once within // a PARALLEL clause. // *Action: specify each desired PARALLEL clause option only once. / 12823, 00000, "default degree of parallelism may not be specified here" // *Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was // specified in the PARALLEL clause of an ALTER DATABASE RECOVER // command. // *Action: respecify with an explicit degree of parallelism. / 12824, 00000, "INSTANCES DEFAULT may not be specified here" // *Cause: INSTANCES DEFAULT was specified in the PARALLEL clause // of an ALTER DATABASE RECOVER command // *Action: respecify with an explicit value for INSTANCES or omit // the INSTANCES option if single instance recovery is desired. / 12825, 00000, "explicit degree of parallelism must be specified here" // *Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER // command. // *Action: respecify with an explicit degree of parallelism. / 12826, 00000, "hung parallel query server was killed" // *Cause: parallel query server was hung and subsequently killed. // *Action: re-execute query and report suspicious events in trace // file to Oracle support representative if error persists. / 12827, 00000, "insufficient parallel query slaves available" // *Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than // minimum slaves were acquired // *Action: either re-execute query with lower PARALLEL_MIN_PERCENT or // wait until some running queries are completed, thus freeing // up slaves / 12828, 00000, "Can't start parallel transaction at a remote site" // *Cause: PDML transaction cannot be started because we are not in the // coordinator site of the distributed transaction. // *Action: Do not use PDML at remote sites. / 12829, 00000, "Deadlock - itls occupied by siblings at block %s of file %s" // *Cause: parallel statement failed because all itls in the current // block are occupied by siblings of the same transaction. // *Action: increase MAXTRANS of the block or reduce the degree of // parallelism for the statement. Reexecute the statement. // Report suspicious events in trace file to Oracle support // representative if error persists. / 12830, 00000, "Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE" // *Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a // command other than COMMIT or ROLLBACK was issued. // *Action: Execute COMMIT or ROLLBACK before issuing another SQL command. / 12831, 00000, "Must COMMIT or ROLLBACK after executing INSERT with APPEND hint" // *Cause: After executing an INSERT statement with an APPEND hint, a // command other than COMMIT or ROLLBACK was issued. // *Action: Execute COMMIT or ROLLBACK before issuing another SQL command. / 12832, 00000, "Could not allocate slaves on all specified instances" // *Cause: After executing a query on a global v$ fixed view, one or more // instances failed to allocate a slave to process query // *Action: To allow results to be returned by sucessfully allocated slaves, // execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, // or check parameters of instances / 12833, 00000, "Coordinator's instance not a member of parallel_instance_group" // *Cause: The coordinator's instance must be a member of the // parallel_instance_group in which this operation will be run. // *Action: Either add the coordinator's instance to the current // parallel_instance_group or change parallel_instance_group. / 12834, 00000, "Instance group name, '%s', too long, must be less than %s characters" // *Cause: The instance group name is too long. // *Action: Either shorten the name or get rid of the instance group. / 12835, 00000, "No instances are active in the GLOBAL_VIEW_ADMIN_GROUP" // *Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP // in order to execute a query on global views // *Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP / 12836, 00000, "Control delayed index maintenance event" // *Document: NO // *Cause: // *Action: Control whether a given index will use delayed maintenance. / 12837, 00000, "Delayed index maintenance debugging event" // *Document: NO // *Cause: // *Action: Control dumping of debugging information for dealyed maintenance / 12838, 00000, "cannot read/modify an object after modifying it in parallel" // *Cause: Within the same transaction, an attempt was made to add read or // modification statements on a table after it had been modified in parallel // or with direct load. This is not permitted. // *Action: Rewrite the transaction, or break it up into two transactions: // one containing the initial modification and the second containing the // parallel modification operation. / 12839, 00000, "cannot modify an object in parallel after modifying it" // *Cause: Within the same transaction, an attempt was made to perform // parallel modification operations on a table after it had been modified. // This is not permitted. // *Action: Rewrite the transaction or break it up into two transactions: // one containing the parallel modification and the second containing the // initial modification operation. / 12840, 00000, "cannot access a remote table after parallel/insert direct load txn" // *Cause: Within a transaction, an attempt was made to perform distributed // access after a PDML or insert direct statement had been issued. // *Action: Commit/rollback the PDML transaction first, and then perform // the distributed access, or perform the distributed access before the // first PDML statement in the transaction. / 12841, 00000, "Cannot alter the session parallel DML state within a transaction" // *Cause: Transaction in progress // *Action: Commit or rollback transaction and then re-execute / 12842, 00000, "schema modified during parallel execution" // *Cause: Schema modified during the parse phase of parallel processing // *Action: No action required, this error should never be seen by the user / 12843, 00000, "pdml lock not held properly on the table" // *Cause: The coodinator crashed or released the lock on the partition which // the slave is trying to aquire currently. // *Action: Check if the coordinator or some of the other slaves died. Also check // that the lock has not been corrupted. Issue the pdml again. /============================================================================ / 12900 - 12919 Reserved for execution errors introduced by / Default Temporary Tablespace /============================================================================ 12900, 00000, "must specify a default temporary tablespace for a locally managed database" // *Cause: a locally managed database must have a temporary tablespace other // than SYSTEM tablespace // *Action: specify the default temporary tablespace when creating a locally // managed database 12901, 00000, "default temporary tablespace must be of TEMPORARY type" // *Cause: in a locally managed database, default temporary tablespace // must be TEMPORARY type // *Action: 12902, 00000, "default temporary tablespace must be SYSTEM or of TEMPORARY type" // *Cause: in a dictionary managed database, default temporary tablespace // must be SYSTEM or TEMPORARY type // *Action: 12903, 00000, "default temporary tablespace must be an ONLINE tablespace" // *Cause: // *Action: 12904, 00000, "default temporary tablespace cannot be altered to PERMANENT type" // *Cause: // *Action: 12905, 00000, "default temporary tablespace cannot be brought OFFLINE" // *Cause: // *Action: 12906, 00000, "cannot drop default temporary tablespace" // *Cause: // *Action: 12907, 00000, "tablespace %s is already the default temporary tablespace" // *Cause: // *Action: 12908, 00000, "cannot specify SYSTEM as default temporary tablespace when creating database" // *Cause: // *Action: 12909, 00000, "TEMPORARY keyword expected" // *Cause: // *Action: 12910, 00000, "cannot specify temporary tablespace as default tablespace" // *Cause: attempt to assign a temporary tablespace to be a user's // default tablespace // *Action: assign a permanent tablespace to be the default tablespace 12911, 00000, "permanent tablespace cannot be temporary tablespace" // *Cause: attempt to assign a permanent tablespace to be a user's // temporary tablespace // *Action: assign a temporary tablespace to be user's temporary tablespace / / 12844 - 12849 unused (parallel query/index creation messages) / / 12980 - 12999 Reserved for Drop Column / 12980, 00000, "checkpoint option not allowed with SET UNUSED" // *Cause: An attempt was made to specify checkpoint option with SET UNUSED. // *Action: Remove checkpoint option. 12981, 00000, "cannot drop column from an object type table" // *Cause: An attempt was made to drop a column from an object type table. // *Action: This action is not allowed. 12982, 00000, "cannot drop column from a nested table" // *Cause: An attempt was made to drop a column from a nested table. // *Action: This action is not allowed. 12983, 00000, "cannot drop all columns in a table" // *Cause: An attempt was made to drop all columns in a table. // *Action: Make sure at least one column remains in the table after // the drop column operation. 12984, 00000, "cannot drop partitioning column" // *Cause: An attempt was made to drop a column used as the partitioning key. // *Action: This action is not allowed. 12985, 00000, "tablespace '%s' is read only, cannot drop column" // *Cause: An attempt was made to drop column from a partition/subpartition // on a read only tablespace. // *Action: Set the tablespace to read write and resubmit statement. 12986, 00000, "columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE" // *Cause: An attempt was made to access a table with columns in partially // dropped state (i.e., drop column operation was interrupted). // *Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop // column operation before accessing the table. 12987, 00000, "cannot combine drop column with other operations" // *Cause: An attempt was made to combine drop column with other // ALTER TABLE operations. // *Action: Ensure that drop column is the sole operation specified in // ALTER TABLE. 12988, 00000, "cannot drop column from table owned by SYS" // *Cause: An attempt was made to drop a column from a system table. // *Action: This action is not allowed 12989, 00000, "invalid value for checkpoint interval" // *Cause: An invalid checkpoint interval specified in statement. // Checkpoint interval must be between 0 and (2^31-1). // *Action: Correct checkpoint interval and resubmit statement 12990, 00000, "duplicate option specified" // *Cause: Duplicate option specified in statement. // *Action: Remove the duplicate option and resubmit statement. 12991, 00000, "column is referenced in a multi-column constraint" // *Cause: An attempt was made to drop a column referenced by some // constraints. // *Action: Drop all constraints referencing the dropped column or // specify CASCADE CONSTRAINTS in statement. 12992, 00000, "cannot drop parent key column" // *Cause: An attempt was made to drop a parent key column. // *Action: Drop all constraints referencing the parent key column, or // specify CASCADE CONSTRAINTS in statement. 12993, 00000, "tablespace '%s' is offline, cannot drop column" // *Cause: An attempt was made to drop a column from a partition/subpartition // on an offline tablespace. // *Action: Bring the tablespace online and resubmit statement. 12994, 00000, "drop column option only allowed once in statement" // *Cause: An attempt was made to repeat the drop column option in // a single statement. // *Action: Separate drop column options into different statements and // resubmit statements. 12995, 00000, "no columns in partially dropped state" // *Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement // while there are no partially dropped columns. // *Action: Cannot submit this statement. 12996, 00000, "cannot drop system-generated virtual column" // *Cause: An attempt was made to drop a virtual column generated by // the system. 12997, 00000, "cannot drop primary key column from an index-organized table" // *Cause: An attempt was made to drop a primary key column from an index- // organized table. // *Action: This action is not allowed. / / 13000 - 13499 (Reserved for Oracle8 Spatial Cartridge) / 13000 - 13199 Spatial Data Option and Spatial Cartridge 8.0 / 13200 - 13499 Spatial Cartridge 8.1.3 / 13200 - 13249 Extensible spatial index / 13250 - 13259 SDO_Metadata Package / 13260 - 13279 Migration utility and package / 13280 - 13329 New spatial operators / 13330 - 13339 SDO_RELATE package / 13340 - 13359 Validate Geometry package / 13360 - 13499 Reserved for future use / 13000, 00000, "dimension number is out of range" // *Cause: The specified dimension is either smaller than 1 or greater than // the number of dimensions encoded in the HHCODE. // *Action: Make sure that the dimension number is between 1 and the maximum // number of dimensions encoded in the HHCODE. / 13001, 00000, "dimensions mismatch error" // *Cause: The number of dimensions in two HHCODEs involved in a binary // HHCODE operation do not match. // *Action: Make sure that the number of dimensions in the HHCODEs match. / 13002, 00000, "specified level is out of range" // *Cause: The specified level is either smaller than 1 or greater // than the maximum level encoded in an HHCODE. // *Action: Verify that all levels are between 1 and the maximum number of // levels encoded in the HHCODE. / 13003, 00000, "the specified range for a dimension is invalid" // *Cause: The specifed range for a dimension is invalid. // *Action: Make sure that the lower bound (lb) is less than the upper bound // (ub). / 13004, 00000, "the specified buffer size is invalid" // *Cause: The buffer size for a function is not valid. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13005, 00000, "recursive HHCODE function error" // *Cause: An error occured in a recursively called HHCODE function. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13006, 00000, "the specified cell number is invalid" // *Cause: The cell identifier is either less than 0 or greater that // (2^ndim - 1). // *Action: Make sure that the cell identifier is between 0 and (2^ndim - 1). / 13007, 00000, "an invalid HEX character was detected" // *Cause: A character that is not in the range [0-9] or [A-Fa-f] was // detected. // *Action: Verify that all characters in a string are in [0-9] or [A-Fa-f]. / 13008, 00000, "the specified date format has an invalid component" // *Cause: Part of specified date format is invalid. // *Action: Verify that the date format is valid. / 13009, 00000, "the specified date string is invalid" // *Cause: The specified date string has a bad component or does not match // the specified format string. // *Action: Make sure that the components of the date string are valid and // that the date and format strings match. / 13010, 00000, "an invalid number of arguments has been specified" // *Cause: An invalid number of arguments was specified for an SDO function. // *Action: Verify the syntax of the function call. / 13011, 00000, "value is out of range" // *Cause: A specifed dimension value is outside the range defined for that // dimension. // *Action: Make sure that all values to be encoded are within the defined // dimension range. / 13012, 00000, "an invalid window type was specifed" // *Cause: An invalid window type was specifed. // *Action: Valid window types are RANGE, PROXIMITY, POLYGON. / 13013, 00000, "the specified topology was not INTERIOR or BOUNDARY" // *Cause: A topology was specified that was not INTERIOR or BOUNDARY. // *Action: Make sure that INTERIOR or BOUNDARY is used to describe an // HHCODE's topology. / 13014, 00000, "a topology identifier outside the range of 1 to 8 was specified" // *Cause: A topology identifier outside the range of 1 to 8 was specified // *Action: Specify a topology in the range of 1 to 8. / 13015, 00000, "the window definition is not valid" // *Cause: The number of values used to define the window does not // correspond to the window type. // *Action: Verify that the number of values used to defined the window is // correct for the window type and number of dimensions. / 13016, 00000, "bad partition definition" // *Cause: The partition common code was not correctly decoded. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13017, 00000, "unrecognized line partition shape" // *Cause: The shape of a 2-D line partition could not be determined. // *Action: This is an internal error. Contact Oracle Worldwide Support. / 13018, 00000, "bad distance type" // *Cause: The specified distance type is invalid. // *Action: The only supported distance functions are EUCLID and MANHATTAN. / 13019, 00000, "coordinates out of bounds" // *Cause: Vertex coordinates lie outside the valid range for specified dimension // *Action: Re-define vertex coordinates within specified boundaries / 13020, 00000, "coordinate is NULL" // *Cause: A vertex coordinate has a NULL value // *Action: Re-define vertex coordinate to have non-NULL value / 13021, 00000, "element not continuous" // *Cause: The coordinates defining a geometric element are not connected // *Action: Re-define coordinates for the geometric element / 13022, 00000, "polygon crosses itself" // *Cause: The coordinates defining a polygonal geometric element represent crossing segments // *Action: Re-define coordinates for the polygon / 13023, 00000, "interior element interacts with exterior element" // *Cause: An interior element of a geometric object interacts with the exterior element of that object // *Action: Re-define coordinates for the geometric elements / 13024, 00000, "polygon has less than three segments" // *Cause: The coordinates defining a polygonal geometric element represent less than three segments // *Action: Re-define the coordinates for the polygon / 13025, 00000, "polygon does not close" // *Cause: The coordinates defining a polygonal geometric element represents an open polygon // *Action: Re-define the coordinates of the polygon / 13026, 00000, "unknown element type for element %s.%s.%s" // *Cause: The SDO_ETYPE column in the _SDOGEOM table contains // an invalid geometric element type value // *Action: Re-define the geometric element type in the _SDOGEOM table // for the specified geometric element using one of the supported // SDO_ETYPE values. See the Oracle Spatial Cartridge user's guide for // an explanation of SDO_ETYPE and its possible values. / 13027, 00000, "unable to read dimension definition from %s" // *Cause: There was a problem reading the dimension definition from the // _SDODIM table. // *Action: Verify that the _SDODIM table exists and that the // appropriate privileges exist on the table. Address any other // errors that might appear with the message. / 13028, 00000, "Invalid Gtype in the SDO_GEOMETRY object" // *Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object. // *Action: Verify that the geometries have valid gtypes. / 13029, 00000, "Invalid SRID in the SDO_GEOMETRY object" // *Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. // The specified SRID may be outside the valid SRID range. // *Action: Verify that the geometries have valid SRIDs. / 13030, 00000, "Invalid dimension for the SDO_GEOMETRY object" // *Cause: There is a mismatch between the dimension in the SDO_GTYPE and // dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object. // *Action: Verify that the geometries have valid dimensionality. / 13031, 00000, "Invalid Gtype in the SDO_GEOMETRY object for point object" // *Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the // VARRAYs are NULL but the SDO_GTYPE is not of type POINT. // *Action: Verify that the geometries have valid gtypes. / 13032, 00000, "Invalid NULL SDO_GEOMETRY object" // *Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or // SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object. // *Action: Verify that the geometries have valid fields. To specify a NULL // Geometry specify the whole SDO_GEOMETRY as NULL instead of // setting each field to NULL. / 13033, 00000, "Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object" // *Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the // SDO_GEOMETRY object. The triplets in this field do not make up a // valid geometry. // *Action: Verify that the geometries have valid data. / 13034, 00000, "Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object" // *Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the // SDO_GEOMETRY object. The coordinates in this field do not make up a // valid geometry. There may be NULL values for X or Y or both. // *Action: Verify that the geometries have valid data. / 13035, 00000, "Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object" // *Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the // SDO_GEOMETRY object. There are arcs in a geometry that has // geodetic coordinates. // *Action: Verify that the geometries have valid data. / 13036, 00000, "Operation [%s] not supported for Point Data" // *Cause: The specified geometry function is not supported for Point data. // *Action: Make sure that the specified geometry function is not called // on point data. / 13037, 00000, "SRIDs do not match for the two geometries" // *Cause: A Spatial operation is invoked with two geometries where // one geometry has an SRID and the other geometry does not have SRID. // *Action: Make sure that the spatial operations are invoked between two // geometries with compatible SRIDs. / 13039, 00000, "failed to update spatial index for element %s.%s.%s" // *Cause: Another error will accompany this message that will indicate the // problem. // *Action: Correct any accompanying errors. If no accompanying error // message appears then contact Oracle Worldwide Support. / 13040, 00000, "failed to subdivide tile" // *Cause: This is an internal error. // *Action: Note any accompanying errors and contact Oracle Worldwide Support. / 13041, 00000, "failed to compare tile with element %s.%s.%s" // *Cause: The spatial relationship between a generated tile and the specified // element could not be determined. // *Action: This is an internal error. Verify the geometry using the // VALIDATE_GEOMETRY procedure. If the procedure does not return any // errors then note any errors which accompany ORA-13041 and contact // Oracle Worldwide Support. / 13042, 00000, "invalid SDO_LEVEL and SDO_NUMTILES combination" // *Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was // read from the _SDOLAYER table. The most likely cause is // that the columns are NULL. // *Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain // valid integer values as described in the // Oracle Spatial Cartridge user's guide. Then retry the operation. / 13043, 00000, "failed to read meta data from the _SDOLAYER table" // *Cause: An error was encountered reading the layer meta data from the // _SDOLAYER table. // *Action: This error is usually the result of an earlier error which should // also have been reported. Address this accompanying error and // retry the current operation. If no accompanying error was // reported contact Oracle Worldwide Support. / 13044, 00000, "the specified tile size exceeds the maximum resolution" // *Cause: The tile size specified for fixed size tessellation exceeds the // maximum resolution as computed from the layer meta data. // *Action: See the Oracle Spatial Cartridge user's guide for an explanation of // tiling levels, tile size, and tiling resolution. Ensure that // the tiling parameters are set such that any generated tile // is always larger than or equal to a tile at the maximum level // of resolution. This can be achieved by using a fewer number of // tiles per geomtric object or specifying a lesser tile size // value than the current one. / 13045, 00000, "invalid compatibility flag" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide support. / 13046, 00000, "invalid number of arguments " // *Cause: An invalid number of arguments were specified for an // SDO_GEOM function. // *Action: Please refer to the Oracle Spatial Cartridge user documentation for a description of // the syntax and semantics of the relevant SDO_GEOM function. / 13047, 00000, "unable to determine ordinate count from table _SDOLAYER" // *Cause: An SDO_GEOM function was unable to determine the number of // ordinates for the SDO layer . // *Action: Verify that the _SDOLAYER table has a valid value for // the column SDO_ORDCNT. Then retry the operation. / 13048, 00000, "recursive SQL fetch error" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / 13049, 00000, "unable to determine tolerance value from table _SDODIM" // *Cause: An SDO_GEOM function was unable to determine the tolerance value // for the SDO layer . // *Action: Verify that the _SDODIM table has a valid value for // the column SDO_TOLERANCE. / 13050, 00000, "unable to construct spatial object" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / 13051, 00000, "failed to initialize spatial object" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / 13052, 00000, "unsupported geometric type for geometry %s.%s" // *Cause: The geometry type for a specific instance in a _SDOGEOM // table is not among the set of geometry types supported by the // Oracle Spatial Cartridge. // *Action: Check the Oracle Spatial Cartridge user guide for the list of supported geometry types // and workarounds that permit the storage and retrieval of // non-supported geometric types with the SDO schema. / 13053, 00000, "maximum number of geometric elements in argument list exceeded" // *Cause: The maximum number of geometric elements that can be specified // in the argument list for an SDO_GEOM function was exceeded. // *Action: Check the Oracle Spatial Cartridge user guide for the syntax of the SDO_GEOM function // and use fewer arguments to describe the geometry // or // check the description of the SDO_WINDOW package for a workaround // that permits storing the object in a table and then using it in // as an argument in a call to the SDO_GEOM function. / 13054, 00000, "recursive SQL parse error" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / 13055, 00000, "Oracle object %s does not exist in specified table" // *Cause: The requested object is not present in the specified table. // *Action: Verify the syntax of the function or procedure that reported // this error and verify that the object does indeed exist in the // specified table. Then retry the operation. / 13108, 00000, "spatial table %s not found" // *Cause: The specified spatial table does not exist. // *Action: Check the Spatial Data option data dictionary to make sure // that the table is registered. / 13109, 00000, "spatial table %s exists" // *Cause: The specified spatial table is registered in the Spatial Data // data dictionary. // *Actions: Remove the existing table from the Spatial Data option data // data dictionary or use a different name. / 13110, 00000, "spatial table %s is not partitioned" // *Cause: The specified spatial table is not partitioned. // *Actions: Check the Spatial Data option data dictionary and make sure // that a high water mark is set. / 13111, 00000, "spatial table %s has no partition key defined" // *Cause: The specified spatial table does not have a partition key defined. // *Actions: Check the Spatial Data option data dictionary and make sure // that the table is partitioned. / 13112, 00000, "invalid count mode %s" // *Cause: The specified count mode is not valid. // *Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT. / 13113, 00000, "Oracle table %s does not exist" // *Cause: The specified Oracle table does not exist. // *Action: Check the Oracle7 data dictionary and make sure that the table // exists. / 13114, 00000, "tablespace %s not found" // *Cause: The specified tablespace does not exist. // *Action: Check the Oracle7 data dictionary and make sure // that the specified tablespace exists and that there is a space // quota defined on it. / 13115, 00000, "tablespace %s is already allocated" // *Cause: The specified tablespace is already allocated to the spatial table. // *Action: Allocate another tablespace name to the table. / 13116, 00000, "tablespace %s is not allocated to table %s" // *Cause: The specified tablespace is not allocated to the specified spatial // table. // *Action: Allocate the tablespace to the spatial table. / 13117, 00000, "partition %s not found" // *Cause: The specified partition does not exist. // *Action: Verify the name of the partition by checking the Spatial Data // option data dictionary. / 13119, 00000, "source and target tablespaces are identical" // *Cause: Identical source and target tablespaces were specified when trying // to move partition. // *Action: Specify different source and target tablespaces if you wish to // move a partition. / 13121, 00000, "failed to create child partition" // *Cause: The creation of a child partition failed. // *Action: Check for other errors that accompany this error and correct them // first. / 13122, 00000, "child partition %s not found" // *Cause: This is an internal error. // *Action Document messages and contact Oracle Worldwide Support. / 13123, 00000, "column %s is already defined" // *Cause: The specified column is already defined for the spatial table. // *Action: Use a different column name. / 13124, 00000, "unable to determine column id for column %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13125, 00000, "partition key is already set" // *Cause: A partition key is already set for the spatial table. // *Action: Only one partition key can be specified per spatial table. / 13126, 00000, "unable to determine class for spatial table %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13127, 00000, "failed to generate target partition" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13128, 00000, "current tiling level exceeds user specified tiling level" // *Cause: This is an internal error. // *Action: Contact World Wide Support. / 13129, 00000, "HHCODE column %s not found" // *Cause: The specified spatial column does not exist. // *Action: Verify that the specified column is a spatial column by checking // the Spatial Data option data dictionary. / 13135, 00000, "failed to alter spatial table" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13136, 00000, "null common code generated" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13137, 0000, "failed to generate tablespace sequence number" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13138, 00000, "could not determine name of object %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13139, 00000, "could not obtain column definition for %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13140, 00000, "invalid target type" // *Cause: The specified target type is not valid. // *Action: Substitute a valid target type. Valid target types are TABLE or // VIEW. / 13141, 00000, "invalid RANGE window definition" // *Cause: The RANGE window specified is not correctly defined. // *Action: A RANGE window is defined by specifying the lower and upper // boundary of each dimension as a pair of values // (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). // There should be an even number of values. / 13142, 00000, "invalid PROXIMITY window definition" // *Cause: The PROXIMITY window specified is not correctly defined. // *Action: A PROXIMITY window is defined by specifying a center point and a // radius. The center point is defined by ND values. There should // be ND+1 values. / 13143, 00000, "invalid POLYGON window definition" // *Cause: The POLYGON window specified is not correctly defined. // *Action: A POLYGON window is defined by specifying N pairs of values // that represent the vertices of the polygon. There should be // an even number of values. / 13144, 00000, "target table %s not found" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13145, 00000, "failed to generate range list" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13146, 00000, "could not find table substitution variable %s" // *Cause: The partition name substitution variable %s was not found in the // SQL filter. // *Action: The substitution variable %s must be in the SQL filter to indicate // where that partition name should be placed. / 13147, 00000, "failed to generate MBR" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13148, 00000, "failed to generate SQL filter" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13149, 00000, "failed to generate next sequence number for spatial table %s" // *Cause: This is an internal error. // *Action: Document messages and contact Oracle Worldwide Support. / 13150, 00000, "failed to insert exception record" // *Cause: Operation failed to insert a record into the exception table // *Action: Fix any other errors reported. / 13151, 00000, "failed to remove exception record" // *Cause: Operation failed to insert a record into the exception table. // *Action: Fix any other errors reported. / 13152, 00000, "invalid HHCODE type" // *Cause: Specified HHCODE type is not valid. // *Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT // and LINE. / 13153, 00000, "invalid high water mark specified" // *Cause: The highwater mark must be greater than or equal to zero. // *Action: Make sure that the highwater mark is an integer greater than // or equal to zero. / 13154, 00000, "invalid precision specified" // *Cause: The precision specified is out of range. // *Action: The precision must be an integer greater than or equal to zero. / 13155, 00000, "invalid number of dimensions specified" // *Cause: The number of dimensions specified is out of range." // *Action: The number of dimension must be between 1 and 32. / 13156, 00000, "table to be registered %s.%s is not empty" // *Cause: The specified table has rows in it. // *Action: Make sure that the table to be registered is empty. / 13157, 00000, "Oracle error ORA%s encountered while %s" // *Cause: Specified Oracle error was encountered. // *Action: Correct the Oracle error. / 13158, 00000, "Oracle object %s does not exist" // *Cause: The specified object does not exist. // *Action: Verify that the specified object exists. / 13159, 00000, "Oracle table %s already exists" // *Cause: The specified table already exists. // *Action: Drop the specified table. / 13181, 00000, "unable to determine length of column %s_SDOINDEX.SDO_CODE" // *Cause: The length of the SDO_CODE column in the _SDOINDEX table // could not be determined. // *Action: Make sure that the _SDOINDEX table exists with the SDO_CODE // column. Verify that the appropriate privileges exist on the table. // Then retry the operation. / 13182, 00000, "failed to read element %s.%s.%s" // *Cause: The specified element could not be read from the _SDOGEOM // table. // *Action: Verify that the specified element exists in the table. // Then retry the operation. / 13183, 00000, "unsupported geometric type for geometry %s.%s" // *Cause: The geometry type in the _SDOGEOM table is unsupported. // *Action: Modify the geometry type to be one of the supported types. / 13184, 00000, "failed to initialize tessellation package " // *Cause: Initialization of the tessellation package failed. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13185, 00000, "failed to generate initial HHCODE" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13186, 00000, "fixed tile size tessellation failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13187, 00000, "subdivision failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13188, 00000, "cell decode failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13189, 00000, "recursive SQL parse failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13190, 00000, "recursive SQL fetch failed" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13191, 00000, "failed to read SDO_ORDCNT value" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13192, 00000, "failed to read number of element rows" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13193, 00000, "failed to allocate space for geometry" // *Cause: There was insufficient memory to read the geometry // from the database. // *Action: Validate the geometry. Record the error messages // that are returned and contact Oracle Worldwide Support. / 13194, 00000, "failed to decode supercell" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / 13195, 00000, "failed to generate maximum tile value" // *Cause: This is an internal error. // *Action: Record the error messages that are returned // and contact Oracle Worldwide Support. / 13196, 00000, "failed to compute supercell for element %s.%s.%s" // *Cause: The system was unable to compute the minimum bounding // HHCODE or supercell for the geometry. // *Action: Another error might accompany this error. Correct the // accompanying error. Also, validate the geometry for // correctness. / 13197, 00000, "element %s.%s.%s is out of range" // *Cause: Tessellation did not generate any tiles for this element. // This error could be caused if the geometry definition // puts the geometry outside the domain defined in the // _SDODIM table. // *Action: Verify that the geometry is valid and within the defined // domain. / 13198, 00000, "Spatial Cartridge error: %s" // *Cause: Internal error in some Spatial Cartridge stored procedure // *Action: Record the sequence of procedure calls or events that // preceeded this error and contact Worldwide Support if the // error message text does not clearly specify the cause // of the error. / 13199, 00000, "%s" // *Cause: This is an internal error. // *Action: Contact Oracle Worldwide Support. / / (13200 - 13499 Reserved for Spatial Cartridge 8.1.3 and future use) 13200, 00000, "internal error [%s] in spatial indexing." // *Cause: This is an internal error. // Action: Contact Worldwide support with the exact error text. / 13201, 00000, "invalid parameters supplied in CREATE INDEX statement" // *cause: An error was encountered while trying to parse the parameters // clause for the spatial CREATE INDEX statement. // *Action: Check the Spatial Cartridge User Guide for the number, syntax, // and semantics of expected parameters for spatial index creation. / 13202, 00000, "failed to create or insert into the SDO_INDEX_METADATA table" // *Cause: An error was encountered while trying to create the // SDO_INDEX_METADATA table or insert data into it. // *Action:Verify that the current user has CREATE TABLE privilege and // that the user has sufficient quota in the default or // specified tablespace. / 13203, 00000, "failed to read USER_SDO_GEOM_METADATA table" // *Cause: An error encountered while trying to read USER_SDO_GEOM_METADATA // table. // *Action: Check that USER_SDO_GEOM_METADATA has an // entry for the current geometry table. / 13204, 00000, "failed to create spatial index table" // *Cause: An error was encountered while trying to create the index table. // *Action: Check that user has create table privilege in the current schema // and that the user has sufficient quota in the default or // specified tablespace. / 13205, 00000, "internal error while parsing spatial parameters" // *Cause: An internal error was encountered while parsing // the spatial parameters. // *Action: Check to make sure that the parameters passed in the parameter // string are all valid / 13206, 00000, "internal error [%s] while creating the spatial index" // *Cause: An internal error was encountered while // creating the spatial index. // *Action: Contact Worldwide Support with exact error text. / 13207, 00000, "incorrect use of the [%s] operator" // *Cause: An error was encountered while evaluating the specified operator. // *Action: Check the parameters and the return type of the specified // operator. / 13208, 00000, "internal error while evaluating [%s] operator" // *Cause: An internal error was encountered. // *Action: Check with Worldwide Support with exact error text. / 13209, 00000, "internal error while reading SDO_INDEX_METADATA table" // *Cause: An internal error was encountered while trying to read // SDO_INDEX_METADATA table. // *Action: Contact Worldwide Support. Note this and accompanying // error numbers. / 13210, 00000, "error inserting data into the index table" // *Cause: An error was encountered while trying to insert data into the // index table. Likely causes are:- // - Insufficient quota in the current tablespace // - User does not appropriate privileges // *Action: Check the accompanying error messages. / 13211, 00000, "failed to tessellate the window object" // *Cause: An internal error was encountered while trying to tessellate the // window object. // *Action: Verify the geometric integrity of the window object using the // VALIDATE_GEOMETRY procedure. / 13212, 00000, "failed to compare tile with the window object " // *Cause: The spatial relationship between a generated tile and the specified // window object could not be determined. // *Action: This is an internal error. Verify the geometry using the // VALIDATE_GEOMETRY procedure. If the procedure does not return any // errors then note any accompanying errors and contact // Oracle Worldwide Support. / 13213, 00000, "failed to generate spatial index for window object" // *Cause: Another error, indicating the real cause of the problem, should // accompany this error. // *Action: Correct any accompanying errors. If no accompanying error // message appears then contact Oracle Worldwide Support. / 13214, 00000, "failed to compute supercell for window object " // *Cause: The system was unable to compute the minimum bounding // tile or supercell for the geometry. // *Action: Another error might accompany this error. Correct the // accompanying error. Also, validate the geometry for // correctness. / 13215, 00000, "window object is out of range" // *Cause: Tessellation did not generate any tiles for this geometry. // This error could be caused if the geometry definition // puts the geometry outside the domain defined in the // USER_SDO_GEOM_METADATA view. // *Action: Verify that the geometry is valid and within the defined // domain. / 13216, 00000, "failed to update spatial index" // *Cause: Another error will accompany this message that will indicate the // problem. // *Action: Correct any accompanying errors. If no accompanying error // message appears then contact Oracle Worldwide Support. / 13217, 00000, "invalid parameters supplied in ALTER INDEX statement" // *Cause: An error was encountered while trying to parse the parameters // clause for the spatial ALTER INDEX statement. // *Action: Check the Spatial Cartridge User Guide for the number, syntax, // and semantics of expected parameters for spatial alter index // command. / 13218, 00000, "max number of supported index tables reached for [%s] index" // *Cause: An add_index parameter is passed to ALTER INDEX when the number of // existing index tables is already at maximum. // *Action: Delete one of the index tables before adding another index table. / 13219, 00000, "failed to create spatial index table [%s]" // *Cause: An error was encountered while trying to create the index table. // *Action: There is a table in the index's schema with the specified // name. The create index will try to create an index table with // this name. Either rename this table or change the name of the index. / 13220, 00000, "failed to compare tile with the geometry" // *Cause: The spatial relationship between a generated tile and the specified // geometry could not be determined. // *Action: This is an internal error. Verify the geometry using the // VALIDATE_GEOMETRY procedure. If the procedure does not return any // errors then note any errors which accompany ORA-13220 and contact // Oracle Worldwide Support. / 13221, 00000, "unknown geometry type in the geometry object" // *Cause: The SDO_GTYPE attribute in the geometry object contains // an invalid value // *Action: Re-define the geometric type in the geometry table // using one of the supported SDO_GTYPE values. // See the Oracle Spatial Cartridge user's guide for // an explanation of SDO_GTYPE and its possible values. / 13222, 00000, "failed to compute supercell for geometry in %s" // *Cause: The system was unable to compute the minimum bounding // tile or supercell for a geometry in the specified table. // *Action: Another error might accompany this error. Correct the // accompanying error. Also, validate the geometry for // correctness. / 13223, 00000, "duplicate entry for %s in SDO_GEOM_METADATA table " // *Cause: There are duplicate entries for the given table and column // value pair in the SDO_GEOM_METADATA table // *Action: Check that the specified table and geometry column names // are correct. There should be only one entry per table, geometry // column pair in the SDO_GEOME_METADATA table. / 13224, 00000, " specified index name is too long for a spatial index " // *Cause: An index name is specified which is longer than the supported // lenght of the spatial index name. // *Action: Check the supported size of the index name and reduce the size // of the index name. / 13225, 00000, " specified index table name is too long for a spatial index " // *Cause: An index table name is specified which is longer than the supported // length of the spatial index table name. // *Action: Check the supported size of the index table name and // reduce the size of the index name. / 13226, 00000, "interface not supported without a spatial index" // *Cause: The geometry table does not have a spatial index. // *Action: Verify that the geometry table referenced in the spatial operator // has a spatial index on it. / 13227, 00000, "SDO_LEVEL values for the two index tables do not match" // *Cause: The SDO_LEVEL values for the two index tables used in the // spatial join operator do not match. // *Action: Verify that two compatible indexes are used for the // spatial join operator. Indexes are compatabile if they // have the same SDO_LEVEL and SDO_NUMTILES values / 13228, 00000, "Spatial index create failed due to invalid type" // *Cause: An Attempt was made to create a spatial index on a column // of type other than SDO_GEOMETRY. // *Action: Make sure that the index is created on a column of type // SDO_GEOMETRY. / 13230, 00000, "failed to create temporary table [%s] during R-tree creation" // *Cause: The specified temporary table either already exists or // there is not enough tablespace. // *Action: Delete the table if it already exists and verify if the current // user has CREATE TABLE privleges and has sufficient space in // the default or specified tablespace. / 13231, 00000, "failed to create index table [%s] during R-tree creation" // *Cause: The specified index table either already exists or // there is not enough tablespace. // Otherwise, contact Oracle Worldwide support. // *Action: Delete the table if it already exists and verify if the current // user has CREATE TABLE privleges and has sufficient space in // the default or specified tablespace. / 13232, 00000, "failed to allocate memory during R-tree creation" // *Cause: This feature assumes a minimum of 64K memory for bulk creation. // *Action: Create the index for a small subset of the data. Then, use // transactional inserts for the rest. / 13233, 00000, "failed to create sequence number [%s] for R-tree" // *Cause: The specified sequence number exists. // *Action: Delete the sequence object, or contact Oracle Worldwide Support. / 13234, 00000, "failed to access R-tree-index table [%s]" // *Cause: The index table is either deleted or corrupted. // *Action: Rebuild the index or contact Oracle Worldwide support with // accompanying error messages. / 13236, 00000, "internal error in R-tree processing: [%s]" // *Cause: An internal error occured in R-tree processing. // *Action: Contact Oracle Worldwide support with message text. / 13237, 00000, "internal error during R-tree concurrent updates: [%s]" // *Cause: An inconsistency is encountered during concurrent updates // possibly due to the use of serializable isolation level. // *Action: Change the isolation level to "read committed" using alter // session or contact Oracle Worldwide Support with the // message text. / 13239, 00000, "sdo_dimensionality not specified during n-d R-tree creation" // *Cause: An error occurred in reading the dimensionality parameter // *Action: Check the documentation for a valid range and specify the // dimensionality as a parameter. / 13240, 00000, "specified dimensionality greater than that of the query mbr" // *Cause: An error occurred because of too few values in query mbr" // *Action: Omit the dimensionality, or use the dimensionality of the query. / 13241, 00000, "specified dimensionality does not match that of the data" // *Cause: An error occurred because the dimensionality specified in the // CREATE INDEX does not match that of the data. // *Action: Change it to the data dimensionality. / 13242, 00000, "failed to read tolerance values for n-d R-tree" // *Cause: An error occurred in reading the information for the specified // table and column in USER_SDO_GEOM_METADATA table. // *Action: Insert appropriate row specifying the tolreance. / 13243, 00000, "speciifed operator is not supported for n-d R-tree: [%s]" // *Cause: Currently, an n-d R-tree only supports sdo_filter operator. // *Action: Check the documentation for querytype parameters for sdo_filter // or contact Oracle Worldwide support. / 13249, 00000, "%s" // *Cause: An internal error was encountered in the extensible spatial index // component. The text of the message is obtained from some // other server component. // *Action: Contact Oracle Worldwide Support with the exact error text. / 13250, 00000, "insufficient privileges to modify metadata table entries" // *Cause: The user requesting the operation does not have the // appropriate privileges on the referenced tables // *Action: Check that the specified feature and geometry table names // are correct and then verify that the current user has // at least SELECT privilege on those tables / / 13251, 00000, "duplicate entry %s in metadata table " // *Cause: The specified entry already exists in the metadata table // *Action: Check that the specified feature and geometry table names // are correct. A feature-geometry table association should // be registered only once. / 13260, 00000, "layer table %s does not exist" // *Cause: Data migration source table _SDOGEOM does not exist // *Action: Ensure that the specified layername is correct and that the // corresponding spatial layer tables exist in the current schema / 13261, 00000, "geometry table %s does not exist" // *Cause: The specified geometry table does not exist in the current schema. // *Action: Create a table containing a column of type SDO_GEOMETRY and // a column of type NUMBER for the GID values. / 13262, 00000, "geometry column %s does not exist in table %s " // *Cause: The specified table does not have a column of type SDO_GEOMETRY. // *Action: Alter or recreate the table such that it includes a column of // type SDO_GEOMETRY and a column of type NUMBER / 13263, 00000, "column %s in table %s is not of type SDO_GEOMETRY" // *Cause: The column intended for storing the geometry is not of // type SDO_GEOMETRY. // *Action: Alter the column definition to be of type SDO_GEOMETRY. / 13264, 00000, "geometry identifier column %s does not exist in table %s " // *Cause: The specified table does not contain a GID column. // *Action: Confirm that the GID columnname was correctly specified and // that it exists in the specified table. / 13265, 00000, "geometry identifier column %s in table %s is not of type NUMBER" // *Cause: GID column is not of type NUMBER. // *Action: Alter the table definition such that the column containing the // geometry identifier (GID) is of type NUMBER. / 13266, 00000, "error inserting data into table %s " // *Cause: An OCI error occurred or the user has insufficient quota in the // active tablespace or the rollback segments are too small. // *Action: There should be an accompanying error message that // indicates the cause of the problem. Take appropriate action // to correct the indicated problem. / 13267, 00000, "error reading data from layer table %s " // *Cause: There was an error reading the geometry data from the // _SDOGEOM table. // *Action: Verify that _SDOGEOM and _SDODIM exist. If they do // then run VALIDATE_GEOMETRY on the specified layer. / 13268, 00000, "error obtaining dimension from USER_SDO_GEOM_METADATA" // *Cause: There is no entry in USER_SDO_GEOM_METADATA for the specified // geometry table. // *Action: Insert an entry for the destination geometry table with // the dimension information obtained from the source // _SDODIM table. / 13269, 00000, "internal error [%s] encountered when processing geometry table" // *Cause: An internal error occurred. // *Action: Conatct Worldwide support with the exact error message text. / 13270, 00000, "OCI error \n%s" // *Cause: OCI error while processing the layer or geometry tables // *Action: Take the appropriate steps to correct the OCI specific error. / 13271, 00000, "error allocating memory for geometry object" // *Cause: Insufficient memory // *Action: Make more memory available to the current session/process. / 13272, 00000, "geometric object %s in table %s is invalid" // *Cause: The specified object failed the geometric integrity checks // performed by VALIDATE_GEOMETRY // *Action: Consult the Spatial Cartridge User Guide for information // on the geometric integrity checks performed by VALIDATE_GEOMETRY // and correct the geometry definition if required. / 13273, 00000, "dimension metadata table %s does not exist" // *Cause: The _SDODIM table does not exist. // *Action: Verify that the specified layer name is correct and that the // _SDODIM table exists in the current schema. / 13274, 00000, "Operator invoked with non compatible SRIDs" // *Cause: A Spatial operator is invoked with a window geometry with an SRID // and the layer without an SRID or window has no SRID and the // layer has an SRID. // *Action: Make sure that the layer and window both have an SRID or they // both do not have an SRID. / 13275, 00000, "Spatial index creation failure on unsupported type" // *Cause: A spatial index create is invoked on a column that is not // of type SDO_GEOMETRY. // *Action: Spatial index can only be created on a column of type // SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type. / 13276, 00000, "internal error [%s] in coordinate transformation " // *Cause: OCI internal error // *Action: Conatct Worldwide support with the exact error message text. / 13278, 00000, "failure to convert SRID to native format" // *Cause: OCI internal error // *Action: Conatct Worldwide support with the exact error message text. / 13281, 00000, "failure in execution of sql statement to retrieve WKT" // *Cause: OCI internal error or SRID does not match a table entry // *Action: Check that a valid SRID is being used / 13282, 00000, "failure on initialization of coordinate transformation" // *Cause: Parsing error on source or destination coordinate system WKT or // incompatible coordinate systems // *Action: Check validity of WKT for table entries and the legitimacy of the // requested transformation / 13283, 00000, "failure to get new geometry object for conversion in place" // *Cause: OCI internal error // *Action: / 13284, 00000, "failure to copy geometry object for conversion in place" // *Cause: OCI internal error // *Action: Conatct Worldwide support with the exact error message text. / 13285, 00000, "Geometry coordinate transformation error" // *Cause: A coordinate pair was out of valid range for a conversion/projection // *Action: Check that data to be transformed is consistent with the desired // conversion/projection / 13287, 00000, "can't transform unknown gtype" // *Cause: A geometry with a gtype of <= 0 was specified for transformation. // Only a gtype >= 1 is allowed. // *Action: / 13288, 00000, "Point coordinate transformation error" // *Cause: An internal error while tranforming points // *Action: Check the accompanying error messages / 13290, 00000, "The specified unit is not supported" // *Cause: Spatial function called with an unknown UNIT. // *Action: Check the supported units by Spatial and call the spatial // function with the correct UNIT parameter. / 13291, 00000, "Conversion error between the specified unit and standard unit" // *Cause: Cannot convert the specified unit from/to standard unit // for linear distance, angle or area. // *Action: Check unit specification and respecify it. / 13292, 00000, "Incorrect ARC_TOLERANCE specification" // *Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a // Geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE // must be specified and it should not be less than the tolerance // specified for the geometry // *Action: Check ARC_TOLERANCE specification and make sure it is correct / 13293, 00000, "Cannot specify unit for geometry without a georeferenced SRID" // *Cause: A Spatial function with unit parameter is called on a geometry // without a georeferenced SRID. // *Action: Make sure that spatial functions with UNIT parameters are only // called on geometries with georeferenced SRIDs. / 13294, 00000, "Cannot transform geometry containing circular arcs" // *Cause: It is impossible to transform a 3-point representation of // a circular arc without distortion // *Action: Make sure a geometry does not contain circular arcs / 13295, 00000, "Geometry objects are in different coordinate systems" // *Cause: A Spatial function is called with two geometries with two different // SRIDs. // *Action: Transform geometry objects to be in the same coordinate system and // call the spatial function. / 13296, 00000, "Incorrect Coordinate System Specification" // *Cause: Wrong numbers in WKT for Earth radius or flattening for the // current SRID // *Action: Check WKT in CS_SRS table for Earth radius and inverse flattening / 13300, 00000, "Single point transform error" // *Cause: Low level coordinate transformation error trap. // *Action: Check the accompanying error messages. / 13303, 00000, "failure to retrieve a geometry object from a table" // *Cause: OCI internal error // *Action: Conatct Worldwide support with the exact error message text. / 13304, 00000, "failure to insert a transformed geometry object in a table" // *Cause: OCI internal error // *Action: Conatct Worldwide support with the exact error message text. / 13330, 00000, "invalid MASK" // *Cause: The MASK you passed to RELATE function is not valid. // *Action: Verify that the mask is not NULL. See the user's guide for // a list of supported masks. / 13331, 00000,"invalid LRS segment" // *Cause: The given LRS segment was not a valid linestring. // *Action: A valid LRS geometric segment is a line string geometry in Oracle // Spatial. It could be a simple or compound line string // (made of lines or arcs, or both). The dimension information must // include the measure dimension as the last element in Oracle Spatial // metadata. Currently, the number of dimensions for an LRS segment must // be greater than 2 (x/y or latitude/longitude plus measure) / 13332, 00000,"invalid LRS point" // *Cause: Given LRS point was not a point-geometry with measure information. // *Action: Check the given point geometry.A valid LRS point is a point // geometry in Oracle Spatial with additional measure dimension / 13333, 00000, "invalid LRS measure" // *Cause: The given measure for linear referencing was out of range. // *Action: Re-define the given measure. / 13334, 00000, "LRS segments not connected" // *Cause: The given geometric segments were not connected // *Action: Check the start/end points of the given geometric segments / 13335, 00000, "LRS measure information not defined" // *Cause: The measure information of a given geometric segments was // not assigned (IS NULL) // *Action: Assign/define the measure information. An LRS geometric segment // is defined if its start and end measure are assigned (non-null). / 13336, 00000, "Failure in converting standard diminfo/geometry to LRS dim/geom" // *Cause: No room for measure dimension in the given diminfo or // the given standard geometry is not a point a linestring // *Action: Check if the diminfo dimensions are less than 3 or given // geometry type is point or linestring / 13337, 00000, "failure in concatenating LRS polygons" // *Cause: LRS concatenation involving LRS polygon(s) is not supported // *Action: Check geometry and element type to make sure the concatnate // operation is not called with a polygon type / 13338, 00000, "failure in reversing LRS polygon/collection geometry" // *Cause: Reversing an LRS polygon/collection geometry produces an // invalid geometry as this operation is not well defined // for polygon geometry // *Action: Check the geometry type to make sure this operation is // called on non polygon type geometry / 13339, 00000, "LRS Polygon clipping across multiple rings" // *Cause: Clipping (dynseg) a polygon across multiple rings // *Action: Polygon clipping only allowed for a single ring / 13340, 00000, "a point geometry has more than one coordinate" // *Cause: A geometry, specified as being a point, has more than one // coordinate in its definition. // *Action: A point has only one coordinate. If this geometry is intended to // represent a point cluster, line, or polygon then set the // appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single // point object then remove the extraneous coordinates from its // definition. / 13341, 00000, "a line geometry has less than two coordinates" // *Cause: A geometry, specified as being a line, has less than two // coordinates in its definition. // *Action: A line must consist of at least two distinct coordinates. // Correct the geometric definition or set the appropriate // SDO_GTYPE or SDO_ETYPE attribute for this geometry. / 13342, 00000, "an arc geometry has less than three coordinates" // *Cause: A geometry, specified as being an arc, has less than three // coordinates in its definition. // *Action: An arc must consist of at least three distinct coordinates. // Correct the geometric definition or set the appropriate // SDO_GTYPE or SDO_ETYPE attribute for this geometry. / 13343, 00000, "a polygon geometry has less than four coordinates" // *Cause: A geometry, specified as being a polygon, has less than four // coordinates in its definition. // *Action: A polygon must consist of at least four distinct coordinates. // Correct the geometric definition or set the appropriate // SDO_GTYPE or SDO_ETYPE attribute for this geometry. / 13344, 00000, "an arcpolygon geometry has less than five coordinates" // *Cause: A geometry, specified as being an arcpolygon, has less than six // coordinates in its definition. // *Action: An arcpolygon must consist of at least five coordinates. // An arcpolygon consists of an ordered sequence of arcs // each of which must be described using three coordinates. // Since arcs are connected the end-point of the first is the // start of the second and does not have to be repeated. // Correct the geometric definition or set the appropriate // SDO_GTYPE or SDO_ETYPE attribute for this geometry. / 13345, 00000, "a compound polygon geometry has less than five coordinates" // *Cause: A geometry, specified as being a compound polygon, has less // than five coordinates in its definition. // *Action: A compound polygon must contain at least five coordinates. // A compound polygon consists of at least one arc and // one line each of which must be described using three // and at least two distinct coordinates respectively. // Correct the geometric definition or set the appropriate // SDO_GTYPE or SDO_ETYPE attribute for this geometry. / 13346, 00000, "the coordinates defining an arc are collinear" // *Cause: Invalid defintion of an arc. An arc is defined using three // non-collinear coordinates. // *Action: Alter the definition or the arc or set the SDO_ETYPE or // SDO_GTYPE to the line type. / 13347, 00000, "the coordinates defining an arc are not distinct" // *Cause: Two or more of the three points defining an arc are the same. // *Action: Alter the definition of the arc ensuring that three distinct // coordinate values are used. / 13348, 00000, "polygon boundary is not closed" // *Cause: The boundary of a polygon does not close. // *Action: Alter the coordinate values or the definition of the // SDO_GTYPE or SDO_ETYPE attribute of the geometry. / 13349, 00000, "polygon boundary crosses itself" // *Cause: The boundary of a polygon intersects itself. // *Action: Correct the geometric definition of the object. / 13350, 00000, "two or more rings of a complex polygon touch" // *Cause: The inner or outer rings of a complex polygon // touch. // *Action: All rings of a complex polygon must be disjoint. // Correct the geometric description of the object. / 13351, 00000, "two or more rings of a complex polygon overlap" // *Cause: The inner or outer rings of a complex polygon // overlap. // *Action: All rings of a complex polygon must be disjoint. // Correct the geometric description of the object. / 13352, 00000, "the coordinates do not describe a circle" // *Cause: The set of coordinates used to describe a circle are // incorrect. // *Action: Confirm that the set of coordinates actually represent points // on the circumference of a circle. / 13353, 00000, "ELEM_INFO_ARRAY not grouped in threes" // *Cause: The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements // than expected. // *Action: Confirm that the number of elements in ELEM_INFO_ARRAY is // divisible by 3. / 13354, 00000, "incorrect offset in ELEM_INFO_ARRAY" // *Cause: The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY // references an invalid array subscript in SDO_ORDINATE_ARRAY. // *Action: Confirm that the offset is a valid array subscript in // SDO_ORINATE_ARRAY. / 13355, 00000, "SDO_ORDINATE_ARRAY not grouped by number of dimensions specified" // *Cause: The number of elements in SDO_ORDINATE_ARRAY is not a mutiple of // the number of dimensions supplied by the user. // *Action: Confirm that the number of dimensions is consistent with data // representation in SDO_ORINATE_ARRAY. / 13356, 00000, "adjacent points in a geometry are redundant" // *Cause: There are repeated points in the sequence of coordinates. // *Action: Remove the redundant point. / 13357, 00000, "extent type does not contain 2 points" // *Cause: Extent type should be represented by 2 points: // lower left and upper right. // *Action: Confirm that there are only 2 points for extent type. / 13358, 00000, "circle type does not contain 3 points" // *Cause: Circle type should be represented by 3 distinct points // on the circumference. // *Action: Confirm that there are only 3 points for circle type. / 13359, 00000, "extent does not have an area" // *Cause: The 2 points representing the extent are identical. // *Action: Confirm that the 2 points describing the extent type are distinct. / 13360, 00000, "invalid subtype in a compound type" // *Cause: This subtype is not allowed within the ETYPE specified. // *Action: Refer to Spatial Data Cartridge User's Reference for type definitions. / 13361, 00000, "not enough sub-elements within a compound ETYPE" // *Cause: The compound type declare more sub-elements than actually defined. // *Action: Confirm that the number of sub-elements is consistent with // the compound type declaration. / 13362, 00000, "disjoint sub-element in a compound polygon" // *Cause: Compound polygon must describe an enclosed area. // *Action: Confirm that all sub-elements are connected. / 13363, 00000, "no valid ETYPE in the geometry" // *Cause: None of the ETYPEs within the geometry is supported. // *Action: Confirm that there is at least one valid ETYPE. / 13364, 00000, "Layer Dimensionality does not match geometry dimensions" // *Cause: Spatial layer has a geometry with a different dimensions than the // dimensions specified for the layer. // *Action: Make sure that all geometries in a layer have the same dimensions // and they match the dimensions in the SDO_DIM_ARRAY object // for the layer in USER_SDO_GEOM_METADATA. / 13365, 00000, "Layer SRID does not match geometry SRID" // *Cause: Spatial layer has a geometry with a different SRID than the // SRID specified for the layer. // *Action: Make sure that all geometries in a layer have the same SRID and // the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer. / 13366, 00000, " Invalid combination of interior exterior rings" // *Cause: In the Spatial geometry, interior and exterior rings are not used // consistently // *Action: Make sure that the interior rings corresponding to an exterior // ring follow the exterior ring in the ordinate array / 13367, 00000, " Wrong orientation for interior/exterior rings" // *Cause: In a sptial geometry, the exterior and/or interior rings are not // oriented correctly // *Action: The exterior rings should be oriented counter clock-wise and // interior rings should be oriented clock wise / 13368, 00000, "Simple Polygon type has more than one exterior ring" // *Cause: In a polygon type geometry there is more than one exterior ring // *Action: Set the type to be multi-polygon if more than one exterior is // present in the geometry / 13369, 00000, " Invalid value for etype in the 4 digit format" // *Cause: A 4 digit etype for non polygon type element is used or // the orientation is not a valid orientation for interior/exterior // rings of the polygon / 13370, 00000, "failure in applying 3D LRS functions" // *Cause: Only Non-geodetic 3D linestring geometry (made of line segments) // are supported for 3D LRS package // *Action: Check the geometry and element types and SRID / 13371, 00000, "invalid position of measure dimension" // *Cause: LRS measure dimension has to be after spatial dimensions. // The position has to be either 3rd or 4th in dim_info_array. // *Action: Check geometry gtype and its dim_info_array / 13372, 00000, "failure in modifying metadata for a table with spatial index " // *Cause: Modifying the metadata after the index is created will cause // inconsistency between geometry gtype and diminfo // *Action: Modify(or Prepare) metadata before creating index on // sdo_geometry column / 13373, 00000, " Element of type Extent is not supported for Geodetic data" // *Cause: Element type extent for a polygon geometry is not supported for // geodetic data // *Action: Convert the extent type polygon to a regular 5 point // polygon and set etype accordingly / 13374, 00000, " SDO_MBR not supported for geodetic data" // *Cause: The SDO_MBR functionality is not supported for geodetic data // *Action: Find an alternative function that can be used in this context / 13375, 00000, "The layer is of type [%s] while geometry inserted has type [%s]" // *Cause: The layer has a type that is different or inconsistent with the // type of the current geometry // *Action: Change the geometry type to agree with the layer type or change // the layer type to agree with the geometry type / 13376, 00000, " Invalid type name specified for layer_gtype parameter" // *Cause: An invalid type name is specified for the layer gtype conctraint // *Action: Consult to user guide to get a list of valid layer gtypes // that can be used in defining a layer gtype constraint / 13400, 00000, "Oracle GeoImage internal error, arguments: [%s], [%s], [%s], [%s], [%s]" // *Cause: This is an internal Oracle GeoImage error. // *Action: Contact Oracle Worldwide Support. / 13401, 00000, "unsupported geoimage format" // *Cause: The GeoImage format is not supported. // *Action: Confirm that the GeoImage format is valid and supported. / 13402, 00000, "NULL destination" // *Cause: The object specified as the destination is NULL. // *Action: Confirm that the object specified as the destination is not NULL. / 13403, 00000, "NULL source geometry" // *Cause: The source GeoImage has a NULL geometry. // *Action: Verify that the geometry of the source GeoImage is not NULL. / 13404, 00000, "not a local source" // *Cause: An attempt has been made to modify a GeoImage which is not stored in the database. // *Action: Import the GeoImage in order to modify it. / 13405, 00000, "NULL source" // *Cause: The object specified as the source is NULL. // *Action: Confirm that the object specified as the source is not NULL. / 13406, 00000, "unsupported image processing command [%s]" // *Cause: The image processing command specified is not supported for a GeoImage. // *Action: Consult the Oracle interMedia manual to verify which image processing commands // are supported within an Oracle GeoImage method. / 13407, 00000, "unrecognized space type qualifier [%s]" // *Cause: The GeoImage space type qualifier is invalid. // *Action: Use a valid space type qualifier (RASTER or MODEL). / 13408, 00000, "NULL table name" // *Cause: The table name parameter is NULL. // *Action: Verify that the parameter used for the table name is not NULL. / 13409, 00000, "Oracle table \"%s\" does not exist." // *Cause: The table specified does not exist. // *Action: Verify that the table name used is valid and the table exists. / 13410, 00000, "NULL column name" // *Cause: The column name parameter is NULL. // *Action: Verify that the parameter used for the column name is not NULL. / 13411, 00000, "Oracle column \"%s\" does not exist." // *Cause: The column specified does not exist. // *Action: Verify that the column name used is valid and the column exists. / 13412, 00000, "invalid ROWID" // *Cause: The ROWID value used in not valid. // *Action: Verify that the ROWID value used is valid. / 13413, 00000, "could not select the GeoImage for initialization" // *Cause: The GeoImage in the table could not be selected. // *Action: Verify that the GeoIMage is present in the table and the supplied parameters are valid. / 13414, 00000, "could not update the table containing the GeoImage" // *Cause: The table containing the GeoImage could not be updated. // *Action: Verify that the table exists and is valid. / 13415, 00000, "invalid domain" // *Cause: The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain. // *Action: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain // specified. / 13416, 00000, "invalid geometry, arguments [%s]" // *Cause: The SDO_GEOMETRY value used is not valid. // *Action: Verify that the SDO_GEOMETRY is valid, cunsult the Oracle Spatial manual for a list of valid geometries. / 13417, 00000, "undefined raster to model space transformation" // *Cause: The raster to model space transformation associated with a GeoImage is undefined. // *Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format. / 13418, 00000, "undefined model to raster space transformation" // *Cause: The model to raster space transformation associated with a GeoImage is undefined. // *Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format. / 13419, 00000, "invalid latitude value" // *Cause: A latitude value outside the valid range [-90,90] has been used. // *Action: Verify that the GeoImage geometry definition is within the domain. / 13420, 00000, "invalid model to raster space transformation" // *Cause: The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated. // *Action: Verify that the transformation is supported and that the GeoImage format is valid. / 13421, 00000, "invalid raster to model space transformation" // *Cause: The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated. // *Action: Verify that the transformation is supported and that the GeoImage format is valid. / 13422, 00000, "uninitialized source" // *Cause: The LOB used for the source is not initialized. // *Action: Verify that the source is properly initialized. / 13423, 00000, "empty source" // *Cause: The LOB used for the source is empty. // *Action: Verify that the source is properly initialized and data has been imported into it. / 13424, 00000, "uninitialized destination" // *Cause: The LOB used for the destination is not initialized. // *Action: Verify that the destination is properly initialized. / 13425, 00000, "empty destination" // *Cause: The LOB used for the destination is empty. // *Action: Verify that the destination is properly initialized and data has been imported into it. / 13426, 00000, "unsupported raster origin" // *Cause: The raster origin specified is not supported. // *Action: Verify that the origin specified is supported. / 13427, 00000, "unknown raster origin" // *Cause: The value specified for the raster origin is invalid. // *Action: Verify that the value used to specify the raster origin is valid and supported. / 13428, 00000, "source does not exist" // *Cause: The source does not exist or cannot be accessed. // *Action: Verify that the source specification is correct and accessible. / 13429, 00000, "operation \"%s\" not supported on GeoImage type \"%s\"" // *Cause: The specified operation is not supported on the particular geoimage type. // *Action: Verify that the operation is supported. / 13430, 00000, "model coordinate system not supported" // *Cause: The model specified for the definition of the coordinate system is not supported. // *Action: Verify that the model value is correct. / 13433, 00000, "NULL crop geometry" // *Cause: The geometry used to crop a GeoImage is NULL. // *Action: Verify that the geometry used for the crop operation is not NULL. / 13442, 00000, "invalid scaling parameters [%s] [%s]" // *Cause: The parameters used in the scale operation are invalid. // *Action: Verify that the scaling parameters are greater than zero. / 13443, 00000, "unrecognized scale mode [%s]" // *Cause: The scale mode used in the scale operation is invalid. // *Action: Consult the Oracle interMedia manual for a list of valid scale mode qualifiers. / 13451, 00000, "unsupported conversion format [%s]" // *Cause: The format specified for conversion is invalid or unsupported. // *Action: Verify that the conversion format specified is valid. / 13461, 00000, "invalid tag/key [%s]" // *Cause: The tag or key is invalid. // *Action: Verify that the format version is supported or the format is valid. / 13462, 00000, "invalid tie point" // *Cause: One of the tie points is invalid. // *Action: Verify that the tie points used are valid (for example all raster tie points are >= 0). / 13463, 00000, "unsupported GeoTIFF geometry definition" // *Cause: The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported. // *Action: Verify that the GeoTIFF format version is supported and the format is valid. / 13464, 00000, "unsupported conversion" // *Cause: The format specified for conversion is not supported. // In GeoTIFF only a limited number of tags/keys combinations are supported for conversion. // *Action: Verify that the GeoTIFF format version is supported and conversion to the desired format is available. / 13465, 00000, "invalid destination window" // *Cause: The window specified as destination in the command in not valid. // *Action: Verify that the window definition is correct. / / / /13499, 00000, "%s" // *Cause: This is an internal Spatial Cartridge error // *Action: Contact Oracle Worldwide Support. / / / 14000 - 14999 reserved for Partitioned object project / / 14000 - 14099 reserved for parsing new syntax introduced by the Partitioned / object project 14000, 00000, "only one LOCAL clause may be specified" // *Cause: CREATE INDEX statement contained more than one LOCAL clause // *Action: Specify LOCAL option at most once 14001, 00000, "LOCAL clause contradicts previosly specified GLOBAL clause" // *CAUSE: CREATE INDEX statement contained a GLOBAL clause and a LOCAL // clause // *Action: Specify LOCAL or GLOBAL clause, but not both 14002, 00000, "only one GLOBAL clause may be specified" // *Cause: CREATE INDEX statement contained more than one GLOBAL clause // *Action: Specify GLOBAL option at most once 14003, 00000, "GLOBAL clause contradicts previosly specified LOCAL clause" // *CAUSE: CREATE INDEX statement contained a LOCAL clause and a GLOBAL // clause // *Action: Specify GLOBAL or LOCAL clause, but not both 14004, 00000, "missing PARTITION keyword" // *Cause: keyword PARTITION missing // *Action: supply missing keyword 14005, 00000, "missing RANGE keyword" // *Cause: keyword RANGE missing // *Action: supply missing keyword 14006, 00000, "invalid partition name" // *Cause: a partition name of the form is // expected but not present. // *Action: enter an appropriate partition name. 14007, 00000, "missing LESS keyword" // *Cause: keyword LESS missing // *Action: supply missing keyword 14008, 00000, "missing THAN keyword" // *Cause: keyword THAN missing // *Action: supply missing keyword 14009, 00000, "partition bound may not be specified for a LOCAL index partition" // *Cause: while parsing a CREATE INDEX statement to create a LOCAL // partitioned index, of one of partitions // was found to contain VALUES LESS THAN clause which is illegal since // a LOCAL index inherits partition bounds from its base table // *Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL // index partitions 14010, 00000, "this physical attribute may not be specified for an index partition" // *Cause: unexpected option was encountered while parsing physical // attributes of an index partition; valid options for Range or // Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, // STORAGE, PCTFREE; only TABLESPACE may be specified for Hash // partitions // *Action: remove invalid option(s) from the list of physical attributes // of an index partition // *Comment: this error could have resulted from omission of a // terminating (right) parenthesis following the list of // partition descriptions 14011, 00000, "names assigned to resulting partitions must be distinct" // *Cause: Names of partitions resulting from splitting of an // existing table or index partition are not distinct // *Action: rename resulting partition(s) to ensure that their names // are distinct and different from those of any other partition // of the table or index 14012, 00000, "resulting partition name conflicts with that of an existing partition" // *Cause: Name of a partition resulting from splitting of an // existing table or index partition is identical to that // of some other existing partition of that table or index // *Action: rename resulting partition(s) to ensure that their names // are distinct and different from those of any other partition // of the table or index 14013, 00000, "duplicate partition name" // *Cause: Name of a partition of a table or index being created is // not unique // *Action: rename partition(s) to ensure that their names are unique // among partitions of the table or index being created 14014, 00000, "maximum number of partitioning columns is 16" // *Cause: number of columns in a partitioning column list exceeded // the legal limit of 16 // *Action: modify partitioning column list so that it consists of at // most 16 columns 14015, 00000, "too many partition descriptions" // *Cause: CREATE TABLE or CREATE INDEX contained too many partition // descriptions; maximum number of partitions is 65535. // *Action: Reduce number of partitions to not exceed 65535. 14016, 00000, "underlying table of a LOCAL partitioned index must be partitioned" // *Cause: User attempted to create a LOCAL partitioned index on a // non-partitioned table which is illegal. Only GLOBAL indices // (partitioned or otherwise) may be created on a // non-partitioned table. // *Action: Correct the statement and reenter 14017, 00000, "partition bound list contains too many elements" // *Cause: Partition bound list contained more elements than there are // partitioning columns // *Action: Ensure that the number of elements in partition bound list is // equal to the number of partitioning columns of the table or index 14018, 00000, "partition bound list contains too few elements" // *Cause: Partition bound list contained fewer elements than there are // partitioning columns // *Action: Ensure that the number of elements in partition bound list is // equal to the number of partitioning columns of the table or index 14019, 00000, "partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE" // *Cause: Partition bound list contained an element of invalid type // (i.e. not a number, non-empty string, datetime or interval literal, // or MAXVALUE) // *Action: Ensure that all elements of partition bound list are of valid type 14020, 00000, "this physical attribute may not be specified for a table partition" // *Cause: unexpected option was encountered while parsing physical // attributes of a table partition; valid options for Range or // Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, // STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified // for Hash partitions // *Action: remove invalid option(s) from the list of physical attributes // of a table partition // *Comment: this error could have resulted from omission of a // terminating (right) parenthesis following the list of // partition descriptions 14021, 00000, "MAXVALUE must be specified for all columns" // *Cause: In the VALUES LESS THAN clause for the highest (last) partition // of a GLOBAL index, MAXVALUE must be specified for all columns // *Action: Ensure that VALUES LESS THAN clause for the last partition of a // GLOBAL index has MAXVALUE specified for all columns 14022, 00000, "creation of LOCAL partitioned cluster indices is not supported" // *Cause: An attempt was made to create a LOCAL partitioned // cluster index, which is currently illegal // *Action: Remove LOCAL along with s, if any, from // the CREATE INDEX statement. 14023, 00000, "creation of GLOBAL partitioned cluster indices is not supported" // *Cause: An attempt was made to create a GLOBAL partitioned // cluster index, which is currently illegal // *Action: Remove PARTITION BY RANGE clause along with // s from the CREATE INDEX statement. 14024, 00000, "number of partitions of LOCAL index must equal that of the underlying table" // *Cause: User attempted to create a LOCAL partitioned index with a // number of partitions which is different from that of the // underlying table. //* Action: Correct the CREATE INDEX statement to specify a correct // number of partitions 14025, 00000, "PARTITION may not be specified for a materialized view or a materialized view log" // *Cause: PARTITION option was encountered while parsing a // definition of a materialized view or a materialized view log // *Action: Ensure that a definition of a MATERIALIZED VIEW does not // include invalid options 14026, 00000, "PARTITION and CLUSTER clauses are mutually exclusive" // *Cause: definition of a table contained both PARTITION and CLUSTER clauses // which is illegal // *Action: Remove one of the conflicting clauses 14027, 00000, "only one PARTITION clause may be specified" // *Cause: CREATE TABLE statement contained more than one PARTITION clause // *Action: Specify PARTITION option at most once 14028, 00000, "missing AT or VALUES keyword" // *Cause: keyword AT or VALUES missing // *Action: supply missing keyword 14029, 00000, "GLOBAL partitioned index must be prefixed" // *Cause: partitioning columns of a global partitioned index must // form a prefix of the index' key columns // *Action: Ensure that the GLOBAL partitioned index being created is prefixed 14030, 00000, "non-existent partitioning column in CREATE TABLE statement" // *Cause: Partitioning column specified in CREATE TABLE statement is // not one of columns of the table being created. // *Action: Ensure that all columns in the partitioning column list // are columns of the table being created. 14031, 00000, "partitioning column may not be of type LONG or LONG RAW" // *Cause: Partitioning column specified by the user was of type LONG // or LONG RAW, which is illegal. // *Action: Ensure that no partitioning column is of type LONG or LONG RAW. 14032, 00000, "partition bound of partition number %s is too high" // *Cause: High bound of the partition whose number (partitions are // numbered starting with 1) is displayed in this message // did not collate lower than that of the following partition, // which is illegal. // *Action: Ensure that high bound of every partition (except for the last // one) collates lower than that of a following partition. 14033, 00000, "ctchvl: unexpected strdef type" // *Document: NO // *Cause: opndef representation of an element of partition bound list had // strtyp set to unexpected value (must be STRTCONS or STRTMAXV) // *Action: Ensure that prsott and prspstr agree on what constitutes a valid // element of partition bound list 14034, 00000, "ctchvl: unexpected operand type" // *Document: NO // *Cause: opndef representation of an element of partition bound list had // opntyp set to unexpected value (must be OPNTSTR) // *Action: Ensure that prsott and prspstr agree on what constitutes a valid // element of partition bound list 14035, 00000, "ctchvl: unexpected string data type" // *Document: NO // *Cause: opndef representation of a string element of partition bound list // had opndty set to unexpected value (must be OPNCHR or OPNNUM) // *Action: Ensure that prsott and prspstr agree on what constitutes a valid // element of partition bound list 14036, 00000, "partition bound value too large for column" // *Cause: Length of partition bound value is longer than that of the // corresponding partitioning column. // *Action: Ensure that lengths of high bound values do not exceed those of // corresponding partitioning columns 14037, 00000, "partition bound of partition \"%s\" is too high" // *Cause: High bound of the partition whose name (explicitly specified // by the user) is displayed in this message did not collate // lower than that of the following partition, which is illegal. // *Action: Ensure that high bound of every partition (except for the last // one) collates lower than that of a following partition. 14038, 00000, "GLOBAL partitioned index must be prefixed" // *Cause: User attempted to create a GLOBAL non-prefixed partitioned index // which is illegal // *Action: If the user, indeed, desired to create a non-prefixed // index, it must be created as LOCAL; otherwise, correct the list // of key and/or partitioning columns to ensure that the index is // prefixed 14039, 00000, "partitioning columns must form a subset of key columns of a UNIQUE index" // *Cause: User attempted to create a UNIQUE partitioned index whose // partitioning columns do not form a subset of its key columns // which is illegal // *Action: If the user, indeed, desired to create an index whose // partitioning columns do not form a subset of its key columns, // it must be created as non-UNIQUE; otherwise, correct the // list of key and/or partitioning columns to ensure that the index' // partitioning columns form a subset of its key columns 14040, 00000, "inadequate number of arguments passed to TABLE$OR$INDEX$PART$NUM" // *Document: NO // *Cause: TABLE$OR$INDEX$PART$NUM was supplied with fewer than 3 // arguments which is illegal // *Action: Supply TABLE$OR$INDEX$PART$NUM with table name, index // dictionary object number or 0, and as many expressions // (e.g. column names) as there are partitioning columns // in the table or index mapping into a partition of which // is to be determined 14041, 00000, "partition bound may not be specified for resulting partitions" // *Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, // of a resulting partition was found to // contain VALUES LESS THAN clause which is illegal // *Action: remove VALUES LESS THAN clause from the description(s) of // partitions resulting from splitting an existing table or // index partition 14042, 00000, "partition bound may not be specified for a partition being moved, modified or rebuilt" // *Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, // ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION // statement, description of new physical attributes of the // partition being moved, modified, or rebuilt was found to // contain VALUES LESS THAN clause which is illegal // *Action: remove VALUES LESS THAN clause from the description of new // attributes of the partition being moved, modified, or rebuilt 14043, 00000, "only one partition may be added" // *Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one // partition to be added // *Action: Ensure that the statement contains exactly one partition // definition and that it does not contain any commas 14044, 00000, "only one partition may be moved" // *Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one // partition to be moved // *Action: Ensure that the statement describes exactly one partition // to be moved and that it does not contain any commas 14045, 00000, "only one partition may be modified" // *Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of // more than one partition to be modified // *Action: Ensure that the statement describes exactly one partition // to be modified and that it does not contain any commas 14046, 00000, "a partition may be split into exactly two new partitions" // *Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain // descriptions of exactly two new partitions into which an existing // table or index partition was to be split // *Action: Ensure that the statement describes exactly two partition // into which an existing partition is to be split 14047, 00000, "ALTER TABLE|INDEX RENAME may not be combined with other operations" // *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine // a RENAME operation with some other operation which is illegal // *Action: Ensure that RENAME operation is the sole operation specified in // ALTER TABLE or ALTER INDEX statement; 14048, 00000, "a partition maintenance operation may not be combined with other operations" // *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine // a partition maintenance operation (e.g. MOVE PARTITION) with some // other operation (e.g. ADD PARTITION or PCTFREE which is illegal // *Action: Ensure that a partition maintenance operation is the sole // operation specified in ALTER TABLE or ALTER INDEX statement; // operations other than those dealing with partitions, // default attributes of partitioned tables/indices or // specifying that a table be renamed (ALTER TABLE RENAME) may be // combined at will 14049, 00000, "invalid ALTER TABLE MODIFY PARTITION option" // *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, // STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was // specified in an ALTER TABLE MODIFY PARTITION statement for // a Range or Composite Range partition. // *Action: Specify only legal options. 14050, 00000, "invalid ALTER INDEX MODIFY PARTITION option" // *Cause: An option other than INITRANS, MAXTRANS, STORAGE, // or DEALLOCATE UNUSED was specified in an // ALTER INDEX MODIFY PARTITION statement. // *Action: Specify only legal options. 14051, 00000, "invalid ALTER MATERIALIZED VIEW option" // *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, // or BACKUP was specified in an ALTER MATERIALIZED VIEW statement. // *Action: Specify only legal options. 14052, 00000, "partition-extended table name syntax is disallowed in this context" // *Cause: User attempted to use partition-extended table name syntax // in illegal context (i.e. not in FROM-clause or INSERT, DELETE, // or UPDATE statement) // *Action: Avoid use of partition-extended table name in contexts other // those mentioned above. 14053, 00000, "illegal attempt to modify %s in %s statement" // *Cause: Certain attributes of objects (e.g. tables) may be // specified at creation time, but may not be modified using ALTER // statement. Unfortunately, user specified one of such attributes. // *Action: Ensure that ALTER statement specifies new values only for // attributes which may be changed once an object has been created 14054, 00000, "invalid ALTER TABLE TRUNCATE PARTITION option" // *Cause: Name of the partition to be truncated may be followed by // DROP STORAGE or REUSE STORAGE // *Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE // are specified with ALTER TABLE TRUNCATE PARTITION 14055, 00000, "keyword REBUILD in ALTER INDEX REBUILD must immediately follow " // *Cause: ALTER INDEX statement contained REBUILD keyword following // some index attributes (e.g. INITRANS.) // *Action: Ensure that keyword REBUILD immediately follows the name // of the index being altered 14056, 00000, "partition number %s: sum of PCTUSED and PCTFREE may not exceed 100" // *Cause: the sum of PCTUSED and PCTFREE for a partition whose number // (partitions are numbered starting with 1) is displayed in this // message exceeds 100. Note that if PCTUSED and/or PCTFREE // values for this partition were not specified explicitly, // default values for the partitioned table or index would be // used. If, in turn, default PCTUSED and/or PCTFREE values // for the partitioned table or index were not specified, // system defaults would be used. // *Action: ensure that a sum of PCTUSED and PCTFREE for the partition // does not exceed 100 14057, 00000, "partition \"%s\": sum of PCTUSED and PCTFREE may not exceed 100" // *Cause: the sum of PCTUSED and PCTFREE for a partition whose name // (explicitly specified by the user) is displayed in this // message exceeds 100. Note that if PCTUSED and/or PCTFREE // values for this partition were not specified explicitly, // default values for the partitioned table or index would be // used. If, in turn, default PCTUSED and/or PCTFREE values // for the partitioned table or index were not specified, // system defaults would be used. // *Action: ensure that a sum of PCTUSED and PCTFREE for the partition // does not exceed 100 14058, 00000, "partition number %s: INITRANS value must be less than MAXTRANS value" // *Cause: Value of INITRANS was found to be greater than that of MAXTRANS // for a partition whose number (partitions are numbered starting // with 1) is displayed in this message. Note that if INITRANS // and/or MAXTRANS values for this partition were not specified // explicitly, default values for the partitioned table or index // would be used. If, in turn, default INITRANS and/or MAXTRANS // values for the partitioned table or index were not specified, // system defaults would be used. // *Action: ensure that value of INITRANS (whether specified explcitly or // derived from the default value for the partitioned table or // index) is no greater than that of MAXTRANS 14059, 00000, "partition \"%s\": INITRANS value must be less than MAXTRANS value" // *Cause: Value of INITRANS was found to be greater than that of MAXTRANS // for a partition whose name (explicitly specified by the user) // is displayed in this message. Note that if INITRANS // and/or MAXTRANS values for this partition were not specified // explicitly, default values for the partitioned table or index // would be used. If, in turn, default INITRANS and/or MAXTRANS // values for the partitioned table or index were not specified, // system defaults would be used. // *Action: ensure that value of INITRANS (whether specified explcitly or // derived from the default value for the partitioned table or // index) is no greater than that of MAXTRANS 14060, 00000, "data type or length of a table partitioning column may not be changed" // *Cause: User issued ALTER TABLE statement attempting to modify // data type and/or length of a column used to partition the // table named in ALTER TABLE statement, which is illegal // *Action: Avoid modifying data type and/or length of table // partitioning column(s) 14061, 00000, "data type or length of an index partitioning column may not be changed" // *Cause: User issued ALTER TABLE statement attempting to modify // data type and/or length of a column used to partition some index // defined on the table named in ALTER TABLE statement, which is // illegal // *Action: Avoid modifying data type and/or length of index // partitioning column(s) 14062, 00000, "one or more of table's partitions reside in a read-only tablespace" // *Cause: User issued ALTER TABLE statement attempting to modify // an existing VARCHAR2 (or VARCHAR) column to be of type CHAR // (or CHARACTER), increase length of an existing CHAR (or // CHARACTER) column, or add a column with user-specified default for // a table one or more partitions of which reside in read-only // tablespaces, which is illegal // *Action: Avoid performing aformentioned operations on a partitioned // table one or more partitions of which reside in read-only // tablespaces 14063, 00000, "Unusable index exists on unique/primary constraint key" // *Cause: User attempted to add or enable a primary key/unique constraint // on column(s) of a table on which there exists an index marked // Index Unusable. // *Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD 14064, 00000, "Index with Unusable partition exists on unique/primary constraint key" // *Cause: User attempted to add or enable a primary key/unique constraint // on column(s) of a table on which there exists an index one or // more partitions of which are marked Index Unusable. // *Action: Drop the existing index or rebuild unusable partitions it // using ALTER INDEX REBUILD PARTITION 14065, 00000, "ALLOCATE STORAGE may not be specified for a partitioned table" // *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement // issued against a partitioned table which is illegal. // *Action: Remove the illegal option. If it is desired to add // storage to individual partitions, ALLOCATE STORAGE clause // may be specified with ALTER TABLE MODIFY PARTITION statement. 14066, 00000, "illegal option for a non-partitioned table" // *Cause: An attempt was made to issue a CREATE TABLE or ALTER TABLE command // on a non-partitioned table, but the command contains an option // that is legal only for partitioned tables. Such options are: // ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT. // *Action: Remove the illegal option(s) from the command. 14067, 00000, "duplicate TABLESPACE_NUMBER specification" // *Cause: TABLESPACE_NUMBER clause was specified more than once for // an table, index or an index partition // *Action: Correct the code generating text of CREATE INDEX statement // sent to the slaves 14068, 00000, "TABLESPACE and TABLESPACE_NUMBER may not be both specified" // *Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified // for a table, index or an index partition // *Action: Correct the code generating text of CREATE INDEX statement // sent to the slaves 14069, 00000, "invalid TABLESPACE_NUMBER value" // *Cause: The TABLESPACE_NUMBER value is not an integer between 0 and // 0x7FFFFFFF // *Action: Correct the code generating text of CREATE INDEX statement // sent to the slaves 14070, 00000, "option may be specified only for partitioned indices or with REBUILD" // *Cause: User issued ALTER INDEX statament containing an option // which is legal only for partitioned indices or in conjunction // with REBUILD against a non-partitioned index. Such options are: // PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and // FREELIST GROUPS inside STORAGE clause // *Action: Remove illegal option(s). 14071, 00000, "invalid option for an index used to enforce a constraint" // *Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, // MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, // UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was // specified for an index used to enforce a constraint. // *Action: Choose one of the valid index options. 14072, 00000, "fixed table may not be truncated" // *Cause: User attempted to truncate a fixed table which is illegal. // *Action: Ensure that the table being truncated is not a fixed table. 14073, 00000, "bootstrap table or cluster may not be truncated" // *Cause: User attempted to truncate a bootstrap table or cluster which // is illegal // *Action: Ensure that the table (or cluster) being truncated is not a // bootstrap table (or cluster) 14074, 00000, "partition bound must collate higher than that of the last partition" // *Cause: Partition bound specified in ALTER TABLE ADD PARTITION // statement did not collate higher than that of the table's // last partition, which is illegal. // *Action: Ensure that the partition bound of the partition to be added // collates higher than that of the table's last partition. 14075, 00000, "partition maintenance operations may only be performed on partitioned indices" // *Cause: Index named in ALTER INDEX partition maintenance operation // is not partitioned, making a partition maintenance operation, // at best, meaningless // *Action: Ensure that the index named in ALTER INDEX statement // specifying a partition maintenance operation is, indeed, // partitioned 14076, 00000, "DROP/SPLIT PARTITION may not be applied to a LOCAL index partition" // *Cause: User attempted to drop or split a partition of a LOCAL index // which is illegal. // *Action: Ensure that the index named in such statement is a GLOBAL // partitioned index. 14078, 00000, "you may not drop the highest partition of a GLOBAL index" // *Cause: User attempted to drop highest partition of a GLOBAL index, // which is illegal. // *Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION // statement is not the highest partition of the index. 14079, 00000, "illegal option for a partition marked Index Unusable" // *Cause: ALTER INDEX MODIFY PARTITION statement against an index // partition marked Index Unusable contained STORAGE and/or // DEALLOCATE SPACE clauses which is illegal // *Action: Ensure that only valid optins are specified 14080, 00000, "partition cannot be split along the specified high bound" // *Cause: User attempted to split a partition along a bound which // either collates higher than that of the partition to be split or // lower than that of a partition immediately preceding the one // to be split // *Action: Ensure that the bound along which a partition is to be split // collates lower than that of the partition to be split and // higher that that of a partition immediately preceding the one // to be split 14081, 00000, "new partition name must differ from the old partition name" // *Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying // which is identical to the name of the // partition being renamed // *Action: Ensure that the new partition name is different from the // name of any (including the one being renamed) existing // partition of a given table or index 14082, 00000, "new partition name must differ from that of any other partition of the object" // *Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying // which is identical to the name of some // existing partition of the object // *Action: Ensure that the new partition name is different from the // name of any (including the one being renamed) existing // partition of a given table or index 14083, 00000, "cannot drop the only partition of a partitioned table" // *Cause: A drop partition command is being executed when there // is only one partition in the table // *Action: Ensure that there is at least one partition. // Drop table to remove all partitions 14084, 00000, "you may specify TABLESPACE DEFAULT only for a LOCAL index" // *Cause: User attempted to specify TABLESPACE DEFAULT for an // object other than a LOCAL index, which is illegal. // *Action: Reenter the statement without TABLESPACE DEFAULT clause. 14085, 00000, "partitioned table cannot have column with LONG datatype" // *Cause: User tried to create a partitioned table with a LONG datatype // or tried to add a LONG datatype column to a partitioned table. // *Action: LONG data types are not supported with partitioned tables. // Create table without LONG column or change table to not // partitioned. If adding column, do not use LONG datatype. // If modifying attributes of a column to change data type to // LONG, it has to be a non partitioned table. 14086, 00000, "a partitioned index may not be rebuilt as a whole" // *Cause: User attempted to rebuild a partitioned index using // ALTER INDEX REBUILD statement, which is illegal // *Action: Rebuild the index a partition at a time (using // ALTER INDEX REBUILD PARTITION) or drop and recreate the // entire index 14087, 00000, "use of PARTITION (|) syntax" // *Document: NO // *Cause: // *Action: // Level 1+ Allow use of aforementioned syntax 14088, 00000, "second argument to TABLE$OR$INDEX$PART$NUM must be an integer constant" // *Document: NO // *Cause: Second argument to TABLE$OR$INDEX$PART$NUM (must be index // object ID or 0) was found not to be an integer constant // *Action: Ensure that the second argument passed to TABLE$OR$INDEX$PART$NUM // is an integer constant representing object ID of an index if it // is desired that that indes' partition mapping descriptor // be used or 0 otherwise 14089, 00000, "base table does not have an index with a specified ID defined on it" // *Document: NO // *Cause: Second argument to TABLE$OR$INDEX$PART$NUM was non-zero, implying // that the partition mapping descriptor of an index defined on // the table whose name was supplied as the first srgument // is to be used, but that table does not have an index with // the specified object ID defined on it. // *Action: Ensure that the object ID suplied as the second argument // is that of an index defined on the table whose name was // supplied as the first argument. 14090, 00000, "index must be partitioned" // *Document: NO // *Cause: Index whose ID was supplied by the user as the second // argument to TABLE$OR$INDEX$PART$NUM was not partitioned // *Action: Second argument passed to TABLE$OR$INDEX$PART$NUM must be an // object ID of a partitioned index defined on the table whose // name was supplied as the first argument if one desires to determine // mapping into an index partition or 0 if one desires to // determine mapping into a partition of the base table itself 14091, 00000, "table must be partitioned" // *Document: NO // *Cause: Table whose name was supplied by the user as the first // argument to TABLE$OR$INDEX$PART$NUM was not partitioned // *Action: If one desires to determine mapping of rows into a // partition of a base table, one must supply a name of // a partitioned table as the first argument and 0 as the // second argument. If, on the other hand, one desires to // determine mapping of rows into a partition of an index // defined on that table, one must supply that index' object // ID as the second argument 14092, 00000, "number of expressions is not equal to the number of partitioning columns" // *Document: NO // *Cause: Number of expressions submitted to TABLE$OR$INDEX$PART$NUM differs // from the number of partitioning columns of the table or index // mapping into partition(s) of which is to be determined // *Action: Supply a correct number of expressions to be used in // determining mapping into partition(s) of a specified // table or index 14093, 00000, "data type of expression incompatible with that of partitioning column" // *Document: NO // *Cause: Data type of an expression was neiher equal to nor // coercible into that of a corresponding partitioning column // of a table or index mapping into partition(s) of which is // of interest // *Action: Ensure that data types of expressions supplied to // TABLE$OR$INDEX$PART$NUM are compatible with those of // corresponding partitioning columns of a table or index // mapping into partition(s) of which is of interest 14094, 00000, "invalid ALTER TABLE EXCHANGE PARTITION option" // *Cause: Name of the table to be EXCHANGED has to be followed // by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] // *Action: Ensure that no options besides INCLDING INDEX or EXCLUDING // INDEX are specified with ALTER TABLE EXCHANGE PARTITION 14095, 00000, "ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table" // *Cause: The table in the EXCHANGE operation is either clustered or // partitioned // *Action: Ensure that the table with which the partition is being exchanged // for is not partitioned or clustered. 14096, 00000, "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns" // *Cause: The two tables specified in the EXCHANGE have different number // of columns // *Action: Ensure that the two tables have the same number of columns // with the same type and size. 14097, 00000, "column type or size mismatch in ALTER TABLE EXCHANGE PARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE PARTITION are of different type or size // *Action: Ensure that the two tables have the same number of columns // with the same type and size. 14098, 00000, "index mismatch for tables in ALTER TABLE EXCHANGE PARTITION" // *Cause: The two tables specified in the EXCHANGE have indexes which are // not equivalent // *Action: Ensure that the indexes for the two tables have indexes which // follow this rule // For every non partitioned index for the non partitioned table, // there has to be an identical LOCAL index on the partitioned // table and vice versa. By identical, the column position, type // and size have to be the same. 14099, 00000, "all rows in table do not qualify for specified partition" // *Cause: There is at least one row in the non partitioned table which // does not qualify for the partition specified in the ALTER TABLE // EXCHANGE PARTITION // *Action: Ensure that all the rows in the segment qualify for the partition. // Perform the alter table operation with the NO CHECKING option. // Run ANALYZE table VALIDATE on that partition to find out the // invalid rows and delete them. 14100, 00000, "partition extended table name cannot refer to a remote object" // *Cause: User attempted to use partition-extended table name syntax // in conjunction with remote object name which is illegal // *Action: Correct the statement and reenter 14101, 00000, "partition extended table name cannot refer to a synonym" // *Cause: User attempted to use partition-extended table name syntax // in conjunction with synonym name which is illegal // *Action: Correct the statement and reenter 14102, 00000, "only one LOGGING or NOLOGGING clause may be specified" // *Cause: LOGGING was specified more than once, NOLOGGING was specified // more than once, or both LOGGING and NOLOGGING were specified. // *Action: Remove all but one of the LOGGING or NOLOGGING clauses and // reissue the statement. 14103, 00000, "LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE" // *Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses // which is disallowed. // *Action: Remove one of the offending clauses. // [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, // create an object with NOLOGGING option and then ALTER it specifying // LOGGING. To duplicate semantics of RECOVERABLE clause, // create an object with LOGGING option. 14104, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices" // *Cause: CREATE TABLE/INDEX statement used to create a partitioned // table/index contained RECOVERABLE or UNRECOVERABLE clause // which is illegal // *Action: Remove offending clause. // [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, // create an object with NOLOGGING option and then ALTER it specifying // LOGGING. To duplicate semantics of RECOVERABLE clause, // create an object with LOGGING option. 14105, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified in this context" // *Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context. // *Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may // only be specified in CREATE TABLE/INDEX statement describing a // non-partitioned table or index and ALTER INDEX REBUILD statement. // [UN]RECOVERABLE is being deprecated in V8 and will be // obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, // create an object with NOLOGGING option and then ALTER it specifying // LOGGING. To duplicate semantics of RECOVERABLE clause, // create an object with LOGGING option. 14106, 00000, "LOGGING/NOLOGGING may not be specified for a clustered table" // *Cause: User attempted to specify LOGGING or NOLOGGING clausein // CREATE TABLE or ALTER TABLE statement involving a // clustered table // *Action: Remove offending clause. 14107, 00000, "partition specification is required for a partitioned object" // *Cause: parameter which supplies partition name is missing. This // parameter is optional for non-partitioned objects, but is required // for partitioned objects. // *Action: supply missing parameter 14108, 00000, "illegal partition-extended table name syntax" // *Cause: Partition to be accessed may only be specified using its name. // User attempted to use a partition number or a bind variable. // *Action: Modify statement to refer to a partition using its name 14109, 00000, "partition-extended object names may only be used with tables" // *Cause: User attempted to use a partition-extended object name // with an object which is not a table. // *Action: Avoid using partition-extended name syntax with objects // which are not tables 14110, 00000, "partitioning column may not be of type ROWID" // *Cause: Partitioning column specified by the user was of type ROWID, // which is illegal. // *Action: Ensure that no partitioning column is of type ROWID. 14111, 00000, "creation of GLOBAL partitioned indices on clustered tables is not supported" // *Cause: An attempt was made to create a GLOBAL partitioned index on a // clustered table which is currently illegal. // *Action: Remove PARTITION BY RANGE() clause along with () // to create a GLOBAL non-partitioned index on a clustered table 14112, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition" // *Cause: Description of a partition or subpartition found in // CREATE TABLE/INDEX statement contained RECOVERABLE or // UNRECOVERABLE clause which is illegal // *Action: Remove offending clause. Use LOGGING or NOLOGGING instead. 14113, 00000, "partitioned table cannot have column with LOB datatype" // *Cause: User tried to create a partitioned table with a LOB datatype // or tried to add a LOB datatype column to a partitioned table. // *Action: LOB data types are not supported with partitioned tables. // Create table without LOB column or change table to not // partitioned. If adding column, do not use LOB datatype. // If modifying attributes of a column to change data type to // LOB, it has to be a non partitioned table. 14114, 00000, "partitioned table cannot have column with object, REF, nested table, array datatype" // *Cause: User tried to create a partitioned table with a object datatype // (object, REF, nested table, array) // or tried to add a object datatype column to a partitioned table. // *Action: object data types are not supported with partitioned tables. // Create table without object column or change table to not // partitioned. If adding column, do not use object datatypes. // If modifying attributes of a column to change data type to // object, it has to be a non partitioned table. 14115, 00000, "partition bound of partition number %s is too long" // *Cause: Length of linear key representation of a high bound of the // partition whose number (partitions are numbered starting with 1) // is displayed in this message exceeded the legal limit (4K). // *Action: Change representation of a partition high bound to bring // its length within legal limit. 14116, 00000, "partition bound of partition \"%s\" is too long" // *Cause: Length of linear key representation of a high bound of the // partition whose name (explicitly specified by the user) is // displayed in this message exceeded the legal limit (4K). // *Action: Change representation of a partition high bound to bring // its length within legal limit. 14117, 00000, "partition resides in offlined tablespace" // *Cause: User attempted an operation requiring that we access data // in a partition which resides in a tablespace which was // taken offline. Such operations include trying to drop a // tablespace of a table which has indices defined on it or // is referenced by a constraint. // *Action: Bring tablespace online before attempting the operation. 14118, 00000, "CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint // defined on them. // *Action: Ensure that the two tables do not have CHECK constraint // defined on any column 14119, 00000, "specified partition bound is too long" // *Cause: Length of a linear key representation of a high bound of a table // partition being added or along which an existing table or // index partition is being split exceeded the legal limit (4K). // *Action: Change representation of a partition high bound to bring // its length within legal limit. 14120, 00000, "incompletely specified partition bound for a DATE column" // *Cause: An attempt was made to use a date expression whose format // does not fully (i.e. day, month, and year (including century)) // specify a date as a partition bound for a DATE column. // The format may have been specified explicitly (using // TO_DATE() function) or implicitly (NLS_DATE_FORMAT). // *Action: Ensure that date format used in a partition bound for a // DATE column supports complete specification of a date // (i.e. day, month, and year (including century)). // If NLS_DATE_FORMAT does not support complete // (i.e. including the century) specification of the year, // use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') // to fully express the desired date. 14121, 00000, "MODIFY DEFAULT ATTRIBUTES may not be combined with other operations" // *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine // MODIFY DEFAULT ATTRIBUTES with some other operation // (e.g. ADD PARTITION or PCTFREE) which is illegal // *Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole // operation specified in ALTER TABLE or ALTER INDEX statement; // operations other than those dealing with partitions, // default attributes of partitioned tables/indices or // specifying that a table be renamed (ALTER TABLE RENAME) may be // combined at will 14122, 00000, "only one REVERSE or NOREVERSE clause may be specified" // *Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX // statement. // *Action: Remove all but one of the REVERSE or NOREVERSE clauses and // reissue the statement. 14123, 00000, "duplicate NOREVERSE clause" // *Cause: NOREVERSE was specified more than once in ALTER INDEX statement. // *Action: Remove all but one of the NOREVERSE clauses and reissue // the statement. 14124, 00000, "duplicate REVERSE clause" // *Cause: REVERSE was specified more than once in ALTER INDEX or // CREATE INDEX statements. // *Action: Remove all but one of the REVERSE clauses and reissue // the statement. 14125, 00000, "REVERSE/NOREVERSE may not be specified in this context" // *Cause: REVERSE/NOREVERSE clause is not allowed in this context. // *Action: Remove offending clause. REVERSE may be specified as an // attribute of an index (not of an individual partition, if // creating a partitioned index) in CREATE INDEX statement // and ALTER INDEX REBUILD statement. // NOREVERSE may be specified only in ALTER INDEX REBUILD statement. 14126, 00000, "only a may follow description(s) of resulting partitions" // *Cause: Descriptions of partition(s) resulting from splitting of a // table or index partition may be followed by an optional // which applies to the entire statement and // which, in turn, may not be followed by any other clause. // *Action: Ensure that all partition attributes appear within the // parenthesized list of descriptions of resulting partitions in // ALTER TABLE/INDEX SPLIT PARTITION statement. 14127, 00000, "illegal index-partition-extended table name syntax" // *Document: NO // *Cause: Index partition may be specified using IND_PARTITION() // or IND_PARTITION(). // Internal user attempted to specify an index partition name. // *Action: Modify statement to refer to an index partition using its number 14128, 00000, "FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY // constraints. // *Action: Ensure that the two tables do not have FOREIGN KEY constraints // defined on any column or disable all FOREIGN KEY constraints // on both tables. Then retry the operation. 14129, 00000, "INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints" // *Cause: Matching UNIQUE constraints in both table are enabled and validated // but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE // PARTITION|SUBPARTITION command. // *Action: Disable currently enabled matching UNIQUE constraints on both // tables or ensure that INCLUDING INDEXES option is used. 14130, 00000, "UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION" // *Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION // command has a UNIQUE constraint for which no matching (vis-a-vis // key columns) constraint is defined on the other table or // a matching constraint is defined on the other table, but it // differs from that defined on the first table vis-a-vis being // enabled and/or validated. // *Action: Ensure that for every UNIQUE constraint defined on one of the // tables named in the ALTER TABLE EXCHANGE PARTITION statement there // is a matching (vis-a-vis key columns and being enabled and/or // validated) UNIQUE constraint defined on the other table. // If UNIQUE constrains are enabled, UNIQUE constraints on the // partitioned table should be enforced using local indexes. 14131, 00000, "enabled UNIQUE constraint exists on one of the tables" // *Cause: One of the tables referenced in the ALTER TABLE EXCHANGE // PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) // defined on it, which prevents EXCHANGE from proceeding. // *Action: Disable constraints defined on tables referenced in the // ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and // retry the statement. 14132, 00000, "table cannot be used in EXCHANGE" // *Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | // SUBPARTITION command, but the non-partitioned table cannot be used // in the EXCHANGE because one or more of the following apply: // - it is a typed table // - it contains ADT columns // - it contains nested-table columns // - it contains REF columns // - it contains array columns // - it is an index-organized table // - it contains LOB columns // - it is a nested table // *Action: Make sure the non-partitioned table does not violate any // of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | // SUBPARTITION command. 14133, 00000, "ALTER TABLE MOVE cannot be combined with other operations" // *Cause: An attempt was made to combine an ALTER TABLE MOVE statement // with another operation, such as MODIFY. // *Action: Make sure that MOVE is the only operation specified in ALTER TABLE // statement; 14134, 00000, "indexes cannot use both DESC and REVERSE" // *Cause: An attempt was made to make a reverse index with some index // columns marked DESC. // *Action: Do not use DESC in reverse indexes. The rule-based optimizer can // scan indexes backwards, which allows a normal reverse index to // simulate a reverse index with columns marked DESC. 14135, 00000, "a LOB column cannot serve as a partitioning column" // *Cause: An attempt was made to specify a column of type BLOB or CLOB as a // partitioning or subpartitioning column. // *Action: Ensure that no partitioning or subpartitioning column is of type // BLOB or CLOB. 14136, 00000, "ALTER TABLE EXCHANGE restricted by fine-grained security" // *Cause: User doing exchange does not have full table access due to VPD // policies. // *Action: Grant exempt priviliges to this user. / / 14150-14249 reserved for parsing errors which may be generated / during parsing of statements added/modified by 8.1 / partitioning project 14150, 00000, "missing SUBPARTITION keyword" // *Cause: keyword SUBPARTITION missing // *Action: supply missing keyword 14151, 00000, "invalid table partitioning method" // *Cause: Invalid partitioning method was specified in CREATE TABLE // statement. A table may be partitioned by RANGE, HASH, or // Composite Range/Hash (R+H). // *Action: Specify one of valid partitioning methods 14152, 00000, "invalid number of partitions specified in PARTITIONS clause" // *Cause: number-of-partitions clause contained in CREATE TABLE or // CREATE INDEX statement specified a number of partitions // outside of legal range (1-65535) // *Action: Specify a number between 1 and 65535 in the // number-of-partitions clause 14153, 00000, "only one of STORE IN or clause may be specified" // *Cause: both STORE IN and clauses were specified // in a CREATE TABLE|INDEX command // *Action: Remove one of offending clauses 14154, 00000, "only one of STORE IN or clause may be specified" // *Cause: both STORE IN and clauses were // specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT // PARTITION or ALTER TABLE MERGE PARTITIONS command for // a Composite Range partitioned object // *Action: Remove one of offending clauses 14155, 00000, "missing PARTITION or SUBPARTITION keyword" // *Cause: expect either PARTITION or SUBPARTITION keyword but none was // supplied // *Action: supply missing keyword 14156, 00000, "invalid number of subpartitions specified in SUBPARTITIONS clause" // *Cause: number-of-subpartitions clause contained in CREATE TABLE or // CREATE INDEX statement specified a number of subpartitions // outside of legal range (1-65535) // *Action: Specify a number between 1 and 65535 in the // number-of-subpartitions clause 14157, 00000, "invalid subpartition name" // *Cause: a subpartition name of the form is expected // but not present. // *Action: enter an appropriate subpartition name. 14158, 00000, "too many subpartition descriptions" // *Cause: CREATE TABLE or CREATE INDEX contained too many subpartition // descriptions; maximum number of subpartitions is 65535. // *Action: Reduce number of subpartitions to not exceed 65535. 14159, 00000, "duplicate subpartition name" // *Cause: Name of a subpartition of a table or index being created // is not unique // *Action: rename subpartition(s) to ensure that their names are unique // among subpartitions of the table or index being created 14160, 00000, "this physical attribute may not be specified for a table subpartition" // *Cause: unexpected option was encountered while parsing physical // attributes of a table subpartition; TABLESPACE is the only valid // option // *Action: remove invalid option(s) // *Comment: this error could have resulted from omission of a // terminating (right) parenthesis following the list of // subpartition descriptions 14161, 00000, "subpartition number %s: sum of PCTUSED and PCTFREE may not exceed 100" // *Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number // (subpartitions are numbered starting with 1) is displayed in this // message exceeds 100. Note that if PCTUSED and/or PCTFREE // values for this subpartition were not specified explicitly, // default values at partition-level would be used. If, in turn, // default PCTUSED and/or PCTFREE values at partition-level were not // specified, default values for the partitioned table or index // would be used. If those values were also not specified explicitly, // system defaults would be used. // *Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition // does not exceed 100 14162, 00000, "subpartition \"%s\": sum of PCTUSED and PCTFREE may not exceed 100" // *Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name // (explicitly specified by the user) is displayed in this // message exceeds 100. Note that if PCTUSED and/or PCTFREE // values for this subpartition were not specified explicitly, // default values at partition-level would be used. If, in turn, // default PCTUSED and/or PCTFREE values at partition-level were not // specified, default values for the partitioned table or index // would be used. If those values were also not specified explicitly, // system defaults would be used. // *Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition // does not exceed 100 14163, 00000, "subpartition number %s: INITRANS value must be less than MAXTRANS value" // *Cause: Value of INITRANS was found to be greater than that of MAXTRANS // for a subpartition whose number (subpartitions are numbered starting // with 1) is displayed in this message. Note that if INITRANS // and/or MAXTRANS values for this subpartition were not specified // explicitly, default values at partition-level would be used. // If, in turn, default INITRANS and/or MAXTRANS values at // partition-level were not specified, default values for the // partitioned table or index would be used. If those values were // also not specified explicitly, system defaults would be used. // *Action: ensure that value of INITRANS (whether specified explicitly or // derived from the default value at partition-level, table-level or // index-level) is no greater than that of MAXTRANS 14164, 00000, "subpartition \"%s\": INITRANS value must be less than MAXTRANS value" // *Cause: Value of INITRANS was found to be greater than that of MAXTRANS // for a subpartition whose name (explicitly specified by the user) // is displayed in this message. Note that if INITRANS // and/or MAXTRANS values for this subpartition were not specified // explicitly, default values at partition-level would be used. // If, in turn, default INITRANS and/or MAXTRANS values at // partition-level were not specified, default values for the // partitioned table or index would be used. If those values were // also not specified explicitly, system defaults would be used. // *Action: ensure that value of INITRANS (whether specified explicitly or // derived from the default value at partition-level, table-level or // index-level) is no greater than that of MAXTRANS 14165, 00000, "MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations" // *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine // MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation // (e.g. ADD PARTITION or PCTFREE) which is illegal // *Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole // operation specified in ALTER TABLE or ALTER INDEX statement; // operations other than those dealing with partitions, // default attributes of partitioned tables/indices or // specifying that a table be renamed (ALTER TABLE RENAME) may be // combined at will 14166, 00000, "missing INTO keyword" // *Cause: keyword INTO missing // *Action: supply missing keyword 14167, 00000, "only one subpartition may be moved" // *Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than // one subpartition to be moved // *Action: Ensure that the statement describes exactly one subpartition // to be moved and that it does not contain any commas 14168, 00000, "only one subpartition may be modified" // *Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of // more than one subpartition to be modified // *Action: Ensure that the statement describes exactly one subpartition // to be modified and that it does not contain any commas 14169, 00000, "invalid ALTER TABLE MODIFY SUBPARTITION option" // *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, // STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION // statement. // *Action: Specify only legal options. 14170, 00000, "cannot specify clause in CREATE TABLE|INDEX" // *Cause: User requested to generate default partition description(s) // (possibly via PARTITIONS ) while at // the same time specified clause which // is illegal // *Action: Remove one of offending clauses. 14171, 00000, "cannot specify clause in CREATE|ALTER TABLE" // *Cause: User requested to generate default subpartition description(s) // (possibly via SUBPARTITIONS) while at the same time specified // clause which is illegal // *Action: Remove one of offending clauses. 14172, 00000, "invalid ALTER TABLE EXCHANGE SUBPARTITION option" // *Cause: Name of the table to be EXCHANGED has to be followed // by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] // *Action: Ensure that no options besides INCLDING INDEX or EXCLUDING // INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION 14173, 00000, "illegal subpartition-extended table name syntax" // *Cause: Subpartition to be accessed may only be specified using its name. // User attempted to use a subpartition number or a bind variable. // *Action: Modify statement to refer to a subpartition using its name 14174, 00000, "only a may follow COALESCE PARTITION|SUBPARTITION" // *Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by // an optional . No partition/subpartition // attributes may be specified // *Action: Ensure that no partition/subpartition attribute was specified. 14175, 00000, "a subpartition maintenance operation may not be combined with other operations" // *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine // a subpartition maintenance operation (e.g. MOVE SUBPARTITION) // with some other operation (e.g. MODIFY PARTITION ADD SUBPARTITION // or PCTFREE) which is illegal // *Action: Ensure that a subpartition maintenance operation is the sole // operation specified in ALTER TABLE or ALTER INDEX statement; // operations other than those dealing with subpartitions, // default attributes of partitioned tables/indices or // specifying that a table be renamed (ALTER TABLE RENAME) may be // combined at will 14176, 00000, "this attribute may not be specified for a hash partition" // *Cause: An invalid option was encountered while parsing physical // attributes of a partition of a table partitioned using the // HASH method. The TABLESPACE option is the only valid // option for such partitions. // *Action: Remove the invalid option(s). 14177, 00000, "STORE-IN (Tablespace list) can only be specified for a LOCAL index on a table which is hash or composite partitioned" // *Cause: STORE-IN (Tablespace list) clause was used while creating a local // index on a table which is range or list partitioned // *Action: Do not use the STORE_IN (Tablespace list) clause while creating // a local index on range or list partitioned table 14183, 00000, "TABLESPACE DEFAULT can be specified only for Composite LOCAL index" // *Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash // partitioned LOCAL index object, which is illegal. // *Action: Replace TABLESPACE DEFAULT with TABLESPACE or remove it. 14184, 00000, "cannot create an UNIQUE partitioned index on a SYSTEM partitioned table" // *Document: NO // *Cause: User attempted to create a UNIQUE partitioned index on a SYSTEM // partitioned table // *Action: Remove UNIQUE keyword 14185, 00000, "incorrect physical attribute specified for this index partition" // *Cause: unexpected option was encountered while parsing physical attributes // of a local index partition; valid options for Range or Composite Range // partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, // LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions // STORE IN () is also disallowed for all but Composite Range partitions // *Action: remove invalid option(s) from the list of physical attributes // of an index partition 14186, 0000, "number of sub-partitions of LOCAL index must equal that of the underlying table" // *Cause: User attempted to create a LOCAL partitioned index with a // number of sub-partitions which is different from that of the // underlying table. //* Action: Correct the CREATE INDEX statement to specify a correct // number of sub-partitions 14187, 0000, "partitioning method for LOCAL index is inconsistent with that of the underlying table" // *Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with // the underlying table. The partitioning types are mismatched. // *Action: Correct the CREATE INDEX statement to ensure that the index partitionining // method is consistent with that of the base table 14188, 0000, "sub-partitioning columns must form a subset of key columns of a UNIQUE index" // *Cause: User attempted to create a UNIQUE partitioned index whose // sub-partitioning columns do not form a subset of its key columns // which is illegal // *Action: If the user, indeed, desired to create an index whose // subpartitioning columns do not form a subset of its key columns, // it must be created as non-UNIQUE; otherwise, correct the // list of key and/or subpartitioning columns to ensure that the index' // subpartitioning columns form a subset of its key columns 14189, 00000, "this physical attribute may not be specified for an index subpartition" // *Cause: unexpected option was encountered while parsing physical // attributes of an index subpartition; TABLESPACE is the only valid // option // *Action: remove invalid option(s) 14190, 00000, "only one ENABLE/DISABLE ROW MOVEMENT clause can be specified" // *Cause: One of three possible actions caused the error: // 1) ENABLE ROW MOVEMENT was specified more than once. // 2) DISABLE ROW MOVEMENT was specified more than once. // 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were // specified. // *Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW // MOVEMENT clauses; then, reissue the command. 14191, 00000, "ALLOCATE STORAGE may not be specified for Composite Range partitioned object" // *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement // issued against a range-partitioned index which is illegal. // *Action: Remove the illegal option. If it is desired to add // storage to individual partitions, ALLOCATE STORAGE clause // may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. // 14192, 00000, "cannot modify physical index attributes of a Hash index partition" // *Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE // clause for an index partition of a Hash partitioned index // *Action: Remove the physical attributes one is trying to modify // 14193, 0000, "invalid ALTER INDEX MODIFY SUBPARTITION option" // *Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED // was specified in an ALTER INDEX MODIFY SUBPARTITION statement. // *Action: Specify only legal options. 14194, 00000, "only one subpartition may be rebuilt" // *Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than // one subpartition to be rebuilt // *Action: Ensure that the statement describes exactly one subpartition // to be rebuilt and that it does not contain any commas 14195, 00000, "ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object" // *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement // issued against a range-partitioned index which is illegal. // *Action: Remove the illegal option. If it is desired to add // storage to individual partitions, ALLOCATE STORAGE clause // may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. 14240, 00000, "use of syntax for SYSTEM and Range Composite/System (R+S) partitioning methods" // *Document: NO // *Cause: // *Action: // Level 1+ Allow use of aforementioned syntax 14241, 00000, "invalid table partitioning method" // *Document: NO // *Cause: Invalid partitioning method was specified in CREATE TABLE // statement. A table may be partitioned by RANGE, SYSTEM, // HASH, or Composite Range (R+S or R+H)." // *Action: Specify one of valid partitioning methods 14242, 00000, "table is not partitioned by System, or Hash method" // *Document: NO // *Cause: The table in the ADD PARTITIONS operation is partitioned by // method other than System, or Hash // *Action: Ensure that the table is partitioned by System, or // Hash method 14243, 00000, "table is not partitioned by Range, System, or Hash method" // *Document: NO // *Cause: The table in the MOVE PARTITION operation is partitioned by // method other than Range, System, or Hash method // *Action: Ensure that the table is partitioned by Range, System, or // Hash method 14244, 00000, "illegal operation for a System or Composite Range/System partitioned table" // *Document: NO // *Cause: any operation done to a System or Composite Range/System // partitioned table is controlled through event 14240 // *Action: Ensure that the event is turned on / / 14250-14349 reserved for errors which may be generated during / processing of DDL statements added/modified by 8.1 / partitioning project 14251, 00000, "Specified subpartition does not exist" // *Cause: Subpartition not found for the object. // *Action: Retry with correct subpartition name. 14252, 00000, "invalid ALTER TABLE MODIFY PARTITION option for a Hash partition" // *Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified // in ALTER TABLE MODIFY PARTITION for a Hash partition. // *Action: Specify only legal options. 14253, 00000, "table is not partitioned by Composite Range method" // *Cause: The table in a subpartition maintenance operation (ALTER TABLE // EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY // PARTITION ADD/COALESCE SUBPARTITION command must be partitioned // by Composite Range method // *Action: Ensure that the table is partitioned by Composite Range method 14254, 00000, "cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table" // *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement // issued against a Range or Composite Range partitioned table // which is illegal. // *Action: Remove the illegal option. If it is desired to add storage to // individual partitions/subpartitions, ALLOCATE STORAGE clause // may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION // statement. If it is desired to add storage to all subpartitions // of a Composite partition, ALLOCATE STORAGE clause may be specified // with ALTER TABLE MODIFY PARTITION. 14255, 00000, "table is not partitioned by Range, Composite Range or List method" // *Cause: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS // command is only valid for table partitioned by Range, List or // Composite Range method // *Action: Ensure that the table is partitioned by Range, List or Composite // Range method 14256, 00000, "invalid resulting partition description(s)" // *Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or // clause in partition description(s) // in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS // statement but the table in the maintenance operation is not // a Composite Range partitioned table which is illegal // *Action: Remove invalid clause(s), or ensure that the table is partitioned // by Composite Range method 14257, 00000, "cannot move partition other than a Range or Hash partition" // *Cause: User attempt to move a partition that is not a Range or Hash // partition which is illegal // *Action: Specify MOVE PARTITION for a Range or Hash partition only 14258, 00000, "invalid partition description" // *Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or // clause in ALTER TABLE ADD PARTITION // statement but the table in the maintenance operation is not a // Composite Range/Hash partitioned table which is illegal // *Action: Remove invalid clause(s), or ensure that the table is partitioned // by Composite Range/Hash method 14259, 00000, "table is not partitioned by Hash method" // *Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned // by Hash method // *Action: Specify valid ALTER TABLE option for the table, or ensure that // the table is partitioned by Hash method 14260, 00000, "incorrect physical attribute specified for this partition" // *Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, // and/or [NO]LOGGING option to a Hash partition via ALTER TABLE // ADD/MOVE PARTITION command which is illegal. // Only TABLESPACE may be specified. // *Action: Remove invalid option(s) 14261, 00000, "partition bound may not be specified when adding this Hash partition" // *Cause: User specified VALUES LESS THAN clause when adding a partition // (via ALTER TABLE ADD PARTITION) to a Hash partitioned table // which is illegal // *Action: Remove VALUES LESS THAN clause from the description of // partition being added 14262, 00000, "new subpartition name must differ from the old subpartition name" // *Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying // which is identical to the name of the // subpartition being renamed // *Action: Ensure that the new subpartition name is different from the // name of any (including the one being renamed) existing // subpartition of a given table or index 14263, 00000, "new subpartition name must differ from that of any other subpartition of the object" // *Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying // which is identical to the name of some // existing subpartition of the object // *Action: Ensure that the new subpartition name is different from the // name of any (including the one being renamed) existing // subpartition of a given table or index 14264, 00000, "table is not partitioned by Composite Range method" // *Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION // operation is partitioned by method other than Composite method // *Action: Ensure that the table is partitioned by Composite method 14265, 00000, "data type or length of a table subpartitioning column may not be changed" // *Cause: User issued ALTER TABLE statement attempting to modify // data type and/or length of a column used to subpartition the // table named in ALTER TABLE statement, which is illegal // *Action: Avoid modifying data type and/or length of table // subpartitioning column(s) 14266, 00000, "data type or length of an index subpartitioning column may not be changed" // *Cause: User issued ALTER TABLE statement attempting to modify // data type and/or length of a column used to subpartition some index // defined on the table named in ALTER TABLE statement, which is // illegal // *Action: Avoid modifying data type and/or length of index // subpartitioning column(s) 14267, 00000, "cannot specify PARALLEL clause when adding a (Composite) Range partition" // *Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL // clause for a Range or Composite Range partition which is illegal // *Action: Remove the PARALLEL clause. 14268, 00000, "subpartition '%s' of the partition resides in offlined tablespace" // *Cause: User attempted an operation requiring that we access data // in a subpartition which resides in a tablespace which was // taken offline. Such operations include trying to drop a // tablespace of a table which has indices defined on it or // is referenced by a constraint. // *Action: Bring tablespace online before attempting the operation. 14269, 00000, "cannot exchange partition other than a Range or Hash partition" // *Cause: User attempt to exchange a partition with a non-partitioned table // but the specified partition is not a Range or Hash partition // which is illegal // *Action: Specify EXCHANGE PARTITION for a Range or Hash partition only 14270, 00000, "table is not partitioned by Range or Hash or List method" // *Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL // INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not // partitioned by Range or Hash method which is illegal. // *Action: Ensure that the table is partitioned by Range or Hash method 14271, 00000, "table is not partitioned by Composite Range/Hash method" // *Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL // INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not // partitioned by Composite Range/Hash method which is illegal. // *Action: Ensure that the table is partitioned by Composite Range/Hash // method 14272, 00000, "only a partition with higher bound can be reused" // *Cause: User attempt to reuse a lower-bound partition in ALTER TABLE // MERGE PARTITIONS statement as the resulting partition which // is illegal. // *Action: Use the higher-bound partition to be the resulting partition // or specify a new partition name 14273, 00000, "lower-bound partition must be specified first" // *Cause: User specified higher-bound partition before lower-bound // partition in ALTER TABLE MERGE PARTITIONS statement which is // illegal // *Action: Specify lower-bound partition then higher-bound partition 14274, 00000, "partitions being merged are not adjacent" // *Cause: User attempt to merge two partitions that are not adjacent // to each other which is illegal // *Action: Specify two partitions that are adjacent 14275, 00000, "cannot reuse lower-bound partition as resulting partition" // *Cause: User attempt to reuse lower-bound partition of the partitions // being merged which is illegal // *Action: Specify new resulting partition name or reuse the higher-bound // partition only 14276, 00000, "EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table" // *Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation // is either clustered or partitioned // *Action: Ensure that the table with which the subpartition is being // exchanged for is not partitioned or clustered. 14277, 00000, "tables in EXCHANGE SUBPARTITION must have the same number of columns" // *Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION // have different number of columns // *Action: Ensure that the two tables have the same number of columns // with the same type and size. 14278, 00000, "column type or size mismatch in EXCHANGE SUBPARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE SUBPARTITION are of different type or size // *Action: Ensure that the two tables have the same number of columns // with the same type and size. 14279, 00000, "index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION" // *Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION // have indexes which are not equivalent // *Action: Ensure that the indexes for the two tables have indexes which // follow this rule // For every non partitioned index for the non partitioned table, // there has to be an identical LOCAL index on the partitioned // table and vice versa. By identical, the column position, type // and size have to be the same. 14280, 00000, "all rows in table do not qualify for specified subpartition" // *Cause: There is at least one row in the non partitioned table which // does not qualify for the subpartition specified in the ALTER TABLE // EXCHANGE SUBPARTITION // *Action: Ensure that all the rows in the segment qualify for // the subpartition. Perform the alter table operation with // the NO CHECKING option. Run ANALYZE table VALIDATE on that // subpartition to find out the invalid rows and delete them. 14281, 00000, "CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint // defined on them. // *Action: Ensure that the two tables do not have CHECK constraint // defined on any column 14282, 00000, "FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION" // *Cause: The corresponding columns in the tables specified in the // ALTER TABLE EXCHANGE SUBPARTITION statement have different // FOREIGN KEY constraints. // *Action: Ensure that the two tables do not have FOREIGN KEY constraints // defined on any column or disable all FOREIGN KEY constraints // on both tables. Then retry the operation. 14283, 00000, "UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION" // *Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION // command has a UNIQUE constraint for which no matching (vis-a-vis // key columns) constraint is defined on the other table or // a matching constraint is defined on the other table, but it // differs from that defined on the first table vis-a-vis being // enabled and/or validated. // *Action: Ensure that for every UNIQUE constraint defined on one of the // tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement // there is a matching (vis-a-vis key columns and being enabled and/or // validated) UNIQUE constraint defined on the other table. // If UNIQUE constrains are enabled, UNIQUE constraints on the // partitioned table should be enforced using local indexes. 14284, 00000, "one or more of table's subpartitions reside in a read-only tablespace" // *Cause: User issued ALTER TABLE statement attempting to modify // an existing VARCHAR2 (or VARCHAR) column to be of type CHAR // (or CHARACTER), increase length of an existing CHAR (or // CHARACTER) column, or add a column with user-specified default for // a table one or more subpartitions of which reside in read-only // tablespaces, which is illegal // *Action: Avoid performing aformentioned operations on a partitioned // table one or more subpartitions of which reside in read-only // tablespaces 14285, 00000, "cannot COALESCE the only partition of this partitioned table" // *Cause: A COALESCE PARTITION command was issued when there is only // one partition in the table which is illegal // *Action: Ensure that there is at least one partition. // Drop table to remove all partitions. 14286, 00000, "cannot COALESCE the only subpartition of this table partition" // *Cause: A COALESCE SUBPARTITION command was issued when there is only // one subpartition in the partition which is illegal // *Action: Ensure that there is at least one subpartition. // Drop partition to remove all subpartitions. 14287, 00000, "cannot REBUILD a partition of a Composite Range partitioned index" // *Cause: User attempted to rebuild a partition of a Composite Range partitioned index // which is illegal // *Action: REBUILD the index partition, a subpartition at a time 14288, 00000, "index is not partitioned by Composite Range method" // *Cause: The index in a partition or subpartition maintenance operation // (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES // FOR PARTITION] // or ALTER INDEX REBUILD SUBPARTITION command must be partitioned // by Composite Range method 14289, 00000, "cannot make local index partition of Composite Range partitioned table unusable" // *Cause: User attempted to rebuild a partition of a Composite Range // partitioned index which is illegal 14290, 00000, "PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION" // *Cause: The corresponding columns in the tables specified in the ALTER // TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY // constraints. // *Action: Ensure that the two tables do not have PRIMARY KEY constraints // defined on any column or disable all PRIMARY KEY constraints // on both tables. Then retry the operation. 14291, 00000, "cannot EXCHANGE a composite partition with a non-partitioned table" // *Cause: A composite partition can only be exchanged with a partitioned // table. // *Action: Ensure that the table being exchanged is partitioned or that // that the partition being exchanged is non-composite. 14292, 00000, "Partitioning type of table must match subpartitioning type of composite partition" // *Cause: When exchanging a partitioned table with a composite partition // the partitioning type of the table must match the subpartitioning // type of the composite partition. // *Action: Ensure that the partitioning type of partitioned table is the // same as the subpartitioning type of the composite partition. 14293, 00000, "Number of partitioning columns does not match number of subpartitioning columns" // *Cause: When exchanging a partitioned table with a composite partition // the number of partitioning columns of the table must match the // number of subpartitioning columns of the composite partition. // *Action: Ensure that the number of partitioning columns in the partitioned // table is the same as the number of subpartitioning columns in the // the composite partition. 14294, 00000, "Number of partitions does not match number of subpartitions" // *Cause: When exchanging a partitioned table with a composite partition // the number of partitions of the table must match the // number of subpartitions of the composite partition. // *Action: Ensure that the number of partitions in the partitioned // table is the same as the number of subpartitions in the // the composite partition. 14295, 00000, "column type or size mismatch between partitioning columns and subpartitioning columns" // *Cause: When exchanging a partitioned table with a composite partition // the type and size of the partitioning columns of the table must // match the type and size of the subpartitioning columns of the // composite partition. // *Action: Ensure that the type and size of the partitioning columns of the // partitioned is the same as the type and size of the // subpartitioning columns of the composite partition. 14296, 00000, "Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION" // *Cause: The block sizes of the two tables specified in the ALTER // TABLE EXCHANGE [SUB]PARTITION statement are different. For // index organized tables, either the block sizes of the index // or the overflow (or both) do not match. // *Action Ensure that the block sizes of the tables involved in the // ALTER TABLE EXCHANGE [SUB]PARTITION statement are the // same. For index organized tables, ensure that the block sizes // of both the index and the overflow of the two tables match. 14297, 00000, "Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION" // *Cause: The block sizes of a pair of indexes being exchanged in the ALTER // TABLE EXCHANGE [SUB]PARTITION statement are different. // *Action Ensure that the block sizes of the corresponding pairs of // indexes that need to be exchanged in the ALTER TABLE EXCHANGE // [SUB]PARTITION statement are the same. 14298, 00000, "LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION" // *Cause: The block sizes of a pair of corresponding LOB columns of // the two tables specified in the ALTER TABLE EXCHANGE // [SUB]PARTITION statement are different. // *Action Ensure that the block sizes of corresponding pairs of LOB // columns of the tables involved in the ALTER TABLE EXCHANGE // [SUB]PARTITION statement are the same. 14301, 00000, "table-level attributes must be specified before partition-level attributes" // *Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level // attributes of LOB columns were encountered after processing // partition-level attributes of LOB columns or // while processing CREATE TABLE statement, table-level // attributes of LOB columns were encountered after processing // partition descriptions. // *Action: Modify the SQL statement to specify table-level attributes prior // to partition-level attributes or partition descriptions; then // retry the statement. 14302, 00000, "only one list of added-LOB-storage-clauses can be specified in a statement" // *Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of // added-LOB-storage-clauses was parsed when another list of // added-LOB-storage-clauses was encountered. There cannot be more // than one list of added-LOB-storage-clauses in a statement; all // added-LOB-storage-clauses must be combined into one list. // *Action: Combine all of the lists of added-LOB-storage-clauses into one // list and retry the statement. 14303, 00000, "partitions or subpartitions are not in the right order" // *Cause: Descriptions of partitions or subpartitions in an // ALTER TABLE ADD COLUMN statement were ordered differently // from the DDL order of partitions or subpartitions. // *Action: Re-order the partitions or subpartitions in the added LOB // storage clause by partition or subpartition DDL order, and // retry the statement. // *Cause: User attempted to rebuild a partition of a Composite Range partitioned index // which is illegal 14304, 00000, "List partitioning method expects a single partitioning column" // *Cause: number of columns in a partitioning column list exceeded // the legal limit of 1 for List partitioned objects // *Action: modify partitioning column list so that it consists of at // most 1 column 14305, 00000, "List value '%s' specified twice in partition '%s'" // *Cause: A list value cannot be specified more that once // *Action: Remove one of the specifications of the value 14306, 00000, "List value '%s' specified twice in partitions '%s', '%s'" // *Cause: A list value cannot be specified more that once // *Action: Remove one of the specifications of the value 14307, 00000, "partition contains too many list values" // *Cause: Partition list contains more than 65535 list values // *Action: Reduce the number of values to not exceed 65535 values 14308, 00000, "partition bound element must be one of: string, datetime or interval literal, number, or NULL" // *Cause: Partition bound list contained an element of invalid type // (i.e. not a number, non-empty string, datetime or interval literal, // or NULL) // *Action: Ensure that all elements of partition bound list are of valid type 14309, 00000, "Total count of list values exceeds maximum allowed" // *Cause: Partitioned object contains more than 65535 list values // *Action: Reduce number of values to less than 65535. 14310, 00000, "VALUES LESS THAN or AT clause cannot be used with List partitioned tables" // *Cause: VALUES LESS THAN or AT clause can be used only with Range // partitioned tables // *Action: Use VALUES () clause with List partitioned tables 14311, 00000, "Expecting VALUES LESS THAN or AT clause" // *Cause: VALUES () clause can be used only with List // partitioned tables // *Action: Use VALUES LESS THAN clause with Range partitioned tables 14312, 00000, "Value %s already exists in partition %s" // *Cause: One of the list values in the ADD PARTITION or ADD VALUES // statement already exists in another partition // *Action: Remove the duplicate value from the statement and try again 14313, 00000, "Value %s does not exist in partition %s" // *Cause: One of the list values in the SPLIT PARTITION or DROP VALUES // statement does not exist in the partition // *Action: Remove the value from the statement and try again 14314, 00000, "resulting List partition(s) must contain atleast 1 value" // *Cause: After a SPLIT/DROP VALUE of a list partition, each resulting // partition(as applicable) must contain at least 1 value // *Action: Ensure that each of the resulting partitions contains atleast // 1 value 14315, 00000, "cannot merge a partition with itself" // *Cause: The same partition name was specified twice for the merge operation // *Action: Re-submit operation with 2 distinct partition names 14316, 00000, "table is not partitioned by List method" // *Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects // *Action: Re-issue the command against a List partitoned object. 14317, 00000, "cannot drop the last value of partition" // *Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition // *Action: Cannot execute the command, unless two or more values exist for partition / / / 14400 - 14499 reserved for execution errors introduced by the Partitioned / object project / 14400, 00000, "inserted partition key does not map to any partition" // *Cause: An attempt was made to insert a record into, a Range or Composite // Range object, with a concatenated partition key that is beyond // the concatenated partition bound list of the last partition -OR- // An attempt was made to insert a record into a List object with // a partition key that did not match the literal values specified // for any of the partitions. // *Action: Do not insert the key. Or, add a partition capable of accepting // the key, Or add values matching the key to a partition specification 14401, 00000, "inserted partition key is outside specified partition" // *Cause: the concatenated partition key of an inserted record is outside // the ranges of the two concatenated partition bound lists that // delimit the partition named in the INSERT statement // *Action: do not insert the key or insert it in another partition 14402, 00000, "updating partition key column would cause a partition change" // *Cause: An UPDATE statement attempted to change the value of a partition // key column causing migration of the row to another partition // *Action: Do not attempt to update a partition key column or make sure that // the new partition key is within the range containing the old // partition key. 14403, 00000, "cursor invalidation detected after getting DML partition lock" // *Cause: cursor invalidation was detected after acquiring a partition lock // during an INSERT, UPDATE, DELETE statement. This error is never // returned to user, because is caught in opiexe() and the DML // statement is retried. // *Action: nothing to be done, error should never be returned to user 14404, 00000, "partitioned table contains partitions in a different tablespace" // *Cause: An attempt was made to drop a tablespace which contains tables // whose partitions are not completely contained in this tablespace // *Action: find tables with partitions which span the tablespace being // dropped and some other tablespace(s). Drop these tables or move // partitions to a different tablespace 14405, 00000, "partitioned index contains partitions in a different tablespace" // *Cause: An attempt was made to drop a tablespace which contains indexes // whose partitions are not completely contained in this tablespace, // and which are defined on the tables which are completely contained // in this tablespace. // *Action: find indexes with partitions which span the tablespace being // dropped and some other tablespace(s). Drop these indexes, or move // the index partitions to a different tablespace, or find the tables // on which the indexes are defined, and drop (or move) them. 14406, 00000, "updated partition key is beyond highest legal partition key" // *Cause: At attempt was made to update a record with a concatenated // partition key that is beyond the concatenated partition bound // list of the last partition. // *Action: Do not update the key. Or, add a partition capable of accepting // the key. 14407, 00000, "partitioned table contains subpartitions in a different tablespace" // *Cause: An attempt was made to drop a tablespace which contains tables // whose subpartitions are not completely contained in this tablespace // *Action: find tables with subpartitions which span the tablespace being // dropped and some other tablespace(s). Drop these tables or move // subpartitions to a different tablespace 14408, 00000, "partitioned index contains subpartitions in a different tablespace" // *Cause: An attempt was made to drop a tablespace which contains indexes // whose subpartitions are not completely contained in this tablespace, // and which are defined on the tables which are completely contained // in this tablespace. // *Action: find indexes with subpartitions which span the tablespace being // dropped and some other tablespace(s). Drop these indexes, or move // the index partitions to a different tablespace, or find the tables // on which the indexes are defined, and drop (or move) them. 14409, 00000, "inserted partition key is outside specified subpartition" // *Cause: the concatenated partition key of an inserted record is outside // the ranges of the two concatenated subpartition bound lists that // delimit the subpartition named in the INSERT statement // *Action: do not insert the key or insert it in another subpartition / / 14450 - 14499 reserved for execution errors introduced by the / Temporary Tables project 14450, 00000, "attempt to access a transactional temp table already in use" // *Cause: An attempt was made to access a transactional temporary table that // has been already populated by a concurrent transaction of the same // session. // *Action: do not attempt to access the temporary table until the // concurrent transaction has committed or aborted. 14451, 00000, "unsupported feature with temporary table" // *Cause: An attempt was made to create an IOT, specify physical attributes, // specify partition or parallel clause. // *Action: do not do that. 14452, 00000, "attempt to create, alter or drop an index on temporary table already in use" // *Cause: An attempt was made to create, alter or drop an index on temporary // table which is already in use. // *Action: All the sessions using the session-specific temporary table have // to truncate table and all the transactions using transaction // specific temporary table have to end their transactions. 14453, 00000, "attempt to use a LOB of a temporary table, whose data has alreadybeen purged" // *Cause: An attempt was made to use LOB from a temporary table whose data // has been dropped either because table was transaction-specific and // transaction has commited or aborted, table was truncated or session // which created this LOB has ended. // *Action: This LOB locator is invalid and cannot be used. 14454, 00000, "attempt to reference temporary table in a referential integrity constraint" // *Cause: An attempt was made to reference temporary table in a referencial // integrity constraint. This is not supported. // *Action: Use triggers. 14455, 00000, "attempt to create referential integrity constraint on temporary table" // *Cause: An attempt was made to create a referential integrity constraint on // a temporary table. This is not supported. // *Action: Use triggers. 14456, 00000, "cannot rebuild index on a temporary table" // *Cause: An attempt was made to rebuild an index on a temp table. // *Action: The index data is anyway lost at end of session/transaction. 14457, 00000, "disallowed VARRAY and Nested Table column in a Temporary table" // *Cause: An attempt made to create a VARRAY or Nested Table column in a // temporary table. This is not supported. // *Action: Do not specify these datatypes for temporary tables. 14458, 00000, "attempt was made to create a temporary table with INDEX organization" // *Cause: An attempt was made to create an Index Organized Temporary table. // This is not supported. // *Action: Create the table with HEAP organization and the primary key. 14459, 00000, "missing GLOBAL keyword" // *Cause: keyword GLOBAL is missing while creating temporary table. // *Action: supply keyword. / / 14500-14550 Analyze errors added by partitioned object project / not used - 14502 14500, 00000, "LOCAL option not valid without partition name" // *Cause: Incorrect syntax specified // *Action: Retry the command 14501, 00000, "object is not partitioned" // *Cause: Table or index is not partitioned. Invalid syntax. // *Action: Retry the command with correct syntax. 14503, 00000, "only one partition name can be specified" // *Cause: More than one partition name has been specified for analyze // *Action: Specify one partition name. 14504, 00000, "syntax not supported for analyze" // *Cause: A partition/subpartition number or bind variable has been used // *Action: Specify a valid partition/subpartition name. 14505, 00000, "LOCAL option valid only for partitioned indexes" // *Cause: Incorrect syntax specified // *Action: Retry the command 14506, 00000, "LOCAL option required for partitioned indexes" // *Cause: Incorrect syntax specified // *Action: Retry the command 14507, 00000, "partition corrupt. all rows do not fall within partition bounds" // *Cause: The partition contains rows which should really be in some // other partition. Possibly due to an exchange partition without // validation // *Action: Delete rows in partition which do not qualify 14508, 00000, "specified VALIDATE INTO 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. 14509, 00000, "specified VALIDATE INTO table form incorrect" // *Cause: The specified table does not have the proper field definitions. // *Action: Specify the correct table to use. See utlvalid.sql for more information. 14510, 00000, "can specify VALIDATE INTO clause only for partitioned tables" // *Cause: The VALIDATE INTO has been specified for a non partitioned table // or cluster or index. // *Action: Use syntax correctly 14511, 00000, "cannot perform operation on a partitioned object" // *Cause: An attempt was made to perform an operation that is not allowed // on partitioned tables or indexes. // *Action: Retry the command with correct syntax. 14512, 00000, "cannot perform operation on a clustered object" // *Cause: An attempt was made to perform an operation that is not allowed // on clustered tables or indexes. // *Action: Retry the command with correct syntax. 14513, 00000, "partitioning column may not be of object datatype" // *Cause: Partitioning column specified by the user was an object datatype // (object, REF, nested table, array) which is illegal. // *Action: Ensure that no partitioning column is an object datatype. 14514, 00000, "LOCAL option not valid without subpartition name" // *Cause: Incorrect syntax specified // *Action: Retry the command 14515, 00000, "only one aubpartition name can be specified" // *Cause: More than one subpartition name has been specified for analyze // *Action: Specify one subpartition name. 14516, 00000, "subpartition corrupt. all rows do not fall within subpartition bounds" // *Cause: The subpartition contains rows which should really be in some // other subpartition. Possibly due to an exchange subpartition without // validation // *Action: Delete rows in subpartition which do not qualify 14517, 00000, "subpartition of index '%s.%s' is in unusable state" // *Cause: An attempt has been made to access an index subpartition // that has been marked unusable by a direct load or by a DDL // operation // *Action: REBUILD the unusable index subpartition 14518, 00000, "partition contains rows corresponding to values being dropped" // *Cause: table partition contains rows for the values being dropped. // *Action: DELETE all rows for the values being dropped and reissue statement 14519, 00000, "Conflicting tablespace blocksizes for %s %s: Tablespace %s block size %s [%s] conflicts with previously specified/implied tablespace %s block size %s [%s]" // *Cause: An attempt has been made to create a partitioned // object in a manner that would require the partitioned // object to span tablespaces of more than one block size. // *Action: Ensure that all tablespaces specified in the DDL command // for the given object as well as any tablespaces implicitly // assigned to partitions or subpartitions of the object being created // are all of the same block size. 14520, 00000, "Tablespace %s block size [%s] does not match existing object block size [%s]" // *Cause: A DDL statement was issued that would require a tablespace of a // block size different from the block size of the specified // partitioned object to be assigned either: // (1) As the object's default tablespace (or one of the // object's partition-level default tablespaces, // if composite partitioning is being used) OR // (2) To one of the object's partitions/subpartitions. // *Action: Specify a tablespace of the same block size as the partitioned // object. 14521, 00000, "Default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]" // *Cause: A DDL statement was issued that would require creation of a new // partition/subpartition in the object-level default // tablespace of an existing partitioned object. However, the // object-level default tablespace block size does not match // the block size of the partitioned object. // *Action: Either // (1) Modify the default tablespace of the partitioned // object to a tablespace of the same block size as the // object and then retry the DDL command, OR // (2) Ensure that tablespaces of the correct block size are // specified for all new partitions/subpartitions being // created. 14522, 00000, "Partition-level default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]" // *Cause: A DDL statement was issued that would require creation of a new // subpartition in one of the partition-level default // tablespaces of an existing composite partitioned // object. However, the partition-level default tablespace // block size does not match the block size of the partitioned object. // *Action: Either // (1) Modify the partition-level default tablespace of the // appropriate partition of the partitioned // object to a tablespace of the same block size as the // object and then retry the DDL command, OR // (2) Ensure that tablespaces of the correct block size are // specified for all new subpartitions being // created. 14523, 00000, "Cannot co-locate [sub]partition of %s %s with table [sub]partition because %s block size [%s] does not match table block size [%s]" // *Cause: A DDL statement was issued that would require // a partition/subpartition of a local index/LOB column to // be co-located with the corresponding partition/subpartition // of the base table. However, this is not possible because // the block sizes of the table and the LOB column/local // index are different. // *Action: Either // (1) Specify an object-level default tablespace (or // partition-level default tablespace for the // appropriate partition, if composite partitioning is // used) for the partitioned local index/LOB column // and then retry the DDL command, OR // (2) Ensure that tablespaces of the correct block size are // specified for all new partitions/subpartitions being // created. // Also ensure that neither of TABLESPACE DEFAULT and // STORE IN (DEFAULT) is specified for a local index whose // block size does not match that of the base table. 14524, 00000, "Always allow partitioning. To be used only by trusted clients" // *Document: NO // *Cause: // *Action: // Level 1+ Allow partitioning irrespective of edition. / /============================================================================ / 14551 - 14570 Reserved for purity errors during execution / / Begin messages for purity error checks /============================================================================ / 14551, 00000, "cannot perform a DML operation inside a query " // *Cause: DML operation like insert, update, delete or select-for-update // cannot be performed inside a query or under a PDML slave. // *Action: Ensure that the offending DML operation is not performed or // use an autonomous transaction to perform the DML operation within // the query or PDML slave. 14552, 00000, "cannot perform a DDL, commit or rollback inside a query or DML " // *Cause: DDL operations like creation tables, views etc. and transaction // control statements such as commit/rollback cannot be performed // inside a query or a DML statement. // *Action: Ensure that the offending operation is not performed or // use autonomous transactions to perform the operation within // the query/DML operation. 14553, 00000, "cannot perform a lob write operation inside a query " // *Cause: A lob write operation cannot be performed inside a query or a // PDML slave. // *Action: Ensure that the offending lob write operation is not performed or // use an autonomous transaction to perform the operation within // the query or PDML slave. /============================================================================ / 16000 - 16499 Reserved for ORACLE HOT STANDBY / / Begin messages for ORACLE HOT STANDBY /============================================================================ / 16000, 00000, "database open for read-only access" // *Cause: The database has been opened for read-only access. Attempts // modify the database using inappropriate DML or DDL statements // generate this error. // *Action: In order to modify the database, it must first be shutdown and // re-opened for read-write access. 16001, 00000, "database already open for read-only access by another instance" // *Cause: The database has been opened for read-only access by another // instance, and cannot be opened for read-write access by this // instance. // *Action: This instance must be opened for read-write access, or all other // instances must first be shutdown and re-opened for read-only access. 16002, 00000, "database already open for read-write access by another instance" // *Cause: The database has been opened for read-write access by another // instance, and cannot be opened for read-only access by this // instance. // *Action: This instance must be opened for read-only access, or all other // instances must first be shutdown and re-opened for read-write access. 16003, 00000, "standby database is restricted to read-only access" // *Cause: To ensure its integrity, a standby database can only be opened // for read-only access. // *Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY. // 16004, 00000, "backup database requires recovery" // *Cause: The controlfile is for a backup database which requires recovery, // and cannot be opened for read-only access by this instance. // *Action: Perform the necessary recovery and re-open for read-only access. // 16005, 00000, "database requires recovery" // *Cause: The database requires recovery, and therefore cannot be opened for // read-only access by this instance. // *Action: Perform the necessary recovery and re-open for read-only access. // 16006, 00000, "audit_trail destination incompatible with database open mode" // *Cause: The audit_trail initialization parameter was set to "DB" (or // TRUE), which is incompatible with a database opened for read-only // access. // *Action: When the database is opened for read-only access, the audit_trail // initialization parameter can only be set to "OS" or "NONE" (FALSE). // 16007, 00000, "invalid backup controlfile checkpoint" // *Cause: The backup controlfile being opened for read-only access does not // contain a valid controlfile checkpoint. Therefore the database // can not be opened for read-only access. // *Action: First open the database for read-write access which will result // in valid controlfile checkpoint. Then re-open the database for // read-only access. 16008, 00000, "indeterminate controlfile checkpoint" // *Cause: The controlfile for the database being opened for read-only access // was created via CREATE CONTROLFILE. Therefore a controlfile // checkpoint could not be calculated and the database can not be // opened for read-only access. // *Action: First open the database for read-write access which will result // in valid controlfile checkpoint. Then re-open the database for // read-only access. 16009, 00000, "remote archivelog destination must be a STANDBY database" // *Cause: The database associated with the archivelog destination service // name is other than the required STANDBY type database. // Remote archival of redo logfiles is not allowed to non-STANDBY // database instances. // *Action: Take the necessary steps to create the required compatible STANDBY // database before retrying the ARCHIVE LOG processing. 16010, 00000, "remote archivelog destination database is opened for update" // *Cause: The database associated with the archivelog destination service // name is opened for update access. // Remote archival of redo logfiles to standby databases opened for // update access is not allowed. // *Action: Shutdown the standby destination instance and re-open for read-only // access or simple leave the standby instance mounted and unopened. 16011, 00000, "Archivelog Remote File Server process in Error state" // *Cause: The archivelog remote file server (RFS) process at the specified // standby database site has experienced an unrecoverable error and // is unable to receive further archivelog data. // *Action: Correct the problem at the standby database site. 16012, 00000, "Archivelog standby database identifier mismatch" // *Cause: The database identifiers of the Primary and Standby database // do not match. Remote archival of redo logfiles is not allowed // to incompatible STANDBY database instances. // *Action: Take the necessary steps to create the required compatible STANDBY // database before retrying the ARCHIVE LOG processing. 16013, 00000, "log %s sequence# %s does not need archiving" // *Cause: An attempt was made to archive the named file manually, but the // file did not require archiving. The file had previously been // successfully archived. // *Action: No action is required. 16014, 00000, "log %s sequence# %s not archived, no available destinations" // *Cause: An attempt was made to archive the named log, but the archive was // unsuccessful. The archive failed because there were no archivelog // destinations specified or all destinations experienced debilitating // errors. // *Action: Verify that archivelog destinations are being specified and/or // take the necessary step to correct any errors that may have // occurred. 16015, 00000, "log %s sequence# %s not archived, media recovery disabled" // *Cause: An attempt was made to archive the named log, but the archive was // unsuccessful. A standby archivelog destination was specified and // the database was not media recovery enabled. This is not allowed. // *Action: Disable the standby destination or enable media recovery and retry. 16016, 00000, "archived log for thread %s sequence# %s unavailable" // *Cause: The managed standby database recovery operation has timed out // waiting for the requested archived log file. // *Action: Verify that the primary database is still archiving redo logs to // the standby recovery database site and reissue the RECOVER STANDBY // DATABASE WAIT command. 16017, 00000, "cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination" // *Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value // when the primary archive destination was set to NULL explicitly. // *Action: Set the primary archive destination to a valid non-NULL value. 16018, 00000, "cannot use %s with LOG_ARCHIVE_DEST_n" // *Cause: One of the following events caused an incompatibility: // 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST // was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter // was encountered while fetching initialization parameters. // 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when // a LOG_ARCHIVE_DEST_n parameter was encountered while fetching // initialization parameters. // 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM // command was used to define a value for either the LOG_ARCHIVE_DEST // or LOG_ARCHIVE_DUPLEX_DEST parameter. // *Action: Eliminate any incompatible parameter definitions. 16019, 00000, "cannot use %s with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST" // *Cause: One of the following events caused an incompatibility: // 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in // use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter // was encountered while fetching initialization parameters. // 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in // use when an attempt was made to use an ALTER SYSTEM or ALTER // SESSION command to define a value for the specified // LOG_ARCHIVE_DEST_n parameter. // 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect // when the specified LOG_ARCHIVE_DEST_n parameter was encountered // while fetching initialization parameters. // 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect // when an attempt was made to use an ALTER SYSTEM or ALTER SESSION // command to define a value for the specified LOG_ARCHIVE_DEST_n // parameter. // *Action: Eliminate any incompatible parameter definitions. 16020, 00000, "less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST" // *Cause: With automatic archiving enabled, the number of archive log // destinations that could be used for the database was less // than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value. // *Action: Either adjust the settings of the log archive destination // parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST. 16021, 00000, "session %s destination cannot be the same as session %s destination" // *Cause: An attempt was made to change the first specified archive log // parameter using ALTER SESSION to have a destination value that // duplicates the session-level destination value of the second // specified archive log parameter. // *Action: Specify a different session destination value for one of the // LOG_ARCHIVE_DEST_n parameters. 16022, 00000, "LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL" // *Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL // when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL. // *Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set // parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value. 16023, 00000, "system %s destination cannot be the same as session %s destination" // *Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n // (n = 1...10) parameter produced a destination that duplicates // the session destination value of the second specified // LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a // non-NULL value with the ALTER SYSTEM command. Or, this error can // occur when setting a NULL value with ALTER SESSION command, because // then the associated system destination value may appear as a // duplicate. // *Action: Specify a different destination value for the first specified // LOG_ARCHIVE_DEST_n parameter. 16024, 00000, "parameter %s cannot be parsed" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter could not be parsed. Common causes for this error are a // misplaced equal sign, an unrecognized option, or an option that is // missing a required value. // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16025, 00000, "parameter %s contains repeated or conflicting options" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter contained either repeated options or options that // conflicted with each other. // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16026, 00000, "parameter %s contains an invalid numeric attribute value" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter contained a REOPEN option with an invalid numeric value. // The valid range is 0-65535. // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16027, 00000, "parameter %s is missing a destination option" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter failed to include a destination option. Valid destination // options are LOCATION or SERVICE. // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16028, 00000, "new %s causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires" // *Cause: With automatic archiving enabled, an attempt was made to change // the specified LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n // parameter (n = 1...10) to a value that reduces the number of // archive log destinations to less than the specified // LOG_ARCHIVE_MIN_SUCCEED_DEST value. // *Action: Either select different options for the LOG_ARCHIVE_DEST_n or // LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for // parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. 16029, 00000, "cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations" // *Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST // parameter when there are no archive log destinations. // *Action: Define one or more log archive destinations using parameters // LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n // (n = 1...10). Then, change the value of parameter // LOG_ARCHIVE_MIN_SUCCEED_DEST. 16030, 00000, "session specific change requires a LOG_ARCHIVE_DEST_n destination" // *Cause: The following event caused an incompatibility: // Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use // when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST // parameter with an ALTER SESSION command. // *Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST // parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters. 16031, 00000, "parameter %s destination string exceeds %s character limit" // *Cause: The value for the specified parameter contained a destination // string that is too long. // *Action: Replace the destination value for the specified parameter with a // character string that has a length below the limit specified in the // error message. 16032, 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. 16033, 00000, "parameter %s destination cannot be the same as parameter %s destination" // *Cause: An attempt was made to change the first specified archive log // parameter to have a destination value that duplicates the // system-level destination value of the second specified archive log // parameter. // *Action: Specify a different value for one of the archive log parameters. 16034, 00000, "FROM parameter is incompatible with MANAGED recovery" // *Cause: Use of the FROM 'location' parameter is not allowed when // MANAGED recovery has been specified. // *Action: Correct the syntax and retry the command. 16035, 00000, "missing required keyword %s" // *Cause: The keywords STANDBY DATABASE are required when MANAGED // recovery has been specified. // *Action: Correct the syntax and retry the command. 16036, 00000, "invalid MANAGED recovery CANCEL option" // *Cause: A mode other than IMMEDIATE follows the CANCEL keyword in // RECOVER MANAGED STANDBY DATABASE statement. // *Action: Specify either nothing or IMMEDIATE following CANCEL. 16037, 00000, "user requested cancel of managed recovery operation" // *Cause: The managed standby database recovery operation has been // canceled per user request. // *Action: No action is required. // 16038, 00000, "log %s sequence# %s cannot be archived" // *Cause: An attempt was made to archive the named file, but the // file could not be archived. Examine the secondary error // messages to determine the cause of the error. // *Action: No action is required. 16039, 00000, "RFS request version mismatch" // *Cause: A request to archive a redo log to a standby site failed // because the request was incompatible with the Remote File // Server (RFS) at the standby site. // *Action: Verify that compatible versions of Oracle are running on // the primary and all standby sites. 16040, 00000, "standby destination archivelog file is locked" // *Cause: The target standby destination archivelog file is currently // locked. This indicates that the file is being archived to by // another Remote File Server (RFS) process. // *Action: Check for and eliminate duplicate standby destination archivelog // service names defined for the primary database. 16041, 00000, "Remote File Server fatal error" // *Cause: The Remote File Server (RFS) process at the standby destination // archivelog site has encountered a disabling error and is no longer // available. Further archiving to the standby site may not be // possible. // *Action: Refer to the appropriate RFS trace file located at the standby // site for details regarding the error encountered and if possible // take corrective action. 16042, 00000, "user requested cancel immediate of managed recovery operation" // *Cause: The managed standby database recovery operation has been // canceled immediately per user request. Processing of the // current archivelog file has been interrupted and therefore // the database is in an inconsistent state. // *Action: No action is required. 16043, 00000, "sustained recovery session canceled" // *Cause: The sustained standby database recovery operation has been // canceled per user request or operation timeout. // *Action: More specific messages will accompany this message. 16044, 00000, "destination %s attribute cannot be specified at session level" // *Cause: An archivelog destination attribute was attempted to be modified // at the session level. // *Action: Use the ALTER SYSTEM command to modify the destination attribute. 16045, 00000, "circular archivelog destination dependency chain" // *Cause: An archivelog destination contains a dependency to another // archivelog destination that also contains a dependency. // *Action: The parent archivelog destination cannot be dependent on another // archivelog destination. Use the ALTER SYSTEM command to remove // one of the dependency attributes. 16046, 00000, "Archivelog destination failed due to failed dependent destination" // *Cause: The archivelog destination is dependent upon another destination, // which has failed. Therefore, this destination also fails. // *Action: No action required. 16047, 00000, "Dependent archivelog destination cannot be a standby database" // *Cause: The parent archivelog destination cannot be a standby database. // It must be a local archivelog destination. // *Action: Change the parent archivelog destination from referencing a // standby database to referencing a local archivelog repository. 16048, 00000, "enable simulated error on archivelog write" // *Cause: Causes an I/O error to be signalled during the writing of // an archival operation. // *Action: No action is required. 16049, 00000, "simulated error on archivelog write" // *Cause: I/O error returned for a simulated archival failure during // an archival operation. // *Action: No action is required. 16050, 00000, "destination exceeded specified quota size" // *Cause: An archivelog was attempted to be created in a destination with // a specified maximum quota size. The creation of the archivelog // exceeded the specified quota size. Therefore, the destination // has been made inaccessible to future archival operations. // *Action: No action is required. 16051, 00000, "parameter %s contains an invalid delay time" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter contained a DELAY option with an invalid numeric value. // The valid range is 0-5760 (in minutes). // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16052, 00000, "Problem with fetching gap sequence, media recovery cancelled." // *Cause: A gap sequence is detected on the standby database while it was // trying to perform managed standby recovery. The fetching of the // the gap sequence fails. The failures are logged in the alert log // on the primary database. // *Action: Check the alert log on primary and standby database. Take // appropriate action to make the gap sequence available again. // Managed standby recovery on the standby database can't proceed // further until the standby database is able to get the gap sequence // redo logfiles. 16053, 0000, "FAL archive failed, can't archive thread# %s sequence# %s" // *Cause: The FAL server on the primary database has problem archiving a // redo log file requested by the standby database. The cause for // this failure are logged in the alert log file. // *Action: Check the alert log on the primary database. Take the appropriate // action to solve the problem. Re-issue Managed Standby Recovery // on the standby database again. 16054, 0000, "Event for automatic RFS gap sequence detection" // *Cause: This is a Oracle internal event code. The condition is posted // when the ARC process is about to request the remote RFS to // detect gap sequence. The event is used to allow run time disabling // of the automatic gap sequence detection. Such run time disable // function allows the ORATST to test the other get gap sequence // code path: kcrrggs()...etc // *Action: N/A, this is a Oracle internal event code 16055, 0000, "FAL request rejected" // *Cause: FAL server rejects the FAL request from the FAL client. This // may be caused by different reasons. // *Action: Check the alert log on the primary database. Take the appropriate // action to solve the problem. 16056, 00000, "backup controlfile archival requires proper syntax" // *Cause: An attempt was made to perform an online logfile archival using // a backup controlfile. However, the USING BACKUP CONTROLFILE syntax // was not specified. // *Action: If the archival operation is correct when using a backup // controlfile, then the USING BACKUP CONTROLFILE syntax is required. 16057, 00000, "current controlfile archival requires proper syntax" // *Cause: An attempt was made to perform an online logfile archival using // a current controlfile. However, the USING BACKUP CONTROLFILE syntax // was specified. // *Action: If the archival operation is correct when using a current // controlfile, then the USING BACKUP CONTROLFILE syntax is not // required. 16058, 00000, "standby database instance is not mounted" // *Cause: The RFS process on the standby database received an internal error. // *Action: Check the standby alert log and RFS trace files for more // information. 16059, 00000, "Log file is empty or invalid next available block" // *Cause: Archiving not allowed of an empty or invalid log file. // *Action: No action is required. 16060, 00000, "Log file is current" // *Cause: The current logfile cannot be archived using it's filename. // *Action: No action is required. 16061, 00000, "Log file status has changed" // *Cause: It is possible the online logfile was reclaimed as a new logfile // either before archival started, or during the archival operation. // *Action: No action is required. 16062, 00000, "The log was NOT archived" // *Cause: Archiving not allowed of current log file. // *Action: Check the alert log and archive trace files for additional // information. 16063, 00000, "remote archival is enabled by another instance" // *Cause: Remote archival of database REDO logfiles has been enabled // by another instance, and cannot be disabled for this instance. // *Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart // this instance. 16064, 00000, "remote archival is disabled by another instance" // *Cause: Remote archival of database REDO logfiles has been disabled // by another instance, and cannot be enabled for this instance. // *Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart // this instance. 16065, 00000, "remote archival disabled at standby destination" // *Cause: Receipt of remote archived REDO logfiles has been disabled // at the associated standby destination host database. // *Action: If appropriate change the associated archivelog parameter to // specify a local destination with the LOCATION keyword or defer // the associated archivelog destination. Or, if possible, set the // standby REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart the // standby database instance before further REDO logfile archivals // occur. 16066, 00000, "remote archival disabled" // *Cause: An archivelog destination parameter has specified a remote // destination with the SERVICE keyword. Remote archival of REDO // logfiles has been disabled for this database. The associated // archivelog destination has been disabled. // *Action: If appropriate change the archivelog parameter to specify a // local destination with the LOCATION keyword or (if appropriate) // set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart // the database instance before further REDO logfile archivals occur. 16067, 00000, "activation identifier mismatch in archive log %s" // *Cause: The activation identifier contained in the archive log file // header does not match the activation identifier of the database // being recovered. The indicated archive log can not be // applied to the database. // *Action: Locate the appropriate archive log for the database. 16068, 00000, "redo log file activation identifier mismatch" // *Cause: The activation identifier of the indicated redo log file // does not match the activation identifier of the database. // *Action: 16069, 00000, "Archivelog standby database activation identifier mismatch" // *Cause: The activation identifiers of the Primary and Standby database // do not match. Remote archival of redo logfiles is not allowed // to incompatible STANDBY database instances. // This can occur when trying to apply an incorrect archivelog to // a standby database, or when trying to archive to a standby database // that does not match the primary database. // *Action: Take the necessary steps to create the required compatible STANDBY // database before retrying the ARCHIVE LOG processing. 16070, 00000, "parameter %s contains an invalid REGISTER attribute value" // *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) // parameter contained a REGISTER attribute that specified an // invalid filename template string. If specified, the REGISTER // filename template string must indicate an O/S-specific file // pathname including thread and log sequence number substitution // directives (%t, %T, %s, %S). // *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. 16071, 00000, "dependency archived log file not found %s" // *Cause: The specified archived log file was not found at the indicated // standby destination. // *Action: Verify the correctness of the dependency archived log filename // template specified for the indicated standby destination against // the actual dependency archived log file. 16072, 00000, "a minimum of one standby database destination is required" // *Cause: No standby database archivelog destinations were specified. // *Action: Specify a standby archivelog destination in the initialization // parameter file. 16073, 00000, "archiving must be enabled" // *Cause: Online logfile archiving is disabled. // *Action: Enable logfile archiving. 16074, 00000, "ARCH processes must be active" // *Cause: There are no active ARCH processes. // *Action: It is required that at least one ARCH process be active. 16075, 00000, "standby database destination mismatch" // *Cause: A standby database destination was specified that is not accessed // by another instance. // *Action: All database instances must access the same standby databases. 16076, 00000, "unknown standby database destination" // *Cause: A standby database destination was specified that is not accessed // by another instance. // *Action: All database instances must access the same standby databases. 16077, 00000, "simulate network transmission error" // *Cause: Used for internal testing - DO NOT USE. // *Action: If set, value will be returned as error. 16078, 00000, "media recovery disabled" // *Cause: The database is not in ARCHIVELOG mode. // *Action: Place the database in ARCHIVELOG mode. 16079, 00000, "standby archival not enabled" // *Cause: The standby database does not have archival enabled. // *Action: In order to allow the standby database to access the standby // logfiles, the ARCH process must be enabled and active. 16080, 00000, "invalid LogMiner session %s for APPLY" // *Cause: Logical standby apply engine was started with an invalid // LogMiner session identifier. // *Action: Fix the problem with the LogMiner session or create a new session. 16081, 00000, "insufficient number of processes for APPLY" // *Cause: Logical standby apply engine was started with fewer processes // available than needed. // *Action: Increase the values of the initialization parameters PROCESSES and // and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter in // SYSTEM.LOGSTDBY$PARAMETERS. 16082, 00000, "logical standby is not initialized correctly" // *Cause: Logical standby apply engine was started but it found // inconsistencies in its metadata. // *Action: Look in the trace file for more information. 16083, 00000, "LogMiner session has not been created" // *Cause: Logical standby apply engine was started without creating a // LogMiner session. // *Action: Create a LogMiner session and restart the apply engine. 16084, 00000, "an apply engine is already running" // *Cause: A logical standby apply engine was running when another was // created. // *Action: Shutdown the previous apply engine before starting a new one. 16085, 00000, "apply engine related event" // *Document: NO // *Cause: // *Action: 16086, 0000, "standby database does not contain available standby logfiles" // *Cause: The primary database is in "no data loss" mode, but the standby // database does not contain any "standby logfiles". // *Action: Add one or more standby logfiles to the standby database. // This can be done while the standby database is mounted. 16087, 0000, "graceful switchover requires standby or current controlfile" // *Cause: An attempt was made to perform a graceful switchover operation // using a backup or clone controlfile. // *Action: Convert the backup controlfile into a current controlfile prior // to attempting a graceful switchover operation. A clone controlfile // cannot be used for a graceful switchover operation. 16088, 0000, "archivelog has not been completely archived" // *Cause: An attempt was made to register an archivelog that has not been // completely archived. The specified archivelog may be a "current" // logfile. // *Action: Specify a completed archivelog. 16089, 0000, "archivelog has already been registered" // *Cause: An attempt was made to register an archivelog that already has // a corresponding thread# and sequence# entry in the standby database // controlfile. Duplicate information is not permitted. // *Action: Use the V$ARCHIVED_LOG fixed view to verify the archivelog // information. 16090, 0000, "archivelog to be replaced not created by managed standby process" // *Cause: An attempt was made to replace an archivelog entry that was not // originally created by the managed standby operation. // *Action: No user action required. 16091, 00000, "dependent archivelog destination already archived" // *Cause: An archivelog destination contains a dependency to another // archivelog destination that has previously been archived. // *Action: The parent archivelog destination cannot be dependent on another // archivelog destination. Use the ALTER SYSTEM command to remove // one of the dependency attributes. 16092, 00000, "dependent archivelog destination is not active" // *Cause: An archivelog destination contains a dependency to another // archivelog destination that is not active" // *Action: The child archivelog destination cannot be dependent on another // invalid archivelog destination. Use the ALTER SYSTEM command to // remove one of the dependency attributes. 16093, 00000, "dependent archivelog destination is not LGWR-enabled" // *Cause: An archivelog destination contains a dependency to another // archivelog destination that is not enabled for the LGWR process" // *Action: The child archivelog destination cannot be dependent on another // archivelog destination not archived by the LGWR. Use the // ALTER SYSTEM command to change the parent archivelog to specify // the LGWR process. 16094, 00000, "database shutdown during archival operation" // *Cause: The database was shutdown while an online logfile archival was active. // *Action: None required. The ARCH process is terminated. 16095, 00000, "Dependent destination removal for inactivation" // *Cause: A dependent archivelog destination was inactivated due to the // parent archivelog destination becoming inelligible for archival. // This may be due to the parent destination being manually // deferred by an application user. // *Action: None required. 16096, 00000, "ALTER DATABASE PREPARE TO SWITCHOVER TO PHYSICAL STANDBY" // *Cause: None // *Action: Specify this command to prepare the primary database for switchover 16097, 00000, "ALTER DATABASE PREPARE TO SWITCHOVER TO PRIMARY" // *Cause: None // *Action: Specify this command to prepare the standby database for switchover 16098, 00000, "inaccessible standby database forced shutdown to protect primary" // *Cause: No standby database archivelog destinations remain accessible // and the primary database is in "protected" no-data-loss mode. // *Action: Specify an alternate standby archivelog destination in // the initialization parameter file. 16099, 00000, "internal error ORA-00600 occurred at standby database" // *Cause: The RFS process on the standby database received an internal error. // *Action: Check the standby alert log and RFS trace files for more // information. // 16100, 00000, "not a valid Logical Standby database" // *Cause: This database has not been completely configured as a Logical Standby // database. // *Action: Verify that the database is the intended Logical Standby database. // Ensure that you already started logical standby apply with the // ALTER DATABASE START LOGICAL APPLY INITIAL statement. // See the Oracle8i SQL Reference manual for the statement syntax. 16101, 00000, "a valid start SCN could not be found" // *Cause: An SCN from which to start could not be found. // *Action: Register the first log file following the backup from which this // database was generated. Using the ALTER DATABASE REGISTER LOGILE // statement to register the database is recommended. Alternatively, // you can provide a starting SCN value with this startement. 16102, 00000, "remote information is not available on the specified primary" // *Cause: The new primary hasn't completed generating the necessary // information for the standby to begin consuming it's log stream. // *Action: Verify that the database link provided references a system that // is about to become a new primary. Wait a short time before // retrying the command to allow the primary some time to generate // the necessary information. 16103, 00000, "Logical Standby apply must be stopped to allow this operation" // *Cause: Logical Standby is currently applying changes. The apply must // complete or be stopped to allow the requested operation. // *Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, // then re-enter or respecify the operation. 16104, 00000, "invalid Logical Standby option requested" // *Cause: The option requested is not valid. // *Action: Check spelling or refer to the Oracle8i SQL Reference manual for // the correct statement syntax, then re-enter the request. 16105, 00000, "Logical Standby is already running in background" // *Cause: A Logical Standby apply operation is already running. // *Action: none 16106, 0000, "Event for enabling netslave testing" // *Cause: This is a Oracle internal event code. It is used to test // LGWR or single ARCH sending logfiles using another netslave // process. // *Action: N/A, this is a Oracle internal event code 16107, 00000, "all log data from primary has been processed" // *Cause: On the primary system, the log stream has been ended by the // ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY command. // *Action: Issue one of the following commands to make this standby a primary // or resume applying changes from a new primary. // ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL PRIMARY; // ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; 16108, 00000, "database is no longer a standby database" // *Cause: The current database has already been made a primary database. // *Action: Issue the following commands to make this primary a standby. // ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY; // ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; 16109, 00000, "failed to apply log data from previous primary" // *Cause: Log data from previous primary could not be completely applied. // *Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective // action. Then, re-issue command. 16110, 00000, "user procedure processing of logical standby apply DDL" // *Cause: A user provided stored procedure has been called to inspect // a DDL statement prior to it being processed. // *Action: No action necessary, this informational statement is provided // to record user involvement in the processing of a statement. // Additional information can be found in the DBA_LOGSTDBY_EVENTS // and the DBA_LOGSTDBY_SKIP views. 16111, 00000, "log mining and apply setting up" // *Cause: This logical standby process is setting up to begin processing // changes. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16112, 00000, "log mining and apply stopping" // *Cause: This logical standby process is cleaning up and stopping Logical // Standby apply. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16113, 00000, "applying change to table or sequence object number %s" // *Cause: The process is applying changes to a specific schema object. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16114, 00000, "applying DDL transaction with commit SCN %s" // *Cause: The process is applying a DDL change that's committed at the given // SCN. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16115, 00000, "loading Log Miner dictionary data" // *Cause: The process is loading dictionary information from the redo stream. // This activity may take a few minutes. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16116, 00000, "no work available" // *Cause: The process is idle waiting for additional changes to be made // available. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16117, 00000, "continue processing" // *Cause: The elapsed wait time is over and the primary function of the // process is continuing. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16118, 00000, "reading stalled waiting for apply" // *Cause: Additional log information cannot be read into memory until // additional changes are applied to the database. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. If this message // occurs often and changes are not being applied quickly, increase // available SGA or the number of apply processes. 16119, 00000, "building transaction at SCN %s" // *Cause: The transaction being committed at the given SCN is being // prepared for apply. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16120, 00000, "scheduling transaction at SCN %s" // *Cause: The transaction committed at the given SCN is being scheduled // for apply. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16121, 00000, "applying transaction with commit SCN %s" // *Cause: The transaction committed at the given SCN is being applied. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16122, 00000, "applying large dml transaction at SCN %s" // *Cause: A large transaction is being applied before the commit has been // seen. The current redo being applied ends as the given SCN. // *Action: No action necessary, this informational statement is provided // to record the event for diagnostic purposes. 16129, 00000, "unsupported dml encountered" // *Cause: DML to tables in the SYS schema have been updated and are not // part of a DDL operation. This may be due to some DBA activity // or DML associated with a kernel PL/SQL request that Logical // Standby doesn't yet support. // *Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table // being processed. Possibly use Log Miner to understand the // transaction, and provide a compensating transaction on the // standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION // with the associated transaction id, and resume apply. 16130, 00000, "supplemental log information is missing from log stream" // *Cause: Supplemental logging is not enabled at the primary database. // *Action: Issue the following command to enable supplemental logging. // ALTER DATABASE ADD // SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS; 16131, 00000, "An error occurred during a Terminal Recovery of the standby." // *Cause: An error occurred during a Terminal Recovery of the standby. // *Action: Check the standby alert log additional information. 16132, 00000, "An error occurred during activation of the standby." // *Cause: An error occurred during activation of the standby database // following a Terminal Recovery. // *Action: Check the standby alert log additional information. 16133, 00000, "Datafile %s has incorrect terminal recovery stamp." // *Cause: After activation of a standby database following a terminal // recovery (recovery of standby using current logs), recovery // of a datafile from before the activation must have completed // the same terminal recovery to avoid corruption. // *Action: A backup of the datafile taken after the terminal recovery // and before activating the standby must be used for recovery. 16134, 00000, "invalid MANAGED recovery FINISH option" // *Cause: A mode other than NOWAIT follows the FINISH keyword in // RECOVER MANAGED STANDBY DATABASE statement. // *Action: Specify either nothing or NOWAIT following FINISH. 16135, 00000, "terminal recovery could not find log for thread# %s seq# %s." // *Cause: A terminal recovery (initiated by the RECOVER MANAGED STANDBY // FINISH command) could not find the current log for the requested // thread and sequence. // *Action: Check that the standby current logs are in the correct location. 16136, 00000, "Managed Standby Recovery not active" // *Cause: An attempt was made to cancel a managed recovery session but // no managed recovery session was active. // *Action: No action is necessary. 16137, 00000, "No terminal recovery is required" // *Cause: All archived logs have been applied, and there are no current // logs to be applied. Terminal recovery is not required. // *Action: No action is necessary. The standby database may be activated as // a new primary or may continue as a standby. 16138, 00000, "end of log stream not received from primary" // *Cause: The standby system has not received notification that the primary // system log stream has been terminated. A graceful switchover is not // possible. // *Action: Verify that the primary log stream has been terminated. Ensure that // the standby has applied all necessary redo from the primary system // and, if appropriate, reissue the graceful switchover command. 16139, 00000, "media recovery required" // *Cause: The database has not been recovered through the end of log stream. // Graceful switchover is not possible. // *Action: Ensure that the entire log stream has been applied. If appropriate, // reissue the graceful switchover command. 16140, 00000, "standby online logs have not been recovered" // *Cause: The standby database has online logs containing redo that has // not been recovered. Activating the standby would lose redo // contained in the online logs. // *Action: To recover the standby online logs issue the following command: // ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then // re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. // To activate the standby without recovering the online logs, // issue the following command: // ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE. 16141, 00000, "enable simulated archivelog error" // *Cause: Causes an error to be signalled during the archival operation. // *Action: No action is required. 16142, 00000, "simulated archivelog error" // *Cause: Error returned for a simulated archival failure during // an archival operation. // *Action: No action is required. 16143, 00000, "RFS connections not allowed during or after terminal recovery" // *Cause: The RFS is attempting to access a standby online logfile during // or after a terminal recovery. // *Action: The primary must not attempt to archive to the standby // after a terminal recovery. 16144, 00000, "simulate RFS error while terminal recovery in progress" // *Cause: Used for internal testing - DO NOT USE. // *Action: If set, value will be returned as error. 16145, 00000, "archival for thread# %s sequence# %s in progress" // *Cause: The indicated archived log file is not available for recovery // due to the fact that it is still being archived. // *Action: Verify that archival of the indicated log file has completed // and reissue the RECOVER STANDBY DATABASE command. 16146, 00000, "standby destination controlfile enqueue unavailable" // *Cause: The target standby destination controlfile is currently // unavailable to the Remote File Server (RFS) process. // This indicates that the target destination is the primary // database itself. // *Action: Check for and eliminate the standby destination archivelog // parameter in question. 16147, 00000, "standby database referenced by multiple archivelog destinations" // *Cause: Multiple archivelog destinations reference the same standby // database, using different service names. This is not allowed. // *Action: Remove one of the duplicate archivelog destinations. 16148, 00000, "user requested expiration of managed recovery operation" // *Cause: The managed standby database recovery operation has been // canceled per user specified EXPIRE option of the RECOVER // MANAGED STANDBY DATABASE statement. // *Action: No action is required. 16149, 00000, "enable simulated ARCH RAC archival testing" // *Cause: Allows ARCH archival even when RAC not enabled // *Action: No action is required. 16150, 00000, "FINISH recovery performed on another, older standby database" // *Cause: An archivelog containing a FINISH recovery indicator was received // by a standby database that has received archivelogs in the future // of the received archivelog. Because of the possibility that these // future archivelogs have been applied to this standby database, // the received archivelog must be rejected. // *Action: No action is required. / / 16500 - 16699 Reserved for Data Guard broker / 16501, 00000, "the Data Guard broker operation failed" // *Cause: The Data Guard broker operation failed. // *Action: See other messages for details. / 16502, 00000, "the Data Guard broker operation succeeded with warnings" // *Cause: The Data Guard broker operation succeeded with warnings. // *Action: See other messages for details. / 16503, 00000, "site ID allocation failure" // *Cause: Number of sites in the Data Guard configuration has exceeded // the limit. // *Action: Delete unused sites. / 16504, 00000, "the Data Guard configuration already exists" // *Cause: A request to create a Data Guard configuration was made on // a site that is part of an existing configuration. // *Action: Delete the existing configuration if you desire to create a // new configuration. / 16505, 00000, "site ID is invalid" // *Cause: The request contained an invalid site ID. // *Action: Make the request again with a valid site iD. / 16506, 00000, "out of memory" // *Cause: Process exceeded private or shared memory limits. // *Action: Check for memory leaks, increase system parameters and restart. / 16507, 00000, "unrecognized request identifier" // *Cause: The specified request identifier was not recognized by // the Data Guard broker. // *Action: Re-issue the request using a valid request identifier. / 16508, 00000, "channel handle not initialized" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16509, 00000, "the request timed out" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16510, 00000, "messaging error using ksrwait" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16511, 00000, "messaging error using ksrget" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16512, 00000, "parameter exceeded maximum size limit" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16513, 00000, "maximum requests exceeded" // *Cause: Non-blocking commands were issued but responses are not read // or the commands did not complete execution. // *Action: Read pending responses or delete outstanding requests and // try again. / 16514, 00000, "the request was not found" // *Cause: An attempt was made to read a response but a matching request // was not found. // *Action: Verify request identifier is valid and references a previously // issued request. / 16515, 00000, "no rcv channel" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16516, 00000, "the resource state is invalid" // *Cause: Specified state is invalid for the resource. // *Action: Verify resource state. / 16517, 00000, "the object handle is invalid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16518, 00000, "unable to allocate virtual instance id" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16519, 00000, "the resource handle is invalid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16520, 00000, "unable to allocate resource id" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16521, 00000, "unable to create generic template id" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16522, 00000, "generic template not found" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16523, 00000, "property count exhausted" // *Cause: Total number of resource properties exceeded the limit. // *Action: / 16524, 00000, "unsupported operation" // *Cause: A command or option is not supported in this release. // *Action: Contact your Oracle support representative. / 16525, 00000, "the Data Guard broker is not yet available" // *Cause: The Data Guard broker process has not yet been started, is // initializing, or failed to start. // *Action: If the broker has not been started set DRS_START to true // and allow the broker to finish initializing before making // the request. If the broker failed to start check the Data Guard // log for possible errors. Otherwise, retry the operation. / 16526, 00000, "unable to allocate task element" // *Cause: The Data Guard broker was unable to allocate memory for // a request. // *Action: Increase the size of your SGA. / 16527, 00000, "unable to allocate SGA heap" // *Cause: The Data Guard broker was unable to allocate a heap within the // SGA. // *Action: Increase SGA memory. / 16528, 00000, "unable to allocate PGA heap" // *Cause: No space in PGA to allocate heap // *Action: Increase process virtual memory. / 16529, 00000, "bad sender id" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16530, 00000, "invalid buffer or length" // *Cause: A NULL buffer or a length of zero is specified. // *Action: Correct command parameters and retry. / 16531, 00000, "unable to post message" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16532, 00000, "Data Guard configuration does not exist" // *Cause: The Data Guard configuration does not exist. // *Action: Create a DRC prior to issuing other requests. / 16533, 00000, "inconsistent Data Guard broker state" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16534, 00000, "no more requests accepted" // *Cause: The Data Guard broker is not accepting any more requests. The // most common cause for this situation is that either a failover // or switchover operation is in progress. // *Action: Wait until the operation is complete and then re-issue the // request. / 16535, 00000, "failover request rejected" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16536, 00000, "unknown object type" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16537, 00000, "child count exceeded" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16538, 00000, "no match on requested item" // *Cause: The Data Guard broker did not recognize the specified // property or state name. // *Action: Verify command parameters and re-issue the request. / 16539, 00000, "task element not found" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16540, 00000, "invalid argument" // *Cause: One of the arguments for the specified request is invalid for // the request type. // *Action: Verify arguments and then re-issue the request. / 16541, 00000, "site is not enabled" // *Cause: The site specified in the request is not enabled. // *Action: Select an enabled site and re-issue the request. / 16542, 00000, "unrecognized operation" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16543, 00000, "invalid request made to broker" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16544, 00000, "unable to make request" // *Cause: The Data Guard broker was unable to accept the request. // *Action: Contact your Oracle support representative. / 16545, 00000, "unable to get response" // *Cause: The Data Guard broker was unable to return the result of // a previous request. // *Action: Contact your Oracle support representative. / 16546, 00000, "missing or invalid piece" // *Cause: The piece of the request to return was not specified or is // invalid. // *Action: Specify the piece of the response starting from 1. / 16547, 00000, "unable to delete request" // *Cause: The Data Guard broker was unable to delete the given request. // *Action: Contact your Oracle support representative. / 16548, 00000, "the resource is not enabled" // *Cause: An attempt was made to modify or query a disabled Data Guard // resource. // *Action: Enable the resource and re-issue the request. / 16549, 00000, "invalid string" // *Cause: A request contains an invalid or NULL string value. // *Action: Correct command parameters and retry. / 16550, 00000, "truncated result" // *Cause: A string property value was truncated due to insufficient // buffer size. // *Action: Specify a larger recieve buffer. / 16551, 00000, "short string copied" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16552, 00000, "the Data Guard broker process (DMON) failed to start" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16553, 00000, "the Data Guard broker process (DMON) failed to shutdown" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16554, 00000, "translation not valid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16555, 00000, "the Data Guard resource is not active" // *Cause: An operation was attempted on a resource that is currently // not active (off path). // *Action: Verify resource is active. / 16556, 00000, "error message is in XML already" // *Cause: Internal error. Invisible to user. // *Action: / 16557, 00000, "the resource is already in use" // *Cause: An attempt was made to create a duplicate resource. // *Action: Check the resource to be added and be sure there are no // duplicates. / 16558, 00000, "the site specified for switchover is not a standby" // *Cause: An attempt was made to switchover to a site that is not a // standby site. // *Action: Locate an enabled standby site and select that site as // the target of the switchover. / 16559, 00000, "out of memory at %s" // *Cause: Internal error. // *Action: Contact your Oracle support representative / 16560, 00000, "unable to convert document, syntax error at \"%s\" " // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16561, 00000, "must use ONLINE parent state, syntax error at \"%s\" " // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16562, 00000, "intended_state not used here, syntax error at \"%s\"" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16563, 00000, "unable to add value, syntax error at \"%s\"" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16564, 00000, "lookup failed, syntax error at %s" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16565, 00000, "duplicate property, syntax error at \"%s\"" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16566, 00000, "unsupported document type" // *Cause: The XML document submitted is not supported. // *Action: Correct the errors and submit the request again. / 16567, 00000, "Data Guard broker internal parser error at \"%s\"" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16568, 00000, "cannot set property %s" // *Cause: The named property could not be modified. // The property may not be editable or may not exist. // *Action: Retry the operation with a valid property. / 16569, 00000, "Data Guard configuration is not enabled" // *Cause: The requested operation requires the Data Guard configuration // to be enabled. // *Action: Enable the Data Guard configuration and re-issue the request. / 16570, 00000, "restart instance on site" // *Cause: Internal error (unused). // *Action: Contact your Oracle support representative. / 16571, 00000, "Data Guard configuration data file creation failure" // *Cause: The Data Guard broker was unable to create the configuration // data on permanent storage. // *Action: Verify that your ORACLE_HOME area is available to the broker. / 16572, 00000, "Data Guard configuration data file not found" // *Cause: The configuration data file is either unavailable or does not // exist. // *Action: Contact your Oracle support representative. / 16573, 00000, "attempt to move configuration file on an enabled DRC" // *Cause: Internal error (not used). // *Action: / 16574, 00000, "Data Guard configuration data file not closed" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16575, 00000, "Data Guard configuration data file not un-identified correctly" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16576, 00000, "failed to update Data Guard configuration data file" // *Cause: A failure was encountered while the broker was updating // the configuration data file on permanent storage. // *Action: Contact your Oracle support representative. / 16577, 00000, "corruption detected in Data Guard configuration data file" // *Cause: The Data Guard broker detected errors while loading the // configuration data file. // *Action: Contact your Oracle support representative. / 16578, 00000, "failed to read Data Guard configuration data file" // *Cause: A failure was encountered while the broker was reading // the configuration data file on permanent storage. // *Action: Contact your Oracle support representative. / 16579, 00000, "bad Data Guard NetSlave state detected" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16580, 00000, "bad Data Guard NetSlave network link" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16581, 00000, "Data Guard NetSlave failed to send message to DRCX" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16582, 00000, "Data Guard connection process received error from NetSlave" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16583, 00000, "bad Data Guard Connection Process DRCX state" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16584, 00000, "illegal operation on a standby site" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16585, 00000, "illegal operation on a primary site" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16586, 00000, "Data Guard broker unable to update configuration on site" // *Cause: The Data Guard broker was unable to update the configuration // data file on a particular site. // *Action: Verify that your Net 8 connections are operational between the // Data Guard sites. / 16587, 00000, "ambiguous object handle" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16588, 00000, "no more internal buffers" // *Cause: See trace file. // *Action: Contact your Oracle support representative. / 16589, 00000, "Data Guard Connect process detected a network transfer error" // *Cause: See trace file. // *Action: Contact your Oracle support representative. / 16590, 00000, "no primary established in Data Guard configuration" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16591, 00000, "unknown field \"%s\" in document" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16592, 00000, "missing field \"%s\" in document" // *Cause: There was an error at the given token. // *Action: Correct the errors and submit the request again. / 16593, 00000, "XML conversion failed" // *Cause: There was an error in the XML request document // *Action: Correct the errors and submit the request again. / 16594, 00000, "%s process discovered that DMON process does not exist" // *Cause: The Data Guard NetSlave (NSV*) process(es) discovered that the // Data Guard broker process (DMON) is not running. // *Action: Check the Data Guard console log and DMON process trace file // to determine why the DMON process is missing. / 16595, 00000, "NetSlave process %s failed to terminate" // *Cause: The specified NetSlave process did not terminate at the // request of the Data Guard broker. // *Action: Contact your Oracle support representative. / 16596, 00000, "site is not a member of the Data Guard configuration" // *Cause: A request was made on a site that is not a member of the // Data Guard configuration. // *Action: Re-issue the request on a site that is a part of the // configuration. / 16597, 00000, "Data Guard broker detects two or more primaries" // *Cause: The Data Guard broker has detected two or more primaries in // the configuration and cannot continue. // *Action: Contact your Oracle support representative. / 16598, 00000, "The Data Guard broker has detected a mismatch in configuration" // *Cause: The Data Guard broker on the this site has detected a mismatch // in configuration generation. This can occur when the primary site // has a stale configuration. // *Action: Contact your Oracle support representative. / 16599, 00000, "The Data Guard broker has detected a stale configuration" // *Cause: The Data Guard broker has detected a stale configuration during // initialization on this site. // *Action: The broker will automatically resolve this situation once the // primary site completes its initialization. / 16601, 00000, "site contains required resources that are disabled" // *Cause: The Data Guard broker detected disabled, required resources // prior to performing an operation that needs those resources to // be enabled. // *Action: Enable all required resources and re-issue the request. / 16602, 00000, "resource must be disabled to perform this operation" // *Cause: An attempt was made to modify a resource that can only // be changed while that resource is disabled. // *Action: Disable the resource and re-issue the request. / 16603, 00000, "Data Guard broker detected mismatch in configuration ID" // *Cause: The Data Guard broker on the this site has detected a mismatch // in configuration Unique ID. This can occur if the original // configuration was recreated while this site was disconnected // from the network or the same site was added to two different // configurations. // *Action: Make sure the site belongs to only one configuration. Remove // configuration metadata files and restart the server. / 16604, 00000, "unable to describe template using package \"%s\"" // *Cause: The Data Guard broker was unable to execute the OnDescribe // function in the named package. // *Action: Verify that the named package is loaded on the primary site. // Also verify that the OnDescribe function is in the package. / 16605, 00000, "unable to delete template, template is in use" // *Cause: The Data Guard broker was unable to delete the template // because the template is still being used by one or more resources. // *Action: Delete all resources using the template before deleting the // template. You cannot delete the database template. / 16606, 00000, "unable to find property \"%s\"" // *Cause: The named property does not exist. // *Action: Specify a valid property name and re-issue the request. / 16607, 00000, "one or more sites have failed" // *Cause: The Data Guard broker detected a failure on one or more sites. // *Action: Locate the site(s) with a failure status and correct it. / 16608, 00000, "one or more sites have warnings" // *Cause: The Data Guard broker detected a warning status on one or // more sites. // *Action: Locate the site(s) with a warning status and correct it. / 16609, 00000, "one or more resources have failed" // *Cause: The Data Guard Broker detected a failure on one or more resources // on a site. // *Action: Locate the resource(s) with a failure status and correct it. / 16610, 00000, "one or more resources have warnings" // *Cause: The Data Guard broker detected a warning status on one or more // resources on a site. // *Action: Locate the resource(s) with a warning status and correct it. / 16611, 00000, "operation aborted at user request" // *Cause: The Data Guard broker aborted an operation at the user's request. // *Action: No action required. / 16612, 00000, "string value too long for attribute \"%s\"" // *Cause: The string value for the named attribute is too long. // *Action: Use a shorter string. / 16613, 00000, "initialization in progress for site" // *Cause: The site received a directive to change its initialization state // or a change in its configuration before it has completed // initialization. // *Action: Wait until the site has completed initialization before // issuing requests to modify run-time state or configuration. / 16614, 00000, "object has an ancestor that is disabled" // *Cause: A request to enable an object that has an ancestor that is // disabled was received by the server. The Data Guard broker // has enabled the object to the extent that it can, but cannot // fully enable the object until its ancestor is enabled. // *Action: Determine the ancestor object that is disabled and enable that // ancestor prior to enabling the child object. / 16615, 0000, "Event for Data Guard NetSlave testing" // *Cause: This is a Oracle internal event code. This event is used for // verifying NetSlave functionality in Data Guard. DO NOT USE. // *Action: N/A, this is a Oracle internal event code. / 16616, 0000, "Event for Data Guard monitor testing" // *Cause: This is a Oracle internal event code. This event is used for // verifying Monitor functionality in Data Guard. DO NOT USE. // *Action: N/A, this is a Oracle internal event code. / 16617, 0000, "Unknown object identifier specified in request" // *Cause: The Data Guard broker returns this error when the object // identifier specified in the request is invalid or unknown. // For example, this error is returned if an invalid or unknown // site object identifier is specified in a request that requires // a site object identifier. // *Action: Verify that a valid object identifier was specified in the // request and then re-issue the request. / 16618, 0000, "response document of size \"%s\" bytes is too large" // *Cause: The document response cannot be returned because the size // of the document is too large. This can occur when displaying // the Data Guard console log. // *Action: View the console log on the given site directly. / 16619, 0000, "Health Check timed out" // *Cause: This status is returned when the Data Guard broker could not reach // a standby site during routine health check. // *Action: This typically indicates a network problem where the standby site // is unable to respond to the primary within the pre-defined time // frame. / 16620, 0000, "one or more sites could not be contacted for a delete operation" // *Cause: This status is returned when the Data Guard broker could not reach // one or more standby sites for either a delete site or a delete // configuration operation. // *Action: This typically indicates a network problem where the standby site // is unable to respond to the primary. In the event of this // situation, examine the Data Guard broker log file on the primary // site to determine which standby sites could not be reached. // Then for each standby site not reached, connect to that site and // shut down the broker by setting the initialization parameter, // drs_start to false. After the broker has been shut down on the // standby site, locate the Data Guard broker configuration files // in the standby site's Oracle home directory and delete them. // See the Data Guard broker manual for the naming conventions of // the configuration files. / / / / 16700 - 16799 reserved for generic resource guards errors / 16701, 00000, "generic resource guard request failed" // *Cause: Request to modify or query the resource failed. // *Action: Check the Data Guard console log for the reason for the failure, // and re-issue the request. / 16702, 00000, "generic resource manager warning" // *Cause: Request to modify or query the resource resulted in a warning. // *Action: Check the console log for the reason for the warning, and // if necessary re-issue the request. / 16703, 00000, "status of request is unknown" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16704, 00000, "a previous set state operation is pending" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16705, 00000, "severe internal error in resource guard" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16706, 00000, "no resource guard is available" // *Cause: No resource guard is available to service the request. // *Action: Contact your Oracle support representative. / 16707, 00000, "the value supplied to resource guard is invalid" // *Cause: The value specified in the request is invalid. // *Action: Check value and re-issue the request. / 16708, 00000, "the state supplied to resource guard is invalid" // *Cause: The state name specified is invalid for the resource. // *Action: Check the state name and re-issue the request. / 16709, 00000, "the resource guard is busy and cannot service the request" // *Cause: Request to resource guard failed becuase the guard is busy. // *Action: Wait for resource guard to finish previous request and then // re-issue the request. / 16710, 00000, "the resource guard is out of memory" // *Cause: The resource guard was unable to allocate memory while trying // to service a request. // *Action: Disable the configuration, shutdown oracle, increase SGA size, // and restart. / 16711, 00000, "the resource guard index is out of bounds" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16712, 00000, "the resource handle is invalid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16713, 00000, "the resource guard timed out while servicing the request" // *Cause: The resource guard timed out while servicing the request. // *Action: Verify that the operation is valid for the resource and then // re-issue the request. / 16714, 00000, "the resource guard exceeded its retry limit" // *Cause: The resource guard exceeded its retry limit while trying to // service a request. // *Action: Verify that the resource is operational and then re-issue the // request. / 16715, 00000, "the logical standby database requires instantiation" // *Cause: The resource guard could not execute the request since the // the logical standby database requires instantiation. // *Action: Instantiate logical standby on the site and then re-issue // the request. / 16716, 00000, "clearing parameter LOG_ARCHIVE_DEST failed" // *Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed. // *Action: Contact your Oracle support representative. / 16717, 00000, "clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed" // *Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed. // *Action: Contact your Oracle support representative. / 16718, 00000, "failed to locate the database resource" // *Cause: The resource guard was unable to locate the database resource // in the configuration. // *Action: Add the database resource and then re-issue the request. / 16719, 00000, "unable to query V$ARCHIVE_DEST fixed view" // *Cause: SQL command to query V$ARCHIVE_DEST failed. // *Action: Test and clear the problem using SQL*Plus. / 16720, 00000, "no available LOG_ARCHIVE_DEST_n parameters to use" // *Cause: All LOG_ARCHIVE_DEST_n parameters have been defined. // *Action: Set some of the LOG_ARCHIVE_DEST_n parameters to empty string. / 16721, 00000, "unable to set LOG_ARCHIVE_DEST_n parameters" // *Cause: An attempt of setting some of the LOG_ARCHIVE_DEST_n parameters // failed. // *Action: Contact your Oracle support representative. / 16722, 00000, "unable to set LOG_ARCHIVE_DEST_STATE_n parameters" // *Cause: An attempt of setting some of the LOG_ARCHIVE_DEST__STATE_n // parameters failed. // *Action: Contact your Oracle support representative. / 16723, 00000, "the connect descriptor is missing from V$ARCHIVE_DEST" // *Cause: The resource guard was unable to set the LOG_ARCHIVE_DEST_n // parameters. // *Action: Reset the values of the LOG_ARCHIVE_DEST_n parameter and // re-issue the request. / 16724, 00000, "the intended state for resource has been set to OFFLINE" // *Cause: The the intended state of the resource has been set to offline. // *Action: If resource is managed, change intended state to online. / 16725, 00000, "the phase supplied to resource manager is invalid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16726, 00000, "the external condition supplied to resource manager is invalid" // *Cause: Internal error. // *Action: Contact your Oracle support representative. / 16727, 00000, "resource guard cannot close database" // *Cause: The resource guard could not close the database. // *Action: Check if there any active sessions connect to the database, // terminate them, then re-issue the request. / 16728, 00000, "Log archive destination could not be set" // *Cause: The resource guard could not set the log archive destination. // *Action: Check the Data Guard console log and the Oracle Alert log for / further details. / 16729, 00000, "Error executing dbms_logstdby.log procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16730, 00000, "Error executing dbms_logstdby.skip_txn procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16731, 00000, "Error executing dbms_logstdby.unskip_txn procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16732, 00000, "Error executing dbms_logstdby.skip procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16733, 00000, "Error executing dbms_logstdby.unskip procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16734, 00000, "Error executing dbms_logstdby.skip_error procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16735, 00000, "Error executing dbms_logstdby.unskip_error procedure" // *Cause: Logical standby package may not be installed. // *Action: Install logical standby packages and re-issue the request. / 16736, 00000, "Standby log archive destination parameter could not be set" // *Cause: Resource guard could not set the standby log archive // destination parameter. // *Action: Check the Data Guard console log for further details. / 16737, 00000, "Log archive format parameter could not be set" // *Cause: Resource guard could not set the log archive format parameter. // *Action: Check the Data Guard console log for further details. / 16738, 00000, "Database file name convert parameter could not be set" // *Cause: Resource guard could not set the database file name convert // parameter. // *Action: Check the Data Guard console log for further details. / 16739, 00000, "Log file name convert parameter could not be set" // *Cause: Resource guard could not set log file name convert parameter. // *Action: Check the Data Guard console log for further details. / 16740, 00000, "Log archive trace parameter could not be set" // *Cause: Resource guard could not set log archive trace parameter. // *Action: Check the Data Guard console log for further details. / 16741, 00000, "Control files parameter could not be set" // *Cause: Resource guard could not set the control files parameter. // *Action: Check the Data Guard console log for further details. / 16742, 00000, "lock name trace parameter could not be set" // *Cause: Resource guard could not set lock name trace parameter. // *Action: Check the Data Guard console log for further details. / 16743, 00000, "FAL client parameter could not be set" // *Cause: Resource guard could not set FAL client parameter. // *Action: Check the Data Guard console log for further details. / 16744, 00000, "FAL server parameter could not be set" // *Cause: Resource guard could not set FAL server. // *Action: Check the Data Guard console log for further details. / 16745, 00000, "Resource guard encountered error during database dismount" // *Cause: Resource guard could not dismount database. // *Action: Check the Data Guard console log for further details. / 16746, 00000, "Resource guard encountered error during database mount" // *Cause: Resource guard could not mount database. // *Action: Check the Data Guard console log for further details. / 16747, 00000, "Logical standby guard could not be turned on" // *Cause: Resource guard could not turn on the logical standby guard. // *Action: Check the Data Guard console log for further details. / 16748, 00000, "Resource guard encountered errors during database open" // *Cause: Resource guard could not open database. // *Action: Check the Data Guard console log for further details. / 16749, 00000, "Resource guard encountered errors in switchover to logical primary" // *Cause: Resource guard could not prepare to switch to logical primary. // *Action: Check the Data Guard console log for further details. / 16750, 00000, "Resource guard encountered errors while activating logical primary" // *Cause: Resource guard could not activate logical primary. // *Action: Check the Data Guard console log for further details. / 16751, 00000, "Resource guard encountered errors in switchover to primary" // *Cause: Resource guard could not prepare to switch to primary. // *Action: Check the Data Guard console log for further details. / 16752, 00000, "Resource guard could not mount standby" // *Cause: Resource guard could not mount standby. // *Action: Check the Data Guard console log for further details. / 16753, 00000, "Resource guard could not open standby database" // *Cause: Resource guard could not open standby database. // *Action: Check the Data Guard console log for further details. / 16754, 00000, "Resource guard could not activate standby" // *Cause: Resource guard could not activate standby. // *Action: Check the Data Guard console log for further details. / 16755, 00000, "Resource guard could not dismount standby" // *Cause: Resource guard could not dismount standby. // *Action: Check the Data Guard console log for further details. / 16756, 00000, "Resource guard could not open standby readonly" // *Cause: Resource guard could not open standby readonly. // *Action: Check the Data Guard console log for further details. / 16757, 00000, "Resource guard could not get property" // *Cause: Resource guard failed to get property // *Action: Check the Data Guard console log for further details. / 16758, 00000, "Resource guard could not verify property" // *Cause: Resource guard failed to verify property. // *Action: Check the Data Guard console log for further details. / 16759, 00000, "Resource guard unable to start logical apply engine with initial SCN" // *Cause: Resource guard failed to start logical apply engine with an // initial SCN. // *Action: Check the Data Guard console log for further details. / 16760, 00000, "Resource guard could not start logical apply engine" // *Cause: Resource guard failed to start logical apply engine. // *Action: Check the Data Guard console log for further details. / 16761, 00000, "Resource guard could not stop logical apply engine" // *Cause: Resource guard failed to stop logical apply engine correctly. // *Action: Check the Data Guard console log for further details. / 16762, 00000, "Invalid database state" // *Cause: Database is not in the intended state. // *Action: Determine the reason for invalid state, and re-issue get status // request. / 16763, 00000, "Log transport service for some site unexpectedly online" // *Cause: Log transport service for some site is online when it should be // offline. // *Action: Check the Data Guard console log for further details. If // necessary, stop the log transport service for the site. / 16764, 00000, "Log tranport service for some site unexpectedly offline" // *Cause: Log transport service for some site is offline when it should be // online. // *Action: Check the Data Guard console log for further details. If // necessary, start the log transport service. / 16765, 00000, "Physical apply service unexpectedly online" // *Cause: Physical apply service is online when it should be offline. // *Action: If necessary, stop the physical apply service. / 16766, 00000, "Physical apply service unexpectedly offline" // *Cause: Physical apply service is offline when it should be online. // *Action: If necessary, start the physical apply service. / 16767, 00000, "Logical apply service unexpectedly online" // *Cause: Logical apply service is online when it should be offline. // *Action: If necessary, stop the logical apply service. / 16768, 00000, "Logical apply service unexpectedly offline" // *Cause: Logical apply service is offline when it should be online. // *Action: If necessary, start the logical apply service. / 16769, 00000, "Error executing apply_set procedure" // *Cause: There was an error executing dbms_logstdby$apply_set procedure. // *Action: Check the values for the property, and set configuration // property again. / 16770, 00000, "Error executing apply_unset procedure" // *Cause: There was an error executing dbms_logstdby$apply_unset procedure. // *Action: Check the values for the property, and set configuration // set property again. / 16771, 00000, "Error starting ARCH process(es)" // *Cause: There was an error starting the archival process(es). // *Action: Check the Data Guard console log for further details. / 16772, 00000, "Error in switching over between primary and standby databases" // *Cause: There was an error during switchover of primary and standby // databases. // *Action: Check the Data Guard console log for further details. / 16773, 00000, "Error in starting the physical apply service (MRP process)" // *Cause: There was an error in starting the physical apply service // (MRP process). // *Action: Check the Data Guard console log for further details. / 16774, 00000, "Error in stopping the physical apply service (MRP process)" // *Cause: There was an error in stopping the physical apply service // (MRP process). // *Action: Check the Data Guard console log for further details. / 16775, 00000, "The physical apply service terminated prematurely" // *Cause: The physical apply service terminated prematurely with an error. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. / 16776, 00000, "Health check of the log transport service failed" // *Cause: Due to some internal failure, the database resource guard cannot // complete the health check of the log transport service. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. / 16777, 00000, "Unable to find the destination entry of a site in V$ARCHIVE_DEST" // *Cause: Some destination may be manually deleted, or no entry is available // for Data Guard. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. / 16778, 00000, "The log transport service for some site has an error" // *Cause: Some problem in communicating with a standby site causes the log // transport to fail. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. Query the LogXptStatus property to see the // error message. / 16779, 00000, "The destination parameter of some site has wrong syntax" // *Cause: The destination is defined in the init.ora file with wrong syntax, // and the Data Guard broker fails to update the destination // when the log transport is turned on. // *Action: Check the Data Guard console log to see which site has the // problem. Fix the syntax error in the init.ora file or remove // the entry from the init.ora. Check if the syntax of the property // LogArchiveDestOptions is correct. / 16780, 00000, "Some site has used up its quota" // *Cause: Some site has used up its quota for storing archived redo logs. // *Action: Check the Data Guard console log to see which site has the // problem. Remove some archived logs at the standby // site or increase its quota. / 16781, 00000, "The status of log transport service for some site is unknown" // *Cause: Log transport to some site has an unknown status. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. / 16782, 00000, "Uable to get values of some critical configurable properties" // *Cause: Log transport cannot be turned on because some critical property // values cannot be retrieved from Data Guard metadata. // *Action: Check the Data Guard console log and Oracle Alert log for // further details. / 16783, 00000, "Some critical configurable property has not been set" // *Cause: Log transport cannot be turned on because some critical property // has not been set. // *Action: Check the Data Guard console log to see which property has not // been set, and set it properly. / 16784, 00000, "Unable to find a site with the name given in ArchiveDestDependency" // *Cause: Property ArchiveDestDependency has a wrong value. // *Action: Reset property ArchiveDestDependency to the correct name of the // site that the standby depends on. / 16785, 00000, "The primary database is not in ARCHIVELOG mode" // *Cause: The primary database is in NOARCHIVELOG mode. // *Action: Reset the primary database to ARCHIVELOG mode by issuing ALTER // DATABASE ARCHIVELOG command. / 16786, 00000, "Resource guard cannot access Data Guard metadata" // *Cause: The metadata files do not exist or the Data Guard configuration // has not been created. // *Action: Check the Data Guard console log for further details. / 16787, 0000, "Event for Data Guard Resource Guard process testing" // *Cause: This is an Oracle internal event code. This event is used for // verifying Resource Guard process functionality. DO NOT USE. // *Action: N/A, this is a Oracle internal event code. / 16788, 0000, "Unable to set one or more database configuration property values" // *Cause: This situation occurs when database resource guard attempts to // set database initialization parameters through configuration // properties. Typical causes of this error are: // a) The values of LogArchiveDestOptions have syntax errors; // b) The Value of LogArchiveTrace is out of range; // c) Database initialization parameter STANDBY_FILE_MANAGEMENT cannot // be set to AUTO because the database compatability is not set // to 9.0.0.0.0 or higher. // *Action: Check the Data Guard console log to see which property has the // problem and reset the property correctly. / / 16900 - 16999 Reserved for Data Guard CLI / 16900, 00000, "Unable to initialize client" // *Cause: The client could not be initialized. // *Action: This is an internal error. Contact your Oracle support // representative / 16901, 00000, "Unable to initialize environment" // *Cause: The database environment could not be allocated and initialized. // *Action: This is an internal error. Contact your Oracle support // representative. / 16902, 00000, "Unable to allocate handle" // *Cause: The database handles could not be allocated. // *Action: This is an internal error. Contact your Oracle support // representative. / 16903, 00000, "Unable to connect to database" // *Cause: The database specified was unreachable because it does not // exist or was not started. // *Action: Correct the request or start the database and try again. / 16904, 00000, "Unable to set attribute" // *Cause: The server attributes could not be set // *Action: check additional error messages / 16905, 00000, "Failed." // *Cause: The given action failed. // *Action: check additional error messages / 16906, 00000, "Unable to accept commands: no memory" // *Cause: No memory was available for the program. // *Action: Increase memory and try again. / 16907, 00000, "missing field" // *Cause: A required field was missing. // *Action: Type "help" for syntax and try again. / 16908, 00000, "Unknown option: \"%s\"" // *Cause: The given option is not supported. // *Action: Try again using the proper command line syntax. / 16909, 00000, "Fatal Error. quitting..." // *Cause: A fatal error was encountered. // *Action: See additional error messages and/or contact your Oracle support // representative. / 16910, 00000, "unable to issue command to server" // *Cause: Commands cannot be issued to the server. // *Action: See additional error messages and/or contact your Oracle support // representative. / 16911, 00000, "Warning:" // *Cause: An action succeeded with warnings. // *Action: See error message and take appropriate action. / 16912, 00000, "Unknown command \"%s\". Try \"help\"" // *Cause: An unknown command was issued. // *Action: Try again using a valid command. / 16913, 00000, "The following commands are available:" // *Document: NO // *Cause: // *Action: / 16914, 00000, "Missing connect string. Try \"help\"" // *Cause: The connect string for the database is missing. // *Action: Try the command again with a valid connect string. / 16915, 00000, "Connected." // *Document: NO // *Cause: // *Action: / 16916, 00000, "Missing site. Try \"help\"" // *Cause: The site name is missing. // *Action: Try the command again using correct syntax / 16917, 00000, "Missing XML document. Try \"help\"" // *Cause: The XML document argument was missing. // *Action: Try the command again using correct syntax. / 16918, 00000, "Unknown document type" // *Document: NO // *Cause: An unknown document type was // *Action: Contact your Oracle support representative. / 16919, 00000, "missing document" // *Document: NO // *Cause: No response came back from the server // *Action: Contact your Oracle support representative. / 16920, 00000, "corrupted document" // *Document: NO // *Cause: A corrupted XML document came back from the server // *Action: Contact your Oracle support representative. / 16921, 00000, "Succeeded." // *Document: NO // *Cause: The given action succeeded. // *Action: No action is required. / 16922, 00000, "Warning: %s" // *Document: NO // *Cause: // *Action: / 16923, 00000, "Error: %s" // *Document: NO // *Cause: // *Action: / 16925, 00000, "exit the program" // *Document: NO // *Cause: // *Action: / 16926, 00000, "display the configuration of the framework, site, or resource" // *Document: NO // *Cause: // *Action: / 16927, 00000, "enable the framework, site, or resource" // *Document: NO // *Cause: // *Action: / 16928, 00000, "disable the framework, site, or resource" // *Document: NO // *Cause: // *Action: / 16929, 00000, "display the help for a given command" // *Document: NO // *Cause: // *Action: / 16930, 00000, "bring the framework, site, or resource ONLINE" // *Document: NO // *Cause: // *Action: / 16931, 00000, "bring the framework, site, or resource OFFLINE" // *Document: NO // *Cause: // *Action: / 16932, 00000, "show the console log for a particular site" // *Document: NO // *Cause: // *Action: / 16933, 00000, "show the alert log for a particular site" // *Document: NO // *Cause: // *Action: / 16934, 00000, "show the version of the framework" // *Document: NO // *Cause: // *Action: / 16935, 00000, "gracefully switch over to a standby site" // *Document: NO // *Cause: // *Action: / 16936, 00000, "fail over to a standby site" // *Document: NO // *Cause: // *Action: / 16937, 00000, "connect to a server" // *Document: NO // *Cause: // *Action: / 16938, 00000, "send a command to the recovery framework" // *Document: NO // *Cause: // *Action: / 16939, 00000, "Could not start up \"%s\" as primary" // *Cause: The named site could not be started in the primary role. // *Action: See additional messages. / 16940, 00000, "Started \"%s\" as new primary" // *Cause: The named site was started as the new primary site. // *Action: No action is required. / 16941, 00000, "Switchover succeeded. New primary is \"%s\"" // *Document: NO // *Cause: The switchover operation succeeded. // *Action: No action is required. / 16942, 00000, "Could not start up \"%s\" as standby" // *Cause: The named site could not be started in the standby role. // *Action: See additional messages. / 16943, 00000, "Started \"%s\" as standby" // *Cause: The named site was started as the new primary site. // *Action: No action is required. / 16944, 00000, "Failover succeeded. New primary is \"%s\"" // *Cause: The failover operation succeeded. // *Action: No action is required. / 16945, 00000, "Syntax error at \"%s\"" // *Cause: The given command could not be processed because a syntax // error occured at the named token. // *Action: Try the command again using valid syntax. / 16946, 00000, "Site \"%s\" was not found" // *Cause: The named site could not be found. // *Action: Try the command again using a valid site. / 16947, 00000, "\"%s\" does not run in the primary role" // *Cause: The named resource does not run in the primary role. // *Action: Try the command again using a resource that runs // in the primary role. / 16948, 00000, "\"%s\" does not run in the standby role" // *Cause: The named resource does not run in the standby role. // *Action: Try the command again using a resource that runs // in the standby role. / 16949, 00000, "Resource \"%s\" was not found" // *Cause: The named resource was not found. // *Action: Try the command again using a valid resource. / 16950, 00000, "Unable to retrieve \"%s\" for editing" // *Cause: The named object could not be retrieved for editing. // *Action: Contact your Oracle support representative. / 16951, 00000, "manager information not found" // *Cause: The manager information could not be retrieved for a // generic resource. // *Action: Contact your Oracle support representative. / 16952, 00000, "unable to describe configuration" // *Cause: The configuration could not be described. // *Action: The framework could not be contacted. Check to see that // The DMON process is running. / 16953, 00000, "site or resource \"%s\" does not exist" // *Cause: The named site or resource does not exist. // *Action: Try the command again using a valid site or resource. / 16954, 00000, "a resource cannot run on multiple sites this way" // *Cause: An attempt was made to create a resource that depends on multiple // sites. This is not possible using one command. // *Action: Issue the command twice; one with the first site and the // second using the second site. / 16955, 00000, "unable to create or locate template" // *Cause: The template could not be found. // *Action: See additional error messages. / 16956, 00000, "missing template name" // *Cause: The template name was omitted from the command. // *Action: Try the command again using a valid template name. / 16957, 00000, "template \"%s\" was not found" // *Cause: The named template could not be found. // *Action: Try the command again using a valid template name. / 16958, 00000, "unable to convert document" // *Cause: The document could not be converted. // *Action: Contact your Oracle support representative. / 16959, 00000, "NULL answer from framework" // *Cause: No answer came from the framework. // *Action: The framework is not available. Check to see that the DMON // process exists. / 16960, 00000, "status not available" // *Cause: The status could not be retrieved. // *Action: The framework is not available. Check to see that the DMON // process exists. / 16961, 00000, "create a configuration, site or resource" // *Document: NO // *Cause: // *Action: / 16962, 00000, "edit a configuration, site or resource" // *Document: NO // *Cause: // *Action: / 16963, 00000, "remove a configuration, site or resource" // *Document: NO // *Cause: // *Action: / 16964, 00000, "remove unused templates" // *Document: NO // *Cause: // *Action: / 16965, 00000, "No help available for help \"%s\"" // *Document: NO // *Cause: // *Action: / 16966, 00000, "no properties" // *Document: NO // *Cause: // *Action: / 16967, 00000, "--Press Return to continue or Q to quit--" // *Document: NO // *Cause: // *Action: / 16968, 00000, "Current status for \"%s\":" // *Document: NO // *Cause: // *Action: / 16969, 00000, "Configuration \"%s\" added with primary site \"%s\"" // *Document: NO // *Cause: // *Action: / 16970, 00000, "Created template \"%s\" as \"%s.%s\"." // *Document: NO // *Cause: // *Action: / 16971, 00000, "Database generic resource \"%s\" added for role \"%s\"." // *Document: NO // *Cause: // *Action: / 16972, 00000, "Database resource \"%s\" added." // *Document: NO // *Cause: // *Action: / 16973, 00000, "Default primary for configuration \"%s\" is now \"%s\"." // *Document: NO // *Cause: // *Action: / 16974, 00000, "Disabled." // *Document: NO // *Cause: // *Action: / 16975, 00000, "Enabled." // *Document: NO // *Cause: // *Action: / 16976, 00000, "Property \"%s\" updated." // *Document: NO // *Cause: // *Action: / 16977, 00000, "Removed configuration." // *Document: NO // *Cause: // *Action: / 16978, 00000, "Removed site \"%s\" from configuration." // *Document: NO // *Cause: // *Action: / 16979, 00000, "Resource \"%s\" default state in primary role is set to \"%s\"." // *Document: NO // *Cause: // *Action: / 16980, 00000, "Resource \"%s\" default state in standby role is set to \"%s\"." // *Document: NO // *Cause: // *Action: / 16981, 00000, "Removed resource \"%s\" from configuration." // *Document: NO // *Cause: // *Action: / 16982, 00000, "Site \"%s\" added to configuration." // *Document: NO // *Cause: // *Action: / 16983, 00000, "Started." // *Document: NO // *Cause: // *Action: / 16984, 00000, "Stopped." // *Document: NO // *Cause: // *Action: / 16985, 00000, "There are %s templates:" // *Document: NO // *Cause: // *Action: / 16986, 00000, "There are no unused templates." // *Document: NO // *Cause: // *Action: / 16987, 00000, "There is one template:" // *Document: NO // *Cause: // *Action: / 16988, 00000, "Unused template \"%s\" removed." // *Document: NO // *Cause: // *Action: / 16989, 00000, "Valid states are:" // *Document: NO // *Cause: // *Action: / 16990, 00000, "Site \"%s\" updated." // *Document: NO // *Cause: // *Action: / 16991, 00000, "ambiguous resource name" // *Cause: The named resource exists on more than one site. // *Action: The request must be more specific. Issue the command again // using the ON SITE clause. / / / 17000 - 17499 Reserved for JDBC / / 17500 - 18000 Reserved for I/O subsystem / 17500, 00000, "ODM err:%s" // *Cause: An error returned by ODM library // *Action: Look at error message and take appropriate action or contact // Oracle support for further assistance / 17501, 00000, "logical block size %s is invalid" // *Cause: logical block size for oracle files must be a multiple of the // physical block size, and less than the maximum // *Action: check init.ora parameters / 17502, 00000, "ksfdcre:%s Failed to create file %s" // *Cause: file creation failed due to either insufficient OS permission or // the file already exists // *Action: check additional error messages / 17503, 00000, "ksfdopn:%s Failed to open file %s" // *Cause: file open failed due to either insufficient OS permission or // the name of file exceeds maximum file name length. // *Action: check additional error messages / 17504, 00000, "ksfddel:Failed to delete file %s" // *Cause: The file thats being deleted is still in use or the process // has insufficient permission to delete file. // *Action: check additional error messages / 17505, 00000, "ksfdrsz:%s Failed to resize file to size %s blocks" // *Cause: There is insufficient space left on the device or the process // has insufficient permission to resize file. // *Action: check additional error messages / 17506, 00000, "I/O Error Simulation" // *Cause: The i/o request is marked with error because the i/o error // simulation event is turned on. // *Action: / 17507, 00000, "I/O request size %s is not a multiple of logical block size" // *Cause: i/o's are done in multiple of logical block size // *Action: Check additional error messages / 17508, 00000, "I/O request buffer ptr is not alligned" // *Cause: i/o request buffer should be alligned, check additional // information for buffer ptr value // *Action: Call Oracle support / 17509, 00000, "Attempt to do i/o beyond block1 offset" // *Cause: When a file is identified with logical block size of 0, only i/o's // to block1 is allowed. // *Action: check additional error messages and call Oracle support / 17510, 00000, "Attempt to do i/o beyond file size" // *Cause: The i/o request points to a block beyond End Of File // *Action: check additional error messages and call Oracle support / 17610, 00000, "file '%s' does not exist and no size specified" // *Cause: An attempt to create a file a file found neither an existing file // nor a size for creating the file. // *Action: Specify a size for the file. / 17611, 00000, "ksfd: file '%s' cannot be accessed, global open closed" // *Cause: An attempt to write to a file which has gone offline/unidentified // *Action: Check for other errno in the stack / / 18000 - 18099 Reserved for PLAN STABILITY / 18000, 00000, "invalid outline name" // *Cause: The parser detected a missing or invalid outline name // *Action: 18001, 00000, "no options specified for ALTER OUTLINE" // *Cause: The parser detected that no clause was specified on the command // Our performance tests, which are not typical as they exercise all // branches of the code, have shown approximately a 30% performance // increase line for ALTER OUTLINE. // *Action: Re-issue the command, specifying a valid ALTER OUTLINE clause. 18002, 00000, "the specified outline does not exist" // *Cause: Either the outline did not exist to begin with, or a timing window // allowed for another thread to drop or alter the outline midstream. // *Action: 18003, 00000, "an outline already exists with this signature" // *Cause: The signature generation algorithm generates signatures that are // are 16 bytes in length so it is highly unlikely that any 2 // signatures will be identical. This message is raised in such a // rare case. // *Action: Either re-issue the statement that led to the outline being created // with some whitespace added or force the outline to be created in a // different category. 18004, 00000, "outline already exists" // *Cause: An outline already exists, either with the specified name, or for // the specified SQL text. // *Action: 18005, 00000, "create any outline privilege is required for this operation" // *Cause: // *Action: 18006, 00000, "drop any outline privilege is required for this operation" // *Cause: // *Action: 18007, 00000, "alter any outline privilege is required for this operation" // *Cause: // *Action: 18008, 00000, "cannot find OUTLN schema" // *Cause: The database creation script that creates this schema must not // have been executed. // *Action: Review the log files to see what happened when the database // was created. 18009, 00000, "one or more outline system tables do not exist" // *Cause: Either the database creation script that creates these tables // was not executed or a user accidently deleted the table // *Action: Review the log files to see what happened when the database // was created. 18010, 00000, "command missing mandatory CATEGORY keyword" // *Cause: User failed to specify the CATEGORY keyword // *Action: Re-issue the command with the CATEGORY keyword included 18011, 00000, "the outline specified in the FROM clause does not exist" // *Cause: // *Action: 18012, 00000, "select_catalog_role role is required for this operation" // *Cause: // *Action: 18013, 00000, "timed out while waiting for resource %s" // *Cause: // *Action: 18014, 00000, "deadlock detected while waiting for resource %s" // *Cause: // *Action: 18015, 00000, "invalid source outline signature" // *Cause: User imported an 8i outline into a 9i database without updating signatures // *Action: execute dbms_outln.update_signatures /============================================================================ / 19000 - 19199 Reserved for XMLType error messages / / Begin messages for XML errors /============================================================================ / 19000, 00000, "missing RELATIONAL keyword" // *Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification. // *Action: Supply the RELATIONAL keyword in the storage clause 19001, 00000, "Invalid storage option specified" // *Cause: An invalid storage option was specified for the XMLType. // *Action: Supply a valid storage option. 19002, 00000, "Missing XMLSchema URL" // *Cause: A XML schema URL must be specified in the storage option. // *Action: Specify a URL for the XMLSchema. 19003, 00000, "Missing XML root element name" // *Cause: A root element in the XMLSchema must be specified if the XML schema is given. // *Action: Specify a root element in the XML schema. 19004, 00000, "Duplicate XMLType OBJECT RELATIONAL storage option" // *Cause: A duplicate storage option for the XMLType column was specified // *Action: Specify a single storage option for an XMLType column 19005, 00000, "Duplicate XMLType LOB storage option" // *Cause: A duplicate storage option for the XMLType column was specified // *Action: Specify a single storage option for an XMLType column 19006, 00000, "XMLType TYPE storage option not appropriate for storage type" // *Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option // *Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column 19007, 00000, "Schema and element do not match " // *Cause: The schema and element specified in the inserted data does not match that of the column // *Action: Insert/Update only the XML documents that conform to that particular schema and element. 19008, 00000, "Invalid version of the XMLType " // *Cause: An invalid version of the XMLType was found. // *Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database. 19009, 00000, "Missing XMLSchema keyword" // *Cause: The XMLSchema keyword is missing // *Action: Specify the XMLSchema URL and element name. 19010, 00000, "Cannot insert XML fragments" // *Cause: XML fragments got from extractNode cannot be inserted into the database. // *Action: Convert the fragment into a proper XML document before insertion. 19011, 00000, "Character string buffer too small" // *Cause: The string result asked for is too big to return back // *Action: Get the result as a lob instead 19012, 00000, "Cannot convert XML fragment to the required datatype" // *Cause: A conversion to a datatype was requested which cannot be performed // *Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype. 19013, 00000, "Cannot create VARRAY columns containing XMLType" // *Cause: An attempt was made to create a VARRAY column which contains a XMLType // *Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead 19015, 00000, "Invalid XML tag identifier (%s)" // *Cause: An invalid XML identifer was detected during XML generation // *Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification 19016, 00000, "attributes cannot occur after element specifications" // *Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML // *Action: Change the order of the types so that the attributes occur in the begining 19017, 00000, "Attributes can only be simple scalars" // *Cause: Attribute values can only be simple scalar values // *Action: Use only simple datatypes for attribute values 19018, 00000, "Invalid character in XML tag '%s'" // *Cause: A tag name was found to have an invalid XML character during XML generation. // *Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters. 19019, 00000, "Invalid context passed to DBMS_XMLGEN.GETXML" // *Cause: The value of context passed to GETXML was invalid. // *Action: Rewrite the query so that the value of context passed to GETXML is valid. / /============================================================================ / 19200 - 19299 Reserved for XMLGEN and XMLAGG error messages / / Begin messages for DBMS_XML errors /============================================================================ / 19200, 00000, "Invalid column specification" // *Cause: All input arguments must be valid columns // *Action: Specify a valid list of columns 19201, 00000, "Datatype not supported" // *Cause: The particular datatype is not supported in the XMLGEN operator // *Action: Specify only supported datatypes as arguments to the XMLGEN operator 19202, 00000, "Error occurred in XML processing%s" // *Cause: An error occurred when processing the XML function // *Action: Check the given error message and fix the appropriate problem 19203, 00000, "Error occurred in DBMS_XMLGEN processing%s" // *Cause: An error occurred when processing the DBMS_XMLGEN functions // *Action: Check the given error message and fix the appropriate problem 19204, 00000, "Non-scalar value '%s' is marked as XML attribute" // *Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@' // *Action: Remove the '@' sign, or make the value a scalar. 19205, 00000, "Attribute '%s' qualifies a non-scalar value in the select list" // *Cause: The attribute immediately follows a value of object or collection type in the select list or type definition. // *Action: Remove the '@' sign, or make the previous value a scalar. / /============================================================================ / 19300 - 19399 Reserved for UriType error messages / / Begin messages for UriType errors /============================================================================ / / 19300 - 19319 = reserved for general uri error messages / 19300, 00000, "Error occurred in uri processing%s" // *Cause: An error occurred when processing the URL // *Action: Check the given error message and fix the appropriate problem / / 19320 - 19329 = reserved for Httpuri error messages / 19320, 00000, "Host name not specified in HTTP URL" // *Cause: A host name was not specified in the HTTP url // *Action: Specify a host name in the HTTP url when creating the URL string 19321, 00000, "Could not open HTTP connection to host (%s): port (%s)" // *Cause: A HTTP connection could not be opened to the host // *Action: Specify a valid host name and port to connect to 19322, 00000, "An error occurred while reading from host (%s): port (%s)" // *Cause: An error occurred while reading from the HTTP host // *Action: Specify a valid host name and port to read from 19323, 00000, "Invalid url string" // *Cause: The URL must be a valid URL string // *Action: Specify a valid url string / / 19330 - 19360 = reserved for DBUri error messages / 19330, 00000, "Type '%s'.'%s' not installed. Please install the type before using the CREATE_DBURI operator" // *Cause: The type required for the CREATE_DBURI operator has not been installed correctly. // *Action: Read the installation notes to install the type correctly. 19331, 00000, "Last argument to CREATE_DBURI operator must be a column" // *Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created. // *Action: Specify a valid column name in the query. 19332, 00000, "Invalid column in the CREATE_DBURI operator" // *Cause: The argument to the CREATE_DBURI operator can only be a column. // *Action: Specify a valid column name for the operator 19333, 00000, "Invalid flags for the CREATE_DBURI operator" // *Cause: The flags argument given to the DBURI operator is invalid // *Action: Specify a valid flag value (TEXT) for the DBURI operator 19334, 00000, "Invalid column specification for CREATE_DBURI operator" // *Cause: All columns must be valid and pointing to the same table or view // *Action: Specify valid list of columns that are from the same table or view. 19335, 00000, "Invalid format type object" // *Cause: An invalid format type object was specified for the XML function // *Action: Specify a valid format type object 19336, 00000, "Missing XML root element" // *Cause: The XML being generated does not have an enclosing root element. // *Action: The XML generated must have a root element / / Error numbers / / 19400 - 19499 are reserved for KOT. / / 19490 - 19499 Reserved for KOKT3 / / 19500 - 19998 Reserved for Server Managed Recovery / 19500-19549: KGF*, KSF* / 19550-19649: KRB*, except KRBI / 19700-19724: KRBI / / 21100 - 21299 Reserved for CORE / 21300 - 22799 Reserved for OI/KO/KG (object Interface and Subsystem) / / 22800 - 22999 Reserved for object SQL: / 23000 - 23299 Reserved for object Management Subsystem (OMS) / / 23300 - 24299 Reserved for errors from DBMS* pl/sql packages / 23300 - 23999: Replication Packages / 24000 - 24099: AQ admin interface / 24100 - 24100: Transaction Management / 24120 - 24140: DBMS_REPAIR package / 24141 - 24159: DBMS_RULE package / 24270 - 24279: DBMS_HO package / / MODIFIED / jingliu 04/08/01 - add 23537 / arrajara 04/05/01 - Add 23536 / arrajara 04/04/01 - add 23535 / kmuthiah 04/05/01 - add 22984 / ciyer 03/07/01 - add 22341 for bad narrowing / jingliu 03/02/01 - add 23534 / jingliu 02/12/01 - add 23533 / gtarora 02/26/01 - add 22297 / nbhatt 02/13/01 - / nbhatt 02/13/01 - move 24085 to 24028 / thoang 02/08/01 - add 22340 / nshodhan 02/12/01 - Remove 23486 / thchang 12/15/00 - add 22828 / sichandr 01/22/01 - add event 22829 : allow LATERAL views / thoang 01/24/01 - Modify ORA-22333 and 22334 / nbhatt 01/23/01 - add error message for transformation / thoang 11/10/00 - Add 22338 & 22339 / vsrihari 01/15/01 - add 19684 for block media recovery / rvenkate 12/18/00 - 1546531: object id support for min_communication / jingliu 12/11/00 - add 23531, 23532 / nireland 12/06/00 - add 23515 / kmuthiah 11/28/00 - add 22983 / sichandr 11/29/00 - event 22827 : remote KGL lookup / liwong 10/23/00 - Add 23496 / nbhatt 11/16/00 - http propagation errors / heneman 10/21/00 - Rename MTS. / thoang 10/12/00 - Update mesg 22337 / fsanchez 07/12/00 - cfile-autobackup / fsanchez 06/14/00 - Modify 19511 / nbhatt 09/19/00 - add error messages / skabraha 09/22/00 - Add 22371 / thoang 08/24/00 - Add new mesg for object - image type vsn mismatch / delson 08/28/00 - remove 24277,8,9 per elimination of ho callouts. / thoang 08/04/00 - Fixed 22326 error msg. / thchang 08/16/00 - Add 22998 / shbose 08/16/00 - remove comments from 23322 and 23321 / banand 08/08/00 - Modify 19595 / fsanchez 07/12/00 - cfile-autobackup / fsanchez 06/14/00 - Modify 19511 / alakshmi 07/31/00 - Bug 1360924: Fix 23436/23437 / sdizdar 07/13/00 - RMAN retention policy (keep): / - add 19603 for KEEP .. UNRECOVERABLE / aahluwal 07/24/00 - Changing xml Auth procedure error messages / molagapp 07/05/00 - add 19683, reuse 19680 / aquser1 07/19/00 - Add AQ 8.2 error messages / banand 07/18/00 - Add 19579, 19582 for archivelog backup failover / skabraha 07/18/00 - Add 22335 for type evolution / elu 07/11/00 - add 23505 / elu 07/11/00 - add 23505 / fsanchez 07/12/00 - cfile-autobackup / thoang 06/27/00 - Add 22333 and 22334 for ALTER TYPE / rkasamse 06/22/00 - error if oid creation fails / fsanchez 06/14/00 - Modify 19511 / masubram 06/20/00 - code review comments / masubram 06/19/00 - add error message for online reorg / liwong 06/19/00 - Add 23491, 23492, 23493, 23494, 23495 / najain 05/19/00 - AQ security support / celsbern 06/21/00 - added 23504. / rxgovind 06/01/00 - update / thoang 05/30/00 - Add 22321 - 22324 for ALTER TYPE / liwong 05/19/00 - Add 23487, 23488, 23489, 23490 / najain 05/19/00 - AQ security support / kmuthiah 05/17/00 - add 22981/2. / fsanchez 05/13/00 - bug-1092966 / thoang 05/11/00 - Add 22312 for type evolution / rxgovind 05/09/00 - add messages for OCIAnyDataSet / liwong 05/08/00 - Add 23486 / molagapp 05/04/00 - add bmr messages / sdizdar 04/12/00 - RMAN configuration: / thoang 04/11/00 - Add new error msg for alter type. / jingliu 04/10/00 - 23503 ias instantiation / rmurthy 04/04/00 - add 22826 for non instantiable / elu 04/03/00 - add 23485 / arrajara 03/24/00 - Add 23502 missing_offline_dirpath / liwong 03/21/00 - Add 23484 / rkasamse 03/13/00 - add error messages for OCIAnyData / jingliu 02/03/00 - Add 23500, 23501 / liwong 01/22/00 - Modify comments for 23480, 23482, 23483 / apadmana 01/06/00 - change SNAPSHOT to MATERIALIZED VIEW / gtarora 01/12/00 - Add LONG to LOB error messages / liwong 10/24/99 - Remove quotes for 23333,23334, etc / swerthei 09/13/99 - add 19711 / liwong 09/09/99 - Add 23484 / liwong 09/01/99 - Add 23483 / elu 08/27/99 - add message for 23482 / vvishwan 08/25/99 - Add error message for -23480 / liwong 08/25/99 - Add 23481 / swerthei 08/04/99 - add 19710 / pmitra 08/11/99 - change OCINumberInit with OCINumberSetZero / skrishna 08/02/99 - mark 24040 as NLS DO NOT TRANSLATE / gtarora 07/16/99 - Add 22295 / rxgovind 06/25/99 - add 22825 - Event for imp/exp of opaque types / mluong 06/24/99 - fix merge / kmeiyyap 05/28/99 - adding 24084 - dblink length check / jwlee 06/10/99 - add error 19736 / qyu 04/14/99 - add 22997 / dbeusee 04/07/99 - bug-864173 / rshaikh 04/02/99 - add ora-19400 / ryaseen 03/12/99 - add 24083 / mimoy 03/02/99 - Eliminate 23390 and 23391 / vnimani 03/26/99 - add event 22822 / smuralid 02/15/99 - add event 22821 - turn off common subexpression elimin / mimoy 01/06/99 - Add error message 23478 / mimoy 12/28/98 - Modify error message 23374 / hasun 12/21/98 - Modify ERROR#23380; Add ERROR#23477 / hasun 12/12/98 - Modify ERROR#13324 / liwong 12/09/98 - Support multiple grps at same snap site / nbhatt 11/25/98 - error message for alter_queue_table / mrhodes 11/24/98 - adding error msg 24080 / kmuthiah 11/18/98 - changed 22894 and 22899 / wesmith 11/03/98 - Add 23476 for exp/imp of RepAPI snapshots / whe 10/30/98 - add message 21614,21615 / swerthei 10/28/98 - noarchivelog -> NOARCHIVELOG in 19573 / npopovic 10/20/98 - nbhatt:add message for Alter_queue_table / mkamath 10/20/98 - add 24076, 24077 / ato 10/20/98 - add 24023, 24024 / swerthei 10/20/98 - add message for bug 719176 enqueue conflict / schandra 10/03/98 - add 24075 for non-NULL protocol with NULL address / schandra 09/22/98 - 24038 - RETRY_DELAY and MAX_RETRIES work for 8.1 multi / mkamath 10/21/98 - modifying 24076 / mkamath 10/18/98 - Adding msgs 24076 and 24077 / ktarkhan 10/23/98 - add 22621 / liwong 09/25/98 - Add 23475 / qyu 09/14/98 - delete 22931, duplicate of 22912 / sbalaram 09/04/98 - fix 23417 - %d -> %s / ato 09/01/98 - change 24071 / ryaseen 09/04/98 - add 24075 / hasun 08/20/98 - Add 23474 for unsupported schema evolution in replicat / rpark 08/20/98 - change NEXT extent check error from 22995 to 22996 / rpark 08/20/98 - add 22995 / ryaseen 08/26/98 - update 24019 / schandra 08/14/98 - disallow retention for exception queues / kmuthiah 08/11/98 - move 22879 to 30726 / araghava 07/10/98 - Add 22879, 22995 / varora 07/17/98 - change 22818 error message / liwong 07/24/98 - Add 23473 / smuralid 06/23/98 - add 22932 / kmuthiah 06/22/98 - add 22879 / ato 06/15/98 - add 24072 / ryaseen 06/19/98 - add 24144 / nmallava 06/09/98 - add new messages / ryaseen 06/08/98 - Add 24071 / schandra 06/05/98 - queue table upgrade/downgrade / nmallava 06/09/98 - change error message for temp lobs / kmuthiah 05/28/98 - change 22979 / ryaseen 05/28/98 - Add misc 8.1 AQ and RE error msgs / qyu 05/28/98 - add 22931 / liwong 05/28/98 - modify error 23457 / hasun 05/28/98 - Add ERROR#23472 / ato 05/12/98 - update 24016 / hasun 05/28/98 - Add ERROR#23472 / celsbern 05/06/98 - Added messages for templates and reassigned used numbe / skrishna 05/13/98 - add 22919: dangling REF or lock err / ato 05/05/98 - add AQ grant/revoke errors / thoang 05/05/98 - Add new msg for VARRAY storage clause / jwlee 05/18/98 - change error 19728 / swerthei 03/26/98 - new messages for SBT 2.0 conversion / lcprice 05/06/98 - errors for DBMS_REPAIR package / ryaseen 05/04/98 - Modify 24033 and 24057 / jstamos 04/27/98 - revise 23455 / fsanchez 04/08/98 - Duplexed backup sets / mkamath 04/30/98 - Adding Error Messages 24064 and 24065 / schandra 03/02/98 - create variant of 24043 / schandra 02/15/98 - add error mesg 24048 / jwlee 05/01/98 - add error 19733 / jwlee 04/27/98 - error 19732 / jwlee 04/11/98 - plugged file media recovery errors / jwlee 04/05/98 - error 19726 / jwlee 03/27/98 - add error 19723 / swerthei 03/26/98 - new messages for SBT 2.0 conversion / jwlee 03/18/98 - more Transportable Tablespace errors / jwlee 03/18/98 - Transporatble/Pluggable Tablespace errors / schandra 03/26/98 - add error messages for attempt to propagate to Oracle / akruglik 04/20/98 - incorporate Randy's comments / ryaseen 04/27/98 - rules engine / ryaseen 04/12/98 - add ; subscriber table import error / rkasamse 04/29/98 - error message s for pickler cart services / tanguyen 04/08/98 - fix 22307 message / rxgovind 04/07/98 - add error messages for ROWTYPE and ROWSET / varora 04/06/98 - add errors for value subquery / araghava 04/14/98 - Partitioned Lobs. / jstamos 04/02/98 - generalize 23316 / ademers 03/28/98 - flavor support / ryaseen 03/31/98 - add error msg 24057 / celsbern 03/30/98 - Added error messages for refresh group templates. / kmuthiah 03/30/98 - additional mesgs for user-defined refs / mluong 03/30/98 - fix comp error / schandra 03/26/98 - add error messages for attempt to propagate to Oracle / emagrath 04/07/98 - / schandra 03/12/98 - add 24051: cant propagate if payload has REF or BFILE / ato 03/12/98 - add 24005, 24008 / lcprice 03/06/98 - reserve error number range for dbms_repair / kmuthiah 03/20/98 - add error msgs to supp usr-defn oids and refs / lcprice 03/06/98 - reserve error number range for dbms_repair / liwong 02/25/98 - flavor support / nbhatt 02/23/98 - add message for alter_queue_table / schandra 02/21/98 - add error message for new procedures / jstamos 02/19/98 - replicated flavor support / nramakri 01/29/98 - add new error / nmallava 02/10/98 - add/change messages for LOBs open/close / sagrawal 01/23/98 - Changing message 22871 / sagrawal 01/20/98 - alter replace incomplete type error / sagrawal 01/23/98 - / rkasamse 01/20/98 - add error messages for cartridge services / ssamu 01/16/98 - reserve cartridge service errors / mkrishna 01/08/98 - add error 22980 / tanguyen 01/05/98 - add 22304 / jingliu 12/04/97 - add error 23428 / sthakur 09/19/97 - add error 21606 / tpystyne 09/02/97 - add 19666, 19667 and 19668 / hasun 08/28/97 - Make error#23364 consistent with error#439 / schandra 08/22/97 - improve error messages / arsaxena 08/12/97 - add error messages for AQ propagation / jweisz 08/07/97 - [497514] add 21526 / nbhatt 07/31/97 - add namelength as a parameter to 24019 / skrishna 07/14/97 - add 21603 / sthakur 07/14/97 - add 21523 - functionality not supported by server / jingliu 07/08/97 - change err-msg 23399 / jingliu 07/02/97 - add sname to error message 23399 / mluong 06/24/97 - merge from 803 / rpark 06/23/97 - add 22994 for lob copies / hasun 05/21/97 - Add error #23435 / anolan 05/21/97 - checkout / anolan 05/14/97 - Demo. / sthakur 05/07/97 - add 22700 for object access tracing / ato 05/05/97 - add AQ export iot error message / schandra 05/05/97 - identifier length > 24 characters / schandra 05/01/97 - Bug# 486481: add error message for schema mismatch / skotsovo 05/01/97 - modify 22993 / skotsovo 04/30/97 - update message 22993 / swerthei 04/11/97 - add 19664, 19665 / nbhatt 04/28/97 - add message for retry delay / jwijaya 04/24/97 - add error 22600 / skotsovo 04/23/97 - make lob messages more user friendly / ramkrish 04/21/97 - Chg 22276, add 22282 / ramkrish 04/18/97 - Chg 22276, add more LBS messages / jdraaije 04/18/97 - Add 24279: insufficient privs to create lib / nbhatt 04/21/97 - final update / nbhatt 04/16/97 - fix error messages in AQ administrative interface / bgoyal 04/16/97 - unsupported feature for returning-clause / skotsovo 04/16/97 - add 22281 for lob buffering / bgoyal 04/16/97 - unsupported feature for returning-clause / schandra 04/15/97 - obsolete 24004 and 24006 / skotsovo 04/14/97 - modify error 22993 / smuralid 04/07/97 - add event 22815 for weak name resolution / mchien 04/04/97 - add to ORA-22285, 22286 / jdraaije 04/03/97 - Cleanup errors generated from dbms_hs / gpongrac 04/01/97 - add error for krbiaor failure / skotsovo 04/01/97 - modify 22993 / ato 03/31/97 - add AQ error message for raw type queue support / skotsovo 03/31/97 - added 22993 / tanguyen 03/27/97 - add 22870 / schandra 03/25/97 - support grouping by transaction / ramkrish 03/24/97 - Move 22280 to 22288. Add more LBS errs 22280-22284 / skotsovo 03/18/97 - add lob buffering errors / nbhatt 03/31/97 - update aq error messages / skrishna 03/17/97 - add 22140 / ktarkhan 02/28/97 - add DBMS_HO 24277 security violation error / skotsovo 02/24/97 - add 22280 for bfiles / schandra 02/18/97 - multiple dequeues / schandra 02/18/97 - multiple dequeues / liwong 02/12/97 - Add 23426, 23427 / masubram 02/11/97 - Add error messages 23424 and 23425 / swerthei 02/05/97 - enhance message 19600 / swerthei 01/27/97 - add 19660, 19661, 19662 / skotsovo 01/03/97 - add lob error 22275. / usundara 12/31/96 - incomplete and mutually-dependent types: / o remove ora-22308 (now done in plsql; see pls-565) / o remove ora-22867 (this is now ora-04055) / bcchang 12/20/96 - error.msg split / 19400, 00000, "System type conflict with object SYS.%s" // *Cause: The user had an object with the same name as one of the system // types. The system types were not initialized properly. // *Action: Remove the conflicting object and rerun migration. 19500, 00000, "device block size %s is invalid" // *Cause: the device block size returned by sequential I/O OSD is invalid // *Action: If the block size was set by using the PARMS option of the // Recovery Manager ALLOCATE CHANNEL command, then the specified // block size must be changed. If no PARMS option was specified on // the ALLOCATE CHANNEL command, then this is an internal error that // should be reported to Oracle. 19501, 00000, "read error on file \"%s\", blockno %s (blocksize=%s)" // *Cause: read error on input file // *Action: check the file 19502, 00000, "write error on file \"%s\", blockno %s (blocksize=%s)" // *Cause: write error on output file // *Action: check the file 19503, 00000, "cannot obtain information on device, name=\"%s\", type=\"%s\", parms=\"%s\"" // *Cause: call to get device information returned an error // *Action: check device name, type and parameters 19504, 00000, "failed to create file \"%s\"" // *Cause: call to create file returned an error // *Action: check additional messages, check access permissions 19505, 00000, "failed to identify file \"%s\"" // *Cause: call to identify the file returned an error // *Action: check additional messages, and check if the file exists 19506, 00000, "failed to create sequential file, name=\"%s\", parms=\"%s\"" // *Cause: call to create the sequential file returned an error // *Action: check additional messages, check access permissions 19507, 00000, "failed to retrieve sequential file, handle=\"%s\", parms=\"%s\"" // *Cause: call to retrieve the sequential file returned an error // *Action: check additional messages, and check if the file exists 19508, 00000, "failed to delete file \"%s\"" // *Cause: call to delete the file returned an error // *Action: check additional messages 19509, 00000, "failed to delete sequential file, handle=\"%s\", parms=\"%s\"" // *Cause: call to delete the sequential file returned an error // *Action: check additional messages 19510, 00000, "failed to set size of %s blocks for file \"%s\" (blocksize=%s)" // *Cause: call to resize the file returned an error // *Action: check additional messages 19511, 00000, "Error received from media manager layer, error text:\n %s" // *Cause: An error occurred in the media management software which // is linked with the Oracle server to perform backup and restore // in cooperation with Recovery Manager. // *Action: If the text of message 19511 does not provide enough // information to resolve the problem, then you should contact the // vendor of the media management software. 19550, 00000, "cannot use backup/restore functions while using dispatcher" // *Cause: Attempted to use backup/restore functions while connected to the // dispatcher in a shared server. // This is not allowed because the device that is // used for backup and restore must remain allocated to a single // process. // *Action: Connect directly to the instance then re-execute the backup or // restore function. 19551, 00000, "device is busy, device type: %s, device name: %s" // *Cause: The indicated device could not be allocated because it is // allocated to another session, or no device was named, or all // devices of the requested type are busy. // *Action: Either attempt to allocate another device or wait until the // required device is no longer busy. 19552, 00000, "device type %s is invalid" // *Cause: The device type indicated is invalid. // *Action: Supply a correct device type and retry the allocation. 19553, 00000, "device name %s is invalid" // *Cause: The device name indicated is invalid. // *Action: Supply a correct device name and retry the allocation. 19554, 00000, "error allocating device, device type: %s, device name: %s" // *Cause: The specified device could not be allocated. // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error and retry the // allocation. 19555, 00000, "invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value" // *Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set // within the valid range. // *Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. // If the archive log parameters LOG_ARCHIVE_DEST or // LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter // LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2. 19556, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred" // *Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred // when it was required to be enabled. The destination was // deferred automatically when an ALTER SYSTEM command for parameter // LOG_ARCHIVE_DEST defined a destination which duplicated an existing // LOG_ARCHIVE_DUPLEX_DEST parameter destination. // *Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST // parameter. 19557, 00000, "device error, device type: %s, device name: %s" // *Cause: An error occurred in the platform-specific device code // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error and retry the // allocation. 19558, 00000, "error de-allocating device" // *Cause: The specified device could not be de-allocated. // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error and retry the // allocation. 19559, 00000, "error sending device command: %s" // *Cause: An error occurred while sending the indicated command to the // session device. // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error and retry the // allocation. 19560, 00000, "%s is not a valid device limit" // *Cause: An invalid type of device limit was specified in a call to // x$dbms_backup_restore.setlimit. // *Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL. 19561, 00000, "%s requires a DISK channel" // *Cause: The attempted command requires that a DISK device channel be // allocated to the session, but a non-DISK device was found. // *Action: Deallocate the current device and allocate a DISK channel, then // then retry the command. 19562, 00000, "file %s is empty" // *Cause: The indicated file, which is an archivelog, controlfile, or // datafile was found to be empty during a copy, backup, or scan] // operation. // *Action: Ensure that the correct files are being specified for the copy // or backup operation. 19563, 00000, "%s header validation failed for file %s" // *Cause: When opening the file to be placed in a copy or backup set, // to be inspected, or used as the target for // an incremental restore, the header was not // recognized as a valid file header for a file of the indicated // type (data file, archived log, or control file), belonging // to the current database. // *Action: Ensure that the correct files are being specified for the copy // or backup operation. 19564, 00000, "error occurred writing %s bytes at block number %s" // *Cause: An error occurred while writing to a file. // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error if possible, then retry // the copy, backup, or restore operation. 19565, 00000, "BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices" // *Cause: An attempt was made to specify duplexing to sequential devices, // but the BACKUP_TAPE_IO_SLAVES initialization parameter was not // enabled. // *Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, // or do not specify duplexing to sequential devices. 19566, 00000, "exceeded limit of %s corrupt blocks for file %s" // *Cause: The user specified limit of allowable corrupt blocks was exceeded // while reading the specified datafile for a datafile copy or backup. // *Action: None. The copy or backup operation fails. // The session trace file contains detailed information // about which blocks were corrupt. 19567, 00000, "cannot shrink file %s because it is being backed up or copied" // *Cause: An ALTER statement attempted to reduce the size of the indicated // file while the same file is being backed up or copied. // *Action: Retry the resize after the backup or copy is complete. 19568, 00000, "a device is already allocated to this session" // *Cause: A device cannot be allocated to a session if another device is // already allocated. // *Action: Deallocate the current device 19569, 00000, "no device is allocated to this session" // *Cause: An operation was attempted which requires a device to be allocated // to the current session, and there is no device allocated. // *Action: Allocate a device then retry the operation. 19570, 00000, "file number %s is outside valid range of 1 through %s" // *Cause: A file number used in a copy, backup, or restore operation is not // valid for the current database. // *Action: Specify a valid file number. 19571, 00000, "%s recid %s stamp %s not found in controlfile" // *Cause: The input file specified for a copy or backup operation could // not be opened because the record describing the file is not found // in the controlfile. // *Action: Specify a correct recid/stamp and retry the copy or backup. 19572, 00000, "cannot process file %s, file is being being resized" // *Cause: The input file specified for a copy or backup operation could // not be opened because the file is being resized. // *Action: Wait for the resize to complete then retry the copy or backup. 19573, 00000, "cannot obtain %s enqueue for datafile %s" // *Cause: The file access enqueue could not be obtained for a file // specified in a backup, copy or restore operation. // If the enqueue type shown is 'shared', then the file is the // input file for a backup or copy. If the type is 'exclusive', then // the file is the output file for a datafile copy or restore which // is attempting to overwrite the currently active version of that // file - in this case, the file must be offline or the database must // be closed. If the type is 'read-only', then you are attempting // to back up or copy this file while the database is in NOARCHIVELOG // mode. // *Action: Wait until the conflicting operation is complete, then retry // the copy or backup. If the database is in NOARCHIVELOG mode, then // all files being backed up must be closed cleanly. 19574, 00000, "output filename must be specified" // *Cause: This type of copy or restore requires an output file name. // *Action: Specify an output filename and retry the copy. 19575, 00000, "expected %s blocks in file %s, found %s" // *Cause: During a backup, restore, copy, or scan operation, the indicated // file did not contain as many blocks as were indicated in the file // header. // *Action: The input copy or backup piece is probably corrupt. If another // backup or copy exists of the file that is being restored, then the // corrupt file can be deleted from the recovery catalog and the // operation can be restarted. 19576, 00000, "datafile %s not defined in control file" // *Cause: The specified file number was not found in the control file. // *Action: Specify a correct file number and retry the operation. 19577, 00000, "file %s is MISSING" // *Cause: A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile // function specified a file // number but no output file name, indicating that the output filename // should be taken from the controlfile. However, the controlfile // entry for this file indicates that it was created for a file that // was present in the data dictionary but not named during the last // CREATE CONTROLFILE statement, so the name in the controlfile cannot // be used for restoration. // *Action: Either specify an output filename or issue a SQL RENAME command // to enter a valid name for this file in the controlfile. 19578, 00000, "end of volume while duplexing to sequential files, backup piece incomplete" // *Cause: An end of volume (EOV) condition was detected while duplexing to // sequential files, and this condition cannot be handled currently. // *Action: Before retrying the backup, make sure the backup pieces will fit in // the volume, or disable duplexing. 19579, 00000, "archivelog record for %s not found" // *Cause: No archived log record corresponding to input file could be // found in the controlfile. // *Action: Specify a valid archivelog file name and retry the operation. 19580, 00000, "%s conversation not active" // *Cause: A backup or restore operation was attempted before a conversation // was started. // *Action: Start a conversation then retry the operation. 19581, 00000, "no files have been named" // *Cause: An attempt was made to proceed from the file naming phase to the // piece processing phase of a backup or restore conversation // before any files have been specified for backup or restore. // *Action: Specify some files then retry the operation. 19582, 00000, "archivelog file header validation for %s failed" // *Cause: Archived log file header is corrupt and could not be validated. // *Action: Provide a valid archivelog file and retry the operation. 19583, 00000, "conversation terminated due to error" // *Cause: An error occurred which forced the termination of the current // backup or restore conversation. // *Action: There should be other error messages to help identify the cause // of the problem. Correct the error and begin another conversation. 19584, 00000, "file %s already in use" // *Cause: The indicated file, which was specified as the target for a copy, // restore, or delete operation is already in use by the database. // *Action: Specify a different name and retry the operation. 19585, 00000, "premature end of volume on piece %s" // *Cause: While creating the indicated backup piece, an end-of-volume // condition was encountered before all of the backup set control // data was written to the backup piece. This is most likely a media // error, because the amount of backup set control data is very small // in relation to the total amount of data in a backup set. // *Action: Retry the piece with a larger piece of output media. 19586, 00000, "%s k-byte limit is too small to hold piece directory" // *Cause: The user-specified limit of k-bytes per backup piece is not enough // to hold the backup set control data. // *Action: Use the setLimit procedure to increase the k-byte limit and // retry the operation. 19587, 00000, "error occurred reading %s bytes at block number %s" // *Cause: An error occurred while reading from a file. // *Action: One or more other messages should be displayed to help pinpoint // the cause of the error. Correct the error then retry the // copy, backup, or restore operation. 19588, 00000, "%s recid %s stamp %s is no longer valid" // *Cause: The indicated record has been marked as deleted. // This indicates that the corresponding file has either been // overwritten by another copy or restore, or that the copy was // 'consumed' by a switchToCopy operation. // *Action: If you know the name of the file you wish to copy, then // inspect it and then retry the copy specifying the new recid. 19589, 00000, "%s is not a snapshot or backup controlfile" // *Cause: The controlfile that is the source for a backup or copy operation // is not a snapshot or backup controlfile. // *Action: Specify the name of a snapshot or backup controlfile. 19590, 00000, "conversation already active" // *Cause: You tried to begin a backup or restore conversation, but another // conversation is already active in this session. // *Action: Either continue the current conversation, or call backupCancel or // restoreCancel to end the current conversation before starting a // new one. /19591, 00000, "unused" 19592, 00000, "wrong %s conversation type" // *Cause: You attempted to specify a type of file to be backed-up or // restored, but the current conversation cannot process this type // of file. For example, you specified an archived log to be // included in a datafile backup set. The specified file will // not be included in the backup or restore operation. // *Action: No action required - the conversation is still active, and // more files can be specified. 19593, 00000, "datafile number %s already included as %s" // *Cause: This datafile is already specified for inclusion in this backup or // restore conversation. // A backup or restore conversation may process only // a single instance of a datafile. // *Action: No action required - the conversation is still active, and // more files can be specified. 19594, 00000, "controlfile already included as %s" // *Cause: The controlfile is already specified for inclusion in this backup // or restore conversation. A backup or restore conversation may // process only a single instance of the controlfile. // *Action: No action required - the conversation is still active, and // more files can be specified. 19595, 00000, "archivelog %s already included in backup conversation" // *Cause: The indicated archivelog has already been specified for inclusion // in this backup conversation. // *Action: No action required - the conversation is still active, and // more files can be specified. 19596, 00000, "snapshot controlfile has not been created" // *Cause: You requested that the snapshot controlfile be included in the // backup set, but no snapshot controlfile has been created for // this instance. // *Action: Specify a different controlfile name, or call // cfileMakeAndUseSnapshot to create the snapshot controlfile. 19597, 00000, "file %s blocksize %s does not match set blocksize of %s" // *Cause: A file was specified for inclusion in a backup set but it has // a logical block size different from the rest of the files in the // backup set. All files in a backup set must have the same logical // block size. // *Action: Specify a file that has the same block size as the rest of the // files in the backup set. The conversation is still active and // more files can be specified. 19598, 00000, "starting SCN must be specified for incremental backup" // *Cause: No starting SCN was specified to backupDataFile or // backupDataFileCopy, but the current backup conversation is for // an incremental backup, which requires that a non-zero // SCN be specified for all datafiles. // *Action: The conversation is still active. Re-specify the datafile with a // non-zero SCN. 19599, 00000, "block number %s is corrupt in %s %s" // *Cause: A corrupt block was found in a controlfile, archivelog, or // backup piece that // is being read for a backup or copy. Corruption shall not be // tolerated in controlfiles, archivelogs, or backup pieces. // *Action: None. The copy or backup operation fails. Note that in the case of // a backup set, the conversation is still active and the piece may // be retried. 19600, 00000, "input file is %s %s (%s)" // *Cause: This message identifies the input file for a failed copy operation. // Both the file number and name (if the name has been determined) // are shown. For a datafile, the file number refers to the // datafile's absolute file number as shown in the DBA_DATA_FILES // view. // For a datafile-copy, the file number refers to the copy's // controlfile record number as shown in the RECID column of the // V$DATAFILE_COPY view. // For an archived log, the file number refers to the log's // controlfile record number as shown in the RECID column of the // V$ARCHIVED_LOG view. // *Action: See other error message. 19601, 00000, "output file is %s %s (%s)" // *Cause: This message identifies the output file for a failed copy // operation. The fields are as described in message 19600. When // creating a new datafile copy, its controlfile record number may not // have been determined when the message is printed. In that case, // the record number shown is zero. // *Action: See other error message. 19602, 00000, "cannot backup or copy active file in NOARCHIVELOG mode" // *Cause: You tried to copy or backup a file that was not closed cleanly, // and the database was in NOARCHIVELOG mode. This is not allowed // because when restored, the file will require redo application // before it is usable, and redo is not currently being saved // beyond the contents of the online redo logs. // *Action: Take the tablespace offline clean or close the database and retry // the copy or backup. 19603, 00000, "cannot backup or copy active file with KEEP .. UNRECOVERABLE option" // *Cause: The user tried to copy or backup a file that was not closed cleanly, // with KEEP .. UNRECOVERABLE option. This is not allowed // because when restored, the file will require redo application // before it is usable, and redo will not be saved because of // KEEP .. UNRECOVEARABLE option. // *Action: Take the tablespace offline cleanly, or close the database and retry // the copy or backup. 19604, 00000, "conversation file naming phase is over" // *Cause: A call was made to specify a file to be backed up or restored after // the first backup piece has been processed. // *Action: You cannot specify more files to be processed during a backup or // restore conversation after the first backup piece has been // processed. If more files must be specified, you must begin // a new conversation. 19605, 00000, "input filename must be specified" // *Cause: The input file name was not specified for a controlfile copy // operation. // *Action: Specify an input file name and retry the operation. 19606, 00000, "Cannot copy or restore to snapshot controlfile" // *Cause: A controlfile copy or restore operation specified the name of the // snapshot controlfile as the output file. It is not permitted to // overwrite the snapshot controlfile in this manner. Other // methods are available to create the snapshot controlfile. // *Action: Specify a different file name and retry the operation. If this // is a restore, then the restore conversation remains active and // more files may be specified. 19607, 00000, "%s is an active controlfile" // *Cause: A controlfile copy, restore, or backup specified the name of a // controlfile named in the INIT.ORA file as the input or output file. // *Action: Specify a different file name and retry the operation. If this // is a backup or restore conversation, then the conversation remains // active and more files may be specified. 19608, 00000, "%s is not a backup piece" // *Cause: The specified file is not a backup piece produced by the // dbms_backup_restore package. Either the first block of the // backup piece is corrupt or this file is not a backup piece. // *Action: Specify a different file name and retry the operation. 19609, 00000, "%s is from different backup set: stamp %s count %s" // *Cause: The specified file is not from the backup set which is // currently being processed. It is part of a different backup set. // The identification of the set containing this piece is shown. // *Action: Specify the correct backup piece and retry the operation. 19610, 00000, "directory block %s is corrupt" // *Cause: The indicated directory block failed checksum validation. // This backup piece is unusable. // *Action: Supply another copy of the same backup piece, or terminate the // restore conversation. 19611, 00000, "backup piece out of order. Expected %s but found %s" // *Cause: This backup piece is out of sequence. // *Action: Supply the correct backup piece. 19612, 00000, "datafile %s not restored due to %s" // *Cause: The indicated file could not be restored, because all of its data // blocks were not found in the backup piece. // *Action: The restore conversation remains active, and the current piece // must be re-processed. If the failure cannot be resolved by // re-processing the current piece, then the restore conversation // must be cancelled. 19613, 00000, "datafile %s not found in backup set" // *Cause: The indicated file could not be restored, because it is not in // this backup set. If the file number is zero, then this refers to // the controlfile. // *Action: This message is issued when the directory from the first backup // piece is read and one or more files named for restoration were not // found. The restore conversation is still active, but no data // has been read and you must supply the first backup piece of // a backup set that contains all of the requested files. 19614, 00000, "archivelog thread %s sequence %s not found in backup set" // *Cause: The indicated archived log file was named explicitely for // restoration but is not contained in this backup set. // *Action: This message is issued when the directory from the first backup // piece is read and one or more files named for restoration were not // found. The restore conversation is still active, but no data // has been read and you must supply the first backup piece of // a backup set that contains all of the requested files. 19615, 00000, "some files not found in backup set" // *Cause: Some files that were specified for restoration were not found // in the backup set directory. Message 19613 or 19614 is issued // for each unfound file. // *Action: See the instructions for message 19613. 19616, 00000, "output filename must be specified if database not mounted" // *Cause: A datafile restore specified no target filename, but the // database is not mounted. The database must be mounted when no // target filename is specified, so that the target filename // can be obtained from the controlfile. // *Action: The restore conversation remains active. If you wish to restore // datafiles without their target filenames, then mount the datbase // before continuing. Otherwise, a target filename must be specified // on all datafile restoration calls. 19617, 00000, "file %s contains different resetlogs data" // *Cause: The indicated file contains resetlogs data which is different from // the archived log files which are already included in the backup // set. All archived log files in a backup set must have the same // resetlogs data. // *Action: The restore conversation remains active, and you may continue to // specify archived log files for inclusion in the backup set. 19618, 00000, "cannot name files after restoreValidate has been called" // *Cause: A call was made to specify a file to restore from a backup set, // but a previous call to restoreValidate has already been made. // *Action: You must cancel and restart the conversation if you wish to // specify files to restore. 19619, 00000, "cannot call restoreValidate after files have been named" // *Cause: restoreValidate was called after some files had already been // specified for restoration. // *Action: You must cancel and restart the conversation if you wish to // call restoreValidate. / 19620, 00000, "archive log destination %s exceeds maximum length of %s" / // *Cause: You specified an archive log destination for restoreSetRedoLog / // which exceeds the system maximum. / // *Action: Retry the operation with a shorter archive log destination. 19621, 00000, "archivelog range has already been specified" // *Cause: A range of logs has already been specified. Only one SCN range // may be specified per conversation. // *Action: The restore conversation remains active and more logs may be // specified by thread and sequence number, if desired. 19622, 00000, "archivelog thread %s sequence %s not restored due to %s" // *Cause: The indicated file could not be restored, because all of its data // blocks were not found in the backup piece. // *Action: The restore conversation remains active, and the current piece // must be re-processed. If the failure cannot be resolved by // re-processing the current piece, then the restore conversation // must be cancelled. 19623, 00000, "file %s is open" // *Cause: A SwitchToCopy operation specified a datafile copy whose parent // datafile is open. // *Action: Take the owning tablespace offline or close the database, then // retry the operation. 19624, 00000, "operation failed, retry possible" // *Cause: A backup, restore or image copy operation failed with an I/O // error. If the source of the I/O error can be corrected, then // the operation may be retried. // *Action: This message is used by recovery manager to decide whether or not // to retry the operation. 19625, 00000, "error identifying file %s" // *Cause: A file specified as input to a copy or backup operation, or as // the target for an incremental restore, could not be identified as // an Oracle file. An OS-specific error accompanies this error to // help pinpoint the problem. // *Action: Specify an different file and retry the operation. 19626, 00000, "backup set type is %s - can not be processed by this conversation" // *Cause: The data in the backup set is not compatible with the current // conversation. // *Action: Either supply the first piece from a backup set that matches // the current conversation or start a new restore conversation which // can process this backup set. 19627, 00000, "cannot read backup pieces during controlfile application" // *Cause: This is a controlfile restore conversation, which is using the // offline range information from one or more controlfiles to update // datafile checkpoint data. Backup sets are not used during this // type of conversation. // *Action: The conversation is still active and more controlfiles may be // applied. 19628, 00000, "invalid SCN range" // *Cause: The starting SCN for restoreRedoLogRange is greater than the // ending SCN. // *Action: Specify a starting SCN which is less than or equal to the // ending SCN. 19629, 00000, "no files in specified archivelog SCN range" // *Cause: This backup set contains no files in the specified range. // *Action: Either supply a backup set that contains files in the correct // range or start a new conversation and specify a range which will // select some files from this backup set. 19630, 00000, "end of volume encountered while copying backup piece" // *Cause: While copying a backup piece from the OS native filesystem to an // output device, the output device encountered end-of-volume. // *Action: The copy fails. This could happen if a tape was used which is // not large enough to hold the entire backup piece. 19631, 00000, "archivelog record contains no file name" // *Cause: This archivelog record represents a switch into an active log // that took place without archiving its prior contents. The prior // contents of the log file are lost. // *Action: Specify the recid of an archivelog record that contains a file // name. Fixed view v$archived_log can be used to examine the // archived logs. 19632, 00000, "file name not found in controlfile" // *Cause: The name passed to getFno was not found in the controlfile. // *Action: Supply a valid filename. 19633, 00000, "controlfile record %s is out of sync with recovery catalog" // *Cause: The controlfile record describing the file to be deleted in // a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete or // deleteArchivedLog does not match the validation data supplied by // recovery manager. // *Action: contact Oracle support 19634, 00000, "filename required for this function" // *Cause: The fname or handle parameter was not specified for // deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete. // *Action: Specify the fname or handle parameter when calling these functions. 19635, 00000, "input and output filenames are identical" // *Cause: Identical input and output file names were specified for a // datafile copy operation. // *Action: Specify an output file name which is different from the input // file name. 19636, 00000, "archivelog thread %s sequence %s already included" // *Cause: The indicated archivelog has already been specified for inclusion // in this restore conversation. A restore conversation may process // only one copy of any archivelog. // *Action: No action required - the conversation is still active, and // more files can be specified. 19637, 00000, "backupPieceCreate requires file name when using DISK device" // *Cause: The session device is currently allocated to disk, and so a file // name is required. // *Action: Supply a filename and retry the operation. 19638, 00000, "file %s is not current enough to apply this incremental backup" // *Cause: The checkpoint of the target for this incremental backup // is less than the start of the incremental backup. If this backup // were applied, then any changes made between the datafile checkpoint // and the start of the incremental backup could be lost. // *Action: Supply a backup set that can be applied and retry the operation. 19639, 00000, "file %s is more current than this incremental backup" // *Cause: The checkpoint of the target for this incremental backup is // greater than or equal to the checkpoint of the file in the // incremental backup set. This backup cannot advance the checkpoint // of the target file, so there is no point in applying it. // *Action: Supply a backup set that can be applied and retry the operation. 19640, 00000, "datafile checkpoint is SCN %s time %s" // *Cause: This message identifies the datafile checkpoint for // a datafile that was too old to take an incremental backup from, or // the target of an incremental restore that could not be applied. // *Action: See other error message. 19641, 00000, "backup datafile checkpoint is SCN %s time %s" // *Cause: This message identifies the checkpoint of a datafile in an // incremental backup set that could not be applied. // *Action: See other error message. 19642, 00000, "incremental-start SCN is %s" // *Cause: This message identifies the starting SCN // of an incremental backup that could not be applied. // *Action: See other error message. 19643, 00000, "datafile %s: incremental-start SCN is too recent" // *Cause: The incremental-start SCN which was specified when starting an // incremental datafile backup is greater than the datafile // checkpoint SCN, which could cause some blocks to be missed. // *Action: Specify a smaller incremental-start SCN. 19644, 00000, "datafile %s: incremental-start SCN is prior to resetlogs SCN %s" // *Cause: The incremental-start SCN which was specified when starting an // incremental datafile backup is less than the resetlogs SCN. // *Action: Specify a larger incremental-start SCN. 19645, 00000, "datafile %s: incremental-start SCN is prior to creation SCN %s" // *Cause: The incremental-start SCN which was specified when starting an // incremental datafile backup is less than the datafile's // creation SCN. // *Action: Specify a larger incremental-start SCN. 19646, 00000, "cannot change size of datafile %s from %s to %s" // *Cause: The indicated file was resized before this incremental backup was // taken, but the incremental backup failed to set the file to the // new size. // *Action: Examine the other messages which should be present to indicate // the cause of the failure. 19647, 00000, "non-zero LEVEL cannot be specified when INCREMENTAL is FALSE" // *Cause: BackupSetDataFile was called with a non-zero backup_level // and a FALSE incremental indication. // *Action: Either set incremental to TRUE or change backup_level to zero. 19648, 00000, "datafile %s: incremental-start SCN equals checkpoint SCN" // *Cause: The incremental-start SCN which was specified when starting an // incremental datafile backup is equal to the // datafile's checkpoint SCN. Since an incremental backup can only // be applied to a datafile whose checkpoint SCN is between the // backup set incremental-start SCN (inclusive) and the backup set // checkpoint SCN (exclusive), there is no datafile that this backup // set could ever be applied to. // *Action: Specify a smaller incremental-start SCN. 19649, 00000, "offline-range record recid %s stamp %s not found in file %s" // *Cause: applyOfflineRange was called with a recid/stamp which was not // found in the indicated controlfile. This probably means that the // specified controlfile is no longer the same controlfile that // Recovery Manager thinks it is. // *Action: Specify the recid/stamp of a record that exists in the controlfile // copy. 19650, 00000, "Offline-range record recid %s stamp %s in file %s has SCN %s" // *Cause: This messages identifies the offline-clean SCN from the indicated // offline-range record in the indicated file. // *Action: See other error message. 19651, 00000, "cannot apply offline-range record to datafile %s: SCN mismatch" // *Cause: applyOfflineRange cannot apply an offline-range record to a // target datafile unless the datafile's checkpoint SCN exactly // matches the offline-clean SCN in the specified offline-range // record. // *Action: Specify an offline-range record whose offline-clean SCN matches // the target datafile's checkpoint. 19652, 00000, "cannot apply offline-range record to datafile %s: file is fuzzy" // *Cause: The target datafile for an applyOfflineRange call is fuzzy. // *Action: Specify a target datafile that is closed cleanly. 19653, 00000, "cannot switch to older file incarnation" // *Cause: SwitchToCopy was called with a datafile copy for a datafile that // was dropped prior to the time this controlfile was backed up. // *Action: Restore and mount an earlier controlfile. It is acceptable to use // a controlfile that was backed up prior to the creation of the // specified datafile. 19654, 00000, "must use backup controlfile to switch file incarnations" // *Cause: This switchToCopy operation is attempting to switch incarnations // of a datafile, but the currently mounted controlfile is not a // backup controlfile. // *Action: Restore and mount a backup controlfile. 19655, 00000, "cannot switch to incarnation with different resetlogs data" // *Cause: This switchToCopy operation is attempting to switch to a datafile // which comes from a different resetlogs version of the database. // *Action: Either restore a backup controlfile that was taken from the same // database version as the target datafile-copy, or switch to a // different datafile-copy. 19656, 00000, "cannot backup, copy, or delete online log %s" // *Cause: The indicated log file is an active log. You can only backup, // copy, or delete archived logs. // *Action: The indicated log file cannot be processed - select another file. 19657, 00000, "cannot inspect current datafile %s" // *Cause: The file being inspected is already part of the currently mounted // database. // *Action: None - the file is already part of the database. 19658, 00000, "cannot inspect %s - file is from different resetlogs" // *Cause: The resetlogs data in the log file being inspected does not match // that in the currently mounted controlfile. // *Action: The indicated file cannot be processed - inspect another file. 19659, 00000, "incremental restore would advance file %s past resetlogs" // *Cause: This incremental backup cannot be applied to the specified // datafile, because the datafile is from an earlier incarnation of // the database, and its checkpoint would be advanced too far to be // recoverable in the current incarnation of the database. // *Action: This incremental cannot be applied to this datafile. If you wish // to recover the file to the resetlogs SCN so that the database // can be opened with the RESETLOGS option, then you must use redo-log // recovery, not incremental restore, to continue recovering this // file. 19660, 00000, "some files in the backup set could not be verified" // *Cause: A restore conversation was made to verify all the files in a backup // set, and the files which were printed in messages 19661 or 19662 // could not be verified because corrupt blocks for those files were // found in the backup set. // *Action: Unless the damage to the backup set can be repaired, the indicated // files cannot be restored from this backup set. 19661, 00000, "datafile %s could not be verified" // *Cause: Some data blocks for the indicated datafile were corrupt in the // backup set. // *Action: Unless the damage to the backup set can be repaired, the indicated // datafile cannot be restored from this backup set. 19662, 00000, "archived log thread %s sequence %s could not be verified" // *Cause: Some data blocks for the indicated archived log were corrupt in the // backup set. // *Action: Unless the damage to the backup set can be repaired, the indicated // archived log cannot be restored from this backup set. 19663, 00000, "cannot apply current offline range to datafile %s" // *Cause: An attempt was made to apply the current offline range to // the specified datafile, but the datafile is either not current // enough or is not at the correct SCN to apply the offline range. // *Action: The datafile remains unchanged. 19664, 00000, "file type: %s, file name: %s" // *Cause: This message is issued to identify the file which is the subject // of an error. // *Action: None - this is an informational message. There should be other // Oracle messages explaining the cause of the error. 19665, 00000, "size %s in file header does not match actual file size of %s" // *Cause: The size of the file as indicated in the file header does not match // the true size of the file. // The two differing sizes are shown in units of logical blocks. // *Action: This file is not usable - it has most likely been truncated. 19666, 00000, "cannot do incremental restore of the controlfile" // *Cause: The controlfile was included in an incremental restore conversation // *Action: If you wish to restore the controlfile, you must do a full restore // of the controlfile 19667, 00000, "cannot do incremental restore of datafile %s" // *Cause: The backup of the datafile is a full backup // *Action: If you wish to restore the datafile, you must do a full restore // of the datafile 19668, 00000, "cannot do full restore of datafile %s" // *Cause: The backup of the datafile is an incremental backup // *Action: If you wish to restore the datafile, you must do an incremental // restore of the datafile 19669, 00000, "proxy copy functions cannot be run on DISK channel" // *Cause: A proxy copy procedure was called, // but the device which is allocated to the current session has // type DISK. // *Action: Allocate a non-DISK channel and retry the operation. Note that // proxy copy requires a 3rd-party media management software product // that supports the this backup/restore feature. 19670, 00000, "file %s already being restored" // *Cause: A proxy restore function has already named this file as a restore // destination. // *Action: Use a different file name. If this message occurs during a // recovery manager job, then this is an internal error in recovery // manager, and you should contact Oracle support. 19671, 00000, "media management software returned invalid proxy handle" // *Cause: During a proxy backup or restore, the media management software // returned an invalid file handle. // *Action: This is an internal error in the media management software which // is linked with Oracle to provide backup/restore services. // Contact the media management software vendor. 19672, 00000, "media management software returned invalid file status" // *Cause: During a proxy backup or restore, the media management software // returned an invalid file status. // *Action: This is an internal error in the media management software which // is linked with Oracle to provide backup/restore services. // Contact the media management software vendor. 19673, 00000, "error during proxy copy of file %s" // *Cause: During a proxy backup or restore, an error occurred while // copying this file, but other files may have been copied // successfully. // *Action: There should be other errors on the error stack which explain // why the file could not be successfully copied. 19674, 00000, "file %s is already being backed up with proxy copy" // *Cause: Recovery manager attempted to back up the specified file with // proxy copy, but the file is already being backed up by another // recovery manager job. // *Action: Wait until the other recovery manager backup of this file is // complete, then retry the backup. 19675, 00000, "file %s was modified during proxy copy" // *Cause: A proxy backup of the specified file failed because the file was // brought on-line or otherwise modified while the proxy backup was // in progress. This file was off-line or read-only when the backup // began, so the file was not put into hot-backup mode, therefore // no modifications are permitted while the backup is in progress. // *Action: Take another backup of this file. 19676, 00000, "one or more files failed during proxy backup or restore" // *Cause: During a proxy backup or restore, errors were encountered while // processing some files. The files for which no error messages are // shown were processed successfully. // *Action: Examine the messages regarding the specific files to determine // the cause of the problems. 19677, 00000, "RMAN configuration name exceeds maximum length of %s" // *Cause: The configuration name string exceeds maximum length. // *Action: Supply a correct configuration name and retry the function. 19678, 00000, "RMAN configuration value exceeds maximum length of %s" // *Cause: The configuration value string exceeds maximum length. // *Action: Supply a correct configuration value and retry the operation. 19679, 00000, "RMAN configuration number %s is outside valid range of 1 through %s" // *Cause: An invalid RMAN Configuration number was specified. // *Action: Specify a correct datafile number and retry the operation. 19680, 00000, "some blocks not recovered. See trace file for details" // *Cause: Some blocks are not recovered during block media recovery. // *Action: See trace files for details of the problem. 19681, 00000, "block media recovery on control file not possible" // *Cause: filenumber 0 specified in block media recovery // *Action: check filenumber 19682, 00000, "file %s not in block media recovery context" // *Cause: Internal error // *Action: 19683, 00000, "real and backup blocksize of file %s are unequal" // *Cause: block size changed between backup & real file // *Action: use right backup 19684, 00000, "block media recovery failed because database is suspended" // *Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement // *Action: Execute ALTER SYSTEM RESUME then retry block media recovery / / ************************************************************************** / * When adding new dbms_backup_restore messages, you must decide if the * / * error is 'retryable' or not, and if so, add the message number to * / * the table in krbrre. * / ************************************************************************** 19700, 00000, "device type exceeds maximum length of %s" // *Cause: The device type indicated is invalid. // *Action: Supply a correct device type and retry the allocation. 19701, 00000, "device name exceeds maximum length of %s" // *Cause: The device name indicated is invalid. // *Action: Supply a correct device name and retry the allocation. 19702, 00000, "device parameter exceeds maximum length of %s" / // *Cause: The device parameter exceeds the port-specific maximum length. / // *Action: Correct the parameter and retry the operation. 19703, 00000, "device command string exceeds maximum length of %s" // *Cause: The device command string exceeds maximum length. // *Action: Correct the command and retry the operation. 19704, 00000, "file name exceeds maximum length of %s" // *Cause: The specified file name, which was a parameter to a copy, backup, // or restore operation, exceeds the maximum file name length for // this operating system. // *Action: Retry the operation with a shorter file name. 19705, 00000, "tag value exceeds maximum length of %s characters" // *Cause: During a backup or copy operation, the user supplied a tag // value too long to fit in the file header. // *Action: Supply a shorter tag and retry the operation. 19706, 00000, "invalid SCN" // *Cause: The input SCN is either not a positive integer or too large. // *Action: Check the input SCN and make sure it is a valid SCN. 19707, 00000, "invalid record block number - %s " // *Cause: The input number is either negative or too large. // *Action: Check the input record block number and make sure it is a valid // number // clauses in the create database statement. 19708, 00000, "log destination exceeds maximum length of %s characters" // *Cause: When starting a restore conversation, the user specified a log // restore destination longer than the port-specific maximum. // *Action: Supply a shorter destination and retry the operation. 19709, 00000, "numeric parameter must be non-negative integer" // *Cause: A numeric parameter to an x$dbms_backup_restore procedure is // negative or contains a fractional portion. // *Action: Supply a valid numeric parameter. 19710, 00000, "unsupported character set %s" // *Cause: When the target database is not mounted, RMAN sets the target // database character set to the value specified in the users // environment. // *Action: Specify a valid character set in the environment. This is usually // done via the NLS_LANG environment variable. 19711, 00000, "cannot use reNormalizeAllFileNames while database is open" // *Cause: An attempt was made to re-normalize all the filenames in the // controlfile while the database is open. // *Action: Close the database before using the reNormalizeAllFileNames // procedure. 19712, 00000, "table name exceeds maximum length of %s" // *Cause: The table name string exceeds maximum length. // *Action: Retry the operation with a shorter table name. 19713, 00000, "invalid copy number: %s " // *Cause: The copy number is not in a valid range or you have reached // maximum limit. // *Action: Report the error and other information to support. 19714, 00000, "length for generated piece name longer than %s" // *Cause: The specified format exceeds the maximum length for the piece name. // *Action: Change the format to create shorter piece names. 19715, 00000, "invalid format for piece name" // *Cause: A restricted format was used incorrectly. // *Action: Change the format by removing the restricted format. / / / 19720 - 19740 reserved for Transportable Tablespace kernel errors / / 19720, 00000, "Error occurred when converting an OCI number into an SCN" // *Cause: This is most likely caused by an invalid SCN number that came // from an external file, such as an export file. // *Action: See other errors on the error stack to look for the source // of the problem. / 19721, 00000, "Cannot find datafile with absolute file number %s in tablespace %s" // *Cause: Can not find one of the datafile that should be in the Pluggable // Set. // *Action: Make sure all datafiles are specified via import command line // option or parameter files. / 19722, 00000, "datafile %s is an incorrect version" // *Cause: The datafile is an incorrect version. It contains either less or // more changes then the desired version. // *Action: Make sure the right datafiles are transported. Make sure the // datafile is copied while its tablespace is read only. / 19723, 00000, "Cannot recreate plugged in read-only datafile %s" // *Cause: The datafile is plugged in read only. It can not recreated. // *Action: Use ALTER DATABASE RENAME FILE command instead. / 19724, 00000, "snapshot too old: snapshot time is before file %s plug-in time" // *Cause: The snapshot SCN is before the SCN at which the referred datafile // is plugged into the database. // *Action: retry the query. / 19725, 00000, "can not acquire plug-in enqueue" // *Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command // issued concurrently, preventing this process from acquiring // the plug-in enqueue. // *Action: retry the operation. / 19726, 00000, "cannot plug data [%s] at level %s into database running at compatibility level %s" // *Cause: Some of the data in the pluggable set requires a compatibility // level higher than what is currently allowed by the database. // The string in square bracket is the name of the compatibility // type associated with the data. // *Action: Raise the "compatible" init.ora parameter and retry the operation. / 19727, 00000, "cannot plug data [%s] at level %s into database running Oracle %s" // *Cause: Some of the data in the pluggable set requires a compatibility // level higher than the release level of the Oracle executable. // The string in square bracket is the name of the compatibility // type associated with the data. // *Action: Upgrade Oracle and retry the operation. / 19728, 00000, "data object number conflict between table %s and partition %s in table %s" // *Cause: The non-partitioned table has the same data object number as // one of the partitions in the partitioned table. One can not // exchange the table with the partition in this case. // *Action: Use "alter table move partition" command to move the offending // partition, so that the partition will get a new data object // number. Retry the operation then. / 19729, 00000, "File %s is not the initial version of the plugged in datafile" // *Cause: The file is not the initial version of the plugged in datafile. // *Action: Use the correct initial version of the plugged in datafile. / 19730, 00000, "can not convert offline plugged-in datafile %s" // *Cause: As part of making a tablespace read-write, we need to convert // datafiles that are plugged in read-only. The file must be // online. // *Action: Online the datafile and retry the operation. / 19731, 00000, "cannot apply change to unverified plugged-in datafile %s" // *Cause: Recovery was not able to verify the referred datafile according // to information in the control file. Before encountering this // change vector for this file, somehow recovery did not // encounter the file conversion redo that is supposed to verify // the file. This may happen due to corrupted or incorrect // control file used for media recovery. // *Action: Use the correct control file and continue recovery. / 19732, 00000, "incorrect number of datafiles for tablespace %s" // *Cause: The number of datafiles in the export file for the referred // tablespace is not the same as expected. This is most likely // caused by a user editing the export file. // *Action: Use the correct export file and retry the operation. / 19733, 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. / 19734, 00000, "wrong creation SCN - control file expects converted plugged-in datafile" // *Cause: When a tablespace is plugged into a database, the tablespace is // initially read-only. Oracle converts the header of the // plugged-in datafiles (assign them a new creation SCN) when // the tablespace is first made read-write. This error occurs // when the creation SCN in the file header is different from the // creation SCN in the controlfile, possibly because this is the // initial version of plugged-in datafile. // *Action: Either restore the converted datafile or continue recovering the // datafile. / 19735, 00000, "wrong creation SCN - control file expects initial plugged-in datafile" // *Cause: When a tablespace is plugged into a database, the tablespace is // initially read-only. Oracle converts the header of the // plugged-in datafiles (assign them a new creation SCN) when // the tablespace is first made read-write. This error occurs // when the creation SCN in the file header is different from the // creation SCN in the controlfile, possibly because this is the // converted datafile. // *Action: Either restore the initial version of the plugged-in datafile, or // continue database recovery, which will recover the control file. / 19736, 00000, "can not plug a tablespace into a database using a different national character set" // *Cause: Oracle does not support plugging a tablespace into a database // using a different national character set. // *Action: Use import/export or unload/load to move data instead. / 19999, 00000, "skip_row procedure was called" // *Cause: The skip_row procedure was called which raises this error // *Action: Skip_row should only be called within a trigger or a procedure // called by a trigger. / / 20000 - 20999 Reserved for callers of the / system_utility.raise_application_error stored procedure. This allows / customers to generate their own exception numbers and deal with them / on the user-side. 20000, 00000, "%s" // *Cause: The stored procedure 'raise_application_error' // was called which causes this error to be generated. // *Action: Correct the problem as described in the error message or contact // the application administrator or DBA for more information. 21000, 00000, "error number argument to raise_application_error of %s%s is out of range" // *Cause: // *Action: Use an error number in the range of -20000 to -20999, inclusive. 21001, 00000, "error number argument to raise_system_error of %s%s is out of range" // *Cause: // *Action: Use an error number in the range of -23300 to -24299, or // -29300 to -29399, inclusive. / / 21100 - 21299 Reserved for CORE / / / 21300 - 22799 Reserved for OI/KO/KG (object Interface and Subsystem) / / Error numbers from 21300 to 21305 are reserved for KOK (common). / 21300, 00000, "objects option not installed" // *Cause: The objects option is not installed at this site. object types // and other object features are, therefore, unavailable. // *Action: Install the objects option. The objects option is not // part of the Oracle Server product and must be purchased // separately. Contact an Oracle sales representative if the // objects option needs to be purchased. 21301, 00000, "not initialized in object mode" // *Cause: This function requires the OCI process to be initialized in object // mode. // *Action: Specify OCI_OBJECT mode when calling OCIInitialize(). / / / Error number 21500 is the OCI's and Cartridge Service internal error. / Error number 21501 is the OCI's or Cartridge Services' memory allocation error. / Error number 21503 is the OCI's and Cartridge Service fatal error. / 21500, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" // *Cause: This is the generic error number for the OCI // environment (client-side) internal errors. This indicates // that the OCI environment has encountered an exceptional // condition. // *Action: Report as a bug - the first argument is the internal error number. / 21501, 00000, "program could not allocate memory" // *Cause: The operating system has run out of memory. // *Action: Take action to make more memory available to the program. / 21503, 00000, "program terminated by fatal error" // *Cause: A program is in an unrecoverable error state. // *Action: Report as a bug. / / / Error numbers from 21505 to 21519 are reserved for ORIG/KOG (general). / / / Error numbers from 21520 to 21559 are reserved for KOD/KOFD/KOUD (data). / 21520, 00000, "database server driver not installed" // *Cause: User attempted to access a database server through an object-mode // OCI environment but the necessary driver for supporting such // access to the database server is not installed or linked // in. // *Action: Check if the driver corresponding to the database server // has been installed/linked in and entered in the server driver // table. 21521, 00000, "exceeded maximum number of connections in OCI (object mode only)" // *Cause: User exceeded the maximum number of connections (255) that can // be supported by an OCI environment in object mode. // *Action: Close some of existing and unused connections before // opening more connections. 21522, 00000, "attempted to use an invalid connection in OCI (object mode only)" // *Cause: User attempted to use an invalid connection or a connection that // has been terminated in an OCI environment (object mode), // or user attempted to dereference a REF obtained from a connection // which has been terminated. // *Action: Ensure that the connection exists and is still valid. 21523, 00000, "functionality not supported by the server (object mode only)" // *Cause: User attempted to use a functionality that the server does not // support. // *Action: Upgrade the server 21524, 00000, "object type mismatch" // *Cause: The object type of the object is different from what is specified. // *Action: Check the type of the object and correct it. / 21525, 00000, "attribute number or (collection element at index) %s violated its constraints" // *Cause: Attribute value or collection element value violated its // constraint. // *Action: Change the value of the attribute or collection element such that // it meets its constraints. The constraints are specified as part // of the attribute or collection element's schema information. 21526, 00000, "initialization failed" // *Cause: The initialization sequence failed. This can happen, for example, // if an environment variable such as NLS_DATE_FORMAT is set to // an invalid value. // *Action: Check that all NLS environment variables are well-formed. / / / Error numbers from 21560 to 21599 are reserved for / common ORI/ORT/ORL/ORC/KO and Cartridge Service errors. / 21560, 00000, "argument %s is null, invalid, or out of range" // *Cause: The argument is expecting a non-null, valid value but the // argument value passed in is null, invalid, or out of range. // Examples include when the LOB/FILE positional or size // argument has a value outside the range 1 through (4GB - 1), // or when an invalid open mode is used to open a file, etc. // *Action: Check your program and correct the caller of the routine // to not pass a null, invalid or out-of-range argument value. / 21561, 00000, "OID generation failed" // *Cause: The handles passed in may not be valid // *Action: Check the validity of the env, svc handles / / Error numbers from 21600 to 21699 are reserved for ORI*/KOI* (interface). / and Memory/Duration Cartridge Service. / 21600, 00000, "path expression too long" // *Cause: The path expression that is supplied by the user is too long. The // path expression is used to specify the position of an attribute in // an object. This error occurs when one of the intermediate elements // in the path expression refers to an attribute of a built-in type. // Thus, the OCI function cannot proceed on to process the rest of the // elements in the path expression. // *Action: User should pass in the correct path expression to locate the // attribute. 21601, 00000, "attribute is not an object" // *Cause: The user attempts to perform an operation (that is valid only for // an object) to an attribute of a built-in type. // An example of such an illegal operation is to dynamically set // a null structure to an attribute of a built-in type. // *Action: User should avoid performing such operation to an attribute of // built-in type. 21602, 00000, "operation does not support the specified typecode" // *Cause: The user attempts to perform an operation that does not support // the specified typecode. // *Action: User should use the range of valid typecodes that are supported // by this operation. 21603, 00000, "property id [%s] is invalid" // *Cause: The specified property id is invalid. // *Action: User should specify a valid property id. Valid property ids are // enumerated by OCIObjectPropId. 21604, 00000, "property [%s] is not a property of transient or value instances" // *Cause: Trying to get a property which applies only to persistent objects. // *Action: User should check the lifetime and only get this property for // persistent objects. 21605, 00000, "property [%s] is not a property of value instances" // *Cause: Trying to get a property which applies only to persistent // and transient objects. // *Action: User should check the lifetime and only get this property for // persistent and transient objects. 21606, 00000, "can not free this object" // *Cause: Trying to free an object that is persistent and dirty and the // OCI_OBJECTFREE_FORCE flag is not specified. // *Action: Either flush the persistent object or set the flag to // OCI_OBJECTFREE_FORCE / 21607, 00000, "memory cartridge service handle not initialized" // *Cause: Attempt to use the handle without initializing it. // *Action: Initialize the memory cartridge service handle. 21608, 00000, "duration is invalid for this function" // *Cause: Attempt to use a duration not valid for this function. // *Action: Use a valid duration - a previously created user duration or // OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout // duration or external procedure duration, use // OCIExtProcAllocCallMemory. 21609, 00000, "memory being resized without being allocated first" // *Cause: Attempt to resize memory without allocating it first. // *Action: Allocate the memory first before resizing it. 21610, 00000, "size [%s] is invalid" // *Cause: Attempt to resize memory with invalid size. // *Action: Pass in a valid size (must be a positive integer). 21611, 00000, "key length [%s] is invalid" // *Cause: Attempt to use an invalid key length. // *Action: Key length is invalid and valid range is 0 to 64 21612, 00000, "key is already being used" // *Cause: Attempt to use a key that is already used. // *Action: Use a new key that is not yet being used. 21613, 00000, "key does not exist" // *Cause: Attempt to use a non-existent key // *Action: Use a key that already exists. 21614, 00000, "constraint violation for attribute number [%s]" // *Cause: Constraints on the attribute were violated // *Action: Correct the value (of the attribute) so that it satisfies // constraints 21615, 00000, "copy of an OTS (named or simple) instance failed" // *Cause: see following message // *Action: Check that no attribute value violates constraints. / / Error numbers from 21700 to 21799 are reserved for KOC (cache). / 21700, 00000, "object does not exist or is marked for delete" // *Cause: User attempted to perform an inappropriate operation to // an object that is non-existent or marked for delete. // Operations such as pinning, deleting and updating cannot be // applied to an object that is non-existent or marked for delete. // *Action: User needs to re-initialize the reference to reference an // existent object or the user needs to unmark the object. 21701, 00000, "attempt to flush objects to different servers" // *Cause: User attempted to flush objects to different servers in one // function call. These objects are obtained by calling a callback // functions provided by the program. // *Action: User should avoid performing such operation. 21702, 00000, "object is not instantiated or has been de-instantiated in cache" // *Cause: User attempted to perform an inappropriate operation to a transient // object that is not instantiated in the object cache. // Operations that cannot be applied to a not-instantiated transient // object include deleting or pinning such an object. // *Action: User should check their code to see if they are performing // such an operation without instantiating the object first, or // performing such an operation after the allocation duration of // the object has expired. 21703, 00000, "cannot flush an object that is not modified" // *Cause: See the error message. // *Action: The object should not be flushed. 21704, 00000, "cannot terminate cache or connection without flushing first" // *Cause: See the error message. // *Action: The transaction should be aborted or committed before terminating // the cache or connection. 21705, 00000, "service context is invalid" // *Cause: The service context that is supplied by the user is not valid. // *Action: User needs to establish the service context. 21706, 00000, "duration does not exist or is invalid" // *Cause: The duration number that is supplied by the user is not valid. // *Action: User needs to establish the duration or use a correct predefined // duration. 21707, 00000, "pin duration is longer than allocation duration" // *Cause: The pin duration supplied by the user is longer than the allocation // duration. This affects operations such as pinning and setting // default parameters. // *Action: User should use a shorter pin duration or use the null duration. 21708, 00000, "inappropriate operation on a transient object" // *Cause: User attempted to perform an inappropriate operation on a // transient object. Operations that cannot be applied to a // transient object include flushing and locking. // *Action: User should avoid performing such operation on a transient object. 21709, 00000, "cannot refresh an object that has been modified" // *Cause: User attempted to refresh an object that has been marked for // delete, update or insert (new). // *Action: User should unmark the object before refreshing it. 21710, 00000, "argument is expecting a valid memory address of an object" // *Cause: The object memory address that is supplied by the user is invalid. // The user may have passed in a bad memory address to a function that // is expecting a valid memory address of an object. // *Action: User should pass in a valid memory address of an object // to the function. / / 21779, 00000, "duration not active" // *Cause: User is trying to use a duration that has been terminated. // *Action: User should avoid performing such operation. / / / Error numbers from 21800 to 21999 are reserved. / / / Error numbers from 22000 to 22299 are reserved for ORL/KOL (language) / including OCIString, OCIDate, OCINumber, OCIColl, OCITable, and OCIArray. / 22053, 00000, "overflow error" // *Cause: This operation's result is above the range of Oracle number. // *Action: Decrease the input value(s) so that the result is in the range // of Oracle number. / 22054, 00000, "underflow error" // *Cause: This operation's result is below the range of Oracle number. // *Action: Increase the input value(s) so that the result is in the range // of Oracle number. / 22055, 00000, "unknown sign flag value [%s]" // *Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED. // *Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag. / 22056, 00000, "value [%s] is divided by zero" // *Cause: Given value is divied by zero. // *Action: Modify divisor value to be non-zero. / 22057, 00000, "bad integer length [%s]" // *Cause: The length of the integer (ie number of bytes) to be converted // to or from an Oracle number is invalid. // *Action: Use integer length 1, 2, 4 or 8 bytes only. / 22059, 00000, "buffer size [%s] is too small - [%s] is needed" // *Cause: The buffer to hold the resulting text string is too small. // *Action: Provide a buffer of the required size. / 22060, 00000, "argument [%s] is an invalid or uninitialized number" // *Cause: An invalid or uninitialized number is passed in. // *Action: Use a valid number. To initialize number call OCINumberSetZero(). / 22061, 00000, "invalid format text [%s]" // *Cause: The numeric format string for converting characters to or // from an Oracle number is invalid. // *Action: Use valid format string as documented in OCI Programmer's Guide. / 22062, 00000, "invalid input string [%s]" // *Cause: The text string for converting to numbers is invalid. // *Action: Use a valid input string as documented in OCI Programmer's Guide. / 22063, 00000, "reading negative value [%s] as unsigned" // *Cause: Attempt to convert a negative number to an unsigned integer. // *Action: Use the sign flag ORLTSB to convert a signed number. / 22064, 00000, "invalid NLS parameter string [%s]" // *Cause: The NLS parameter string for converting characters to or // from an Oracle number is invalid. // *Action: Use valid format string as documented in OCI Programmer's Guide. / 22065, 00000, "number to text translation for the given format causes overflow" // *Cause: Rounding done due to the given string format causes overflow. // *Action: Change the string format such that overflow does not occur. / 22130, 00000, "buffer size [%s] is less than the required size [%s]" // *Cause: The size of the buffer into which the hexadecimal REF string // is to be written is too small. // *Action: Provide a buffer of the required size. / 22131, 00000, "hexadecimal string length is zero" // *Cause: The given hexadecimal string length must be greater than zero. // *Action: Specify a length greater than zero. / 22132, 00000, "hexadecimal string does not correspond to a valid REF" // *Cause: The given hexadecimal string is invalid. // *Action: Provide a valid hexadecimal string which was previously returned // by a call to OCIRefToHex(). / 22140, 00000, "given size [%s] must be in the range of 0 to [%s]" // *Cause: The given resize size is invalid. // *Action: Ensure that the given size is in the required range. / 22150, 00000, "variable-length array has not been initialized" // *Cause: An un-initialized variable-length array is being operated upon. // *Action: Initialize the variable-length array prior to calling // this function. / 22151, 00000, "cannot resize non-zero variable-length array to zero elements" // *Cause: Trying to resize a non-zero variable-length array to 0 elements. // *Action: Specify a non-zero size. / 22152, 00000, "destination variable-length array is not initialized" // *Cause: The variable-length array on the right-hand-side of an // assignment or the destination array of an append // is not initialized. // *Action: Initialize the destination variable-length array prior to calling // this function. / 22153, 00000, "source variable-length array is not initialized" // *Cause: The variable-length array on the left-hand-side of an // assignment or the source array of an append // is not initialized. // *Action: Initialize the destination variable-length array prior to calling // this function. / 22160, 00000, "element at index [%s] does not exist" // *Cause: Collection element at the given index does not exist. // *Action: Specify the index of an element which exists. / 22161, 00000, "type code [%s] is not valid" // *Cause: Given type code is not valid. // *Action: Use one of the typecodes enumerated in OCITypeCode. / 22162, 00000, "element at index [%s] has been previously deleted" // *Cause: Trying to delete a non-existent collection element. // *Action: Check for the existence of the element prior to calling this // function. / 22163, 00000, "left hand and right hand side collections are not of same type" // *Cause: Left hand and right side collections are not of same type. // *Action: Ensure that the same collection type is passed for both left // hand and right hand side of this function. / 22164, 00000, "delete element operation is not allowed for variable-length array" // *Cause: Trying to delete an element of a variable-length array. // *Action: Ensure that the collection is not a variable-length array prior // to calling this function. / 22165, 00000, "given index [%s] must be in the range of 0 to [%s]" // *Cause: Given index is not in the required range. // *Action: Ensure that the given index is in the required range. / 22166, 00000, "collection is empty" // *Cause: Given collection is empty. // *Action: Test if collection is empty prior to invoking this function. / 22167, 00000, "given trim size [%s] must be less than or equal to [%s]" // *Cause: Given trim size is greater than the current collection size. // *Action: Ensure that the given size is less than or equal to the // collection size prior to calling this function. / / 22275 to 22279 reserved for KOLL - LOBs / 22275, 00000, "invalid LOB locator specified" // *Cause: There are several causes: (1) the LOB locator was never // initialized; (2) the locator is for a BFILE and the routine // expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a // BLOB/CLOB/NCLOB and the routine expects a BFILE locator; // (4) trying to update the LOB in a trigger body -- LOBs in // trigger bodies are read only. // *Action: For (1), initialize the LOB locator by selecting into the locator // variable or by setting the LOB locator to empty. For (2) and (3), // pass the correct type of locator into the routine. For (4), // remove the trigger body code that updates the LOB value. / 22276, 00000, "invalid locator for LOB buffering" // *Cause: There are several causes: (1) the locator was never enabled for // buffering (2) it is not an updated locator but is being used for // a write/flush operation // *Action: For (1) enable the locator for buffering; (2) ensure that only // an updated locator is used for a LOB update operation / 22277, 00000, "cannot use two different locators to modify the same LOB" // *Cause: LOB buffering is enabled and an attempt was made to modify the // LOB using two different LOB locators. // *Action: When using LOB buffering, modify the LOB through one LOB // locator only. / 22278, 00000, "must update the LOB only through the LOB buffers" // *Cause: LOB buffering is enabled for this LOB and there are buffers // for this LOB in the buffer pool. Thus, updating the LOB // through means other than the LOB buffers is not allowed. // *Action: Update the LOB through the LOB buffers using the locator that // has LOB buffering enabled. If this operation is required, // buffers associated with this LOB should either be flushed as // necessary or buffering should be disabled. Once this is done, // reissue the command. / 22279, 00000, "cannot perform operation with LOB buffering enabled" // *Cause: The operation attempted is not allowed when LOB buffering is // enabled. // *Action: If the operation is required, LOB buffering should not be used. // In this case, flush buffers associated with the input LOB locator // as necessary, disable buffering on the input LOB locator and // reissue the command. / / 22280 to 22299 reserved for LOBs - LBS(KOLB), DBMS_LOB(KKXL) and BFILE(KOLF) / 22280, 00000, "no more buffers available for operation" // *Cause: There are two causes: (1) All buffers in the buffer pool have been // used up by previous operations (2) Attempt to flush a LOB without // any previous buffered update operations. // *Action: For (1), flush the LOB(s) through the locator that is // being used to update the LOB. For (2), write to the LOB through a // locator enabled for buffering before attempting to flush buffers. / 22281, 00000, "cannot perform operation with an updated locator" // *Cause: The input locator has buffering enabled and was used to update // the LOB value through the LOB buffering subsystem. The // modified buffer has not been flushed since the write that was // performed by the the input locator; thus, the input locator is // considered an updated locator. Updated locators cannot be the // source of a copy operation. Only one locator per LOB may be used // to modify the LOB value through the LOB buffering subsystem. // *Action: Depending on whether the modifications made through the input // locator to the LOB buffering subsystem should be written to // the server, either flush the buffer to write the modifications, // or, disable buffering on the locator to discard the // modifications. Then, reissue the command. / 22282, 00000, "non-contiguous append to a buffering enabled LOB not allowed" // *Cause: The buffered write operation has an input offset value more // than one byte or character past the end of the LOB. // *Action: Specify an input offset value which is exactly one character or // byte greater than the length of the LOB that you are attempting // to update through a buffered write operation. / 22285, 00000, "non-existent directory or file for %s operation" // *Cause: Attempted to access a directory that does not exist, or attempted // to access a file in a directory that does not exist. // *Action: Ensure that a system object corresponding to the specified // directory exists in the database dictionary, or // make sure the name is correct. / 22286, 00000, "insufficient privileges on file or directory to perform %s operation" // *Cause: The user does not have the necessary access privileges on the // directory alias and/or the file for the operation. // *Action: Ask the database/system administrator to grant the required // privileges on the directory alias and/or the file. / 22287, 00000, "invalid or modified directory occurred during %s operation" // *Cause: The directory alias used for the current operation is not valid // if being accessed for the first time, or has been modified by // the DBA since the last access. // *Action: If you are accessing this directory for the first time, provide // a valid directory name. If you have been already successful in // opening a file under this directory before this error occured, // then close the file and retry the operation with a valid // directory alias as modified by your DBA. Oracle recommends that // directories should be modified only during quiescent periods. / 22288, 00000, "file or LOB operation %s failed\n%s" // *Cause: The operation attempted on the file or LOB failed. // *Action: See the next error message in the error stack for more detailed // information. Also, verify that the file or LOB exists and that // the necessary privileges are set for the specified operation. If // the error still persists, report the error to the DBA. / 22289, 00000, "cannot perform %s operation on an unopened file or LOB" // *Cause: The file or LOB is not open for the required operation to be // performed. // *Action: Precede the current operation with a successful open operation // on the file or LOB. / 22290, 00000, "operation would exceed the maximum number of opened files or LOBs" // *Cause: The number of open files or LOBs has reached the maximum limit. // *Action: Close some of the opened files or LOBs and retry the operation. / 22291, 00000, "Open LOBs exist at transaction commit time" // *Cause: An attempt was made to commit a transaction with open LOBs at // transaction commit time. // *Action: Close the LOBs before committing the transaction. / 22292, 00000, "Cannot open a LOB in read-write mode without a transaction" // *Cause: An attempt was made to open a LOB in read-write mode before // a transaction was started. / *Action: Start a transaction before opening the LOB in read-write mode. // Ways to start a transaction include issuing a SQL DML or SELECT // FOR UPDATE command. Opening hte LOB in read-only mode does not // require a transaction. / 22293, 00000, "LOB already opened in the same transaction" // *Cause: An attempt was made to open a LOB that already is open in // this transaction. // *Action: Close the LOB before attempting to re-open it. / 22294, 00000, "cannot update a LOB opened in read-only mode" // *Cause: An attempt was made to write to or update a LOB opened // in read-only mode. // *Action: Close the LOB and re-open it in read-write mode before // attempting to write to or update the LOB. 22295, 00000, "cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement" // *Cause: An attempt was made to bind data more than 4000 bytes of data to both // LOB and LONG columns in the same insert or update statement. You can // bind more than 4000 bytes of data to either a LONG column or one or // more LOB columns but not both. // *Action: Bind more than 4000 bytes of data to either the LONG column or one or // more LOB columns but not both. 22296, 00000, "invalid ALTER TABLE option for conversion of LONG datatype to LOB" // *Cause: An attempt was made to specify ALTER TABLE options which are // disallowed during conversion of LONG datatype to LOB. The only ALTER // TABLE options allowed during conversion of LONG datatype to LOB are // the default clause and LOB storage clause for the column being // converted to LOB. // *Action: Remove the disallowed options. 22297, 00000, "warning: Open LOBs exist at transaction commit time" // *Cause: An attempt was made to commit a transaction with open LOBs at // transaction commit time. // *Action: This is just a warning. The transaction was commited successfully, // but any domain or functional indexes on the open LOBs were not // updated. You may want to rebuild those indexes. / / Error numbers from 22300 to 22599 are reserved for ORT/KOT (type). / 22303, 00000, "type \"%s\".\"%s\" not found" // *Cause: The user is trying to obtain information for a type that // cannot be found. // *Action: Check that the schema is correct and that the type has been // created correctly. / 22304, 00000, "input type is not an object type" // *Cause: The user is trying to obtain the supertype information for a // non-object type. // *Action: Pass in only an object type. / 22305, 00000, "attribute/method/parameter \"%s\" not found" // *Cause: Type element with the given name is not found in the type. // *Action: Check to make sure that the type element exists. / 22306, 00000, "type \"%s\".\"%s\" already exists" // *Cause: The user is trying to create a type that already // exists. // *Action: Check to make sure that the type has not been created prior to // this. / 22307, 00000, "operation must be on a user-defined type" // *Cause: attempt to perform an operation that is allowed only on a // user-defined type, and the type is not a user-defined type. // *Action: Check to make sure that only user-defined types are being // operated on. / 22308, 00000, "operation not allowed on evolved type" // *Cause: An attempt was made to replace a type whose attribute definition // been been altered. // *Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE // REPLACE. / 22309, 00000, "attribute with name \"%s\" already exists" // *Cause: The user is attempting to create an object type where // more than one attributes have the same name. // *Action: Check to make sure that all attribute names are unique. / 22310, 00000, "ALTER TYPE error. Refer to table \"%s\".\"%s\" for errors" // *Cause: An invalid alter type statement was submitted. // *Action: Correct the errors listed in specified table and resubmit // statement. / 22311, 00000, "type for attribute \"%s\" does not exist" // *Cause: The type of the attribute does not exist. // *Action: No types were created/modified for this DDL transaction. Redo // the DDL transaction and add the creation of the attribute's type // in the DDL transaction. / 22312, 00000, "must specify either CASCADE or INVALIDATE option" // *Cause: An attempt was made to alter a type which has a dependent type // or table without specifying the CASCADE or INVALIDATE option. // *Action: Resubmit the statement with either the CASCADE or INVALIDATE // option. Specify CASCADE if you want to cascade the type change to // dependent types and tables; otherwise, specify INVALIDATE to // invalidate all dependents. / 22313, 00000, "cannot use two versions of the same type \"%s\"" // *Cause: The version of this type conflicts with the version of this // type used by another library that was linked in with the // application. An application may only use one version of a type. // *Action: Check that the libraries being linked with this application and // use the same versions of the type. / 22314, 00000, "method information mismatch in ALTER TYPE" // *Cause: The number of methods or the method signature do not match that // of the original type declaration. This is not supported. // *Action: Make sure the method signature stay identical for the previously // declared method. Do not drop existing methods. / 22315, 00000, "type \"%s\" does not contain a map or order function" // *Cause: The input type does not contain a map or order function so one // cannot be returned. // *Action: Add a map or order function to the type or catch this error. / 22316, 00000, "input type is not a collection type" // *Cause: The user is trying to obtain information for collection types // on a non-named collection type. // *Action: Use a named collection type for the function. / 22317, 00000, "typecode %d is not legal as a number type" // *Cause: The user is trying to use a number typecode that is not valid. // *Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, // OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, // OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL. / 22318, 00000, "input type is not an array type" // *Cause: The user is trying to obtain the number of elements for a // non-array type. // *Action: Pass in only a named collection type which is an array. / 22319, 00000, "type attribute information altered in ALTER TYPE" // *Cause: The type attribute information does not match that of the // original type declaration when altering type. Attributes // cannot be altered during ALTER TYPE. Only new methods can // be added. // *Action: Check that all type alterations are legal. / 22320, 00000, "missing user version string" // *Cause: The VERSION option is specified without a user version string. // *Action: Resubmit the statement with the version string following the // VERSION keyword. / 22321, 00000, "method does not return any result" // *Cause: OCITypeResult() was called on a method that does not return any // results. // *Action: Check that you are passing in the correct method descriptor, // or that your method creation was done correctly. / 22322, 00000, "error table \"%s\".\"%s\" has incorrect structure" // *Cause: The specified error table does not have the expected table // structure. // *Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure // to create an error table, then resubmit the statement using the // new error table. / 22323, 00000, "error table \"%s\".\"%s\" does not exist" // *Cause: The error table does not exist. // *Action: Resubmit the statement with a correct error table name. / 22324, 00000, "altered type has compilation errors" // *Cause: The use of the ALTER TYPE statement caused a compilation error. // *Action: Correct the error reported and resubmit the statement. / 22325, 00000, "event for create type with user version string" // *Cause: // *Action: / 22326, 00000, "cannot change a type to FINAL if it has subtypes" // *Cause: An attempt was made to change a type with subtypes to FINAL. // *Action: Drop all subtypes of the target type before changing it to FINAL. / 22327, 00000, "cannot change a type to NOT INSTANTIABLE if it has dependent tables" // *Cause: An attempt was made to change a type with dependent tables to NOT // INSTANTIABLE. // *Action: Drop all dependent tables of the target type and resubmit the // statement. / 22328, 00000, "object \"%s\".\"%s\" has errors.\n%s" // *Cause: Altering the target type causes errors in its dependent object. // *Action: Correct the problem in the dependent object and resubmit the // statement. / 22329, 00000, "cannot alter a non-object type" // *Cause: An attempt was made to execute ALTER TYPE on a non-object type. // *Action: Drop the non-object type first, then re-create it as an object type. / 22330, 00000, "cannot alter a type that is not valid" // *Cause: An attempt was made to perform ALTER TYPE on an invalid type. // *Action: Use the CREATE OR REPLACE TYPE command to modify the type. / 22331, 00000, "cannot alter an incomplete type" // *Cause: An attempt was made to perform ALTER TYPE on an incomplete type. // *Action: Use CREATE TYPE to completely define the original type before // executing the ALTER TYPE. / 22332, 00000, "a dependent object in schema \"%s\" has errors.\n%s" // *Cause: Altering the target type causes errors in its dependent object. // *Action: Correct the problem in the dependent object and resubmit the // statement. / 22333, 00000, "cannot reset type \"%s\".\"%s\" due to invalid dependent types and tables" // *Cause: An attempt was made to reset the type version with invalid // dependent types and tables. // *Action: Use the ALTER TYPE COMPILE statement to compile all invalid // dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA to // upgrade all the dependent tables then resubmit the statement. / 22334, 00000, "cannot reset type \"%s\".\"%s\". Dependent tables must be upgraded to latest version" // *Cause: An attempt was made to reset the type version when the data in // the dependent table has not been upgraded to the latest type // version. // *Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade // the data in the dependent tables then resubmit the statement. / 22335, 00000, "The client cannot work with an altered type" // *Cause: A pre 8.2 client has requested a type that has been altered on the // server. // *Action: Only 8.2 or higher clients could access altered types / 22336, 00000, "table contained 8.0 image format, must specify INCLUDING DATA" // *Cause: One of the following: // 1) An attempt was made to alter a type with a dependent table in 8.0 // image format and the NOT INCLUDING TABLE DATA option was specified. // 2) An attempt was made to upgrade a table in 8.0 image format with // the NOT INCLUDING DATA option specified. // *Action: Resubmit the statement with INCLUDING DATA option. / 22337, 00000, "the type of accessed object has been evolved" // *Cause: The type of the accessed object has been altered and the client's // object is based on an earlier type definition. // *Action: The user needs to exit application and modify application to // accommodate the type change. // From SQL/PLUS, reconnect and resubmit statement. / 22338, 00000, "must specify CASCADE INCLUDING DATA when altering the final property" // *Cause: An attempt was made to alter the final property of a type with // dependent table(s) without specifying the CASCADE INCLUDING DATA . // option. // *Action: Resubmit the statement with the CASCADE INCLUDING DATA option. / 22339, 00000, "cannot alter to not final since its attribute column is substitutable" // *Cause: An attempt was made to alter a type to not final when its // embedded attribute is defined as substitutable in some tables. // Note, this is a restriction in 9.0 version because when a type is // altered to not final, column of that type is set to not // substitutable at all levels; thus, it is an error if one of its // embedded attribute column is already marked substitutable. // *Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS // for all columns of non final type. Then resubmit the ALTER TYPE // statement. / 22340, 00000, "cannot %s type \"%s\".\"%s\". Dependent tables must be upgraded to latest version" // *Cause: An attempt was made to reset the version, drop or alter a type // when the data in dependent table has not been upgraded to // the latest version. // *Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade // the data in the dependent tables then resubmit the statement. / 22341, 00000, "cannot assign supertype instance to subtype" // *Cause: An attempt was made to assign or copy a supertype instance to // a container (destination) that can only hold a subtype instance. // *Action: Make sure the runtime type of the source of the assignment or // copy is the same type as the destination or is a subtype of the // destination type / / Error numbers from 22350 to 22370 are reserved for ORT/KOT (Opaque Types). / / Error numbers from 22369 to 22370 are used by SYS.DBMS_INDEXING. / 22369, 00000, "invalid parameter encountered in method %s" // *Cause: An invalid parameter is being passed to this method of SYS.AnyType // ,SYS.AnyData or SYS.AnyDataSet // *Action: Check the parameters being passed to this method and make sure // that the parameters are allowed. / 22370, 00000, "incorrect usage of method %s" // *Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is // being used inappropriately. // *Action: Check the documentation for correct usage. / 22371, 00000, "Table contains data of type %s.%s, version %s, which does not exist" // *Cause: Some of the older versions of the type may have got deleted // because one or more of the types it were referencing was dropped. // *Action: These data could not be read as the whole ADT. Read the data at // individual scalar attribute level. / / Error numbers from 22600 to 22699 are reserved for KOP* (pickler) and / Pickler Cartridge Service. / 22600, 00000, "encountered 8.0.2 (Beta) VARRAY data that cannot be processed" // *Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data // which was created and stored by Oracle8 8.0.2 (Beta 2). // Production Oracle8 cannot understand or process such VARRAY data. // *Action: Delete the VARRAY data from the table by dropping the table, // deleting the rows, or nulling out the VARRAY columns, and then // re-insert the VARRAY data. There is no provided // script or tool to help automate this conversion. / 22601, 00000, "pickler TDS context [%s] is not initialized" // *Cause: Attempt to use the pickler TDS context without initializing it. // *Action: Use OCIPicklerTdsCtxInit to initialize the context. 22602, 00000, "pickler TDS handle [%s] is not well-formed" // *Cause: Attempt to use the pickler TDS handle without initializing/ // constructing it. // *Action: Use OCIPicklerTdsInit to initialize the handle before it is // constructed. Use OCIPicklerTdsGenerate to generate the // TDS before its attributes can be accessed. 22603, 00000, "cannot add an attribute to the already generated TDS handle" // *Cause: Attempt to add an attribute to the already constructed TDS. // *Action: Use a TDS handle that is initialized but not yet constructed. 22604, 00000, "TDS handle already generated" // *Cause: Attempt to geneate TDS that is already genearated. // *Action: Use a TDS handle that is initialized but not yet generated. 22605, 00000, "FDO handle [%s] is not initialized" // *Cause: Attempt to use an uninitialized FDO handle. // *Action: Use OCIPicklerFdoInit to initialize FDO handle". 22606, 00000, "pickler image handle [%s] is not well-formed" // *Cause: Attempt to use the image handle without initializing/ // constructing it. // *Action: Use OCIPicklerImageInit to initialize the handle before it is // constructed. Use OCIPicklerImageGenerate to generate the // image before its attributes can be accessed. 22607, 00000, "image handle already generated" // *Cause: Attempt to geneate image that is already genearated. // *Action: Use a image handle that is initialized but not yet generated. 22608, 00000, "cannot add an attribute to the already generated image handle" // *Cause: Attempt to add an attribute to the already constructed image. // *Action: Use a image handle that is initialized but not yet constructed. 22609, 00000, "error %s during initialization of FDO" // *Cause: Error during FDO initialization. // *Action: Take an action based on the specified error. / 22610, 00000, "error while adding a scalar to the image handle" // *Cause: Error while adding a scalar attribute to the image handle // *Action: Make sure image handle is initialized before adding scalar / 22611, 00000, "TDS version is not recognized" // *Cause: Incorrect TDS handle is passed // *Action: Make sure image handle is initialized with the correct TDS / 22612, 00000, "TDS does not describe a collection TDS" // *Cause: collection construct/access routines are being on an image but // the TDS does not describe that a collection TDS // *Action: Make sure a collection TDS is used before invoking collection // routines on the image handle / 22613, 00000, "buflen does not match the size of the scalar" // *Cause: buflen is incorrect // *Action: Make sure buflen is correct and matches the size of the scalar / 22614, 00000, "error while construction the collection in the image" // *Cause: Error during the construction of collection // *Action: Make sure image handle is initialized and // OCIPicklerImageCollBegin is called to begin collection / 22615, 00000, "attribute is not a collection" // *Cause: collection routine is invoked upon a non-collection attribute // *Action: Make sure attribute is a collection / 22616, 00000, "image is not of Oracle 8.1 format" // *Cause: The function being invoked is applicable only for 8.1 images // *Action: Make sure image is of 8.1 format / 22617, 00000, "error while accessing the image handle collection" // *Cause: Error while accessing collection in the image handle // *Action: Make sure image is initialized correctly and the collection // is constructed properly. / 22618, 00000, "attribute is a BAD NULL in the image handle" // *Cause: attribute in question is probably the attribute of a null // embedded image // *Action: Make sure attribute number is valid or it is NULL or // NOT NULL. / 22619, 00000, "all collection elements have already been accessed" // *Cause: Accessing a collection element after all the collection // elements are already accessed // *Action: This function should not be invoked any more. / 22620, 00000, "buffer size too small to hold the value" // *Cause: Buffer size is not enough to hold the value. Most likely // while doing the character set conversion, a bigger buffer // is needed. // *Action: Pass in a bigger buffer. If the client character set format // differs from that of server, doing the conversion may result // in 4X expansion. 22621, 00000, "error transfering an object from the agent" // *Cause: Any error returned from pickler routines on the agent side. // *Action: Contact Oracle Support. / 22625, 00000, "OCIAnyData is not well-formed" // *Cause: Attempt to use the OCIAnyData without initializing // constructing it. // *Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is // adding attributes. Use OCIAnyDataEndConstruct to complete the // construction. Or use OCIAnyDataConvert to do the construction. // MAke sure it is properly constructed before accessing attributes. / 22626, 00000, "Type Mismatch while constructing or accessing OCIAnyData" // *Cause: Type supplied is not matching the type of the AnyData. // If piece wise construction or access is being attempted, the // type supplied is not matching the type of the current attribute. // *Action: Make sure the type supplied matches the type of object to // to be constucted or accessed. / 22627, 00000, "tc [%s] must be that of object/varray/nested table" // *Cause: Type code is not that of object/varray/nested table // *Action: Make sure the type code is OCI_TYPECODE_OBJECT or // OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE / 22628, 00000, "OCIAnyData already constructed" // *Cause: Attempt to add attributes to OCIAnyData that is already constructed. // *Action: Use the OCIAnyData that is initialized but not yet constructed. / 22629, 00000, "OCIAnyData is null" // *Cause: Attempting an operation that is not valid on null OCIAnyData // *Action: Make sure OCIAnyData is not null. / 22630, 00000, "attribute [%s] is null or it is not well-formed" // *Cause: Passing an attribute that is null or not well-formed // *Action: Make sure the attribute is not null or is well-formed. / 22631, 00000, "attribute [%s] is is not well-formed or does not match the type" // *Cause: Passing an attribute that is not well-formed or does not match the // input type. // *Action: Make sure the attribute is well-formed and matches the type specified. / 22632, 00000, "AnyDataSet parameter is not valid for the current operation" // *Cause: The AnyDataSet parameter is null or it is somehow invalid for // the current operation. // *Action: Check the documentation for the current operation. / 22633, 00000, "Error freeing AnyDataSet" // *Cause: AnyDataSet that is passed in may not be valid. // *Action: Check all the AnyDataSet parameters. / 22634, 00000, "Error adding new instance to AnyDataSet" // *Cause: Current instance in the AnyDataSet has not been fully constructed. // *Action: Make sure that the current instance is fully constructed before // adding new instance. / / Error numbers from 22700 to 22799 are reserved for debugging event numbers. / 22700, 00000, "object access trace event number" // *Cause: N/A // *Action: If the trace event number is set to a level greater than 0 then // all the dangling REFs are dumped. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / / 22799 IS THE MAXIMUM ERROR NUMBER for ORI/KO (object Interface and Subsystem) / / 22800 - 22999 Reserved for object SQL: / 22800 - 22849 Reserved for object SQL Query/DML / (parse, semantics, type checkin, execution) / 22850 - 22879 Reserved for object SQL DDL / (parse, semantics, type checkin, execution) / 22880 - 22899 Reserved for object SQL REF/DEREF Support / (parse, semantics, type checkin, execution/KOKA) / 22900 - 22919 Reserved for SQL Nested Tables and Collections / (parse, semantics, type checkin, execution) / 22920 - 22929 Reserved for SQL LOBs / 22930 - 22949 Reserved for object SQL Dictionary Support / 22950 - 22969 Reserved for object SQL Method Support / 22970 - 22989 Reserved for object Views / 22990 - 22999 Reserved for SQL LOBs / / / 22800 - 22849 Reserved for object SQL Query/DML / (parse, semantics, type checkin, execution) / 22800, 00000, "invalid user-defined type" // *Cause: An attempt was made to use an incomplete type as a constructor. // *Action: Complete the type definition before using it in a query. 22801, 00000, "invalid object row variable" // *Cause: The specified object row variable is not available in the scope // of name resolution. // *Action: Verify the specified object row variable is correct, // or use an object row variable visible in scope. //22802, 00000, "cannot update attributes of packed ADTs in SQL" // *Cause: An attempt was made to update an attribute of a packed ADT // column in an // UPDATE statement. // *Action: Use an unpacked ADT column, OR update the entire ADT instead. 22803, 00000, "object type contains zero attributes" // *Cause: An attempt was made to create or specify a column or constructor // of an object type that has no attributes. Only object types // that have at least one attribute are allowed in this context. // *Action: specify a valid object type 22804, 00000, "remote operations not permitted on object tables or user-defined type columns" // *Cause: An attempt was made to perform queries or DML operations on // remote object // tables or on remote table columns whose type is one of object, // REF, nested table or VARRAY. 22805, 00000, "cannot insert NULL object into object tables or nested tables" // *Cause: An attempt was made to insert a NULL object into an object table // or a Nested Table. // *Action: Ensure that a non-NULL object is inserted into the table or // insert an object with attributes whose values are NULL. 22806, 00000, "not an object or REF" // *Cause: An attempt was made to extract an attribute from an item that is // neither an object nor a REF. // *Action: Use an object type or REF type item and retry the operation. 22807, 00000, "cannot resolve to a scalar type or a collection type" // *Cause: Invalid use of a non-scalar (for example, object type) item. // *Action: Change the item's data type and retry the operation. 22808, 00000, "REF dereferencing not allowed" // *Cause: An attempt was made to access an object type's attributes by // dereferencing // a REF item. // *Action: Make the item an object type instead of a REF to an object type. 22809, 00000, "nonexistent attribute" // *Cause: An attempt was made to access a non-existent attribute of an // object type. // *Action: Check the attribute reference to see if it is valid. Then retry // the operation. 22810, 00000, "cannot modify object attributes with REF dereferencing" // *Cause: An attempt was made to modify the attributes an object by // dereferencing a REF column in an UPDATE statement. // *Action: Update the table containing the object that the REF points to, or // change the REF column to an object type column. //22811, 00000, "cannot access attributes of packed adts in SQL" // *Cause: Attempt to access an attribute of a packed adt column/table // *Action: Use an unpacked adt, OR retrieve the entire adt instead 22812, 00000, "cannot reference nested table column's storage table" // *Cause: An attempt to access the nested table column's storage table is // not allowed in the given context. // *Action: Issue the statement against the parent table containing the // nested table column. 22813, 00000, "operand value exceeds system limits" // *Cause: Object or Collection value was too large. The size of the value // might have exceeded 30k in a SORT context, or the size might be // too big for available memory. // *Action: Choose another value and retry the operation. 22814, 00000, "attribute or element value is larger than specified in type" // *Cause: Value provided for the object type attribute or collection element // exceeded the size specified in the type declaration. // *Action: Choose another value and retry the operation. 22815, 00000, "sql name resolution event" // *Document: NO // *Cause: N/A // *Action: Sets weak name resolution on for object sql 22816, 00000, "unsupported feature with RETURNING clause" // *Cause: RETURNING clause is currently not supported for object type // columns, LONG columns, remote tables and INSERT with subquery. // *Action: Use separate select statement to get the values. 22817, 00000, "subquery not allowed in the default clause" // *Cause: An attempt was made to use a subquery in the column default // clause expression. // *Action: Remove the subquery from the default clause. 22818, 00000, "subquery expressions not allowed here" // *Cause: An attempt was made to use a subquery expression where these // are not supported. // *Action: Rewrite the statement without the subquery expression. 22819, 00000, "scope of input value does not correspond to the scope of the target" // *Cause: An attempt to operate on a REF value scoped to a different table // than the expected one // *Action: Use a ref which is scoped to the expected table and retry // the operation 22820, 00000, "Event to turn off redundant join elimination by the optimizer" // *Document: NO // *Cause: N/A // *Action: Turns off redundant-join-elimination 22821, 00000, "Event to turn off common subexpression elimination" // *Document: NO // *Cause: N/A // *Action: Turns off common subexpression elimination 22822, 00000, "Event to accept dot notation in the insert statement" // *Document: NO // *Cause: N/A // *Action: Enables dot notation in insert statements 22825, 00000, "event set during import/export" // *Document: NO // *Cause: N/A // *Action: Enables logical transformation of opaque types 22826, 00000, "cannot construct an instance of a non instantiable type" // *Cause: An attempt was made to use a non instantiable type // as a constructor. // *Action: None. 22827, 00000, "Event to lookup remote objects using KGL" // *Document: NO // *Cause: N/A // *Action: Enables lookup of remote objects through the remote // tranfer KGL mechanism instead of ddfnet. 22828, 00000, "input pattern or replacement parameters exceed 32K size limit" // *Cause: Value provided for the pattern or replacement string in the form of // VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit. // *Action: Use a shorter pattern or process a long pattern string in multiple // passes. 22829, 00000, "Event to allow LATERAL views" // *Document: NO // *Cause: N/A // *Action: Enables usage of LATERAL views. This event can // be removed once this feature is tested and documented. / / / 22850 - 22879 Reserved for object SQL DDL / (parse, semantics, type checkin, execution) / 22850, 00000, "duplicate LOB storage option specificed" // *Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, // TABLESPACE, STORAGE, INDEX) was specified more than once. // *Action: Specify all LOB storage options only once. / 22851, 00000, "invalid CHUNK LOB storage option value" // *Cause: The specified CHUNK LOB storage option value must be an integer. // *Action: Choose an appropriate integer value and retry the operation. / 22852, 00000, "invalid PCTVERSION LOB storage option value" // *Cause: The specified PCTVERSION LOB storage option value must be an // integer. // *Action: Choose an appropriate integer value and retry the operation. / 22853, 00000, "invalid LOB storage option specification" // *Cause: A LOB storage option was not specified // *Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, // STORAGE, INDEX as part of the LOB storage clause. / 22854, 00000, "invalid option for LOB storage index" // *Cause: A valid LOB store index option was not specified. // *Action: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as // part of the LOB storage index. / 22855, 00000, "optional name for LOB storage segment incorrectly specified" // *Cause: The optional name for LOB storage segment was specified with // multiple columns in the column list. // *Action: Specify each column LOB storage only with optional name(s). / 22856, 00000, "cannot add columns to object tables" // *Cause: An attempt was made to add columns to an object table. Object // tables cannot be altered to add columns since its // definition is based on an object type. // *Action: Create a new type with additional attributes, and use the new // type to create an object table. The new object table will have // the desired columns. / 22857, 00000, "cannot modify columns of object tables" // *Cause: An attempt was made to alter the object table by modifing // existing columns. An object table cannot be altered to modify // existing columns since it is based on an object type. The table // definition must be in sync with the corresponding type. // *Action: Create a new type with the desired attribute types and use it // to create an object table. The new object table will have the // desired columns. / 22858, 00000, "invalid alteration of datatype" // *Cause: An attempt was made to modify the column type to object, REF, // nested table, VARRAY or LOB type. // *Action: Create a new column of the desired type and copy the current // column data to the new type using the appropriate type // constructor. / 22859, 00000, "invalid modification of columns" // *Cause: An attempt was made to modify an object, REF, VARRAY, nested // table, or LOB column type. // *Action: Create a new column of the desired type and copy the current // column data to the new type using the appropriate type // constructor. 22860, 00000, "object type expected" // *Cause: An attempt was made to create an object table using a non- // object type, or to create a column that is a REF to a non-object // type. // *Action: Use a valid object type in the table or column definition. 22861, 00000, "invalid user-defined type" // *Cause: An attempt was made to create a column or object table of a non- // existent type. // *Action: Specify a valid type in the table or column definition. 22862, 00000, "specified object identifier doesn't match existing object identifier" // *Cause: An attempt was made to specify an object identifier for the type // that does not match the existing identifier of the incomplete // type of the same name. // *Action: Specify the correct object identifier or leave it out of the // statement. 22863, 00000, "synonym for datatype %s.%s not allowed" // *Cause: A synonym specification for a datatype is not supported // *Action: do not use the synonym for the datatype 22864, 00000, "cannot ALTER or DROP LOB indexes" // *Cause: An attempt was made to ALTER or DROP a LOB index. // *Action: Do not operate directly on the system-defined LOB index. // Perform operations on the corresponding LOB column. 22865, 00000, "more than one column specified" // *Cause: An attempt was made to specify multiple columns where only one is // allowed. // *Action: Specify a single column and retry the operation. 22866, 00000, "default character set is of varying width" // *Cause: A character LOB was defined but the default character // set is not fixed width. // *Action: Ensure that the character set is of fixed width before defining // character LOBs. 22868, 00000, "table with LOBs contains segments in different tablespaces" // *Cause: An attempt was made to drop a tablespace which contains the // segment(s) for the LOB columns of a table but does not contain // the table segment. // *Action: Find table(s) with LOB columns which have non-table segments in // this tablespace. Drop these tables and reissue drop tablespace. 22869, 00000, "depth of type dependency hierarchy exceeds maximum limit" // *Cause: The type dependency hierarchy was structured to have depth greater // than 1024. // *Action: Re-structure the type dependency hierarchy to a shorter depth. 22870, 00000, "ALTER TYPE with REPLACE option a non-object type" // *Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type // *Action: drop the non-object type first, then re-create it as an object type 22871, 00000, "ALTER TYPE with REPLACE is not allowed for pure incomplete types" // *Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure incomplete type // *Action: Completely define the original type, before using the ALTER TYPE with REPLACE option. 22872, 00000, "OID INDEX clause not allowed on tables with primary key based object identifiers" // *Cause: An attempt to create an OID INDEX on a table with primary key // based object identifiers. // *Action: Remove the OID INDEX clause 22873, 00000, "primary key not specified for primary key based object table" // *Cause: An attempt to create a primary key based object table without // specifying a primary key // *Action: Specify a primary key and retry the operation 22874, 00000, "attribute \"%s\" is not part of the type \"%s\"" // *Cause: Attribute specified in the user_defined clause is not an // attribute of the REF type // *Action: Ensure that the name specified in the user_defined // clause is the name of a valid attribute of the REF type 22875, 00000, "cannot drop primary key of an object table whose object identifier is primary key based" // *Cause: An attempt to drop the primary key of an object table which has // a primary key based object identifier // *Action: Remove the drop primary key clause 22876, 00000, "this user-defined type is not allowed or it cannot be used in this context" // *Cause: An attempt to create a kind of user-defined type which is not // allowed, or an attempt to create table columns or use default // constructor with a type on which these are not supported. // *Action: Ensure that the type is permitted in this context. 22877, 00000, "invalid option specified for a HASH partition or subpartition of a LOB column" // *Cause: One or more invalid options were encountered while parsing the // physical attributes of a LOB partition or subpartition. Either // the LOB partition is in a table partitioned using the HASH method, // or the LOB subpartition is in a table subpartitioned using the // HASH method. TABLESPACE is the only valid option for a HASH // partition or subpartition. // *Action: Remove the invalid option(s). // *Comment: This error could result from omission of a // terminating (right) parenthesis following the list of // subpartition descriptions. 22878, 00000, "duplicate LOB partition or subpartition specified" // *Cause: An attempt was made to specify a partition or subpartition that // has already been specified for the LOB column. // *Action: Remove the duplicate specification. 22879, 00000, "cannot use the LOB INDEX clause for partitioned tables" // *Cause: An attempt was made to specify a LOB INDEX clause in a CREATE // TABLE or ALTER TABLE statement for a partitioned table. // *Action: Remove the LOB INDEX clause. / / / Put errors here. / / 22880 - 22899 Reserved for object SQL REF/DEREF Support / (parse, semantics, type checkin, execution/KOKA) / 22880, 00000, "invalid REF" // *Cause: An invalid REF was accessed. // *Action: Modify the REF and retry the operation. / 22881, 00000, "dangling REF" // *Cause: The object corresponding to the REF that was accessed does not // exist. // *Action: Ensure that the REF value is pointing to an existing object. / 22882, 00000, "object creation failed" // *Cause: The object cannot be created in the database. // *Action: Check to see if the object table exists and the object size is // not too big. Then retry the operation. / 22883, 00000, "object deletion failed" // *Cause: The object could not be deleted from the database. // *Action: Check to see if the object table exists.Then retry the operation. / 22884, 00000, "object modification failed" // *Cause: The object could not be modified in the database. // *Action: Check to see if the object table exists and the object size is // not too big. Then retry the operation. 22885, 00000, "cannot get REF to a non-persistent object" // *Cause: An attempt was made to get a REF for something other than an // object in an object table. REFs can only be taken for objects // in object tables. // *Action: Rewrite the query to obtain REF values from object tables. 22886, 00000, "scoped table \"%s\" in schema \"%s\" is not an object table" // *Cause: The scoped table specified for a REF column is not an object // table. // *Action: Ensure that the scoped table is an object table.Then retry the // operation. 22887, 00000, "type of REF column is not the same as that of its scoped table" // *Cause: The type specified for the REF column and the type specified // for the scope table are different. // *Action: Ensure that the types of a REF column and its scoped table are // the same. 22888, 00000, "duplicate SCOPE clauses for a REF column" // *Cause: Multiple SCOPE clauses were specified for a single REF column. // *Action: Remove the duplicate SCOPE clauses and retry the operation. 22889, 00000, "REF value does not point to scoped table" // *Cause: An attempt was made to insert a REF value that does not point // to the scoped table. // *Action: Ensure that the REF values point to the scoped table. 22890, 00000, "cannot specify name for REF column constraint" // *Cause: An attempt was made to specify a constraint name for a // constraint on a REF column. // *Action: Remove the constraint name and retry the operation. 22891, 00000, "cannot have multiple columns in REF constraint" // *Cause: An attempt was made to specify multiple columns in a single // REF constraint. // *Action: Specify separate constraints for each column and retry the // operation. 22892, 00000, "scoped table \"%s\" does not exist in schema \"%s\"" // *Cause: The scoped table specified for a REF column does not exist. // *Action: Ensure that the scoped table exists and retry the operation. 22893, 00000, "constraint can be specified only for REF columns" // *Cause: The constraint specified does not apply to non-REF columns. // *Action: Remove the constraint and retry the // operation. 22894, 00000, "cannot add constraint on existing unscoped REF columns of non-empty tables" // *Cause: An attempt was made to add a constraint to existing unscoped // REF columns of a table which contains one or more rows. // *Action: Remove the constraint specification or add the constraint after // emptying the table. 22895, 00000, "referenced table \"%s\" in schema \"%s\" is not an object table" // *Cause: The referenced table specified for a REF column is not an object // table. // *Action: Ensure that the referenced table is an object table.Then retry the // operation. 22896, 00000, "cannot have both scope and referential constraint on REF column \"%s\"" // *Cause: REF column has both a referential and a scope constraint. A // referential constraint implies a scope constraint. // *Action: Remove either the referential or scope constraint and then // retry the operation. 22897, 00000, "no scope clause specified for user-defined REF column \"%s\"" // *Cause: User-defined REF column does not have a scope constraint. // *Action: Specify a scope constraint for the user-defined REF column and // retry the operation. 22898, 00000, "existing scope clause on \"%s\" points to a table other than the one mentioned in the referential constraint" // *Cause: Table mentioned in the referential integrity constraint is // different from the scope table of the REF column. // *Action: Specify the scope table of the REF column in the referential // integrity constraint and then retry the operation. 22899, 00000, "cannot specify both scope and rowid constraint on ref column" // *Cause: An attempt was made to specify both a scope and a rowid constraint // on a REF column. // *Action: Remove either the rowid or scope constraint and then // retry the operation. / / / / 22900 - 22919 Reserved for SQL Nested Tables and collections / (parse, semantics, type checkin, execution) / 22900, 00000, "the SELECT list item of THE subquery is not a collection type" // *Cause: The THE subquery must SELECT a nested table or VARRAY item. // *Action: change the subquery to SELECT a nested table or VARRAY item. / 22901, 00000, "cannot compare nested table or VARRAY or LOB attributes of an object type" // *Cause: Comparison of nested table or VARRAY or LOB attributes of an // object type was attempted in the absence of a MAP or ORDER // method. // *Action: define a MAP or ORDER method for the object type. / 22902, 00000, "CURSOR expression not allowed" // *Cause: CURSOR on a subquery is allowed only in the top-level // SELECT list of a query. // *Action: / 22903, 00000, "MULTISET expression not allowed" // *Cause: MULTISET expressions are allowed only inside a CAST // to a nested table or VARRAY type. // *Action: put the MULTISET(subquery) expression inside a CAST to a // nested table or VARRAY type. / 22904, 00000, "invalid reference to a nested table column" // *Cause: invalid use of a nested table column // *Action: remove invalid reference to the nested table column / 22905, 00000, "cannot access rows from a non-nested table item" // *Cause: attempt to access rows of an item whose type is not known at // parse time or that is not of a nested table type // *Action: use CAST to cast the item to a nested table type / 22906, 00000, "cannot perform DML on expression or on nested table view column" // *Cause: Attempted to perform a DML on an expression or on a nested table // view column where a nested table column of a base table is // expected. // *Action: Only nested table column of a base table is allowed in the DML. / 22907, 00000, "invalid CAST to a type that is not a nested table or VARRAY" // *Cause: Attempted to CAST to a type that is not a nested table or // VARRAY // *Action: Re-specify CAST to a nested table or VARRAY type. / 22908, 00000, "reference to NULL table value" // *Cause: The evaluation of the THE subquery or nested table column // resulted in a NULL value implying a NULL table instance. // The THE subquery or nested table column must identify a // single non-NULL table instance. // *Action: Ensure that the evaluation of the THE subquery or nested table // column results in a single non-null table instance. If happening // in the context of an insert statement where the THE subquery is // the target of an insert, then ensure that an empty nested table // instance is created by updating the nested table column of the // parent table's row specifying an empty nested table constructor. 22909, 00000, "exceeded maximum VARRAY limit" // *Cause: The total number of elements used in VARRAY construction // exceeds the specified VARRAY limit. // *Action: Don't use the more than the specified limit of elements for // VARRAY construction. 22910, 00000, "cannot specify schema name for nested tables" // *Cause: Table name was qualified with schema name in the nested table // column's (or attribute's) storage clause. // *Action: Re-specify the nested table item's storage clause without the // schema name qualification. By default, the storage table for the // nested table item is created in the same schema as the containing // table. / 22911, 00000,"duplicate storage specification for the nested table item" // *Cause: The storage clause is specified more than once for the NESTED // TABLE column. // *Action: Remove the duplicate storage specification. / 22912, 00000,"specified column or attribute is not a nested table type" // *Cause: The storage clause is specified for a column or attribute // that is not a nested table column or attribute. // *Action: Specify a valid nested table column or attribute. / 22913, 00000,"must specify table name for nested table column or attribute" // *Cause: The storage clause is not specified for a nested table column // or attribute. // *Action: Specify the nested table storage clause for the nested table // column or attribute. / 22914, 00000,"DROP of nested tables not supported" // *Cause: Attempted to DROP a nested table. // *Action: nested tables cannot be explicitly dropped. nested tables can // only be dropped by dropping their containing parent table. / 22915, 00000,"cannot ALTER nested tables to ADD/MODIFY columns" // *Cause: Attempt was made to ADD or MODIFY columns of a nested table. // *Action: Columns cannot be added or modified for a nested table. You must // alter the parent table's nested table column to cause any such // change. / 22916, 00000,"cannot do an exact FETCH on a query with Nested cursors" // *Cause: Exact FETCH on a query was specified which is not allowed if // the query returns any cursors. // *Action: Do not use an exact FETCH. / 22917, 00000,"use VARRAY to define the storage clause for this column or attribute" // *Cause: Not using VARRAY to define storage clause for VARRAY column or // attribute. // *Action: Specify VARRAY before the column storage clause and resubmit // statement. / 22918, 00000,"specified column or attribute is not a VARRAY type" // *Cause: Attemp to define a VARRAY storage clause for a column or // attribute which is not VARRAY type. // *Action: Specify VARRAY storage clause for a VARRAY column or attribute. / 22919, 00000, "dangling REF error or lock object failed for no wait request" // *Cause: The error could be one of the following. The object corresponding // to the REF does not exist or the object was locked // by another user and the lock with nowait request failed. // *Action: Ensure that the REF value is pointing to an existing object or // issue a lock request without the nowait option. / / Put errors here. / / 22920 - 22929 Reserved for SQL LOBs / 22920, 00000, "row containing the LOB value is not locked" // *Cause: The row containing the LOB value must be locked before // updating the LOB value. // *Action: Lock the row containing the LOB value before updating the LOB // value. 22921, 00000, "length of input buffer is smaller than amount requested" // *Cause: The buffer length is not big enough to hold the amount of data // requested. // *Action: Verify that the number of bytes/characters specified in the // input amount parameter is not bigger than the number of bytes // specified in the input buffer length parameter. Allocate more // space for the input buffer if necessary. 22922, 00000, "nonexistent LOB value" // *Cause: The LOB value associated with the input locator does not exist. // The information in the locator does not refer to an existing LOB. // *Action: Repopulate the locator by issuing a select statement and retry // the operation. 22923, 00000, "amount of data specified in streaming LOB write is 0" // *Cause: Trying to write LOB value via the streaming mechanism (i.e. // unlimited write) but the input amount of data to stream was // specified as 0. Thus, the user is trying to write 0 bytes to // the LOB value. // *Action: Write more than 0 bytes to the LOB value. 22924, 00000, "snapshot too old" // *Cause: The version of the LOB value needed for the consistent read was // already overwritten by another writer. // *Action: Use a larger version pool. 22925, 00000, "operation would exceed maximum size allowed for a LOB value" // *Cause: Trying to write too much data to the LOB value. LOB size is // limited to 4 gigabytes. // *Action: Either start writing at a smaller LOB offset or write less data // to the LOB value. 22926, 00000, "specified trim length is greater than current LOB value's length" // *Cause: The input length for which to trim the LOB value to is greater // than the current length of the LOB value. // *Action: May not need to trim the LOB value because it's already smaller // than the trim length specified. Or, if trimming the LOB value // really is required, use a smaller trim length. 22927, 00000, "invalid LOB locator specified" // *Cause: There are several causes: (1) the LOB locator was never // initialized; (2) the locator is for a BFILE and the routine // expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a // BLOB/CLOB/NCLOB and the routine expects a BFILE locator; // (4) trying to update the LOB in a trigger body -- LOBs in // trigger bodies are read only. // *Action: For (1), initialize the LOB locator by selecting into the locator // variable or by setting the LOB locator to empty. For (2) and (3), // pass the correct type of locator into the routine. For (4), // remove the trigger body code that updates the LOB value. 22928, 00000, "invalid privilege on directories" // *Cause: An attempt was made to grant or revoke an invalid privilege on a // directory. // *Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or // revoked on directories. Do not grant or revoke other privileges. 22929, 00000, "invalid or missing directory name" // *Cause: The required directory name is invalid or missing. // *Action: Specify a valid name. / Put errors here. / / 22930 - 22949 Reserved for object SQL Dictionary Support / 22930, 00000, "directory does not exist" // *Cause: Attempt to access a directory that does not exist. // *Action: Make sure the name is correct. 22932, 00000, "event to create tables in 8.0 image format" // *Document: NO // *Cause: N/A // *Action: Causes adt columns to be stored in 8.0 format. / Put errors here. / / 22950 - 22969 Reserved for object SQL Method Support / 22950, 00000, "cannot ORDER objects without MAP or ORDER method" // *Cause: an object type must have a MAP or ORDER method defined for // all comparisons other than equality and inequality comparisons. // *Action: Define a MAP or ORDER method for the object type // / 22951, 00000, "NULL returned by ORDER method" // *Cause: ORDER method used to compare two object values returned NULL // which is not allowed. // *Action: Redefine the ORDER method to not return a NULL. // / / 22970 - 22989 Reserved for object Views / 22970, 00000, "name does not correspond to an object view" // *Cause: Either the expression is not a view name or the name // specified does not correspond to an object view. // *Action: Replace the expression with the name of an object view. // 22971, 00000, "invalid datatype for PRIMARY KEY-based object identifier" // *Cause: When creating an object view, the datatype of an expression // in the WITH OBJECT OID clause is not allowed for // PRIMARY KEY-based OID. // *Action: Replace the expression with one of appropriate scalar datatype. // 22972, 00000, "NULL value not allowed in PRIMARY KEY-based object identifier" // *Cause: A value constituting the PRIMARY KEY-based object identifier is // NULL. // *Action: Ensure the expressions in MAKE_REF system function or attributes // in the WITH OBJECT OID clause of an object view do not evaluate // to NULL. // 22973, 00000, "size of object identifier exceeds maximum size allowed" // *Cause: Size of the PRIMARY KEY-based object identifier of an object // view exceeds the maximum size of 65535 bytes. // *Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH // object OID clause when creating the object view. // 22974, 00000, "missing WITH OBJECT OID clause" // *Cause: WITH OBJECT OID clause is not specified when creating an object // view. // *Action: Specify the WITH OBJECT OID clause. 22975, 00000, "cannot create a PRIMARY KEY-based REF to this object view" // *Cause: The object view specified in the MAKE_REF function does not // have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based // REF cannot be created for such a view. // *Action: Specify an object view that has a PRIMARY KEY-based object // identifier in the MAKE_REF function. 22976, 00000, "incorrect number of arguments to MAKE_REF" // *Cause: Number of arguments for MAKE_REF is different from the number // of PRIMARY KEY attributes of the object view. // *Action: Specify all the necessary arguments for MAKE_REF. 22977, 00000, "missing or invalid attribute" // *Cause: Either the attribute name is missing in the WITH OBJECT OID clause // or it is invalid. // *Action: Specify a valid attribute of the object type of the object view. 22978, 00000, "only simple attribute name is allowed in the WITH OBJECT OID clause" // *Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID // clause. // *Action: Specify a top-level attribute of the object type of the object // view. 22979, 00000, "cannot INSERT object view REF or user-defined REF" // *Cause: Attempt to insert an object view REF or user-defined REF in a // REF column created to store system generated REF values" // *Action: Make sure the REF to be inserted is not from an object view // or from a user-defined REF column 22980, 00000, "must specify a set of attributes for the WITH OBJECT OID clause" // *Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying // view or table does not have a OID. // *Action: Specify attributes for the WITH OBJECT OID clause to create a // primary key based object identifier for the object view. 22981, 00000, "must specify a table/view having system generated OID" // *Cause: The super-view is based on a table/view having the system generated // OID and the sub-view must also be based on a similar table/view. // *Action: Specify table/view having system generated OID and retry the // the operation. 22982, 00000, "cannot create sub-view under this view" // *Cause: The view derives its OID from a table/view having primary key based // OID and sub-views cannot be created under such views. // *Action: Specify view having system generated OID or a view created with // the specification of attributes in the WITH OBJECT ID clause // and retry the operation. 22983, 00000, "not a user-defined REF" // *Cause: Attempt to use a system generated REF value where a // user-defined REF value should be used. // *Action: Make sure the REF value is user-defined. 22984, 00000, "view query cannot contain references to a super view" // *Cause: The query defining the view contains references to a super-view // of the view being created. // *Action: Make sure that the view query does not reference a super-view. / / / / 22990 - 22999 Reserved for SQL LOBs / 22990, 00000, "LOB locators cannot span transactions" // *Cause: A LOB locator selected in one transaction cannot be used in // a different transaction. // *Action: Re-select the LOB locator and retry the operation. 22991, 00000, "insufficient space allocated for argument %s" // *Cause: The data to be returned in the argument is greater than the // amount of space allocated for the argument. // *Action: Allocate more space for the argument. / 22992, 00000, "cannot use LOB locators selected from remote tables" // *Cause: A remote LOB column cannot be referenced. // *Action: Remove references to LOBs in remote tables. / 22993, 00000, "specified input amount is greater than actual source amount" // *Cause: (1) For LOB write, the amount of data received is different // from the amount that was indicated would be sent. (2) For // LOB copy and loadfromfile, the end of the source LOB/FILE // value was reached before the specified input amount was // copied/loaded. // *Action: (1) will happen when using OCI's piecewise mechanism with polling // or with a callback function. Modify the code either to send // the amount specified or to pass 0 as the input amount so that any // amount of data can be sent. (2) will happen if the specified // input amount is too large for the source LOB/FILE given the // starting source offset. Either decrease the starting source // offset, or decrease the amount to copy/load. / 22994, 00000, "source offset is beyond the end of the source LOB" // *Cause: The source offset for a LOB COPY or LOB LOADFROMFILE // is beyond the end of the source LOB. // *Action: Check the length of the LOB and then adjust the source offset. / 22995, 00000, "TABLESPACE DEFAULT option is invalid in this context" // *Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in // the following contexts: // - at the table level for a partitioned table // - at the partition level for a composite partition. // An attempt was made to use the TABLESPACE DEFAULT option in a // different context. // *Action: Remove the TABLESPACE DEFAULT option. / 22996, 00000, "NEXT extent size is smaller than LOB chunksize" // *Cause: An attempt was made to create or alter a LOB segment so that its // NEXT extent size was less than the LOB chunksize // *Action: Specify a NEXT extent size that is // greater than or equal to the LOB chunksize / 22997, 00000, "VARRAY stored as LOB is not specified at the table level" // *Cause: An attempt was made to specify a VARRAY column to be stored as LOB // at the partition/subpartition level in a partition maintenance // or a move table statement. However, the VARRAY column was not // specified to be stored as LOB at the table level when the table // was created. // *Action: Specify the VARRAY column to be stored as LOB at the table level // when the table is created. Alternatively, do not specify the VARRAY // column to be stored as LOB at the partition/subpartition level // if it is not specified at the table level when the table is created. / 22998, 00000, "CLOB or NCLOB in multibyte character set not supported" // *Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte // character set was passed to a SQL character function which // does not support multibyte LOB data. // *Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR() / or use PLSQL DBMS_LOB.READ/WRITE to access LOB data. / / 22999 IS THE MAXIMUM ERROR NUMBER for object SQL / / / 23000 - 23299 Reserved for object Management Subsystem (OMS) / / / 23300 - 24299 Reserved for errors from DBMS* pl/sql pakages / These messages are generated from the dbms_sys_error package. / Messages can be given explicitly in this file or they can be passed as / a (single) string parameter to the / The dbms_sys_error.raise_system_error call. / If an error message is not found in this file, the string passed to the / call is used as the error message. / /////////////////////////////////////////////////////////////////////////////// // 23300-23999 Reserved for Replication PL/SQL packages /////////////////////////////////////////////////////////////////////////////// 23300, 00000, "%s" // *Cause: The stored procedure 'raise_system_error' // was called which causes this error to be generated. // *Action: Correct the problem as described in the error message or contact // the application administrator or DBA for more information. 23301, 00000, "mixed use of deferred rpc destination modes" // *Cause: Replication catalog determined deferred RPC destinations were // mixed with destination determined by other mechanisms in the // same transaction. // *Action: Do not mix destination types in the same transaction. 23302, 00000, "application raised communication failure during deferred RPC" // *Cause: An application declared a communication failure during a // defered RPC. // *Action: Retry the application when communication is restored. 23303, 00000, "application raised generic exception during deferred RPC" // *Cause: An application declared a generic failure during a // defered RPC. // *Action Determined by the application 23304, 00000, "malformed deferred rpc at arg %s of %s in call %s, in tid %s" // *Cause: A deferred RPC call was issued without the correct number of // arguments as determined by the count parameter to dbms_defer.call // *Action: Be sure the number of actuals matches the count. 23305, 00000, "internal deferred RPC error: %s" // *Cause: An internal error occurred in deferred rpc. // *Action: Report the error and other information to support. 23306, 00000, "schema %s does not exist" // *Cause: The schema name was null or misspelled, or the schema does not // exist locally. // *Action: Specify the schema correctly, or create it with CREATE USER. 23307, 00000, "replicated schema %s already exists" // *Cause: The given database already replicates the given schema. // *Action: Choose a different schema or a different database. 23308, 00000, "object %s.%s does not exist or is invalid" // *Cause: The given name was null or misspelled, the given type was wrong, // the object does not exist as a valid database object, or the object // does not exist as a replicated object with the appropriate status. // *Action: Ensure the object is valid in the database, is visible to the // user, and, if appropriate, is a valid object in all_repobject. 23309, 00000, "object %s.%s of type %s exists" // *Cause: An object in the same namespace exists, perhaps with a different // type or shape, or the same object has already been registered as an // repobject in another object group. // *Action: Remove the offending object with the SQL DROP command, unregister // the offending object with dbms_repcat.drop_master_repobject(), or // reinvoke the request using TRUE for a boolean parameter such as // retry or use_existing_object. 23310, 00000, "object group \"%s\".\"%s\" is not quiesced" // *Cause: The requested operation requires the object group to be // suspended. // *Action: Invoke suspend_master_activity at the repgroup's masterdef, // wait until the status has changed to quiesced, and then retry the // original request. 23312, 00000, "not the masterdef according to %s" // *Cause: The group name is null, the group name is misspelled, the // invocation or given database is not the masterdef, or one of the // masters does not believe the invocation database is the masterdef. // *Action: If the given group name and masterdef were both correct, // connect to the masterdef and retry the request, or relocate the // masterdef at the (errant) databases using relocate_masterdef. 23313, 00000, "object group \"%s\".\"%s\" is not mastered at %s" // *Cause: The group name is null, the group name is misspelled, the // invocation database is not a master, or the invocation database // does not believe the given database is a master. // *Action: If the given group name was correct, connect to a current master // and retry the request, make the invocation database a master // with add_master_database, or use switch_mview_master if the // invocation database is a materialized view site. 23314, 00000, "database is not a materialized view site for \"%s\".\"%s\"" // *Cause: The invocation database is not a materialized view database for the // given object group. // *Action: Connect to the desired materialized view database and retry the // request, or make the invocation database a materialized view site // with create_mview_repschema or create_mview_repgroup. 23315, 00000, "repcatlog version or request %s is not supported by version %s" // *Cause: Either incompatible repcat versions are used, or a repcatlog record // has been corrupted. // *Action: Convert the master to a compatible version of repcat or retry // the request. 23316, 00000, "the masterdef is %s" // *Cause: The requested operation is not permitted on a masterdef site. // *Action: Relocate the masterdef to another master and retry the operation. 23317, 00000, "a communication failure has occurred" // *Cause: The remote database is inaccessible. // *Action: Ensure the remote database is running, the communications network // is functioning, and the appropriate database links are present. 23318, 00000, "a ddl failure has occurred" // *Cause: User-supplied or system-generated ddl did not execute successfully. // *Action: Examine ddl, database state, repcatlog, and all_errors to determine // why the failure occurred. 23319, 00000, "parameter value %s is not appropriate" // *Cause: The given value of a parameter is either null, misspelled, or not // supported. // *Action: Refer to the documentation and use parameter values that are // appropriate for the given situation. 23320, 00000, "the request failed because of values %s and %s" // *Cause: A missing ddl record for a repcatlog record, or inconsistency in // repcat views. // *Action: Retry the request, or make the views consistent. // 23321, 00000, "Pipename may not be null" // *Cause: You called dbms_pipe with a null pipe name. // *Action: Find out the name of the pipe and call function with non-null // pipename. 23322, 00000, "Privilege error accessing pipe" // *Cause: You either tried to create a pipe that already existed and // belonged to someone else, or remove a pipe that you were not // authorized to use, or put a message into a pipe that you were // not authorized for, or get a message from a pipe that you were // not authorized for. // *Action: You may have to use a different pipename. 23323, 00000, "parameter length exceeds deferred RPC limits" // *Cause: A deferred rpc parameter was longer than the deferred rpc limits // of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw // parameters. // *Action: Use smaller parameters. 23324, 00000, "error %s, while creating deferror entry at \"%s\" with error %s" // *Cause: The given error was encountered while attempting to create a // deferor entry for the give error code and the give database. // *Action: Correct the cause of the given error. 23325, 00000, "parameter type is not %s" // *Cause: A conflict resolution priority function was given a type // different than the type assigned to the priority group; // or the priority group has no type assigned or a function; // or dbms_defer_sys_query was called to retrieve a deferred rpc // parameter from the deferred rpc queue, but the type of the // parameter does not match the return type of the function. // *Action: Use the function corresponding to the parameter type. 23326, 00000, "object group \"%s\".\"%s\" is quiesced" // *Cause: Either suspend_master_activity has been called before the object // group has resumed normal operation or a (deferred) rpc operation // was attempted while the object group was quiesced. // *Action: If suspend_master_activity has been called and a // resume_master_activity request is pending, wait until it // completes, and then reinvoke suspend_master_activity. // Otherwise, resume database activity with the resume_master_activity // call. 23327, 00000, "imported deferred rpc data does not match %s of importing db" // *Cause: Deferred rpc queues were imported from a database with a different // global name or operating system than importing database. // *Action: Deferred rpc data should only be imported into a database with // the same global name and hardware and operating system. 23328, 00000, "mview base table \"%s\".\"%s\" differs from master table \"%s\".\"%s\"" // *Cause: When creating a materialized view through repcat, the materialized // view base table name did not match a replicated table name at the // master. // *Action: Change the materialized view ddl to use the same base table as the // replicated table name at the master. // 23329, 00000, "successful user-provided ddl but no materialized view \"%s\".\"%s\"" // *Cause: The DDL provided by the user to create a materialized view was // executed without error, but materialized view does not exist. // *Action: Manually back-out the DDL, and reregister with matching ddl // and materialized view. // 23330, 00000, "column group %s already exists" // *Cause: The column group was already registered in the object group. // *Action: Use a column group name not yet registered in the replicated // object group. // 23331, 00000, "column group %s does not exist" // *Cause: The given column group is either null, misspelled or not registered. // *Action: Use a registered column group. // 23332, 00000, "group %s is in use; cannot drop" // *Cause: The given column group or priority group is being used to // resolve conflicts. // *Action: Call dbms_repcat procedures drop_update_resolution, // drop_delete_resolution, drop_unique_resolution so that the column // group or priority group is no longer in use before dropping. // 23333, 00000, "column %s is already part of a column group" // *Cause: Attempted to add a column to a column group when the column was // already a member of a column group. // *Action: Drop the column from its existing column group before trying // to add it to another. // 23334, 00000, "column %s does not exist in table or column group" // *Cause: The given column is either null, misspelled or is not part of the // given table or column group. // *Action: Use a column that is a member of the table or column group. // 23335, 00000, "priority group %s already exists" // *Cause: The priority group was already registered in the object group. // *Action: Use a column group name not yet registered in the object group. // 23336, 00000, "priority group %s does not exist" // *Cause: The priority group was already registered in the object group. // *Action: Use a priority group name not yet registered in the object group. // 23337, 00000, "priority or value not in priority group %s" // *Cause: The specified value or priority has not been registered // as part of the priority group. // *Action: Either specify a different value or priority that is already part // of the priority group, or add the value to the priority group. // 23338, 00000, "priority or value already in priority group %s" // *Cause: The specified value or priority has already been registered // as part of the priority group. // *Action: Either specify a different value or priority that not already part // of the priority group, or drop the value to the priority group. // 23339, 00000, "duplicate conflict resolution information" // *Cause: The specified combination of column group, sequence, conflict // type and/or parameter table name, parameter column name, // and parameter sequence number has already been registered. // *Action: Verify that additional conflict resolution information // needs to be added and provide a new sequence number. If // modifying existing information, the existing information must // be dropped first. // 23340, 00000, "incorrect resolution method %s" // *Cause: User function is specified when conflict resolution method was // not "USER FUNCTION" or specified resolution method is not one of // the predefined methods. // *Action: If user function is specified when conflict resolution method was // not "USER FUNCTION", either reregister function with method as // "USER FUNCTION" or specify a NULL user function. Otherwise // Specify one of the documented supported conflict resolution methods. // 23341, 00000, "user function required" // *Cause: A NULL user function was specified for the "USER FUNCTION" method. // *Action: Provide user function name (e.g., "schema"."package"."function") // that conforms to the documented user function specifications or // specify one of the documented supported conflict resolution methods. // 23342, 00000, "invalid parameter column %s" // *Cause: The parameter column name is null or misspelled, the // invocation database is not a master, or is of the wrong type // for the specified conflict resolution method. // *Action: Specify a parameter column from the specified column group // that has a correct type for the conflict resolution method. // 23343, 00000, "no match for specified conflict resolution information" // *Cause: The specified combination of column group, sequence, conflict // type has not been registered (e.g., for adding a comment). // *Action: Specify a combination of column group, sequence, conflict // type has been registered. // 23344, 00000, "constraint (%s.%s) does not exist" // *Cause: A null, misspelled or nonexistent constraint was specified // when registering a uniqueness conflict. // *Action: Register a named constraint for the specified table. // 23345, 00000, "table \"%s\".\"%s\" not registered to collect statistics" // *Cause: A procedure that deals with conflict resolution statistics-gathering // was called for a table that was not registered to collect // statistics. // *Action: Call dbms_repcat.register_statistics to register the table. // 23346, 00000, "primary key or object ID is undefined for table or materialized view %s" // *Cause: Trying to generate replication support for a table or materialized // view without a primary key (as defined by a constraint or // dbms_repcat.set_columns) or an object ID. // *Action: For a table, add a primary key constraint or define a primary // key using dbms_repcat.set_columns or use object tables. // For a ROWID materialized view, set min_communication to false // or use primary key or object ID materialized views. // 23347, 00000, "datatype %s for column %s table %s not supported" // *Cause: The table has a column whose datatype is not supported by repcat. // *Action: Remove the column from the table, or alter the column to have // one of the supported datatypes. // 23348, 00000, "cannot replicate procedure %s; only IN parameters supported" // *Cause: Trying to generate replication support for a package that has // a procedure with OUT or IN OUT parameters. // *Action: Remove the procedure from the package, or remove the OUT or IN OUT // parameters from the procedure. // 23349, 00000, "cannot generate replication support for functions" // *Cause: Trying to generate replication support for a package that has // a public function, or for a stand-alone function. // *Action: Remove the public function from the package, or alter the function // to be a procedure. // 23350, 00000, "maximum number of recursive calls exceeded" // *Cause: This usually occurs when trying to resolve conflicts in a table // while concurrent updates to the same row create more conflicts. // *Action: Re-execute the deferred transaction from DefError using // dbms_defer_sys.execute_error // 23351, 00000, "parameter datatype %s for procedure %s not supported" // *Cause: The procedure has a parameter whose datatype is not supported by // repcat. // *Action: Remove the parameter from the procedure, or alter the parameter // to have one of the supported datatypes. 23352, 00000, "duplicate destination for deferred transaction" // *Cause: A duplicate destination was specified for a deferred transaction // either in a dbms_defer.call call or an earlier // dbms_defer.transaction call or a dbms_defer_sys.add_default_dest // call. // *Action: Remove the duplicate entry 23353, 00000, "deferred RPC queue has entries for object group \"%s\".\"%s\"" // *Cause: The requested action cannot be performed until the queue is empty // for the given object group // *Action: Use dbms_defer_sys.execute or dbms_defer_sys.delete_tran to // empty the queue. 23354, 00000, "deferred RPC execution disabled for \"%s\" with \"%s\"" // *Cause: Deferred RPC can not be executed at the destination with // the specified catchup value because their propogation has // been disabled. // *Action: Enable deferred RPC execution with the // dbms_defer_sys.set_disabled call. // 23355, 00000, "object %s.%s does not exist or is invalid at master site" // *Cause: The given name was null or misspelled, the given type was wrong, // the object does not exist as a valid database object at the master // site, or the object does not exist as a replicated object with // the appropriate status. // *Action: Ensure the object is valid in the master database, and is visible // to the user, and, if appropriate, is a valid object in // all_repobject. 23356, 00000, "masterdef recognizes a master which does not recognize the masterdef" // *Cause: Possibly drop_master_repgroup was run at a master site but // remove_master_databases was not run at master definition site // for that master. // *Action: Run remove_master_databases from master definition site to // remove the appropriate master (see associated error messages). 23357, 00000, "the propagator does not exist" // *Cause: The propagator does not exist. // *Action: Register a new propagator. // 23358, 00000, "invalid remote user" // *Cause: The local user does not match the remote user connected via // a database link. // *Action: Drop and recreate the identified database link with the // connect-to user identical to the owner of the database link. // 23359, 00000, "error on creating a ddl record for a repcatlog record" // *Cause: The userid in the repcatlog record does not match the userid // of the connected user. // *Action: Retry the operation with a different user. // 23360, 00000, "only one materialized view for master table \"%s\" can be created" // *Cause: Trying to create more than one materialized view on a given master // table in the same rep group. // *Action: Create these other materialized views in a different rep group at // another site. // 23361, 00000, "materialized view \"%s\" does not exist at master site" // *Cause: The materialized view does not exist at the master site for offline // instantiation of the materialized view. // *Action: The correct procedure is to create the materialized view in a // different schema at the master site, and then follow the // instructions for offline instantiation of materialized views. // 23362, 00000, "invalid user" // *Cause: The given user does not exist. // *Action: // 23363, 00000, "mismatch of mview base table \"%s\" at master and mview site" // *Cause: The name of the base table of the materialized view at the master // site is different from the base table at the materialized view // site. This error may arise during offline instantiation of // materialized views. // *Action: Retry offline instantiation with a materialized view name less than // 24 bytes // 23364, 00000, "Feature not enabled: Advanced replication" // *Cause: The Advanced Replication feature is not enabled at this site. // Updatable materialized views, deferred RPCs, and other replication // features are, therefore, unavailable. // *Action: Do not attempt to use this feature. Contact an Oracle Customer // Support representative if the Advanced Replication feature has // been purchased but not enabled. // 23365, 00000, "site %s does not exist" // *Cause: site specified in argument "reference_site" or argument // "comparison_site" in call to "differences()" routine // or "rectify()" routine does not name an existing site. // *Action: Make sure that database sites specified really do exist, // and re-run the routine. // 23366, 00000, "integer value %s is less than 1" // *Cause: Value of argument "max_missing" to routine "differences()" // cannot be less than 1. Value of argument "commit_rows" to // routines "differences()" and "rectify()" cannot be less than 1. // *Action: Choose an integer value for those arguments to be 1 or greater. // 23367, 00000, "table %s is missing the primary key" // *Cause: Table specified in argument "oname1" or "oname2" in call // to "differences()" routine does not contain either a primary // key or a virtual primary key (defined through dbms_repcat package // under symmetric replication). // *Action: Make sure the tables specified have a primary key defined. // 23368, 00000, "name %s cannot be null or the empty string" // *Cause: Argument "sname1," "sname2," "oname1," "oname2," // "missing_rows_sname," "missing_rows_oname1," // "missing_rows_oname2" to "differences()" or "rectify()" // cannot be NULL or '' (empty string). // *Action: Change argument to non-null or non-empty string. // 23369, 00000, "value of \"%s\" argument cannot be null" // *Cause: Argument "max_missing" to "differences()" routine // cannot be NULL. // *Action: Legal values for "max_missing" are integers 1 or greater. // 23370, 00000, "table %s and table %s are not shape equivalent (%s)" // *Cause: The tables specified are not shape equivalent, which means // intuitively that the number of columns, the names, their datatypes // and lengths are not the same. Specifically, problem is // in the parentheses and is one of the following: the number of // columns are not equal, datatypes of columns with // same name in different tables are different, lengths of // varchar2 and char columns are not equal, precision and // scale of number datatypes are not equal. // *Action: Make sure the two tables being compared have the same // number of columns, same column names, and same datatypes. // 23371, 00000, "column %s unknown in table %s" // *Cause: Some column in "array_columns" argument (or "column_list" argument) // to "differences()" routine does not correspond to a column in // the specified table. // *Action: Make sure that all the columns in either "array_columns" or // "column_list" are present in the specified table. // 23372, 00000, "type %s in table %s is unsupported" // *Cause: Certain types in the table comparison utility are not supported. // *Action: Make sure that the types of columns in the tables to be compared // are the ones supported by symmetric replication. // 23373, 00000, "object group \"%s\".\"%s\" does not exist" // *Cause: The group name was null or misspelled, or the group does not // exist locally. // *Action: Specify the group correctly, or create it with // dbms_repcat.create_master_repgroup(). // 23374, 00000, "object group \"%s\".\"%s\" already exists" // *Cause: The given database already replicates the given object group. // A materialized view repgroup cannot be created at a given site // where a master repgroup with the same name already exists. // *Action: Choose a different group or a different database. // 23375, 00000, "feature is incompatible with database version at %s" // *Cause: A feature not compatible with the specified database was used // *Action: Set or raise the value of the "compatible" INIT.ORA parameter // to match the necessary compatibility level. // 23376, 00000, "node %s is not compatible with replication version \"%s\"" // *Cause: A feature not compatible with the remote database was used // *Action: Upgrade the remote database and retry the operation // 23377, 00000, "bad name %s for missing_rows_oname1 argument" // *Cause: An attempt was made to use the name of the reference site table // as the name of the missing_rows_oname1 argument. // *Action: Provide a separately created table with a different name for // missing_rows_oname1 argument. The separately created table will // contain the differences between the tables being compared. // 23378, 00000, "connection qualifier \"%s\" is not valid for object group \"%s\".\"%s\"" // *Cause : The connection qualifier used in the database link for the // specified object group does not match the qualifier specified for // the group in create_master_repgroup. // *Action: Use or create a database link which contains the correct connection // qualifier. // 23379, 00000, "connection qualifier \"%s\" is too long" // *Cause: The maximum length of a database link, including the connection // qualifier, is 128 bytes. // *Action: Use a shorter connection qualifier, or shorten the name of // the database link // 23380, 00000, "propagation mode \"%s\" is not valid" // *Cause: The specified propagation may be misspelled, or is not supported. // For materialized view sites, all materialized view object groups // at the same materialized view site with the same master object // group must all have the same propagation method. // *Action: Refer to the manual on replicated data for valid propagation modes. // For materialized view sites, also ensure that the propagation modes // of all materialized view object groups with the same master object // group are the same. // 23381, 00000, "generated object for base object %s.%s@%s does not exist" // *Cause: The system generated object(s) for the specified base object // do not exist at the specified site. The current operation // requires the base object to have generated replication support. // *Action: Ensure that the generated replication object(s) for the base // object exist and are valid at the specified site. // If the generated object(s) do not exist, then the procedure // dbms_repcat.generate_replication_support() needs to be // called from the master definition site for the base object. // missing_rows_oname1 argument. The separately created table will // contain the differences between the tables being compared. 23382, 00000, "materialized view repgroup \"%s\".\"%s\" is not registered at site %s" // *Cause: The materialized view repgroup is not currently registered at // the master and so cannot be unregistered. // *Action: None // 23383, 00000, "registration for materialized view repgroup \"%s\".\"%s\" failed at site %s" // *Cause: Insertion into local repschema table failed. // *Action: None // 23384, 00000, "replication parallel push %s argument out of range" // *Cause: Specified numeric argument to dbms_defer_sys.push is invalid. // *Action: Fix the argument value and try again. // 23385, 00000, "replication parallel push %s argument not valid" // *Cause: Specified string argument to dbms_defer_sys.push is invalid. // *Action: Fix the argument value and try again. // 23386, 00000, "replication parallel push cannot create slave processes" // *Cause: An error was occurred while creating slave processes for // parallel push. // *Action: // 23387, 00000, "replication parallel push dequeue error" // *Cause: An attempt to dequeue a deferred transaction failed while trying // to assign a new queue batch number. // *Action: // 23388, 00000, "replication parallel push watermark error" // *Cause: An error occurred during parallel push while trying to update // the high-water-mark information in system.def$_destination. // *Action: // 23389, 00000, "obsolete procedure; drop objects and recreate using new master" // *Cause: dbms_repcat.switch_mview_master is no longer supported. // *Action: Drop the objects in the object group and recreate them using // the new master. // 23392, 00000, "could not find materialized view to be associated with \"%s\".\"%s\"" // *Cause: Could not find materialized view associated with a trigger or index // that is being pulled from the master site. // *Action: Ensure that materialized view, master, and master index or trigger // is registered as replicated objects. // 23393, 00000, "the user is already the propagator" // *Cause: The given user is already the current propagator. // *Action: // 23394, 00000, "duplicate propagator" // *Cause: More than one valid propagator exist. // *Action: Unregister any duplicate propagator. // 23395, 00000, "object \"%s\".\"%s\" of type \"%s\" does not exist or is invalid" // *Cause: The given name was null or misspelled, the given type was wrong, // the object does not exist as a valid database object, or the object // does not exist as a replicated object with the appropriate status. // *Action: Ensure the object is valid in the database, is visible to the // user, and, if appropriate, is a valid object in all_repobject. // 23396, 00000, "database link \"%s\" does not exist or has not been scheduled" // *Cause: the database link does not exist in the schema of the replication // propagator or has not been scheduled. // *Action: Ensure that the database link exists in the database, is accessible // and is scheduled for execution. // 23397, 00000, "global name \"%s\" does not match database link name \"%s\"" // *Cause: the database link name at the local node does not match the global // name of the database that the link accesses. // *Action: Ensure that global names is set to true and the link name matches // the global name. // 23398, 00000, "user name \"%s\" at database link \"%s\" does not match local user name \"%s\"" // *Cause: the user name of the replication administration user at // the local node and the user name at the node corresponding to the // database link are not the same. Symmetric replication expects the // two users to be the same. // // *Action: Ensure that the user ID of the replication administration user at // the local node and the user ID at the node corresponding to the // database link are the same. // 23399, 00000, "generation of replication support for \"%s\".\"%s\" is not complete" // *Cause: Replication support for the specified object has not been generated // or the generation process is not yet complete. // *Action: Ensure that replication support has been generated for the object. // Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate // replication support for the object. // 23400, 00000, "invalid materialized view name \"%s\"" // *Cause: A null, misspelled, or badly formed materialized view name was given // to dbms_mview.refresh. // *Action: Provide a valid materialized view name to dbms_mview.refresh. // 23401, 00000, "materialized view \"%s\".\"%s\" does not exist" // *Cause: A materialized view name was given to dbms_mview.refresh that is not // in sys.snap$ or its associated views. // *Action: Provide a materialized view name that is in sys.snap$, all_mviews // or user_mviews. // 23402, 00000, "refresh was aborted because of conflicts caused by deferred txns" // *Cause: There are outstanding conflicts logged in the DefError table // at the materialized view's master. // *Action: Resolve the conflicts in the master DefError table and // refresh again after the table is empty. Alternatively, // refresh with refresh_after_errors set to TRUE, which // will proceed with the refresh even if there are conflicts // in the master's DefError table. Proceeding despite conflicts // can result with an updatable materialized view's changes appearing // to be temporarily lost (until a refresh succeeds after the // conflicts are resolved). // 23403, 00000, "refresh group \"%s\".\"%s\" already exists" // *Cause: Making a new refresh group when there is already a group of // the same name in sys.rgroup$. // *Action: Choose a diifferent refresh group name. // 23404, 00000, "refresh group \"%s\".\"%s\" does not exist" // *Cause: A refresh group name was given that is not in sys.rgroup$. // *Action: Provide a refresh group name that is in sys.rgroup$ or dbs_rgroup. // 23405, 00000, "refresh group number %s does not exist" // *Cause: A refresh group number was given that is not in sys.rgroup$. // *Action: Provide a refresh group number that is in sys.rgroup$ or dbs_rgroup. // 23406, 00000, "insufficient privileges on user \"%s\"" // *Cause: The caller is not the owner of the materialized view and does not // have ALTER ANY MATERIALIZED VIEW privileges. // *Action: Perform the operation as the owner of the materialized view or as a // user with ALTER ANY MATERIALIZED VIEW privileges. // 23407, 00000, "object name %s must be shaped like \"schema\".\"object\" or \"object\"" // *Cause: The object name (e.g., the rollback segment, the materialized view // name, the refresh group) was incorrectly specified. // *Action: Retry the operation with the object name properly specified // (like "schema"."object" or "object") // 23408, 00000, "this replication operation is not supported in a mixed configuration" // *Cause: operation is not supported if the object group is replicated at a // pre-V8 node. // // *Action: Ensure that all nodes of the replicated object group are V8. // 23409, 00000, "could not find an unused refresh group number" // *Cause: 1000 consecutive refresh group numbers, as defined by the // rgroupseq number, were already used by rows in sys.rgroup$. // *Action: Alter the sequence number to be within a legal unused range // and destroy unneeded refresh groups. // 23410, 00000, "materialized view \"%s\".\"%s\" is already in a refresh group" // *Cause: A materialized view of the same name is already in a refresh group. // *Action: Subtract the materialized view from the current refresh group and // add it to its new refresh group, or combine the two refresh // groups into a single refresh group. // 23411, 00000, "materialized view \"%s\".\"%s\" is not in refresh group \"%s\".\"%s\"" // *Cause: The specified materialized view is not in the specified refresh // group. // *Action: Try again with the proper materialized view and refresh group // names. // 23412, 00000, "master table's primary key columns have changed" // *Cause: The master table's primary key constraint was modified after // the primary key materialized view was created. // *Action: Drop and recreate the primary key materialized view // 23413, 00000, "table \"%s\".\"%s\" does not have a materialized view log" // *Cause: The fast refresh can not be performed because the master table // does not contain a materialized view log. // *Action: Use the CREATE MATERIALIZED VIEW LOG command to create a // materialized view log on the master table. // 23414, 00000, "materialized view log for \"%s\".\"%s\" does not record rowid values" // *Cause: A rowid materialized view is being fast refreshed, but the // materialized view log does not record rowid information. // *Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin // recording rowid information in the materialized view log. // 23415, 00000, "materialized view log for \"%s\".\"%s\" does not record the primary key" // *Cause: A primary key materialized view is being fast refreshed, but the // materialized view log does not record primary key information. // *Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to // begin recording primary key information in the materialized view // log. // 23416, 00000, "table \"%s\".\"%s\" does not contain a primary key constraint" // *Cause: The master table does not constaint a primary key constraint or // the primary key constraint has been disabled. // *Action: Create a primary key constraint on the master table or enable the // existing constraint. // 23417, 00000, "unknown materialized view type: %s" // *Cause: A fast refresh is being performed on a materialized view of an // unknown or unsupported type. // *Action: Check all_mviews and ensure that the materialized view being // refreshed a valid materialized view. // 23418, 00000, "cannot unregister the propagator who is currently in use" // *Cause: The propagator is currently used in propagating replication RPCs. // *Action: Try again later when there is no transaction active in // propagating replication RPCs. // 23419, 00000, "regenerate replication support before resuming master activity" // *Cause: There are tables in the object group that require regeneration // of replication support. // *Action: Check the generation_status column in the all_repobjects view. // Regenerate replication support for any table in the object group // with a 'NEEDSGEN' status. Resume master activity. // 23420, 00000, "interval must evaluate to a time in the future" // *Cause: The parameter "interval" evaluates to a time earlier than SYSDATE. // *Action: Choose an expression that evaluates to a time later than SYSDATE. // 23421, 00000, "job number %s is not a job in the job queue" // *Cause: There is no job visible to the caller with the given job number. // *Action: Choose the number of a job visible to the caller. // 23422, 00000, "Oracle Server could not generate an unused job number" // *Cause: Oracle Server could not generate a job number that was not used to // identify another job. // *Action: Retry the operation. // 23423, 00000, "job number %s is not positive" // *Cause: The given job number is less than 1. // *Action: Choose a positive integer. // 23424, 00000, "materialized view \"%s\".\"%s\" at %s not registered" // *Cause: The specified materialized view has not be successfully registered // at this site. // *Action: Register the materialized view manually at either the master site // or the materialized view site. // 23425, 00000, "invalid materialized view identifier %s" // *Cause: The argument provided to dbms_mview.purge_mview_from_log is // an invalid materialized view identifer or it does not identify an // Oracle 8 fast refreshable materialized view or the materialized view // has been already purged. // *Action: If the materialized view is an Oracle 8 fast refreshable // materialized view then provide purge_mview_from_log with its valid // materialized view identifier. // 23426, 00000, "deferred RPC queue has entries for %s" // *Cause: The requested action cannot be performed until the queue is empty // for the given site/dblink // *Action: Use dbms_defer_sys.push, dbms_defer_sys.purge_queue // or dbms_defer_sys.delete_tran to empty the queue. // 23427, 00000, "deferred purge queue argument %s out of range" // *Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid. // *Action: Fix the argument value and try again. // 23428, 00000, "job associated instance number %s is not valid" // *Cause: A job is associated with an instance that is not running. // *Action: Choose a running instance for job affinity, or set force // parameter to TRUE. // 23430, 00000, "argument \"%s\" cannot be NULL or empty string" // *Cause: The caller has provided an argument whose value cannot be // NULL or the empty string. // *Action: Check that the varchar2 value provided is not NULL or the // empty string, and retry the call. // 23431, 00000, "wrong state: %s" // *Cause: The routine was executed against a replicated object group // that was in the wrong state. // *Action: Make sure that the replicated object group is in the // state given in the error message. // 23432, 00000, "master site %s already exists" // *Cause: An attempt was made to instantiate a replicated object group // at a master site that was already a part of the object group. // *Action: If you were trying to add this site, do nothing because it // already exists; otherwise, pick the name of another site, // and re-run the routine. // 23433, 00000, "executing against wrong master site %s" // *Cause: An attempt was made to execute the routine at a site // that is different from the site specified in the argument // of the routine. // *Action: Provide an argument to the routine that correctly indicates // the site against which the routine should be executing. // 23434, 00000, "master site %s not known for object group" // *Cause: The site name given as an argument to a routine was not already // known to the replicated object group. // *Action: Execute the dbms_offline_og.begin_instantiation() routine to // add a new site to the replicated object group. // 23435, 00000, "cannot create an updatable ROWID materialized view with LOB columns" // *Cause: The propagation of LOB data from materialized view sites to the // master site requires a primary key on the replicated table. Thus // updatable ROWID materialized views that contain LOB columns are not // supported. // *Action: Create a primary key materialized view instead of a ROWID // materialized view. If the materialized view already exists, it can // be converted to a primary key materialized view using the ALTER // MATERIALIZED VIEW DDL command. // 23436, 00000, "missing template authorization for user" // *Cause: The specified template authorization does not exist. // *Action: Check the values for user name and refresh template name to // ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS // view. // 23437, 00000, "template authorization already exists for user" // *Cause: The specified user already has been authorized to use the // specified refresh group template. // *Action: Check the values for user name and refresh template name or // query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that // the correct values were passed as parameters. // 23438, 00000, "missing refresh group template" // *Cause: The specified refresh group template does not exist. // *Action: Verify that the refresh group template does not exist by // querying the DBA_REPCAT_REFRESH_TEMPLATES view. // 23439, 00000, "refresh group template already exists" // *Cause: The specified refresh group template already exists. // *Action: Verify that the refresh group template exists by querying // the DBA_REPCAT_REFRESH_TEMPLATES view. // 23440, 00000, "incorrect public template value" // *Cause: The public template parameter is not 'Y', 'N' or NULL. // *Action: Correct the value of the public template parameter. It must // be 'Y','N' or NULL. // 23441, 00000, "object does not exist for refresh group template" // *Cause: The specified object does not exist in the refresh group template. // *Action: Correct the object name and object type parameters. Check // the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct // name and type of the object. // 23442, 00000, "object already exists for the refresh group template" // *Cause: The specified object already exists in the refresh group // template. // *Action: Change the object name and object type paramters. Query // the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct // name and type of the object. // 23443, 00000, "missing template parameter" // *Cause: The specified template parameter does not exist. // *Action: Correct the template parameter value and execute the procedure // again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the // name of the refresh group template and parameter name. // 23444, 00000, "duplicate template parameter" // *Cause: The template parameter already exists for the specified // refresh group template. // *Action: Correct the template parameter value and execute the procedure // again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the // name of the refresh group template and paramter name. // 23445, 00000, "missing template site" // *Cause: The template site specified by the site name, user name and // refresh group template name does not exist. // *Action: Correct the invalid paramter and execute the procedure again. // Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing // template sites. // 23446, 00000, "duplicate template site" // *Cause: The template site specified by the site name, user name and // refresh group template name already exists. // *Action: Correct the invalid parameter and execute the procedure again. // Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing // template sites. // 23447, 00000, "missing user parameter value" // *Cause: The user parameter value specified by the user name, // parameter name and refresh group template name does not exist. // *Action: Correct the invalid parameter and execute the procedure again. // Use the DBA_REPCAT_USER_PARMS view to query the existing // user parameters. // 23448, 00000, "duplicate user parameter value" // *Cause: The user parameter value specified by the user name, // parameter name and refresh group template name already exists. // *Action: Correct the invalid parameter and execute the procedure again. // Use the DBA_REPCAT_USER_PARMS view to query the existing // user parameters. // 23449, 00000, "missing user name" // *Cause: The user specified by the user name parameter does not exist // in the database. // *Action: Correct an invalid user name or create the user in the // master database. Use the DBA_USERS view to select the valid // database users. // 23450, 0000, "flavor already contains object \"%s\".\"%s\"" // *Cause: The flavor already contains the specified object. // *Action: Check that the specified object is correct. To add all // columns of a table object, delete the object from the // flavor and then add it again. // 23451, 0000, "flavor %s already defined for object group \"%s\".\"%s\"" // *Cause: The given object group already contains a (possibly unpublished) // definition of the specified flavor. // *Action: Check the spelling of the flavor name. Check for an unpublished // flavor of the desired name. // 23452, 0000, "flavor %s of object group \"%s\".\"%s\" is already published" // *Cause: The given object group already contains a (published) definition // of the specified flavor. // *Action: Check the spelling of the flavor name. // // 23453, 00000, "requested operation is not supported on top flavor" // *Cause: The TOP flavor has a NULL name and may not be directly defined // or deleted. // *Action: Supply the name of a flavor other than the TOP flavor or use // dbms_repcat routines to implicitly change the TOP flavor. // 23454, 00000, "flavor %s not defined for object group \"%s\".\"%s\"" // *Cause: The given object group does not contain a (published) definition // of the specified flavor. // *Action: Check the spelling of the flavor name. Ensure the flavor has // been defined (and published) for the object group. // 23455, 00000, "flavor %s contains object \"%s\"" // *Cause: The given flavor contains the object to be dropped. // *Action: Purge the flavor or choose another object to drop. // 23456, 00000, "flavor %s does not contain \"%s\"" // *Cause: The flavor does not contain the given object, column, or // attribute. // *Action: Either drop the flavor or choose a different object, column, // or attribute. // 23457, 00000, "invalid flavor ID %s" // *Cause: The given flavor ID is invalid. // *Action: Make sure this flavor has been instantiated. If the flavor ID is // outside the range (-2147483647, 2147483647), contact customer // support. // 23458, 00000, "inappropriate flavor %s at %s" // *Cause: The given flavor at the given database prevents the // operation from succeeding. // *Action: Either change the database flavor or choose a different // operation. // 23459, 00000, "flavor %s must contain \"%s\"" // *Cause: The flavor must contain the given object, column, or // attribute. // *Action: Either choose a different database flavor or ensure the // object, column, or attribute is available. // 23460, 00000, "missing value for column %s in resolution method \"%s\" for \"%s\".\"%s\".\"%s\"" // *Cause: before resolving conflicts, some values necessary resolving // conflicts are not available, // or after resolving conflicts, some values necessary for // re-trying of the SQL are not available // *Action: define appropriate flavors, provide necessary values through // availability vector in USER FLAVOR FUNCTION for conflict // resolution 23461, 00000, "fail to resolve conflict for \"%s\".\"%s\".\"%s\"" // *Cause: // // *Action: // 23462, 0000, "flavor %s in use at site %s" // *Cause: The given flavor cannot be deleted because it is being used // at the given site. // *Action: Change the flavor of the site, or unregister it if it is // a materialized view site. // 23463, 0000, "flavor incompatible with object \"%s\".\"%s\"" // *Cause: An existing flavor includes the specified object with // an incompatible type. // *Action: Change the type of the object, or delete the flavor if it is // not in use. // 23464, 0000, "flavor lacks column %s of \"%s\".\"%s\"" // *Cause: The flavor includes some columns of an object group but not // all the required columns. // *Action: Change the flavor definition to include all required columns. // 23465, 0000, "flavor already includes column %s of \"%s\".\"%s\"" // *Cause: The flavor includes the specified column which // is being added. // *Action: Check that the specified column is correct. // 23466, 0000, "flavor requires missing object \"%s\".\"%s\"" // *Cause: The flavor includes the specified object which // does not exist // *Action: Check that the specified object name is correct, and // create the object if appropriate. // 23467, 0000, "flavor lacks object \"%s\".\"%s\"" // *Cause: The flavor does not include the specified object which // is being dropped. // *Action: Check that the specified object is correct. // 23468, 0000, "missing %s %s" // *Cause: The template is missing the object with the specified key. // *Action: Add the object to the template. // 23469, 0000, "%s is different between templates" // *Cause: The values for the specified columns are different in // each template for the same key values. // *Action: Correct the column values to make the templates the same. // 23470, 0000, "invalid status" // *Cause: The status should be DELETED, INSTALLING or INSTALLED. // Any other status is invalid. // *Action: Check that the specified status value is correct. // 23471, 0000, "template not authorized for user" // *Cause: The refresh template is private and the user has not // been authorized to instantiate the template. // *Action: Authorize the user to use the template. // 23472, 0000, "materialized view \"%s\".\"%s\" must be atomically refreshed" // *Cause: Non-atomic refresh is not supported for the specified materialized // view. // *Action: Set the value of the ATOMIC parameter to FALSE in the refresh // procedure being used or remove the specified materialized view from // the set of materialized views being refreshed. // 23473, 0000, "replication RPC processing for \"%s\".\"%s\" is disabled" // *Cause: The processing of replication RPCs for the object group that // contains this object is disabled. This includes RPCs in the error // queue. // *Action: Processing of replication RPCs is disabled when the object group // is being offline instantiated. Wait until offline instantiation is // finished. // 23474, 0000, "definition of \"%s\".\"%s\" has changed since generation of replication support" // *Cause: The current columns in the specified table and their column types // do not match the columns and column types when replication support // was last generated. // *Action: Regenerate replication support for the affected table. // All flavors that include the specified table should be checked // for validity. Types for any UDT columns should also be checked // for validity. // 23475, 0000, "key column %s must be sent and compared" // *Cause: The specified column is a key column and must be // sent and compared during replication propagation. // *Action: Make sure every key column is sent and compared. // // 23476, 00000, "cannot import from %s to %s" // *Cause: This object was imported from a database with a different // global name than the importing database. // *Action: Only import this object into a database with the // same global name. // 23477, 00000, "unable to alter propagation mode for object group \"%s\".\"%s\"" // *Cause: The propagation method of a materialized view object group can only // be altered when no other object groups with the same master object // group are sharing the materialized view site. // *Action: Ensure that there are no other materialized view object groups at // the local site with the same master object group. // 23478, 00000, "object group \"%s\" is already mastered at %s" // *Cause: There is at least one other materialized view repgroup at the local // site with the same group name but a different master site. // *Action: Ensure that all materialized view repgroups at the local site with // the same group name have the same master. 23480, 00000, "Column %s is not a top-level column of \"%s\".\"%s\"." // *Cause: The column is either not a top-level column // or is not present in the table or materialized view. // *Action: Ensure only valid top-level columns are used. 23481, 00000, "unexpected name string \"%s\"" // *Cause: // *Action: 23482, 00000, "column %s of \"%s\".\"%s\": object types not allowed." // *Cause: The column is of Object Type. // *Action: Ensure that all the columns are not of Object Type. 23483, 00000, "object \"%s\".\"%s\" not allowed in this operation." // *Cause: The specified operation does not support the given object. // *Action: Do not invoke the operation for this object. 23484, 00000, "internal internet Application Server error: %s" // *Cause: An internal error occurred in internet Application Server. // *Action: Report the error and other information to support. 23485, 00000, "Column group \"%s\" must consist of a single numeric column only" // *Cause: The column group doesn't contain only one numeric column. // *Action: Use a column group containing a single numeric column. 23487, 00000, "object groups \"%s\".\"%s\" and \"%s\".\"%s\" do not have the same connection qualifier" // *Cause: The specified two object groups do not have the same connection // qualifier. // *Action: Do not invoke the operation on the above object groups, or // ensure they have the same connection qualifier. 23488, 00000, "propagation mode \"%s\" for \"%s\" is not allowed for this operation" // *Cause: This operation does not support the specified dblink in the above // propagation mode. // *Action: Do not invoke the operation for this dblink, or change the // propagation mode for this dblink. 23489, 00000, "duplicate entry \"%s\"" // *Cause: The specified value is duplicated in the parameter list. // *Action: Remove duplicated entries in the parameter list. 23490, 00000, "extension request \"%s\" with status \"%s\" not allowed in this operation" // *Cause: The specified operation is not allowed for the extension request // with the specified status. // *Action: Ensure the extension request has the appropriate status before // retrying this operation. 23491, 00000, "no valid extension request at \"%s\"" // *Cause: The specified database does not have a valid extension request. // *Action: Ensure there is a valid extension request in DBA_REPEXTENSIONS // view before retrying this operation. 23492, 00000, "no new sites for extension request \"%s\"" // *Cause: There is no new site with the specified extension request. // *Action: Ensure there is at least one new site in DBA_REPSITES_NEW view // for this request before retrying this operation. 23493, 00000, "\"%s\" is not a new site for extension request \"%s\"" // *Cause: The specified extension request does not include the specified // site as a new site. // *Action: Ensure the specified site is a new site for this extension request // before retrying this operation. 23494, 00000, "too many rows for destination \"%s\"" // *Cause: The specified destination has too many rows in // system.def$_destination table. // *Action: Ensure the specified destination has at most two valid rows before // retrying this operation. 23495, 00000, "serial propagation can not be used for \"%s\"" // *Cause: The sites involved may be in the process of adding a new site // without quiescing. // *Action: Check the def$_destination table for this destination and // try parallel propagation. 23496, 00000, "can not change disabled status for \"%s\" and \"%s\"" // *Cause: The disabled status for this site is set internally for // synchronization during adding a new master without // quiescing. // *Action: Ensure adding a new master without quiescing finished // before invoking this procedure. // 23500, 00000, "cannot switch master for a multi-tier materialized view repgroup \"%s\".\"%s\"" // *Cause: An attempt was made to switch master for a materialized view // repgroup when its parent repgroup is also a materialized view // repgroup. This is not allowed. // *Action: Drop and recreate the materialized view repgroup based on // a proper parent repgroup. 23501, 00000, "refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0" // *Cause: Instantiation of a refresh template is not supported for // database compatibility 8.0 or less. // *Action: Be sure the database compatibility is 8.1 or above. // 23502, 00000, "valid directory for offline instatiation is not specified" // *Cause: An attempt was made to offline instantiate to // a directory which is not specified or null. // *Action: There are two ways to specify the directory: // o As a parm offline_dirpath to the API // o As an init.ora parm named utl_file_dir // Make sure you have specified an appropriate // directory in which the offline file can be created. // 23503, 00000, "error occurred during IAS instantiation" // *Cause: An attempt was made to instantiate a IAS site. Error occurred // during IAS instantiation. // *Action: See other errors on the error stack to look for the source of // the problem. If the error still persists, contact Oracle Support. 23504, 00000, "columns added to table do not match list of columns to be added" // *Cause: The list of columns passed as a parameter does not match the // columns to be added to the table. // *Action: Correct the DDL string or list of columns and rexecute. // 23505, 00000, "Object \"%s\".\"%s\" is missing." // *Cause: The specified object does not exist. // *Action: Check that the specified object is correct. // 23514, 00000, "invalid or incorrect number of arguments" // *Cause: The arguments passed to the online redefinition API were invalid // or missing. // *Action: Call the online redefinition API with the right number of valid // arguments. // 23515, 00000, "materialized views and/or their indices exist in the tablespace" // *Cause: An attempt was made to drop a tablespace which contains // materialized views and/or their indices. // *Action: Drop the materialized views in this tablespace. Also, // find indices belonging to materialized views in this // tablespace and drop then. Then try dropping the tablespace. // 23531, 00000, "site owner already exists in the template." // *Cause: Site owner for the template already exists. // *Action: Do not create multiple siteowners for this template. // 23532, 00000, "tables with different synchronization mechanisms are in the same group" // *Cause: Tables belonging to the same replication group were specified to // be cached with different synchronization mechanisms. // *Action: Do not specify different synchronization mechanisms while caching // tables belonging to the same replication group. // 23533, 00000, "object \"%s\".\"%s\" can not be cached" // *Cause: An attempt was made to cache an object which is not supported. // *Action: Do not cache an object which is not supported. // 23534, 00000,"missing column in materialized view container table \"%s\".\"%s\"" // *Cause: After import, the materialized view container table has missing // columns. // *Action: Check if materialized view container table was imported correctly. // 23535, 00000,"instantiating templates from multiple back ends is not allowed." // *Cause: An attempt was made to set a new non-null back end database for an // iAS site. // *Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink. // Then, call the same procedure with the new non-null dblink. // 23536, 00000, "the object \"%s\".\"%s\" is not cached at the middle tier as expected." // *Cause: The object may have been dropped or renamed at the back end // after dbms_ias_inst.start_ias_inst was executed. // *Action: Check the validity of the object at the back end and retry // the instantiation. 23537, 00000,"function or procedure %s is not allowed to be invoked from this site." // *Cause: This function or procedure is restricted to the backend or // middle tier site // *Action: Connect to the proper site before calling this function or procedure. // /////////////////////////////////////////////////////////////////////////////// // 24000 - 24099 - Reserved for ADMINISTRATIVE INTERFACE FOR AQ /////////////////////////////////////////////////////////////////////////////// 24000, 00000, "invalid value %s, %s should be of the form [SCHEMA.]NAME" // *Cause: An invalid value was specified for the paramerter. // *Action: Specify a string of the form [SCHEMA.]NAME . // 24001, 00000, "cannot create QUEUE_TABLE, %s already exists" // *Cause: The queue table already exists in the queueing system. // *Action: Drop the table first using the DROP_QUEUE_TABLE() command or // specify another table. // 24002, 00000, "QUEUE_TABLE %s does not exist" // *Cause: Queue_table not exist. // *Action: Query on the user view USER_QUEUE_TABLES to find out existing queue // tables. // 24003, 00000, "Queue table index %s inconsistent with queue table %s" // *Cause: The queue table index has not yet been successfully imported. // *Action: Import the queue table index before attempting to use the queue // table. If the import failed, correct the problem and try to import // the queue table index again. // // 24004, 00000, "invalid column name %s in SORT_LIST, should be ENQ_TIME or PRIORITY" // *Cause: Invalid column name was specified in the SORT_LIST. // *Action: The valid column names are ENQ_TIME and PRIORITY. // 24005, 00000, "must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables" // *Cause: An attempt was made to use the SQL command DROP TABLE for queue // tables, but DROP TABLE is not supported for queue tables. // *Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the // DROP TABLE command. // 24006, 00000, "cannot create QUEUE, %s already exists" // *Cause: The queue requested to be created already exists. // *Action: Specify another queue name. Query USER_QUEUES for all the exisiting // queues in the users's schema. // 24007, 00000, "invalid value %s, MAX_RETRIES should be non-negative integer" // *Cause: An invalid value was specified for MAX_RETRIES. // *Action: Specify a non-negative integer. // 24008, 00000, "queue table %s.%s must be dropped first" // *Cause: An error was detected when dropping a queue table in a cluster, // tablespace, or schema. // *Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified // queue table first; then, retry the operation. // 24009, 00000, "invalid value %s, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE" // *Cause: Invalid queue type parameter // *Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE // for exception queue. // 24010, 00000, "QUEUE %s does not exist" // *Cause: The specified queue does not exist. // *Action: Specify a valid queue. Query USER_QUEUES for all the valid // queues. // 24011, 00000, "cannot drop QUEUE, %s should be stopped first" // *Cause: The queue has not been stopped i.e. either enqueue or // dequeue is still enabled. // *Action: Stop the queue first using the STOP_QUEUE command and disable // it from both enqueueing and dequeueing. // 24012, 00000, "cannot drop QUEUE_TABLE, some queues in %s have not been dropped" // *Cause: A queue exists in the queue table which has not been dropped. // All queues need to be dropped first. // *Action: Drop all queues belonging to this queue table using the drop_queue() // command. Be sure to stop the queues appropriately before dropping // them. Alternately, use the force option in drop_queuetable. // 24013, 00000, "invalid value %s, RETRY_DELAY should be non-negative" // *Cause: A negative value was specified for RETRY_DELAY. // *Action: Specify a non-negative value for RETRY_DELAY. 24014, 00000, "invalid value %s, RETENTION_TIME should be FOREVER or non-negative" // *Cause: Queue retention was specified, but the retention time was // specified to be less than zero. // *Action: Specify the retention time to be non-negative or FOREVER. // Alternately don't specify retention. // 24015, 00000, "cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE %s.%s does not exist" // *Cause: An invalid QUEUE_PAYLOAD_TYPE specified during create_queue_table. // *Action: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already // exists in the database. // 24016, 00000, "cannot create QUEUE_TABLE, user %s does not have execute privileges on QUEUE_PAYLOAD_TYPE %s.%s" // *Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during // create_queue_table. // *Action: The user should have execute priviliges on the object type specified // for the queue. // 24017, 00000, "cannot enable enqueue on QUEUE, %s is an exception queue" // *Cause: User tried to enable enqueueing to an exception queue. // *Action: None. 24018, 00000, "STOP_QUEUE on %s failed, outstanding transactions found" // *Cause: There were outstanding transactions on the queue, and WAIT was set to // false, so STOP_QUEUE was unsucessful in stopping the queue. // // *Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all // outstanding transactions are completed. // 24019, 00000, "identifier for %s too long, should not be greater than %s characters" // *Cause: The identifier specified is too long. // *Action: Try again with a shorter identifier. // 24020, 00000, "Internal error in DBMS_AQ_IMPORT_INTERNAL, %s" // *Cause: Internal Error occured in the package DBMS_AQ_IMPORT_INTERNAL. // *Action: Internal error, call Oracle Support. // 24021, 00000, "queue table definition not imported for %s.%s" // *Cause: The queue definition is not updated because the queue table // was not imported properly // // *Action: Import the queue table again. 24022, 00000, "the specified parameters has no effect on the queue" // *Cause: The parameter combination will not cause the queue to // be started or stoped. // *Action: None. This is just a warning. // 24023, 00000, "Internal error in DBMS_AQ_EXP_INTERNAL.%s [%s] [%s]" // *Cause: Internal Error occured in the package DBMS_AQ_EXP_INTERNAL. // *Action: Internal error, call Oracle Support. // 24024, 00000, "Internal error in DBMS_AQ_IMP_INTERNAL.%s [%s] [%s]" // *Cause: Internal Error occured in the package DBMS_AQ_IMP_INTERNAL. // *Action: Internal error, call Oracle Support. // 24025, 00000, "invalid value %s, QUEUE_PAYLOAD_TYPE should be RAW or an object type" // *Cause: Parameter queue_payload_type has invalid value. // *Action: Specify a valid object type or RAW. // 24026, 00000, "operation failed, queue %s.%s has errors" // *Cause: An attempt was made to enqueue, dequeue or administer a queue which // has errors. // *Action: Drop the queue table setting the force option to true. // 24027, 00000, "AQ HTTP propagation encountered error, status-code %s, %s" // *Cause: AQ propagation's HTTP request to the propagation servlet at the // specified address encountered an error // *Action: Specify a valid address in the connect string of the propagation // destination dblink, the dblink user has the correct permissions, // check if the AQ propagation servlet was properly installed. 24028, 00000, "cannot create a reciever non-repudiable single consumer queue" // *Cause: Tried to create a reciever non-repudiable single consumer queue // *Action: This feature is not supported 24031, 00000, "invalid value, %s should be non-NULL" // *Cause: Parameter is NULL. // *Action: Specify a non NULL value for the parameter. // 24032, 00000, "object %s exists, index could not be created for queue table %s" // *Cause: Oracle AQ tried to create an index with the name // specified in the error message. The // index could not be created for the specified queue // table because a object exists with the same name. // *Action: Drop the object specified in the error message and retry the // command. You can also choose a different name for the queue table. // 24033, 00000, "no recipients for message" // *Cause: An enqueue was performed on a queue that has been set up for // multiple dequeuers but there were neither explicit recipients // specified in the call nor were any queue subscribers determined // to be recipients for this message. // *Action: Either pass a list of recipients in the enqueue call or add // subscribers to the queue for receiving this message. 24034, 00000, "application %s is already a subscriber for queue %s" // *Cause: An application name that was already a subscriber for the queue // was specified in the dbms_aq.subscribe call. // *Action: 24035, 00000, "AQ agent %s is not a subscriber for queue %s" // *Cause: An AQ agent that was not a subscriber for the queue // was specified. // *Action: Check the name and/or address of the agent and retry the call. // 24036, 00000, "invalid SORT_ORDER column %s specified for queue table " // *Cause: The create queue table command was issued with // message_grouping set to TRANSACTIONAL and a sort order column // other than priority. Only the priority column can be specified // in the sort order for queue tables with transactional grouping. // *Action: Change the sort order list in the create queue table command and // retry the call. // 24037, 00000, "schema %s in QUEUE_NAME is not same as schema %s in QUEUE_TABLE" // *Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE // is not the same as the schema specified in the QUEUE_TABLE // parameter. // *Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE // parameters and retry the command. // 24038, 00000, "RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue" // *Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero // RETRY_DELAY and a QUEUE_TABLE that was created for multiple // consumers and with COMPATIBLE parameter set to '8.0'. // *Action: Either set the RETRY_DELAY to zero or upgrade the queue table to // 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. // 24039, 00000, "Queue %s not created in queue table for multiple consumers" // *Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER // procedure, or an ENQUEUE with a non-empty recipient list, was // issued on a queue that was not created for multiple consumers. // *Action: Create the queue in a queue table that was created for // multiple consumers and retry the call. // // NLS_DO_NOT_TRANSLATE [24040,24040] 24040, 00000, "AQ tracing event" // *Cause: N/A // *Action: Event used to trace operation of AQ. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. // 24041, 00000, "propagation schedule exists for QUEUE %s and DESTINATION %s" // *Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair // which has an existing propagation schedule. // *Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and // then reissue the SCHEDULE_PROPAGATION call. // 24042, 00000, "no propagation schedule exists for QUEUE %s and DESTINATION %s" // *Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination // pair which has no existing propagation schedule. // *Action: Verify the spelling of the specified QUEUE and DESTINATION and // then reissue the call with the correct spelling. // 24043, 00000, "destination %s uses a reserved name, names with AQ$_ prefix are not valid" // *Cause: An attempt was made to specify a reserved name for a destination. // *Action: Enter a different value or NULL for the local destination. // Then retry the operation. // 24044, 00000, "source %s and destination %s object types do not match" // *Cause: A message recipient's queue has a different object structure // than the sender's queue. The message cannot be propagated. // // *Action: Either remove the recipient from the subscriber's list for the // sender's queue or create the destination queue with an object type // that matches the source queue's object type. // 24045, 00000, "invalid agent address %s, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]" // *Cause: An invalid value was specified for the agent address parameter. // *Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK]. // 24046, 00000, "protocol attribute reserved for future use" // *Cause: The protocol attribute of the AQ agent object type is reserved for // future use. // *Action: Do not specify the protocol attribute in the agent object type. // 24047, 00000, "invalid agent name %s, agent name should be of the form NAME" // *Cause: An invalid value was specified for the agent name parameter. // *Action: Specify a string of the form NAME. Then retry the operation. // 24048, 00000, "cannot create QUEUE_TABLE, user does not have access to AQ object types" // *Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but // the user who issued the command does not have access to internal // AQ object types. // *Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the // user access to the AQ object types. // 24049, 00000, "invalid agent name %s, names with AQ$_ prefix are not valid" // *Cause: An attempt was made to use a reserved prefix in the agent name. // *Action: Enter a different value for the agent name. Then, retry the // operation. // 24050, 00000, "subscribers are not supported for exception queue %s" // *Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER // procedure was issued on a queue that was created as an // EXCEPTION_QUEUE. // *Action: Specify a NORMAL_QUEUE in the procedure. // 24051, 00000, "cannot propagate object type payloads that have a REF or BFILE attribute" // *Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address // field in the agent type was issued on a queue whose payload has a // REF or BFILE attribute. Propagation of object type payloads // that have a REF or BFILE attribute currently is not supported. // *Action: Specify an agent with a NULL address field so that the agent can // dequeue from the same queue. Or, change the object type definition // to one that does not use REF or BFILE attributes. 24052, 00000, "cannot propagate object type payloads with LOB attributes to an 8.0 release" // *Cause: The recipient of a message with LOB attributes was using an Oracle // 8.0 release. Propagation of LOB attributes is supported only in // Oracle 8.1 and higher releases. // *Action: Upgrade the target release to Oracle 8.1 and retry. Or, change // the object type definition to one that does not use LOBs. 24053, 00000, "PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative" // *Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative. // *Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE. // 24054, 00000, "cannot propagate to an Oracle 8.0.3 release or lower release" // *Cause: The recipient of a message was using an Oracle 8.0.3 release or // lower release. Propagation is supported only in Oracle 8.0.4 and // higher releases. // *Action: Upgrade the target release to Oracle 8.0.4 or higher and retry. // // 24055, 00000, "cannot delete propagation status rows that are in prepared state" // *Cause: An attempt was made to use the internal administration procedure // to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table // that were in the prepared state. // *Action: Wait for the propagation to complete successfully before retrying // the operation. 24056, 00000, "internal inconsistency for QUEUE %s and destination %s" // *Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table // were inconsistent for the given queue and destination. // *Action: Contact Oracle Worldwide Support. // 24057, 00000, "cannot define subscriber with rule for queue %s" // *Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was // issued on a queue for which rule based subscribers are not // supported. Rule based subscribers currently are supported only // for NORMAL (persistent) multi-consumer queues created using an // Oracle release 8.1.0 or higher compatible queue table. // *Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 // or higher compatible queue table, and retry the call. // Or, if the queue is a normal (persistent) multi-consumer queue, // convert the queue table to Oracle 8.1.0 or higher compatibility // and retry. // 24058, 00000, "cannot downgrade QUEUE_TABLE that has propagation in a prepared state" // *Cause: An attempt was made to downgrade the queue table when there were // messages being propagated that were in the prepared state. // *Action: Wait for the propagation to complete before retrying the operation. // 24059, 00000, "invalid COMPATIBLE parameter setting %s specified in DBMS_AQADM.%s" // *Cause: An invalid compatible parameter was specified in the // DBMS_AQADM procedure. The parameter setting must be of the form // '8.x.y' where x is the release number and y is the update number. // *Action: Specify a valid COMPATIBLE parameter setting, and retry the // operation. // 24060, 00000, "cannot convert QUEUE_TABLE, %s already is compatible with release %s" // *Cause: The source queue table in the DBMS_AQADM procedure is // compatible with the specified COMPATIBLE parameter setting. // *Action: Choose a different COMPATIBLE parameter setting to convert the // queue table to the desired compatibility. // 24061, 00000, "cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero" // *Cause: A non-zero value was specified for SECONDARY_INSTANCE when // PRIMARY_INSTANCE was zero. // *Action: Specify a non-zero primary instance before you specify a non-zero // secondary instance. // // 24062, 00000, "Subscriber table %s inconsistent with queue table %s" // *Cause: The subscriber table has not yet been successfully imported. // *Action: Import the subscriber table before attempting to use the queue // table. If the import failed, correct the problem and try to import // the subscriber table again. 24063, 00000, "cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers" // *Cause: An attempt was made to downgrade the queue table when there were // queues on which rule based subscribers are defined. // *Action: Remove the rule based subscribers for all queues in this queue // table and retry. // 24064, 00000, "propagation for QUEUE %s and DESTINATION %s already enabled" // *Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and // destination pair whose propagation schedule already was enabled. // *Action: Make sure the QUEUE and DESTINATION are correct when you issue // the ENABLE_SCHEDULE_PROPAGATION command. // 24065, 00000, "propagation for QUEUE %s and DESTINATION %s already disabled" // *Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and // destination pair whose propagation schedule already was disabled. // *Action: Make sure the QUEUE and DESTINATION are correct when you issue // the DISABLE_SCHEDULE_PROPAGATION command. // 24066, 00000, "invalid privilege specified" // *Cause: An invalid privilege is specified for granting or revoking // privilege // *Action: Specify a valid privilege. // 24067, 00000, "exceeded maximum number of subscribers for queue %s" // *Cause: An attempt was made to add new subscribers to the specified, // but the number of subscribers for this queue has exceeded the // maximum number (1024) of subscribers allowed per queue. // *Action: Remove existing subscribers before trying to add new subscribers. // 24068, 00000, "cannot start queue %s, queue table %s is being migrated" // *Cause: An attempt was made to start a queue in a queue table that is // being migrated. // *Action: Complete the queue table migration, and retry the operation. // 24069, 00000, "cannot downgrade queue table %s while it is being upgraded" // *Cause: An attempt was made to downgrade a queue table, but a previous // command to upgrade the queue table has not yet completed // successfully. // *Action: Complete the upragde of the queue table by re-executing the // DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade // the queue table. 24070, 00000, "cannot upgrade queue table %s while it is being downgraded" // *Cause: An attempt was made to upgrade a queue table, but a previous // command to downgrade the queue table has not yet completed // succesfully. // *Action: Complete the downgrade of the queue table by re-executing the // DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the // queue table. 24071, 00000, "cannot perform operation %s, queue table %s is being migrated" // *Cause: An attempt was made to perform an operation on a queue in a // queue table that is being migrated. // *Action: Complete the queue table migration, and retry the operation. // 24072, 00000, "cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table" // *Cause: An attempt was made to upgrade or downgrade a queue table // using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the // user who executed the procedure does not own the queue. // *Action: Reconnect as the owner of the queue table, and then execute // the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. // 24073, 00000, "cannot specify RETENTION_TIME on exception queue %s.%s" // *Cause: An attempt was made to create or alter an exception queue by // specifying a non-zero RETENTION_TIME. // *Action: Use the default RETENTION_TIME parameter value for exception queues. // 24074, 00000, "RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %.%s" // *Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero // RETRY_DELAY and an exception queue. // *Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues. 24075, 00000, "cannot specify agent with NULL address and non-NULL protocol" // *Cause: An ADD_SUBSCRIBER or enqueue was attemoted with an agent that had // a NULL address and a non-NULL protocol. // *Action: Either specify a non-NULL address or set the protocol to NULL. // 24076, 00000, "cannot perform operation %s for NON_PERSISTENT queue %s.%s" // *Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, // DEQUEUE was issued for a NON_PERSISTENT queue. // *Action: Do not specify a NON_PERSISTENT queue for these operations. // 24077, 00000, "cannot create propagation schedule for EXCEPTION queue %s.%s" // *Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. // Propagation schedules can be created only for NORMAL queues. // *Action: To propagate messages from a queue specify the queue type // as NORMAL. // 24078, 00000, "cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL" // *Cause: A non-NULL value was specified for SECONDARY_INSTANCE when // PRIMARY_INSTANCE was NULL. // *Action: Specify a non-NULL primary instance before you specify a non-NULL // secondary instance. 24079, 00000, "invalid name %s, names with AQ$_ prefix are not valid for %s" // *Cause: An attempt was made to use a reserved prefix for the object name. // *Action: Enter a different name for this object. Then, retry the operation. 24080, 00000, "unschedule_propagation pending for QUEUE %s and DESTINATION %s" // *Cause: A propagation administration command was issued for a queue and // destination pair whose propagation is being unscheduled. // *Action: Do not issue propagation administration commands for a propagation // schedule on which there is a pending unschedule request. 24081, 00000, "compatible parameter needs to be %s or greater" // *Cause: The compatible parameter was not high enough to allow the operation. // *Action: shutdown and startup with a higher compatibility setting. 24082, 00000, "propagation may still be happening for the schedule for QUEUE %s and DESTINATION %s" // *Cause: The snapshot process executing the propagation schedule did not // respond to the disable propagation command. // *Action: Make sure that the job for the propagation schedule has been // ended. 24083, 00000, "cannot specify remote subscribers for %s QUEUE %s " // *Cause: An add_subscriber call with a non-null address field was issued on a // queue which does not support remote subscribers. Remote subscribers // are not supported for NON_PERSISTENT QUEUES. // *Action: Specify a null address field and retry the call. 24084, 00000, "DBLINK name in address field of agent %s is not unique within the first 24 bytes" // *Cause: Advanced Queuing requires that the agent's dblink name should // be unique within the first 24 bytes (for 8.0 compatible // queuetables) // *Action: Specify a dblink name that is unique within the first 24 // bytes or migrate to 8.1 compatible queuetables where this // restriction is not there. 24085, 00000, "operation failed, queue %s is invalid" // *Cause: An attempt was made to enqueue, dequeue or administer a queue which // is invalid. This could have occured because the payload type of the // queue's queue table was dropped. // *Action: Drop the queue table setting the force option to true. 24086, 00000, "cannot create a 8.0 compatible non-repudiable queue" // *Cause: Tried to create a 8.0 compatible non-repudiable queue // *Action: This feature is not supported 24087, 00000, "Invalid database user %s " // *Cause: An invalid database username was specified // *Action: Specify a valid database user // 24088, 00000, "user %s not registered for AQ internet access" // *Cause: This username has not been registered for AQ internet access // *Action: Specify a valid aq internet user. Check the AQ$INTERNET_USERS view // for a list of valid aq internet users // 24089, 00000, "user %s already registered for AQ internet access" // *Cause: This username has already been registered for http/smtp request // *Action: Specify another username or use the ALTER api to modify the user // information. // 24090, 00000, "at least one protocol must be enabled" // *Cause: No protocol was enabled for aq agent // *Action: Enable one of the protocols by setting one of the enable // parameters to true. // 24093, 00000, "AQ internet user %s not granted privileges of database user %s" // *Cause: The specified AQ internet user does not have privileges of the // specified database user // *Action: Specify a valid combination of AQ internet user and database user // 24094, 00000, "invalid transformation, target type does not match that of the queue" // *Cause: The target type of the transformation specified was different // from the type of the queue. // *Action: Provide a valid transformation whose target type is the same // as the queue type. 24095, 00000, "invalid transformation, source type does not match that of the queue" // *Cause: The source type of the transformation specified was different // from the type of the queue. // *Action: Provide valid transformation whose source type is the same // as the queue type. 24096, 00000, "invalid message state specified" // *Cause: Invalid value is specified for message state // *Action: Provide a valid message state as specified in the documentation 24097, 00000, "Invalid value %s, %s should be non-negative" // *Cause: A negative value or NULL was specified for the parameter. // *Action: Specify a non negative integer. 24098, 00000, "invalid value %s for %s" // *Cause: An Invalid value or NULL was specified for the parameter. // *Action: Check the documentation for valid values. 24099, 00000, "operation not allowed for 8.0 compatible queues" // *Cause: The specified operation is only supported for queues with // compatibility 8.1 or greater // *Action: Upgrade the 8.0 compatible queue to release 8.1 using // DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with // compatibility 8.1 / / 24100 - ERROR MESSAGE FOR THE TRANSACTION LAYER / 24100, 00000, "error in ktz testing layer" // *Cause: There is an error in the Transaction layer test ICDs // // *Action: // / 24120 - 24140 ERROR MESSAGES FOR THE DBMS_REPAIR PACKAGE / 24120, 00000, "invalid %s parameter passed to DBMS_REPAIR.%s procedure" // *Cause: An invalid parameter was passed to the specified DBMS_REPAIR // procedure. // *Action: Specify a valid parameter value or use the parameter's default. // 24121, 00000, "both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure" // *Cause: Both cascade and a block range were specified in a call to // DBMS_REPAIR.CHECK_OBJECT. // *Action: Use either cascade or a block range, or do not use either one. // 24122, 00000, "invalid block range specification" // *Cause: An incorrect block range was specified. // *Action: Specify correct values for the BLOCK_START and BLOCK_END // parameters. // 24123, 00000, "feature %s is not yet implemented" // *Cause: An attempt was made to use the specified feature, but the feature is // not yet implemented. // *Action: Do not attempt to use the feature. // 24124, 00000, "invalid ACTION parameter passed to DBMS_REPAIR.%s procedure" // *Cause: An invalid ACTION parameter was specified. // *Action: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION // parameter. // 24125, 00000, "Object %s.%s has changed" // *Cause An attempt was made to fix corrupt blocks on an object that // has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run. // *Action Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table // and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are // any corrupt blocks to be fixed. 24126, 00000, "invalid CASCADE_FLAG passed to DBMS_REPAIR.%s procedure" // *Cause: CASCADE_FLAG was specified for an object that is not a table. // *Action: Use CASCADE_FLAG only for tables. // 24127, 00000, "TABLESPACE parameter specified with an ACTION other than CREATE_ACTION" // *Cause: The TABLESPACE parameter can only be used with CREATE_ACTION. // *Action: Do not specify TABLESPACE when performing actions other than // CREATE_ACTION. // 24128, 00000, "partition name specified for a non-partitioned object" // *Cause: A partition name was specified for an object that is not // partitioned. // *Action: Specify a partition name only if the object is partitioned. // 24129, 00000, "table name %s does not start with %s prefix" // *Cause: An attempt was made to pass a table name parameter without the // specified prefix. // *Action: Pass a valid table name parameter. // 24130, 00000, "table %s does not exist" // *Cause: An attempt was made to specify a map, repair, or sync table that // does not exist. // *Action: Specify a valid table name parameter. // 24131, 00000, "table %s has incorrect columns" // *Cause: An attempt was made to specify a map, repair, or sync table that // does not have a correct definition. // *Action: Specify a table name that refers to a properly created table. // 24132, 00000, "table name %s is too long" // *Cause: An attempt was made to specify a table name is greater than 30 // characters long" // *Action: Specify a valid table name parameter. // / / 24141 - 24159 ERROR MESSAGES FOR THE DBMS_RULE PACKAGE / 24141, 00000, "ruleset specified does not exist" // *Cause: An attempt to access or modify a ruleset was made, which failed // because the ruleset does not exist. // *Action: Only access or modify existing rulesets. 24142, 00000, "invalid ruleset name" // *Cause: An attempt to create a ruleset with an invalid name was made. // The ruleset name can not be NULL, and can not be more // than 26 characters, unless a rules_table_name is also specified, // in which case the ruleset name may be up to 30 characters. // *Action: Retry the create with a valid ruleset name. 24143, 00000, "invalid table name" // *Cause: An attempt to create a ruleset on an invalid table name was made. // The data_table name can not be NULL, and can not be more // than 30 characters. The table with the name specified // must exist. // *Action: Retry the create with a valid table name. 24144, 00000, "rules engine internal error, arguments: [%s], [%s] " // *Cause: An internal error occurred in the rules engine. This indicates // that the rules engine has encountered an exception condition. // *Action: Please report this error as a bug. The first argument is the // error and the second argument is the package. / / 24180 - 242200 ERROR MESSAGES FOR THE DBMS_TRANSFORM PACKAGE / 24180, 00000, "invalid transformation expression, the transformation expression does not evaluate to the target type/attribute " // *Cause: The transformation expression does not evaluate to the target type // or the target type's specified attribute. // *Action: Provide valid transformation expression which evaluates to the // target type or the target type's specified attribute. 24181, 00000, "The type %s does not exist " // *Cause: The source or destination type for the transformation does not exist // *Action: Create the type or specify one that exists 24182, 00000, "attribute number specified does not exist " // *Cause: The target type of the transformation does not have the attribute // number specified in the ADD_ATTRIBUTE_TRANSFORMATION command // *Action: check the target type definition and specify a valid attribute // number 24183, 00000, "invalid transformation" // *Cause: The transformation specified is invalid because the source or // the target type have been dropped/modified. // *Action: Drop and recreate the transformation // 24184, 00000, "transformation %s.%s, already exists " // *Cause: A transformation of the given name already exists // *Action: Specify another name for the transformation being created. 24185, 00000, "Transformation %s.%s, does not exist" // *Cause: The transformation being specified does not exist. // *Action: Create the transformation before using it or specify an existing // transformation. 24186, 00000, "wrong object type, could not transform message" // *Cause: The object type of the message to be transformed does not match // the source type of the specified transfomation. // *Action: Specify another transformation, or specify a message of the // correct type. / / 24270 - 24279 ERROR MESSAGES FOR THE DBMS_HS SUPPORT PACKAGE / 24270, 00000, "a row already exists in the %s table for these parameters" // *Cause: A call was made to create a new row in the specified table. // A row already exists in the table with the specified values. // // *Action: Delete the existing row using the appropriate API or check // the parameters used to create the row. // 24271, 00000, "translation type must be either T, S or M" // *Cause: The translation type parameter is not a T, S or an M. A value // other than T, S or M was specified. // // *Action: Correct the translation type and reexecute the API call. // 24272, 00000, "initialization value must be either F or T" // *Cause: The initialization value must be either F or T. A value // other than F or T was specified. // // *Action: Correct the initialization value and reexecute the API call. // 24273, 00000, "translation text is required if translation type is T or S" // *Cause: If a translation type of T or S is specified, translation text // must be supplied. // // *Action: Provide translation text and reexecute the API call. // 24274, 00000, "no row exists in the %s table for these parameters" // *Cause: A call was made to update a row that does not exist or // a foreign key value supplied to create a table does // not exist. // // *Action: Create the row using the appropriate API or check // the parameters used to create the new row to ensure that // all specified values exist. // 24275, 00000, "function '%s' parameter '%s' missing or invalid" // *Cause: The function was called with a parameter // that was null, 0 length, or had an invalid value. // *Action: Correct the parameter to supply values that comply with // its datatype and limits as specified in the documentation. // 24276, 00000, "function '%s' output '%s' maximum value exceeded" // *Cause: The function computed a value for the // output that exceeded the maximum allowed. // This can occur when multiple input parameters, each valid // separately, combine to specify an invalid result. // For example, when a length parameter multiplied by a copies // parameter yields a total length exceeding the maximum for // the output datatype. // *Action: Correct the input values to produce a result that will // comply with the limits as specified in the documentation. / / / 24280-24299 Reserved for DBMS_LOB (FILE) package / / 24280, 00000, "invalid input value for parameter %s" // *Cause: The parameter has been provided a negative, out of range, or // NULL input value. // *Action: Correct the input value such that it is valid, and is within // the range as specified in the documentation. / 24281, 00000, "invalid access past the maximum size of LOB parameter %s" // *Cause: The value of positional or size parameters exceeds the maximum // allowed LOB size of 4 Gigabytes. // *Action: Correct the input values for amount and offset such that their // sum is less than or equal to 4 Gigabytes. If error occurs in // a read or write loop, check the looping conditions and/or offset // increments. / / / 24300 - 24999 Reserved for OCI/UPI/TTC/OPI/RPI/PSDs etc / / 24500 - 24550 Reserved for OCI codepoint length semantics and UTF16 / 24750 - 24800 Reserved for Transaction OCI / 24800 - 24849 Reserved for OCI Lob/File related Calls / 24850 - 24874 Reserved for Shared OCI / 24900 - 24949 Reserved for OCI Notification / 24950 - 24959 Reserved for PL/SQL Notification / 24300, 00000, "bad value for mode" // *Cause: An undefined mode value was specified. // *Action: Check that the correct mode is selected and that an allowed // value for that mode is specified. / 24301, 00000, "null host specified in thread-safe logon" // *Cause: An HDA was not specified in the logon call while running in a // thread safe environment. // *Action: Make sure that HDA is not NULL when calling the logon routine. / 24302, 00000, "host connection in use by another thread" // *Cause: An attempt was made to use the host connection while it was in use // by another thread. // *Action: Wait for another thread to finish before using this connection. / 24303, 00000, "call not supported in non-deferred linkage" // *Cause: One of the calls that is supported in deferred mode // linkage exclusively was invoked when the client was linked // non-deferred. // *Action: Use this call in deferred mode of linkage. / 24304, 00000, "datatype not allowed for this call" // *Cause: Data of this datatype cannot be sent or fetched in pieces. // *Action: Use other bind or define calls for this datatype. / 24305, 00000, "bad bind or define context" // *Cause: The call was executed on a cursor for which this is invalid. // *Action: Verify that this call is valid for this cursor. For example, Get // piece information and set piece information are valid on a cursor // if appropriate binds and defines have been done on this cursor. / 24306, 00000, "bad buffer for piece" // *Cause: A zero length buffer or a null buffer pointer was provided. // *Action: Verify that the buffer pointing to this piece or its length is // non-zero. The buffer pointer for the next piece or its length // can be zero if it is the last piece to be inserted and there are // no more data for the column. / 24307, 00000, "invalid length for piece" // *Cause: The length of the piece exceeded the maximum possible size. // *Action: Verify that the length of this piece and the cumulative length of // all the previous pieces is not more than the desired value supplied // by the application. / 24308, 00000, "illegal define position" // *Cause: Call to modify attributes was done for a non-existent position // *Action: Verify that a define has been done for this position / 24309, 00000, "already connected to a server" // *Cause: This server handle is already attached to a server. // *Action: Disconnect from the server and then retry the call to establish a // connection. / 24310, 00000, "length specified for null connect string" // *Cause: The connect string is null, but a length was specified for it. // *Action: Set length to zero if connect string is null. / 24311, 00000, "memory initialization failed" // *Cause: Cannot initialize user memory. // *Action: Contact customer support. / 24312, 00000, "illegal parameters specified for allocating user memory" // *Cause: An illegal size or null pointer was specified for user memory. // *Action: Specify a legal size and a valid pointer for user memory. / 24313, 00000, "user already authenticated" // *Cause: A user has already been authenticated on this service handle. // *Action: Terminate the service context before using it for another user. / 24314, 00000, "service handle not initialized" // *Cause: The server context does not done exist. // *Action: Establish the server context in the service context. / 24315, 00000, "illegal attribute type" // *Cause: An illegal attribute type was specified for the handle. // *Action: Consult user manual to specify an attribute valid for this handle. / 24316, 00000, "illegal handle type" // *Cause: An illegal handle type was specified. // *Action: Consult user manual to specify a valid handle type. / 24317, 00000, "define handle used in a different position" // *Cause: A define was done with an existing handle on a different position. // *Action: Specify the same position as before on a re-define. / 24318, 00000, "call not allowed for scalar data types" // *Cause: This call is valid only for object types. // *Action: Verify that the data-type for this variable is an object type / 24319, 00000, "unable to allocate memory" // *Cause: Process was unable to allocate memory to store diagnostics. // *Action: Terminate other processes in order to reclaim needed memory. 24320, 00000, "unable to initialize a mutex" // *Cause: An attempt to initialize a mutex failed. // *Action: Contact customer support. 24321, 00000, "inconsistent parameters passed" // *Cause: One of the three memory function pointers is null or non-null. // *Action: Verify that either all the memory functions are null or non-null. 24322, 00000, "unable to delete an initialized mutex" // *Cause: An attempt to delete an initialized mutex failed. // *Action: Contact customer support. 24323, 00000, "value not allowed" // *Cause: A null value or a bogus value was passed in for a mandatory // parameter. // *Action: Verify that all mandatory parameters are properly initialized. 24324, 00000, "service handle not initialized" // *Cause: An attempt was made to use an improper service context handle. // *Action: Verify that the service context handle has all the parameters // initialized prior to this call. 24325, 00000, "this OCI operation is not currently allowed" // *Cause: An attempt was made to use a context handle outside its scope. // *Action: Verify that the context handle is set to a service context handle // that has been converted to a logon data area for other OCI calls. // The logon data area must be converted back to a service context // before it can be used. 24326, 00000, "handle passed in is already initialized" // *Cause: An attempt was made to pass an initialized handle. // *Action: Verify that the parameter passed in to retrieve a handle does // not already point to a handle. 24327, 00000, "need explicit attach before authenticating a user" // *Cause: A server context must be initialized before creating a session. // *Action: Create and initialize a server handle. 24328, 00000, "illegal attribute value" // *Cause: The attribute value passed in is illegal. // *Action: Consult the users manual and specify a legal attribute value // for the handle. 24329, 00000, "invalid character set identifier" // *Cause: The character set identifier specifed is invalid // *Action: Specify a valid character set identifier in the OCI call. / 24330, 00000, "internal OCI error" // *Cause: An internal OCI error has occurred. // *Action: Please contact Oracle customer support. 24331, 00000, "user buffer too small" // *Cause: The user buffer to contain the output data is too small. // *Action: Specify a bigger buffer. 24332, 00000, "invalid object type" // *Cause: An invalid object type is requested for the describe call. // *Action: Specify a valid object type to the describe call. / 24333, 00000, "zero iteration count" // *Cause: An iteration count of zero was specified for the statement // *Action: Specify the number of times this statement must be executed / 24334, 00000, "no descriptor for this position" // *Cause: The application is trying to get a descriptor from a handle // for an illegal position. // *Action: Check the position number. / 24335, 00000, "cannot support more than 1000 columns" // *Cause: The number of columns exceeds the maximum number supported. // *Action: / 24336, 00000, "invalid result set descriptor" // *Cause: The result set descriptor should have valid data fetched into // it before it can be converted to a statement handle // *Action: Fetch valid data into the descriptor before attempting to // convert it into a statement handle / 24337, 00000, "statement handle not prepared" // *Cause: A statement cannot be executed before making preparing a request. // *Action: Prepare a statement before attempting to execute it. / 24338, 00000, "statement handle not executed" // *Cause: A fetch or describe was attempted before executing a // statement handle. // *Action: Execute a statement and then fetch or describe the data. / 24339, 00000, "cannot set server group name after connecting to server" // *Cause: An attempt was made to set the server group in a server handle // after connecting to the server. However, once the connection // is established to a server, the server group name cannot be // set anymore. // *Action: Attach to the server after setting the server group name in // the server handle. / 24340, 00000, "cannot support more than 255 columns" // *Cause: The number of columns exceeds maximum supported by the server. // *Action: Limit your operation to 255 columns. / 24341, 00000, "bad mode specified" // *Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client. // *Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been // specified at process initialization. / 24342, 00000, "unable to destroy a mutex" // *Cause: An attempt to destroy a mutex failed. / 24343, 00000, "user defined callback error" // *Cause: The only valid return value for a user defined callback // function is OCI_CONTINUE. Any other value will cause this // error. // *Action: Please insure that OCI_CONTINUE is returned from the user // defined callback function. 24344, 00000, "success with compilation error" // *Cause: A sql/plsql compilation error occurred. // *Action: Return OCI_SUCCESS_WITH_INFO along with the error code // 24345, 00000, "A Truncation or null fetch error occurred" // *Cause: A truncation or a null fetch error" // *Action: Please ensure that the buffer size is long enough to // store the returned data. 24346, 00000, "cannot execute without binding variables" // *Cause: None of the bind variables in the SQL statement are bound. // *Action: Please bind all the variables before the execute is done. // 24347, 00000, "Warning of a NULL column in an aggregate function" // *Cause: A null column was processed by an aggregate function // *Action: An OCI_SUCCESS_WITH_INFO is returned. // 24348, 00000, "Update or Delete without Where" // *Cause: An update or delete was executed without where clause // *Action: An OCI_SUCCESS_WITH_INFO is returned. // 24350, 00000, "OCI call not allowed" // *Cause: OCI used is not permitted from external procedures. // *Action: Refer to user manual for usage restrictions. / 24351, 00000, "invalid date passed into OCI call" // *Cause: A bad date was passed into one of the OCI calls. // *Action: Check your date bind values and correct them. / 24352, 00000, "invalid COBOL display type passed into OCI call" // *Cause: A bad COBOL display type was passed into one of the OCI calls. // *Action: Check your COBOL display type bind values and correct them. / 24353, 00000, "user buffer too small to accommodate COBOL display type" // *Cause: User supplied buffer for a COBOL display type was too small // to accommodate fetched number. // *Action: Increase the allocation for COBOL display type buffer. / 24354, 00000, "number fetched too large to fit in COBOL display type buffer." // *Cause: The number fetched was beyond the range that can be displayed. // *Action: Please check the number in the database. / 24355, 00000, "attempt to store a negative number in an Unsigned Display type." // *Cause: An attempt was made to convert a negative number into an unsigned // display type. // *Action: Please check the number in the database or change the defined // datatype. / 24356, 00000, "internal error while converting from to COBOL display type." // *Cause: An internal error was encountered during conversion to // COBOL display type. // *Action: Contact customer support. / 24357, 00000, "internal error while converting from to OCIDate." // *Cause: An internal error was encountered during conversion to // OCIDate type. // *Action: Contact customer support. / 24358, 00000, "OCIBindObject not invoked for a Object type or Reference" // *Cause: OCIBindObject was not invoked resulting in an incomplete // bind specification for a Object Type or Reference. // *Action: Please invoke the OCIBindObject call for all Object Types and // References. / 24359, 00000, "OCIDefineObject not invoked for a Object type or Reference" // *Cause: OCIDefineObject was not invoked resulting in an incomplete // bind specification for a Object Type or Reference. // *Action: Please invoke the OCIDefineObject call for all Object Types and // References. / 24360, 00000, "Type Descriptor Object not specified for Object Bind/Define" // *Cause: Type Descriptor Object is a mandatory parameter for Object Types // Binds and Defines. // *Action: Please invoke the OCIBindObject() or OCIDefineObject() call // with a valid Type Descriptor Object. / 24361, 00000, "basic bind call not invoked before invoking advanced bind call" // *Cause: One of the basic bind calls was not invoked on this bind handle // before performing an advanced bind call. // *Action: Please invoke the advanced bind call on this bind handle only // after performing a basic bind call. / 24362, 00000, "improper use of the character count flag" // *Cause: When the character count flag is set, then the maximum size of // the buffer in the server should be specified as a non-zero value. // *Action: Please use a non-zero value for the mamimum size of the buffer // in the server. / 24363, 00000, "measurements in characters illegal here" // *Cause: Measurements in characters instead of bytes are illegal if // either the server's or client's character set is varying width. // *Action: If either the client's or server's character set is varying // width then do not use the OCI_ATTR_CHAR_COUNT attribute for the // bind handle. Use OCI_ATTR_MAXDATA_SIZE instead. / 24364, 00000, "internal error while padding blanks" // *Cause: An internal error has occurred while attempting to blank pad // string data. This error should not occur normally. // *Action: Contact customer support. / 24365, 00000, "error in character conversion" // *Cause: This usually occurs during conversion of a multibyte // character data when the source data is abnormally terminated // in the middle of a multibyte character. // *Action: Make sure that all multibyte character data is properly terminated. / 24366, 00000, "migratable user handle is set in service handle" // *Cause: This occurs during user authentication, a migratable user handle // has been set in the service handle. // *Action: Service handle must not be set with migratable user handle when it // is used to authenticate another user. / 24367, 00000, "user handle has not been set in service handle" // *Cause: This occurs during authentication of a migratable user. // the service handle has not been set with non-migratable user handle. // *Action: Service handle must be set with non-migratable user handle when it // is used to authenticate a migratable user. / 24368, 00000, "OCI mutex counter non-zero when freeing a handle" // *Cause: This is an internal OCI error. // *Action: Contact customer support. / 24369, 00000, "required callbacks not registered for one or more bind handles" // *Cause: No callbacks have been registered for one or more of the bind // handles which are part of the RETURNING clause. // *Action: The bind handles which are to receive data in a DML statememt // with a RETURNING clause must have their mode set as DATA_AT_EXEC // and callback functions must be registered for these bind handles // using OCIBindDynamic. / 24370, 00000, "illegal piecewise operation attempted" // *Cause: Data of a certain datatype that does not support piecewise // operation is being sent or fetched in pieces. // *Action: Always set the piece value to OCI_ONE_PIECE for datatypes that // does not support piecewise operation. / 24371, 00000, "data would not fit in current prefetch buffer" // *Cause: An internal OCI error has occurred. // *Action: Please contact Oracle customer support. / 24372, 00000, "invalid object for describe" // *Cause: The object to be described is not valid. // It either has compilation or authorization errors. // *Action: The object to be described must be valid. / 24373, 00000, "invalid length specified for statement" // *Cause: The length specified for the statement is either 0 or too large. // *Action: Specify a valid length for the statement. / 24374, 00000, "define not done before fetch or execute and fetch" // *Cause: The application did not define output variables for data being // fetched before issuing a fetch call or invoking a fetch by // specifying a non-zero row count in an execute call. // *Action: Issue OCI define calls for the columns to be fetched. / 24375, 00000, "Cannot use V6 syntax when talking to a V8 server" // *Cause: V6 syntax is no longer supported in V8 server. // *Action: Change syntax to V7 syntax or higher. / 24376, 00000, "cannot register/get user callback for non-environment handle" // *Cause: A user callback registration or get was attempted on a handle which // is not an environment handle. // *Action: Pass the environment handle to register/get user callback. / 24377, 00000, "invalid OCI function code" // *Cause: An invalid function code was used to register or get user callback" // *Action: Use a valid OCI function code. / 24378, 00000, "user callbacks not allowed for this call" // *Cause: An attempt was made to register a user callback for an OCI call for // which it not allowed to register user callbacks. // *Action: Do not register user callback for this OCI call. / 24379, 00000, "invalid user callback type" // *Cause: An invalid type of user callback was specified. // *Action: Specify a valid user callback type. / 24380, 00000, "invalid mode specification" // *Cause: The mode parameter in an OCIU* call is invalid // *Action: Use only valid mode parameter / 24381, 00000, "error(s) in array DML" // *Cause: One or more rows failed in the DML. // *Action: Refer to the error stack in the error handle. / 24382, 00000, "statement handled already executed or described" // *Cause: The Statement handle was executed or described successfuly before. // *Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY. 24383, 00000, "Overflow segment of an IOT cannot be described" // *Cause: The name specified in the OCIDescribeAny call referred to an // IOT overflow segment. // *Action: Use OCIDescribeAny to describe only documented objects. 24384, 00000, "Application context size is not initialized" // *Cause: The size of the application context must be initialized before // populating each context element. // *Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size 24385, 00000, "Application context size or index is not valid" // *Cause: The size or index of the application context must be non-zero and // non-negative. // *Action: Use an appropriate value for the size. 24386, 00000, "statement/server handle is in use when being freed" // *Cause: This is an internal OCI error. // *Action: The user should reset in-use flag in statement handle before // freeing the handle. 24387, 00000, "Invalid attach driver" // *Cause: Trying to attach using the wrong driver // *Action: Relink the application in the right mode 24388, 00000, "Unsupported functionality in fast path mode" // *Cause: Feature not supported in fast path mode // *Action: Avoid using the functionality in this mode 24389, 00000, "Invalid scrollable fetch parameters" // *Cause: All the requested rows in this fetch could not be received. // *Action: Check the fetch orientation, scroll offset, // OCI_ATTR_CURRENT_POSITION and number of rows in OCIStmtFetch2 call. // If required, change some of above parameters and fetch again. 24390, 00000, "Unsupported scrollable cursor operation" // *Cause: The scrollable cursor execute or fetch has failed. // *Action: Check the documentation for supported types, and other restrictions // while using scrollable cursors. 24391, 00000, "invalid fetch operation" // *Cause: Scrollable cursor operation requested with non-scrollable cursor. // *Action: Check if the statement was executed in the scrollable mode. Else // the only acceptable orientation is OCI_FETCH_NEXT that ignores the // scroll offset parameter. / / Connection Pooling messages / 24392, 00000, "no connection pool to associate server handle" // *Cause: OCIServerAttach called in OCI_POOL mode but no connection pool // found to associate the server handle. // *Action: 1) Verify that OCIConnectionPoolCreate is called before calling // OCIServerAttach. // 2) Verify that the database link specified in OCIServerAttach // matches with that of the connection pool database link. 24393, 00000, "invalid mode for creating connection pool" // *Cause: Mode specified in OCIConnectionPoolCreate is invalid. // *Action: Use a valid mode. 24394, 00000, "invalid mode for destroying connection pool" // *Cause: Mode specified in OCIConnectionPoolDestroy is invalid. // *Action: Use a valid mode. 24395, 00000, "cannot reinitialize non-existent pool" // *Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this // pool handle. // *Action: Create a connection pool prior to reinitializing it. 24396, 00000, "invalid attribute set in server handle" // *Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server // handle and attached in OCI_POOL mode. Connection pooling does // not support non blocking mode. // *Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server // handle while attaching in OCI_POOL mode. 24397, 00000, "error occured while trying to free connections" // *Cause: An internal error occured while trying to free connections. // *Action: Contact customer support. 24398, 00000, "connection pool already exists" // *Cause: A connection pool has already been created for the specified // pool handle. // *Action: 1) Specify a different pool handle to create a new connection pool. // 2) If you wish to modify the pool parameters, call // OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode. 24399, 00000, "invalid number of connections specified" // *Cause: An invalid combination of minimum, maximum and increment number of // connections was specified in the OCIConnectionPoolCreate call. // *Action: Specify a valid combination of parameters. 24400, 00000, "error occured while creating connections in the pool" // *Cause: The database link specified in OCIConnectionPoolCreate might be an // invalid one. // *Action: Specify a valid database link. 24401, 00000, "cannot open further connections" // *Cause: Sufficient number of connections are not present in the pool to // execute the call. No new connections can be opened as the // connMax parameter supplied in OCIConnectionPoolCreate has been // reached. // *Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and // increase the value of the connMax parameter. 24402, 00000, "error occured while creating connections in the pool" // *Cause: The username and password specified in OCIConnectionPoolCreate // might be invalid. // *Action: Specify a valid username and password. 24403, 00000, "error occured while trying to destroy the connection pool" // *Cause: Some connections in the pool were busy when an attempt to destroy // the connection pool was made. // *Action: Ensure no connections from the pool are being used. 24404, 00000, "connection pool does not exist" // *Cause: An attempt was made to use the connection pool before creating it. // *Action: Create the connection pool. 24405, 00000, "error occured while trying to create connections in the pool" // *Cause: An internal error occured while creating connections in the pool. // *Action: Contact customer support. 24406, 00000, "API mode switch is disallowed when a call is in progress." // *Cause: A mode switch from OCI8 to OCI7 was attempted in a callback. // *Action: The user should perform the API mode switch either prior to // initiating the top call or after the main call is done. 24407, 00000, "connection pool already exists" // *Cause: A connection pool has already been created for the specified // pool name. // *Action: Specify a different pool name to create a new connection pool. 24408, 00000, "could not generate unique server group name" // *Cause: An internal error occured while generating unique server group name. // *Action: Contact customer support. 24409, 00000, "client cannot understand the object" // *Cause: The client cannot process all the new features in the object. // *Action: Upgrade the client so that features like inheritance and SQLJ // objects can be used. 24410, 00000, "scrollable cursor max size exceeded" // *Cause: Result set size exceeded the max limits. // *Action: Check the documentation for allowable maximum result set size for // scrollable cursors. Re-execute with a smaller expected result set // size or make the cursor non-scrollable. / / Codepoint length semantics and UTF16 related OCI error messages / 24500, 00000, "invalid UTF16 mode" // *Cause: UTF16 mode is allowed only at environment handle creation time. // *Action: Remove UTF16 mode for functions other than OCIEnvCreate() 24501, 00000, "invalid UTF16 string passed in" // *Cause: Non-UTF16 string is passed in while UTF16 string is expected // *Action: Check the parameter which is actually a string 24502, 00000, "codepoint length overflows" // *Cause: Returned buffer has more codepoints than allowed // *Action: Set OCI_MAXCHAR_SIZE large enough to accommodate 24503, 00000, "codepoint length overflows for piecewise operation" // *Cause: Accumulated codepoint length exceeds allowed codepoint length // *Action: Set OCI_MAXCHAR_SIZE large enough to accommodate 24504, 00000, "data length larger than expected" // *Cause: Incoming data larger than receiving buffer // *Action: Set OCI_MAXDATA/MAXCHAR_SIZE appropriately or remove the setting 24505, 00000, "cannot change character set id on the handle" // *Cause: Attempts to change character set id on non-environment handles // *Action: Only try to change character set id on environment handles 24506, 00000, "invalid attempt to change character set id on env handle" // *Cause: Attempts to change character set id after other handles have been // allocated from the env handle // *Action: Change character set id after creating environment handle / but before allocating any handles from it. / / Transaction Related OCI error messages (24750 - 24799) / 24750, 00000, "incorrect size of attribute" // *Cause: Transaction ID attribute size is incorrect. // *Action: Verify that the size parameter is correct. 24752, 00000, "OCI_TRANS_NEW flag must be specified for local transactions" // *Cause: Application attempted to start a local transaction without using // OCI_TRANS_NEW. // *Action: Use OCI_TRANS_NEW when starting local transactions. 24753, 00000, "local transactions cannot be detached" // *Cause: An attempt to detach a local transaction was made. // *Action: Local transactions may only be committed or rolled back. 24754, 00000, "cannot start new transaction with an active transaction" // *Cause: An attempt to start a new transaction was made when there was an // active transaction. // *Action: Commit, rollback or detach the existing transaction before // starting a new transaction. 24755, 00000, "OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported" // *Cause: These flags are currently not supported. // *Action: 24756, 00000, "transaction does not exist" // *Cause: An invalid transaction identifier or context was used or the // transaction has completed. // *Action: Supply a valid identifier if the transaction has not completed // and retry the call. 24757, 00000, "duplicate transaction identifier" // *Cause: An attempt was made to start a new transaction with an identifier // already in use by an existing transaction. // *Action: Verify that the identifier is not in use. 24758, 00000, "not attached to the requested transaction" // *Cause: An attempt was made to detach or complete a transaction that is // not the current transaction. // *Action: Verify that the transaction context refers to the current // transaction. 24759, 00000, "invalid transaction start flags" // *Cause: An invalid transaction start flag was passed. // *Action: Verify that one of the following values - OCI_TRANS_NEW, // OCI_TRANS_JOIN, OCI_TRANS_RESUME was specified. 24760, 00000, "invalid isolation level flags" // *Cause: An invalid isolation level flag was passed. // *Action: Verify that only one of following values - OCI_TRANS_READONLY, // OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used. 24761, 00000, "transaction rolled back" // *Cause: // *Action: 24762, 00000, "server failed due to unspecified error" // *Cause: An internal error has occured in the server commit protocol. // *Action: Contact customer support. 24763, 00000, "transaction operation cannot be completed now" // *Cause: The commit or rollback cannot be performed now because the // session cannot switch to the specified transaction. // *Action: Retry the operation later. 24764, 00000, "transaction branch has been heuristically committed" // *Cause: // *Action: 24765, 00000, "transaction branch has been heuristically rolled back" // *Cause: // *Action: 24766, 00000, "transaction branch has been partly committed and aborted" // *Cause: // *Action: 24767, 00000, "transaction was read-only and has been committed" // *Cause: // *Action: 24768, 00000, "commit protocol error occured in the server" // *Cause: // *Action: Contact customer support 24769, 00000, "cannot forget an active transaction" // *Cause: Transaction identifier refers to an active transaction. // *Action: Verify that the identifier of an active transaction was not // passed as an argument. 24770, 00000, "cannot forget a prepared transaction" // *Cause: Transaction identifier refers to a prepared transaction. // *Action: Verify that the identifier of a prepared transaction was not // passed as an argument. 24771, 00000, "cannot detach, prepare or forget a local transaction" // *Cause: Service handle contains a local transaction context. // *Action: Verify that the transaction context does not refer to a local // transaction. 24772, 00000, "Cannot mix tightly-coupled and loosely-coupled branches" // *Cause: Application attempted to start a transaction with a global // transaction identifier and a wrong option. // *Action: Verify that all branches of a global transaction are started with // either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the // application is correct and uses distributed updates, // contact customer support. 24773, 00000, "invalid transaction type flags" // *Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified. // *Action: Verify that the right parameters are being used. 24774, 00000, "cannot switch to specified transaction" // *Cause: The transaction specified in the call refers to a transaction // created by a different user. // *Action: Create transactions with the same authentication so that they // can be switched. 24775, 00000, "cannot prepare or commit transaction with non-zero lock value" // *Cause: An attempt was made to detach the transaction with a non-zero lock // value. // *Action: Detach the transaction with lock value set to zero and then try to // prepare or commit the transaction. 24776, 00000, "cannot start a new transaction" // *Cause: An attempt was made to start a new transaction when session was // already attached to an existing transaction. // *Action: End the current transaction before creating a new transaction. 24777, 00000, "use of non-migratable database link not allowed" // *Cause: The transaction, which needs to be migratable between sessions, // tried to access a remote database from a non-multi threaded // server process. // *Action: Perform the work in the local database or open a connection to // the remote database from the client. If multi threaded server // option is installed, connect to the Oracle instance through the // dispatcher. 24778, 00000, "cannot open connections" // *Cause: The migratable transaction tried to access a remote database when // the session itself had opened connections to remote database(s). // *Action: Close the connection(s) in the session and then try to access the // remote database from the migratable transaction. If the error // still occurs, contact Oracle customer support. 24779, 00000, "detach not allowed with open remote cursor" // *Cause: The migratable transaction tried to detach from the current // session while having an open remote cursor. // *Action: Close any open remote cursor prior to detach. 24780, 00000, "cannot recover a transaction while in an existing transaction" // *Cause: An attempt was made to commit or roll back a transaction // while in a different transaction, and the transaction for // which the action is requested is in a recovery state // (this happens if it is idle too long). // *Action: Detach from the current transaction and retry the operation. 24781, 00000, "branches don't belong to the same global transaction" // *Cause: The list of xids passed into kpotxmp() don't have the same gtrid // *Action: 24782, 00000, "Cannot detach from a non-migratable transaction" // *Cause: An attempt was made to detach from a non-migrateable transaction. // *Action: Either commit or rollback the transaction. 24783, 00000, "Cannot switch non-migratable transactions" // *Cause: An attempt was made to prepare/commit a txn different from current. // *Action: 24784, 00000, "Transaction exists" // *Cause: An attempt was made to start a transaction, while attached // to a non-migrateable transaction // *Action: 24785, 00000, "Cannot resume a non-migratable transaction" // *Cause: An attempt was made to resume a non-migrateable transaction. // *Action: 24786, 00000, "separated transaction has been completed" // *Cause: The current transaction has been completed by another process. // *Action: Start a new transaction 24787, 00000, "remote cursors must be closed before a call completes" // *Cause: The previous operation did not close all the remote cursors it // opened. Since separated transactions are enabled, this is not // allowed. // *Action: Close all remote cursors in each call, or start a regular // (non-separated) transaction. 24788, 00000, "cannot switch to specified transaction (server type)" // *Cause: The transaction specified was created by a shared server and // the requestor is a dedicated server, or the transaction was // created by a dedicated server and the requestor is a shared // server. // *Action: All parts of this application should connect as dedicated // or as shared. / / / / OCI Lob/File Related Error message (24800 - 24900) / 24801, 00000, "illegal parameter value in OCI lob function" // *Cause: One of the parameter values in the OCI lob function is illegal. // *Action: Check every parameter in the OCI Lob function call to make sure // they are correct. Offsets should be greater than or equal to one. 24802, 00000, "user defined lob read callback error" // *Cause: The only valid return value for a user defined lob read callback // function is OCI_CONTINUE. Any other value will cause this error. // *Action: Verify that OCI_CONTINUE is returned from the user defined // lob read callback function. 24803, 00000, "illegal parameter value in lob read function" // *Cause: Internal error . // *Action: This error should not normally occur. If it persists, // please contact your customer service representative. 24804, 00000, "illegal parameter value in lob write function" // *Cause: Internal error. // *Action: This error should not normally occur. If it persists, // please contact your customer service representative. 24805, 00000, "LOB type mismatch" // *Cause: When copying or appending LOB locators, both source and // desctination LOB locators should be of the same type. // *Action: Pass the same type of LOB locators for copying or appending. 24806, 00000, "LOB form mismatch" // *Cause: When reading from or writing into LOBs, the character set // form of the user buffer should be same as that of the LOB. // *Action: Make sure that the buffer you are using to read or write // has the same form as that of the LOB. 24807, 00000, "LOB form mismatch" // *Cause: When copying or appending LOBs, both source and // desctination LOB locators should have the same character // set form. // *Action: Pass locators of the same character set form for copying // or appending LOBs. / 24808, 00000, "streaming of lob data is not allowed when using lob buffering" // *Cause: Attempted to stream lob data via the polling mode or a callback // when lob buffering was enabled for the input lob locator. // *Action: Lob buffering is useful when reading/writing small amounts of // lob data so streaming should not be necessary. Rewrite the // OCILobRead/OCILobWrite call so that it does not use streaming. // If streaming of data is required, lob buffering should not be // used. In this case, flush buffers associated with the input // lob locator as necessary, disable buffering on the input lob // locator and reissue the OCILobRead/OCILobWrite call. / 24809, 00000, "amount specified will not fit in the lob buffers" // *Cause: LOB buffering is enabled for the input lob locator so buffering // will be used. However, the amount of lob data to read or write // is larger than what the lob buffers can hold. // *Action: Either disable buffering on the input lob locator and reissue // the command or pass a smaller amount. / 24810, 00000, "attempting to write more data than indicated" // *Cause: While writing into a LOB, more data was supplied than // indicated. // *Action: If data is written in pieces, then make sure that you // do not provide more data in the pieces (cumulatively), than // you indicated. / 24811, 00000, "less data provided for writing than indicated" // *Cause: While writing into a LOB, less data was provided than // indicated. // *Action: If writing data in single pieces, then make sure that the buffer // length specified is big enough to accommodate tha data being // provided. If data is written in pieces, then make sure that all // the data has been provided before specifying OCI_LAST_PIECE. / 24812, 00000, "character set conversion to or from UCS2 failed" // *Cause: If the database character set is varying-width, the CLOB/NCLOB // value is implicitly converted to or from UCS2. This implicit // conversion failed. // *Action: Contact Oracle Worldwide Support. / 24813, 00000, "cannot send or receive an unsupported LOB" // *Cause: An attempt was made to send a LOB across the network, but either // the server does not support the LOB sent by the client, or the // client does not support the LOB sent by the server. This error // usually occurs when the client and server are running different // versions of Oracle. // *Action: Use a version of the Oracle that supports the LOB on both // the client and the server. / / / / OCI Shared Structures Related Error Messages (24850 - 24874) / 24850, 00000, "failed to startup shared subsystem" // *Cause: While attempting to initialize OCI in shared mode, a problem // was encountered in starting up the shared subsystem. // *Action: Contact Oracle Customer support. / 24851, 00000, "failed to connect to shared subsystem" // *Cause: While attempting to initialize OCI in shared mode, a problem // was encountered in connecting the process to the shared subsystem. // *Action: Contact Oracle Customer Support. / 24852, 00000, "protocol error during statement execution" // *Cause: An internal protocol error occurred while receiving describe data // from the server during execution of a statement. // *Action: Contact Oracle Customer Support. / 24853, 00000, "failed to connect thread to shared subsystem" // *Cause: While attempting to initialize OCI in shared mode, a problem // was encountered in connecting the thread to the shared subsystem. // *Action: Contact Oracle Customer Support. / / / / OCI Notification Related Error message (24900 - 24949) / / 24900, 00000, "invalid or unsupported mode paramater passed in call" // *Cause: The mode parameter passed into the OCI Client Notification call // is incorrect. // *Action: Please correct the mode parameter passed into OCI. / 24901, 00000, "handles belonging to different environments passed into an OCI call" // *Cause: All handles passed into an OCI call should belong to the same // environment. In the call that returned this error, handles // belonging to different environments were passed in. // *Action: Please ensure that the handle parameters in the call to come from // the same OCI Environment. / 24902, 00000, "invalid subscription name or name-length in subscription handle" // *Cause: The subscription handle passed into the OCI call does not have // a proper name or name-length attribute. // *Action: Please set the name and name-length attributes using the // OCIAttrSet() call. / 24903, 00000, "invalid namespace attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call does not have // a proper namespace attribute. // *Action: Please set the namespace attribute using the OCIAttrSet() // call. / 24904, 00000, "invalid callback attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call does not have // a proper callback attribute. // *Action: Please set the callback attribute using the OCIAttrSet() // call. / 24905, 00000, "invalid recepient protocol attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call does not have // a proper recepient protocol attribute. // *Action: Please set the recepient protocol attribute using the OCIAttrSet() // call. / 24906, 00000, "invalid recepient attribute passed into OCI call" // *Cause: The subscription handle passed into the OCI call does not have // a proper recepient attribute. // *Action: Please set the recepient attribute using the OCIAttrSet() // call. / 24907, 00000, "invalid pair of callback and recepient protocol attributes" // *Cause: The subscription handle passed into the OCI call can't have // both the callback defined and a recepient protocol other than // OCI_SUBSCR_PROTO_OCI at the same time. // *Action: Please set the appropriate callback and recepient protocol // attributes using the OCIAttrSet() call. 24908, 00000, "invalid recipient presentation attribute" // *Cause: The subscription handle passed into the OCI call does not have a // valid recipient presentation attribute. // *Action: Set the recipient presentation attribute using the OCIAttrSet() // call / / / / PL/SQL Notification Related Error message (24950 - 24959) / 24950, 00000, "unregister failed, registeration not found" // *Cause: The registeration that was asked to be unregistered could // not be found. // *Action: Please check the callback function name and the subscription name // in the unregister call. / 24951, 00000, "EMON tracing event" // *Cause: N/A // *Action: Event used to trace EMON. // *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. / / / / 25000-25099 Reserved for Trigger errors / 25000, 00000, "invalid use of bind variable in trigger WHEN clause" // *Cause: A bind variable was used in the when clause of a trigger. // *Action: Remove the bind variable. To access the table columns use // (new/old).column_name. 25001, 00000, "cannot create this trigger type on views" // *Cause: Only INSTEAD OF triggers can be created on a view. // *Action: Change the trigger type to INSTEAD OF. 25002, 00000, "cannot create INSTEAD OF triggers on tables" // *Cause: Only BEFORE or AFTER triggers can be created on a table. // *Action: Change the trigger type to BEFORE or AFTER. 25003, 00000, "cannot change NEW values for this column type in trigger" // *Cause: Attempt to change NEW trigger variables of datatype object, REF, // nested table, VARRAY or LOB datatype which is not supported. // *Action: Do not change the NEW trigger variables in the trigger body. 25004, 00000, "WHEN clause is not allowed in INSTEAD OF triggers" // *Cause: WHEN clause is specified in an INSTEAD OF trigger. // *Action: Remove the WHEN clause when creating an INSTEAD OF // trigger. 25005, 00000, "cannot CREATE INSTEAD OF trigger on a read-only view" // *Cause: attempt to create an INSTEAD OF trigger on a view // created with read-only option. The view cannot be // updated using INSTEAD OF triggers. // *Action: Do not create the trigger. 25006, 00000, "cannot specify this column in UPDATE OF clause" // *Cause: Attempt to create a trigger on update of a column whose // datatype is disallowed in the clause, such as LOB and // nested table. // *Action: Remove the UPDATE OF clause. 25007, 00000, "functions or methods not allowed in WHEN clause" // *Cause: PLSQL function call or method invocation is not allowed // in the WHEN clause when creating a trigger. // *Action: Remove the function call or method invocation from // the WHEN clause. 25008, 00000, "no implicit conversion to LOB datatype in instead-of trigger" // *Cause: When inserting or updating a view using instead-of trigger, // the new value for a LOB view column is of a different datatype. // *Action: Specified a LOB value as the new value for the LOB view column. // 25009, 00000, "Nested table clause allowed only for INSTEAD OF triggers" // *Cause: Triggers on nested tables can only be created on view columns // using INSTEAD OF triggers. // *Action: Use view nested table columns for defining nested table triggers. // 25010, 00000, "Invalid nested table column name in nested table clause" // *Cause: The column name specified in the nested table clause of an // INSTEAD OF trigger does not correspond to a nested table column. // *Action: Specify a nested table column on which the trigger is to be defined. // 25012, 00000, "PARENT and NEW values cannot be identical" // *Cause: The referencing clause specifies identical values for PARENT and OLD. // *Action: Re-specify either the PARENT or NEW referencing value. // 25013, 00000, "OLD and PARENT values cannot be identical" // *Cause: The referencing clause specifies identical values for OLD and PARENT. // *Action: Re-specify either the OLD or PARENT referencing value. // 25014, 00000, "cannot change the value of a PARENT reference variable" // *Cause: Parent values can only be read and not changed. // *Action: Do not attempt to change a Parent variable. // 25015, 00000, "cannot perform DML on this nested table view column" // *Cause: DML cannot be performed on a nested table view column except through // an INSTEAD OF trigger // *Action: Create an INSTEAD OF trigger over the nested table view column // and then perform the DML. // 25016, 00000, "cannot specify column list for insert into nested table view column" // *Cause: A column list cannot be specified for inserts into the nested table // view column. // *Action: Specify all the columns for insert into the nested table. // 25017, 00000, "cannot reference NEW ROWID for movable rows in before triggers" // *Cause: NEW ROWID was referenced in a before row trigger which is defined // on an index-organized table, or a partitioned table with enabled // movement of rows. The ROWID cannot be computed in a before row // update trigger because it depends on the actual values of the row // *Action: Remove references to NEW ROWID from the trigger definition. // 25018, 00000, "conflicting trigger %s already exists" // *Cause: Conflicting instead of DDL trigger on schema/database already // exists. // *Action: Remove the old trigger // 25019, 00000, "too much concurreny" // *Cause: cannot pin the database/schema because of too much concurrency // *Action: try the operation later // 25020, 00000, "renaming system triggers is not allowed" // *Cause: renaming system triggers is not allowed // *Action: Drop the trigger, and create a new one for the same // / / 25100-25199 Reserved for Parser errors (e.g. v7) / 25175-25199 reserved for index-organized tables ( v8 ) / Additional parser errors begin at 30560 / 25100, 00000, "TABLESPACE option can only be used with ALTER INDEX REBUILD" // *Cause: The TABLESPACE option to ALTER INDEX was used without the // REBUILD option. // *Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name. 25101, 00000, "duplicate REBUILD option specification" // *Cause: The REBUILD option to ALTER INDEX is specified more than once. // *Action: Specify the option at most once. 25102, 00000, "PARALLEL option can only be used with ALTER INDEX REBUILD" // *Cause: The PARALLEL option to ALTER INDEX was used without the // REBUILD option. // *Action: Use ALTER INDEX REBUILD. 25103, 00000, "NOPARALLEL option can only be used with ALTER INDEX REBUILD" // *Cause: The NOPARALLEL option to ALTER INDEX was used without the // REBUILD option. // *Action: Use ALTER INDEX REBUILD. 25104, 00000, "UNRECOVERABLE option can only be used with ALTER INDEX REBUILD" // *Cause: The UNRECOVERABLE option to ALTER INDEX was used without the // REBUILD option. // *Action: Use ALTER INDEX REBUILD. 25105, 00000, "RECOVERABLE option can only be used with ALTER INDEX REBUILD" // *Cause: The RECOVERABLE option to ALTER INDEX was used without the // REBUILD option. // *Action: Use ALTER INDEX REBUILD. 25106, 00000, "only one of PARALLEL or NOPARALLEL clause may be specified" // *Cause: PARALLEL was specified more than once, NOPARALLEL was specified // more than once, or both PARALLEL and NOPARALLEL were specified // in an ALTER INDEX REBUILD statement. // *Action: Remove all but one of the PARALLEL or NOPARALLEL clauses. 25107, 00000, "duplicate TABLESPACE option specification" // *Cause: the TABLESPACE was specified more than once // in an ALTER INDEX REBUILD statement. // *Action: Remove all but one of the TABLESPACE clauses. 25108, 00000, "standby lock name space exceeds size limit of %s characters" // *Cause: The lock name space for the standby database exceeded the maximum // string length. // *Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to // a character string of less than the specified characters. 25109, 00000, "standby lock name space has illegal character '%s'" // *Cause: An invalid lock name space was specified for the standby database. // The lock name space for the standby database can only contain // A-Z, 0-9, '_', '#', '$', '.' and '@' characters. // *Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to // a valid character string. 25110, 00000, "NOSORT may not be used with a bitmap index" // *Cause: An attempt was made to create a bitmap index using // the NOSORT option. // *Action: Remove NOSORT from the CREATE BITMAP INDEX statement. 25111, 00000, "creation of BITMAP cluster indices is not supported" // *Cause: An attempt was made to create a cluster index with the // BITMAP attribute. // *Action: Remove BITMAP from the CREATE INDEX statement. 25112, 00000, "maximum number of BITMAP index columns is 30" // *Cause: Too many columns were specified for the index. // *Action: Create an index on fewer columns. 25113, 00000, "GLOBAL may not be used with a bitmap index" // *Cause: An attempt was made to create a bitmap index using // the GLOBAL option. // *Action: Remove GLOBAL from the CREATE BITMAP INDEX statement, // and/or add a LOCAL partition descriptor if the table is // partitioned. 25114, 00000, "invalid file number specified in the DUMP DATAFILE/TEMPFILE command" // *Cause: An invalid file number was used in dumping a datafile or tempfile. // *Action: Specify a valid file number. 25115, 00000, "duplicate BLOCK option specification" // *Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE // command. // *Action: Specify only one BLOCK option. 25116, 00000, "invalid block number specified in the DUMP DATAFILE/TEMPFILE command" // *Cause: An invalid block number was used in dumping a datafile or tempfile. // *Action: Specify a valid block number. 25117, 00000, "MIN/MAX/Block Number expected" // *Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command. // *Action: Correct the syntax. 25118, 00000, "invalid DUMP DATAFILE/TEMPFILE option" // *Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command. // *Action: Correct the syntax. 25119, 00000, "LOGGING/NOLOGGING option already specified" // *Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were // specified more than once. // *Action: Remove all but one of the logging specifications. 25120, 00000, "MINIMUM EXTENT option already specified" // *Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was // specified more than once. // *Action: Remove all but one of the MINIMUM EXTENT specifications. 25121, 00000, "MINIMUM EXTENT value greater than maximum extent size" // *Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT // option was greater than the maximum extent size. // *Action: Choose a lower value for the MINIMUM EXTENT option. 25122, 00000, "Only LOCAL bitmap indexes are permitted on partitioned tables" // *Cause: An attempt was made to create a global bitmap index on a partioned // table. // *Action: create a local bitmap index instead. 25123, 00000, "Too many components specified in the name." // *Cause: Specifying more components to a name than allowed. // *Action: Check the name specified for the operation. 25124, 00000, "Database link name not allowed." // *Cause: Specifying a database link name when it is not permitted. // *Action: Check the name specified for the operation. 25125, 00000, "BUFFER_POOL storage option not allowed" // *Cause: The user attempted to specify the BUFFER_POOL storage // option. This option may only be specified during // CREATE/ALTER TABLE/CLUSTER/INDEX. // *Action: Remove this option and retry the statement. 25126, 00000, "Invalid name specified for BUFFER_POOL" // *Cause: The name of the buffer pool specified by the user is // invalid. The only valid names are KEEP, RECYCLE // and DEFAULT. // *Action: Use a valid name or remove the BUFFER_POOL clause. 25127, 00000, "RELY not allowed in NOT NULL constraint" // *Cause: An attempt to set RELY on for NOT NULL constraint. // *Action: only NORELY may be specified for a NOT NULL constraint. // 25128, 00000, "No insert/update/delete on table with constraint (%s.%s) disabled and validated" // *Cause: Try to insert/update/delete on table with DISABLE VALIDATE constraint. // *Action: Change the constraint's states. // 25129, 00000, "cannot modify constraint (%s) - no such constraint" // *Cause: the named constraint does not exist for this table. // *Action: Obvious 25130, 00000, "cannot modify primary key - primary key not defined for table" // *Cause: Attempted to modify a primary key that is not defined for the // table. // *Action: None 25131, 00000, "cannot modify unique(%s) - unique key not defined for table" // *Cause: attempted to modify a unique key that is not deined for the table. // *Action: None 25132, 00000, "UNIQUE constraint (%s.%s) disabled and validated in ALTER TABLE EXCHANGE PARTITION" // *Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the // table have a disabled and validated unique constraints AND the unique keys // in the partion is not mutually exclusive from the rest of the table. // *Action: Change the constraint's status. 25133, 00000, "duplicate SINGLE TABLE option specified" // *Cause: The SINGLE TABLE option was specified more than once. // *Action: Specify the SINGLE TABLE option only once. 25134, 00000, "keyword TABLE expected" // *Cause: The keyword TABLE is missing from the SINGLE TABLE option. // *Action: Place the keyword TABLE after the keyword SINGLE in the command. 25135, 00000, "cannot use the SINGLE TABLE option" // *Cause: The SINGLE TABLE option is only valid for hash clusters. // *Action: Do not specify the SINGLE TABLE option. 25136, 00000, "this cluster can contain only one table" // *Cause: An attempt was made to store more than one table in a cluster // that was created with the SINGLE TABLE option. // *Action: Do not attempt to store more than one table in the cluster. 25137, 00000, "Data value out of range" // *Cause: Value from cast operand is larger than cast target size. // *Action: Increase size of cast target. 25138, 00000, "%s initialization parameter has been made obsolete" // *Cause: An obsolete initialization parameter has been specified // *Action: The system will come up, but parameters must be examined 25139, 00000, "invalid option for CREATE TEMPORARY TABLESPACE" // *Cause: An invalid option appears. // *Action: Specify one of the valid options: TEMPFILE, // EXTENT MANAGEMENT LOCAL, UNIFORM / 25140, 00000, "%s space policy cannot be specified for the %s extent management" // *Cause: An invalid option appears. // *Action: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE // is specified, and for DICTIONARY extent management UNIFORM or // AUTOALLOCATE are not specified / 25141, 00000, "invalid EXTENT MANAGEMENT clause" // *Cause: An invalid option appears for EXTENT MANAGEMENT clause // *Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE / 25142, 00000, "default storage clause specified twice" // *Cause: default storage clause was specified twice for create tablespace // *Action: Specify it once. / 25143, 00000, "default storage clause is not compatible with allocation policy" // *Cause: default storage clause was specified for a tablespace with // AUTOALLOCATE or UNIFORM policy // *Action: Omit the storage clause / 25144, 00000, "invalid option for CREATE TABLESPACE with TEMPORARY contents" // *Cause: An invalid option appears. // *Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, // USER / 25145, 00000, "allocation policy already specified" // *Cause: In CREATE TABLESPACE, the allocation policy was specified more // than once, for example, AUTOALLOCATE and UNIFORM. // *Action: Remove all but one of the allocation policy specifications. / 25146, 00000, "EXTENT MANAGEMENT option already specified" // *Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was // specified more than once. // *Action: Remove all but one of the EXTENT MANAGEMENT specifications. / 25147, 00000, "UNIFORM SIZE value greater than maximum extent size" // *Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size. // *Action: Choose a lower value for the UNIFORM SIZE option. / 25148, 00000, "ONLINE option not permitted" // *Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE // on a table that is not index-organized. The ONLINE option is // currently supported only for index-organized tables. // *Action: Remove the ONLINE option from the command. / 25149, 00000, "Columns of UROWID type may not be indexed" // *Cause: An attempt was made to create an index on a column of UROWID type // *Action: Remove the column from the list of indexed columns / 25150, 00000, "ALTERING of extent parameters not permitted" // *Cause: An attempt was made to alter the extent parameters for a segment // in a tablespace with autoallocate or uniform extent allocation // policy. // *Action: Remove the appropriate extent parameters from the command. / 25151, 00000, "Rollback Segment cannot be created in this tablespace" // *Cause: An attempt was made to create a rollback segment in a tablespace // with autoallocate extent allocation policy. // *Action: Specify a different tablespace for the rollback segment / 25152, 00000, "TEMPFILE cannot be dropped at this time" // *Cause: An attempt was made to drop a TEMPFILE being used by online users // *Action: The TEMPFILE has been taken offline. Try again, later. / 25153, 00000, "Temporary Tablespace is Empty" // *Cause: An attempt was made to use space in a temporary tablespace with // no files. // *Action: Add files to the tablespace using ADD TEMPFILE command. / 25154, 00000, "column part of USING clause cannot have qualifier" // *Cause: Columns that are used for a named-join (either a NATURAL join // or a join with a USING clause) cannot have an explicit qualifier. // *Action: Remove the qualifier. / 25155, 00000, "column used in NATURAL join cannot have qualifier" // *Cause: Columns that are used for a named-join (either a NATURAL join // or a join with a USING clause) cannot have an explicit qualifier. // *Action: Remove the qualifier. / 25156, 00000, "old style outer join (+) cannot be used with ANSI joins" // *Cause: When a query block uses ANSI style joins, the old notation // for specifying outer joins (+) cannot be used. // *Action: Use ANSI style for specifying outer joins also. / 25157, 00000, "Specified block size %s is not valid" // *Cause: An attempt was made to create a tablespace with a block // size which is not supported. // *Action: Specify one of the valid blocksizes i.e the standard // blocksize or one of (2k, 4k, 8k, 16k, 32k) subject // to the maximum and minimum blocksizes supported by // the platform. / 25175, 00000, "no PRIMARY KEY constraint found" // *Cause: A PRIMARY KEY constraint must be defined for a table // with this organization // *Action: Define a PRIMARY KEY 25176, 00000, "storage specification not permitted for primary key" // *Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint // for a table with this organization // *Action: Remove storage specification for primary key 25177, 00000, "UNRECOVERABLE option not permitted" // *Cause: The UNRECOVERABLE option may not be specified for a primary // key for a table with this organization // *Action: Remove UNRECOVERABLE option for primary key 25178, 00000, "duplicate PCTTHRESHOLD storage option specification" // *Cause: The storage option PCTTHRESHOLD is specified more than once. // *Action: Specify storage options at most once. 25179, 00000, "invalid PCTTHRESHOLD storage option value" // *Cause: The specified value must be a positive integer. // *Action: Specify an appropriate value. 25180, 00000, "PCTTHRESHOLD only valid for certain table organizations" // *Cause: PCTTHRESHOLD can only be specified for tables with certain // organizations. // *Action: Remove the PCTTHRESHOLD option. 25181, 00000, "missing ON keyword for NESTED INDEX" // *Cause: ON keyword required to specify nested index column nest // *Action: Add ON keyword 25182, 00000, "feature not currently available for index-organized tables" // *Cause: An attempt was made to use one or more of the following feature(s) not // currently supported for index-organized tables: // CREATE TABLE with LOB/BFILE/VARRAY columns, // partitioning/PARALLEL/CREATE TABLE AS SELECT options, // ALTER TABLE with ADD/MODIFY column options, CREATE INDEX // *Action: Do not use the disallowed feature(s) in this release. 25183, 00000, "index-organized table top index segment is in a different tablespace" // *Cause: An attempt was made to drop a tablespace which contains an index // only table's overflow segment but not the top index segment" // *Action: find index-organized tables which span the tablespace being // dropped and some other tablespace(s). Drop these tables. 25184, 00000, "column name expected" // *Cause: A column name is not present where required by the // CREATE TABLE for specifying last column to be included in // the index segment of the index-organized table // *Action: Specify a column name where required by the syntax. 25185, 00000, "index column other than last can not be specified for INCLUDE clause" // *Cause: An index column name other than the last is specified as // including column // *Action: Specify either a column name which is not part of index-organized // table primary key index , or the last key column of the primary // key for the INCLUDING clause. 25186, 00000, "INCLUDING clause specified for index-organized table without OVERFLOW" // *Cause: INCLUDING clause of a CREATE TABLE is an valid option only for // index-organized tables with OVERFLOW clause (at creation time) // or if an OVERFLOW segment already exists (at ALTER time). // *Action: Specify OVERFLOW clause for the index-organized table // : For ALTER, perform ADD OVERFLOW first. 25187, 00000, "specified exceptions table form incorrect" // *Cause: The specified table does not have the proper field definitions. // *Action: Specify the correct table to use. 25188, 00000, "cannot drop/disable/defer the primary key constraint for index-organized tables" // *Cause: // *Action: 25189, 00000, "illegal ALTER TABLE option for an index-organized table" // *Cause: During ALTER of a index-organized table, the user attempted // to enter one or more of the following options: // TABLESPACE, ALLOCATE/DEALLOCATE EXTENT, // PCTFREE/PCTUSED for IOT top index segment // *Action: Remove the illegal option(s). 25190, 00000, "an index-organized table maintenance operation may not be combined with other operations" // *Cause: ALTER TABLE statement attempted to combine an index-organized table // maintenance operation (e.g. changing physical attributes) with // some other operation (e.g. ADD constraint) which is illegal // *Action: Ensure that a index-organized table maintenance operation is the sole // operation specified in ALTER TABLE statement; 25191, 00000, "cannot reference overflow table of an index-organized table" // *Cause: An attempt to directly access the overflow table of an // index-organized table // *Action: Issue the statement against the parent index-organized table // containing the specified overflow table. 25192, 00000, "invalid option for an index-organized table" // *Cause: An attempt to specify one or more of the following options for // an index-organized table: // [NO]CACHE, NO LOGGING, CLUSTER // *Action: Remove the illegal option(s) 25193, 00000, "cannot use COMPRESS option for a single column key" // *Cause: An attempt to use COMPRESS option on single column key // *Action: Remove the COMPRESS option. 25194, 00000, "invalid COMPRESS prefix length value" // *Cause: The specified value must be a positive integer less than the number // of key columns // *Action: Specify an appropriate value. 25195, 00000, "invalid option for index on an index-organized table" // *Cause: An attempt to specify one or more of the following options for // index on an IOT: // BITMAP, REVERSE, PCTUSED 25196, 00000, "keyword MOVE in ALTER TABLE MOVE must immediately follow
" // *Cause: MOVE specified after one/more other ALTER options // *Action: Change order of options, MOVE should be first // *Action: Remove the illegal option(s) 25197, 00000, "an overflow segment already exists for the indexed-organized table" // *Cause: An attempt was made to ADD OVERFLOW segment on an index-organized // table that already has an overflow segment // *Action: 25198, 00000, "only range and hash partitioning are supported for index-organized table" // *Cause: System, or Composite partitioning schemes are not supported yet // *Action: Select a different partitioning scheme 25199, 00000, "partitioning key of a index-organized table must be a subset of the primary key" // *Cause: An attempt to specify a partitioning key which is not a prefix // of the primary key of the index-organized table // *Action: Select a different partitioning key / / 25200-25699 Reserved for OLTP / 25200-25299 Reserved for AQ / 25350-25375 Reserved for V8 Transaction OCI / 25400-25425 Reserved for Application Failover / 25426-25435 Reserved for Dblink Concentration / 25436-25475 Reserved for Rules Engine / / 25200 - 25224 Reserved for DBMS_AQ.ENQUEUE / 25200, 00000, "invalid value %s, QUEUE_NAME should be [SCHEMA.]NAME" // *Cause: A NULL parameter was specified for QUEUE_NAME. // *Action: Specify a non-NULL queue name. // 25201, 00000, "invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE" // *Cause: An invalid value specified for parameter VISIBILITY. // *Action: Specify either ON_COMMIT or IMMEDIATE. // 25202, 00000, "invalid value NULL, %s should be non-NULL" // *Cause: A NULL value was specified for the parameter. // *Action: Specify a non-NULL value. // 25203, 00000, "invalid value %s, DELAY should be non-negative" // *Cause: A negative value or NULL was specified for DELAY. // *Action: Specify a non negative integer for DELAY. // 25204, 00000, "invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP" // *Cause: An invalid SEQUENCE_DEVIATION was specified. // *Action: Specify either the option 'BEFORE' or 'TOP'. // 25205, 00000, "the QUEUE %s.%s does not exist" // *Cause: The specified queue does not exist. // *Action: Create the queue first before specifying it for enqueue or dequeue. // 25206, 00000, "enqueue failed, enqueue to exception queue %s.%s not permitted" // *Cause: An attempt was made to enqueue to an exception queue. // *Action: Try enqueueing to another queue. // 25207, 00000, "enqueue failed, queue %s.%s is disabled from enqueueing" // *Cause: The queue has been stopped to prevent any further enqueueing. // *Action: Enable the queue first by using an administrative operation. // 25208, 00000, "RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE" // *Cause: A relative message identifier should be specified if sequence // deviation is specified as BEFORE. // *Action: Either specify an existing relative message identifier or // don't specify sequence deviation as BEFORE. // 25209, 00000, "invalid value %s, EXPIRATION should be non-negative or NEVER" // *Cause: The expiration is less than zero or NULL. // *Action: Specify a valid value for expire_after which should be greater // than or equal to zero or NEVER. // 25210, 00000, "invalid value for RELATIVE_MSGID, no message in queue with that msgid" // *Cause: No message inm the queue with the msgid equal to the specified // RELATIVE_MSGID. // *Action: Try again with a valid RELATIVE_MSGID. // 25211, 00000, "invalid DELAY specified when using sequence deviation" // *Cause: The DELAY specified in the enqueue is greater than the delay // of the message with the given relative message id. // *Action: Set the DELAY to be less than or equal to the delay of the // message with the given relative message id. If the TOP option // is used the delay must be less than or equal to the delay of // all the messages in the queue. // 25212, 00000, "invalid PRIORITY specified when using sequence deviation" // *Cause: The PRIORITY specified in the enqueue is less than the priority // of the message with the given relative message id. // *Action: Set the PRIORITY to be less than the delay of the message with // the given relative message id. If the TOP option is used the // prioirty must be greater than or equal to the priority of // all the messages in the queue. 25213, 00000, "message with specified RELATIVE_MSGID has been dequeued" // *Cause: The message specified by the RELATIVE_MSGID field in the // sequence deviation BEFORE option has been dequeued. // *Action: 25215, 00000, "user_data type and queue type do not match" // *Cause: A user tries to enqueue an object to a queue that was // created for objects of different type. // *Action: Try enqueue again with an object of the right type. 25216, 00000, "invalid recipient, either NAME or ADDRESS must be specified" // *Cause: Both attributes, NAME and ADDRESS, were specified null for one of // the recipients in the recipient list. // *Action: Specify a non-null NAME or ADDRESS for the recipient. 25217, 00000, "enqueue failed, visibility must be IMMEDIATE for queue %s.%s" // *Cause: An attempt was made to enqueue to a non-persistent queue without // setting visibility to IMMEDIATE. // *Action: Set visibility to IMMEDIATE. 25218, 00000, "enqueue failed, delay must be zero for queue %s.%s" // *Cause: An attempt was made to enqueue to a non-persistent queue with // delay greater than zero seconds. // *Action: Set delay to zero. 25219, 00000, "enqueue failed, sequence deviation not allowed for queue %s.%s" // *Cause: An attempt was made to enqueue to a non-persistent queue with // sequence deviation specified. // *Action: Do not specify sequence deviation. 25220, 00000, "enqueue failed, signature not specified for a non-repudiable queue" // *Cause: An attempt was made to enqueue to a non-repudiable queue without // specifying the signature // *Action: Give the signature 25221, 00000, "enqueue failed, signature specified queue not supporting non-repudiation" // *Cause: An attempt was made to enqueue to a queue specifying the signature // for a queue not supporting non-repudiation // *Action: Remove the signature 25222, 00000, "enqueue failed, complete sender info. not provided for a queue supporting non-repudiation" // *Cause: An attempt was made to enqueue to a queue without giving the // complete sender information (name) for a queue supporting // non-repudiation // *Action: Provide the sender information // 25223, 00000, "user_data type used is not supported" // *Cause: An attempt was made to enqueue data into a non persistent queue // that is of a type other than the supported raw or object type. // *Action: Enqueue the message again with data of raw or object type. // / / 25225-25249 Reserved for DBMS_AQ.DEQUEUE / 25225, 00000, "invalid value %s, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED" // *Cause: An invalid parameter has been specified for DEQUEUE_MODE. // // *Action: Specify either REMOVE, BROWSE or LOCKED. // 25226, 00000, "dequeue failed, queue %s.%s is not enabled for dequeue" // *Cause: The queue has not been enabled for dequeue. // // *Action: Enable the queue using START_QUEUE. // 25228, 00000, "timeout or end-of-fetch during message dequeue from %s.%s" // *Cause: User-specified dequeue wait time has passed or the end of the // queue has been reached but no message has been retrieved. // *Action: Try dequeue again with the appropriate WAIT_TIME or the // FIRST_MESSAGE option. // 25229, 00000, "error on transformation of message %s %s" // *Cause: There was an error when transforming a message at enqueue, // dequeue or propagation time. // *Action: Correct the transformation function. // 25230, 00000, "invalid value %s, WAIT should be non-negative" // *Cause: A negative value has been specified for WAIT. // *Action: specify a non negative value or FOREVER. // 25231, 00000, "cannot dequeue because CONSUMER_NAME not specified" // *Cause: A user tried to dequeue from a queue that has been created for // multiple consumers but a CONSUMER_NAME was not been specified in // the dequeue options. // *Action: Specify the CONSUMER_NAME in the dequeue options. // 25232, 00000, "duplicate recipients specified for message" // *Cause: An enqueue was performed with duplicate queue agents in the // recipients parameter. // *Action: Remove the duplicate queue agent and retry the call. // 25233, 00000, "invalid parameter specified for NAVIGATION" // *Cause: An invalid parameter has been specified for NAVIGATION. // *Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. // Use FIRST_MESSAGE for dequeuing the first message that satisifies // the criterion, NEXT_MESSAGE for dequeuing the next message // that satisifies the criterion and NEXT_TRANSACTION for moving to a // set of messages enqueued by another transaction. // 25234, 00000, "NEXT_TRANSACTION navigation option invalid for queue table %s.%s" // *Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from // a queue in a queue table that was not created for transactional // grouping. // *Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation // option. If you want to dequeue messages using transactional grouping // create the queue in a queue table that has transactional grouping // enabled. // 25235, 00000, "fetched all messages in current transaction" // *Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when // there were no more messages that belong to the same transaction. // *Action: Use the NEXT_TRANSACTION navigation option to move to the next // also use the FIRST_MESSAGE option to start from the head of the // queue again. // 25236, 00000, "buffer too small for user data" // *Cause: The variable or buffer used for the out parameter payload is // too small for the user data dequeued. // *Action: Increase the size of the buffer or the size of the variable. // Maximum size allowed is 32K. // 25237, 00000, "navigation option used out of sequence" // *Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after // dequeuing all the messages. // *Action: Reset the dequeuing position using the FIRST_MESSAGE naviagtion // option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION // option. // 25238, 00000, "too many recipients specified for message destination %s" // *Cause: An ENQUEUE was performed with more than 32 recipients for // the given destination (address). // *Action: Reduce the number of recipients to 32 or less, and retry the call. // 25239, 00000, "message ID not supplied when dequeuing from exception queue %s.%s" // *Cause: An attempt was made to dequeue from a release 8.0-compatible // exception queue without including a message ID in the dequeue // options. // *Action: Check the application to ensure that the queue name has been // specified correctly. If the queue name is correct supply a message // ID when dequeuing from a release 8.0-compatible exception queue. // Otherwise, upgrade the queue_table containing the queue to // release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE // procedure. // 25240, 00000, "message ID and dequeue condition/correlation ID specified in dequeue options" // *Cause: An attempt was made to dequeue by including both a message ID and // a dequeue condition/correlation ID in the dequeue options. // In the dequeue options, you are permitted to specify either // message ID or dequeue condition/correlation ID, or neither. // *Action: To dequeue a message, specify a message ID or a dequeue // condition/correlation ID in the dequeue options, but do not // specify both. If you want to dequeue in the queue's sort order, // then do not specify either the message ID or dequeue // condition/correlation ID in the dequeue options. 25241, 00000, "cannot change correlation ID from %s to %s without FIRST_MESSAGE option" // *Cause: An attempt was made to change the correlation ID while using the // NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. // *Action: To use a correlation ID that is different from the previous // dequeue call, reset the dequeuing position by using the // FIRST_MESSAGE navigation option. // 25242, 00000, "cannot change subscriber name from %s to %s without FIRST_MESSAGE option" // *Cause: An attempt was made to change the subscriber name while using the // NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. // *Action: To use a subscriber name that is different from the previous // dequeue call, reset the dequeuing position by using the // FIRST_MESSAGE navigation option. // 25243, 00000, "CONSUMER_NAME cannot be specified when dequeuing from exception queue %s.%s" // *Cause: An attempt was made to dequeue from an exception queue by specifying // the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only // be specified when dequeuing from a normal queue created for multiple // consumers. // *Action: Specify only the message id in the dequeue options to dequeue a // message from an exception queue. // 25244, 00000, "dequeue index key not found, QUEUE %s, rowid %s" // *Cause: An internal error was encountered. There may be an inconsistency in // the queue table index. // *Action: Contact your Oracle customer support representative. You may need // to provide the trace file and information about reproducing the // error. // // 25245, 00000, "agent name cannot be specified if address is a single-consumer queue or an exception queue" // *Cause: The agent name for the agent in the LISTEN call was specified // when the agent address was a single-consumer queue or an exception // queue. // *Action: Do not specify the agent name. 25246, 00000, "listen failed, the address %s is an 8.0 style exception queue" // *Cause: An 8.0 style exception queue was specified in the agent-list for // the LISTEN call. // *Action: Specify a normal 8.0 style queue or an 8.1 style queue in the // agent-list. // 25247, 00000, "%s is not a recipient of specified message" // *Cause: The consumer name specified in the dequeue options is not a // recipient of the message specified by the message id. // *Action: Ensure that the agent specified by the consumer name is a // recipient of the message specified by the message id. // 25248, 00000, "duplicate agent specified in the agent list" // *Cause: An agent was specified more than once in the agent list of the // LISTEN call. // *Action: Remove the duplicate agent specification(s), and retry the call. 25249, 00000, "dequeue failed, dequeue not allowed for queue %s.%s" // *Cause: An attempt was made to dequeue from a non-persistent queue. // *Action: Dequeue from a different queue. 25250, 00000, "Cannot specify a remote recipient for the message" // *Cause: A recipient for the message enqueued to a non-persistent queue // had a non-local address. // *Action: Do not specify the address field or specify the queue which // is the target of the enqueue 25251, 00000, "exceeded maximum number of recipients for message" // *Cause: An attempt was made to issue an ENQUEUE call that exceeded the // the maximum number (1024) of recipients per message. // *Action: Reduce the number of recipients to 1024 or less, and retry // the call. 25252, 00000, "listen failed, the address %s is a non-persistent queue" // *Cause: A non-persistent queue was specified as an address for an agent in // the LISTEN call. // *Action: Specify a normal queue as address for the agent, and retry the // the LISTEN call. 25253, 00000, "listen failed, queue %s.%s is not enabled for dequeue" // *Cause: An attempt was made to specify a queue that is not enabled for // dequeue in a LISTEN call. // *Action: Enable the queue for dequeue using START_QUEUE, and retry // the LISTEN call. 25254, 00000, "time-out in LISTEN while waiting for a message" // *Cause: The specified wait time has elapsed and there were no messages for // any of the agents in the agent-list. // *Action: Try the LISTEN call with an appropriate time-out. 25255, 00000, "incorrect subscription string %s" // *Cause: An incorrect subscription string was specified with OCIRegister. // *Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE // form. 25256, 00000, "consumer cannot be specified with a single-consumer queue or an exception queue " // *Cause: An attempt was made to specify a consumer in the subscription // string when registering for notification on a single-consumer // queue or an exception queue. // *Action: Do not specify the consumer in the subscription string. 25257, 00000, "consumer must be specified with a multi-consumer queue" // *Cause: An attempt was made to register on a multi-consumer queue without // specifying a consumer in the subscription string. // *Action: Specify a consumer in the subscription string. 25258, 00000, "cannot register for notifications on an 8.0 style exception queue" // *Cause: An attempt was made to specify an 8.0 style exception queue in the // subscription string of OCIRegister. // *Action: Specify a normal queue or a non-persistent queue. 25259, 00000, "cannot specify protocol for agent" // *Cause: The user specified the protocol attribute for an agent in the // agent list. // *Action: Do not specify the protocol attribute of the agent object type. / 25260, 00000, "AQ latch cleanup testing event" // *Cause: N/A. // *Action: event used for AQ statistics latch cleanup testing. 25261, 00000, "JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation" // *Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that // is insufficient for AQ propagation. // *Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ // propagation. 25262, 00000, "agent name cannot be NULL if address is a multi-consumer queue" // *Cause: The name for the agent in the LISTEN call was not specified // when the agent address was a multi-consumer queue. // *Action: Specify a non-NULL name for the agent. / 25263, 00000, "no message in queue %s.%s with message ID %s" // *Cause: An attempt was made to dequeue a message with a specific // message ID, but no such message exists in the queue. // *Action: Try dequeue again with a valid message ID. 25264, 00000, "cant get signature for this queue" // *Cause: An attempt was made to dequeue the signature from this queue, which // is not reciever non-repidiable. // *Action: Try dequeue again without the get signature option 25265, 00000, "specified signature for a queue which does not support reciever non-repudiation" // *Cause: An attempt was made to dequeue the message from a queue which // does not support reciever non-repudiation, but the signature was // specified for verification // *Action: Try dequeue again without the signature 25266, 00000, "didnt try to dequeue by message id. with the signature" // *Cause: The signature was specified for a queue, but the dequeue was not // done by message id. // *Action: Try dequeue again by message id. 25267, 00000, "didnt specify the signature for a reciever non-repudiable queue" // *Cause: The signature was not specified for a reciever non-repudiable queue // *Action: Try dequeue again along with the signature 25268, 00000, "didnt dequeue in browse mode with get signature option" // *Cause: The dequeue was not performed in browse mode with get signature option // *Action: Try dequeue again in browse mode 25269, 00000, "cant specify sognature with get signature option" // *Cause: The signature is not required for the dequeue with get signature // option // *Action: Try dequeue again without the signature in dequeue options 25270, 00000, "sender info does not match with the actual sender of the message" // *Cause: The sender info. and the message id. do not match // *Action: Provide the right sender info. // *Action: Try dequeue again without the signature in dequeue options 25271, 00000, "queue table not found for the given queue" // *Cause: The queue table does not exist for the given queue // *Action: Provide the right queue name 25272, 00000, "Signature does not exist for the given reciever and message id." // *Cause: Signature does not exist for the given reciever and message id. // *Action: Check the message id. and the reciever's information 25273, 00000, "AQ QMN process alternate cleanup event" // *Cause: N/A. // *Action: event used for AQ QMN alternate cleanup mode. / / 25276-25300 Reserved for AQ administration callouts / 25276, 00000, "table specified is not a queue table" // *Cause: An invalid queue table name is specified. // *Action: Check the dictionary views to see if the table is a queue table. // 25277, 00000, "cannot grant or revoke object privilege on release 8.0 compatible queues" // *Cause: An attempt was made to grant or revoke object privilege on // release 8.0 style queues. // *Action: Convert the release 8.0 compatible queue table to release 8.1 // compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting // or revoking object privilege. // 25278, 00000, "grantee name cannot be NULL" // *Cause: An attempt was made to specify NULL for the grantee parameter. // *Action: Specify a valid grantee parameter. // 25279, 00000, "dequeue as select not supported before 8.2" // *Cause: Dequeue as select not supported before 8.2. // *Action: Dont use select condition while dequeuing 25280, 00000, "complete sender information not provided to non-repudiate sender" // *Cause: complete sender information not provided to non-repudiate sender // *Action: Provide the complete sender information 25281, 00000, "complete reciever information not provided to non-repudiate reciever" // *Cause: complete reciever information not provided to non-repudiate reciever // *Action: Provide the complete reciever information 25282, 00000, "message id. not provided for non-repudiation" // *Cause: message id. was not provided // *Action: Provide the message id. 25283, 00000, "either agent's name or address needed for non-repudiation" // *Cause: neither agent's name nor address provided for non-repudiation" // *Action: Provide the agent info. 25284, 00000, "Invalid value %s for %s" // *Cause: An Invalid value or NULL was specified for the parameter. // *Action: Check the documentation for valid values. 25285, 00000, "Invalid value %s for array_mode" // *Cause: An Invalid value or NULL was specified for the array_mode. // *Action: Check the documentation for valid values. 25286, 00000, "Invalid number of elements in the message properties array" // *Cause: Number of elements in the message properties array do not match the // number of elements in the payload array. // *Action: Create a message property array with one element (that // applies for all the elements in the payload array) or // create a message property array with the same number of elements as // there are in the payload array. 25287, 00000, "Invalid value %s, %s should be non-negative" // *Cause: An Invalid value or NULL was specified for the parameter. // *Action: Specify a non negative integer. 25288, 00000, "AQ HTTP propagation encountered error, status-code %d, %s" // *Cause: AQ propagation's HTTP request to the propagation servlet at the // specified address encountered an error // *Action: Specify a valid address in the connect string of the propagation // destination dblink, the dblink user has the correct permissions, // check if the AQ propagation servlet was properly installed. / / 25350-25375 Reserved for V8 Transaction OCI 25350, 00000, "maximum number of concurrent transaction branches exceeded" // *Cause: the limit on the number of concurrent transaction branches has // been reached // *Action: Increase the INIT.ORA parameter 'transactions' and restart the // system. 25351, 00000, "transaction is currently in use" // *Cause: The transaction is currently used by a different session. // *Action: Do not switch to a transaction attached to some other session. 25352, 00000, "no current transaction" // *Cause: The user session is not attached to any transaction. // *Action: Do not attempt to detach when there is no current transaction. 25353, 00000, "branch marked for deletion" // *Cause: The branch specified cannot be killed immediately because another // session is using the branch, but it has been marked for kill. This // means it will be deleted as soon as possible after the current // uninterruptable operation is completed. // *Action: No action is required for the branch to be deleted. / / 25400-25425 Reserved for Application Failover / 25400, 00000, "must replay fetch" // *Cause: A failure occured since the last fetch on this statement. Failover // was able to bring the statement to its original state to allow // continued fetches. // *Action: This is an internally used error message and should not be seen // by the user. 25401, 00000, "can not continue fetches" // *Cause: A failure occured since the last fetch on this statement. Failover // was unable to bring the statement to its original state to allow // continued fetches. // *Action: Reexecute the statement and start fetching from the beginning 25402, 00000, "transaction must roll back" // *Cause: A failure occured while a transaction was active on this // connection. // *Action: The client must roll back. // 25403, 00000, "could not reconnect" // *Cause: The connection to the database has been lost, and attempts to // reconnect have failed. // *Action: Manually reconnect. // 25404, 00000, "lost instance" // *Cause: The primary instance has died. // *Action: This is an internally used error message and should not be seen // by the user. // 25405, 00000, "transaction status unknown" // *Cause: A failure occured while a transaction was attempting to commit. // Failover could not automatically determine instance status. // *Action: The user must determine the transaction's status manually. 25406, 00000, "could not generate a connect address" // *Cause: Failover was unable to generate an address for a backup instance. // *Action: Contact Oracle customer support. // 25407, 00000, "connection terminated" // *Cause: The connection was lost while doing a fetch. // *Action: This is an internally used error message and should not be seen // by the user. // 25408, 00000, "can not safely replay call" // *Cause: The connection was lost while doing this call. It may not be // safe to replay it after failover. // *Action: Check to see if the results of the call have taken place, and then // replay it if desired. // 25425, 00000, "connection lost during rollback" // *Cause: The connection was lost while issuing a rollback. // *Action: If the transaction is not externally coordinated, then Oracle // implicitly rolled back, so no action is required. Otherwise // examine pending_trans$ to determine if "rollback force" is // required. / / 25426-25435 Reserved for Dblink Concentration / 25426, 00000, "remote instance does not support shared dblinks" // *Cause: A shared dblink is being used to connect to a remote instance // that does not support this feature because it is an older version. // *Action: Use a normal dblink if you need to connect to this instance. / / 25436-25475 Reserved for Rules Engine / 25436, 00000, "ruleset specified does not exist" // *Cause: An attempt to access a ruleset was made, but the ruleset // referenced does not exist. // *Action: Look up the correct name of the ruleset in USER_RULESETS. 25437, 00000, "rule %s does not exist" // *Cause: An attempt to access a rule was made, which failed because the // rule does not exist. // *Action: Look up the rule in the rules storage table, which can be found // from USER_RULESETS. 25438, 00000, "table specified does not exist" // *Cause: An attempt to define a ruleset on a table was made, which failed // because the rule does not exist. // *Action: Define rulesets only on existing tables. / 25439 is reserved for the dump 25440, 00000, "duplicate ruleset" // *Cause: An attempt to define a ruleset was made, which failed because // a ruleset with the same name exists in the same schema. // *Action: Define a ruleset with a different name. 25441, 00000, "duplicate rule %s" // *Cause: An attempt to define a rule was made, which failed because // a rule with the same name already exists in the same ruleset. // *Action: Define a rule with a different name. / / 25500-25525 Reserved for Quiesce Database Feature Errors / 25500, 00000, "database is not open" // *Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED // command. // *Action: Open the database and retry this command. 25501, 00000, "ALTER SYSTEM QUIESCE RESTRICTED command failed" // *Cause: Database resource manager failed to change plan. // *Action: Look at the alert logs to see detailed description of the error. 25502, 00000, "concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running" // *Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER // SYSTEM UNQUIESCE command running in the system. // *Action: Contact the database administrator who is responsible for the // concurrent command. 25503, 00000, "cannot open database because the database is being quiesced" // *Cause: Database cannot be opened because the system is being or has // been quiesced. // *Action: Open the database after the system has been quiesced. 25504, 00000, "the system is already in quiesced state" // *Cause: Cannot quiesce the system because the system is already quiesced. // *Action: 25505, 00000, "the system is not in quiesced state" // *Cause: Cannot unquiesce the system because the system is not in quiesced // state. // *Action: 25506, 00000, "resource manager has not been continuously on in some instances" // *Cause: Cannot quiesce the system because resource manager has not been // continuously on since startup in this or some other instances. // *Action: 25507, 00000, "resource manager has not been continuously on" // *Cause: Cannot quiesce the system because resource manager has not been // continuously on since startup. // *Action: 25508, 00000, "database is not mounted" // *Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE // command. // *Action: Mount the database and retry this command. / / 25950-25999 Reserved for Join Index Errors / 25509, 00000, "operation on \"%s\".\"%s\".%s not allowed" // *Cause: A column has been added to a replicated table, but replication // support processing has not completed. // *Action: Wait until replication support processing has completed // before updating the column / / 25950-25999 Reserved for Join Index Errors / 25950, 00000, "missing where clause in join index specification\n" // *Cause: An attempt to create a join index was made, which failed // because no valid where clause was found. // *Action: Ensure that a where clause with valid join conditions is // specified in the create index statement. 25951, 00000, "join index where clause cannot contain OR condition\n" // *Cause: An attempt to create a join index was made, which failed // because there was an OR branch in the where clause. // *Action: Reformulate the where clause without using ORs. 25952, 00000, "join index must only contain inner equi-joins\n" // *Cause: An attempt to create a join index was made, which failed // because it included a predicate which wasn't an equi-inner join. // *Action: Remove the inappropriate predicate. 25953, 00000, "join index cannot be a functional index\n" // *Cause: An attempt to create a join index was made, which failed // because a functional index was requested or necessary (such as // is the case for indexing columns using timezone). // *Action: Remove any functional indexing columns. 25954, 00000, "missing primary key or unique constraint on dimension\n" // *Cause: An attempt to create a join index was made, which failed // because one or more dimensions did not have an appropriate // constraint matching the join conditions. // *Action: Ensure that the where clause is correct (contains all of the // constraint columns) and that an enforced constraint is on // each dimension table. 25955, 00000, "all tables must be joined in the where clause\n" // *Cause: An attempt to create a join index was made, which failed // because one of the tables in the from clause did not appear // in the where clause. // *Action: Ensure that the where clause contains all from clause tables. 25956, 00000, "join index cannot be created on tables owned by SYS\n" // *Cause: An attempt to create a join index was made, which failed // because one of the tables was owned by SYS. // *Action: Ensure that no join index related table is owned by SYS. 25957, 00000, "join index where clause cannot contain cycles\n" // *Cause: An attempt to create a join index was made, which failed // because the where clause contains a cycle. // *Action: Ensure that the where clause is in the form of a star // or snowflake schema. 25958, 00000, "join index where clause predicate may only contain column references\n" // *Cause: An attempt to create a join index was made, which failed // because a predicate in the where clause contained something // other than a simple column. // *Action: Ensure that the where clause only contains columns. 25959, 00000, "join index must be of the bitmap type\n" // *Cause: An attempt to create a join index was made, which failed // because no bitmap keyword was used. // *Action: Make the index a bitmap index. 25960, 00000, "join index cannot be based on a temporary table\n" // *Cause: An attempt to create a join index was made, which failed // because one of the tables was temporary. // *Action: Ensure no underlying tables are temporary. 25961, 00000, "join index prevents dml cascade constraint operation\n" // *Cause: An attempt to execute dml resulted in the need to perform // dml on another table because of a cascade constraint. // The join index only allows one of its underlying tables // to me modified at a time. // *Action: Drop the join index or remove the constraint. 25962, 00000, "join index prevents multitable insert or merge\n" // *Cause: An attempt to execute an merge or multitable insert on // a table that was used to create a bitmap join index was made. // Merge and multitable inserts are not supported on tables // that were used to create a bitmap join index. // *Action: Drop the join index. / / 26000-26099 Reserved for Direct Path Load Errors / 26000, 00000, "partition load specified but table %s is not partitioned\n" // *Cause: The Loader control file contains a PARTITION clause but the // table being loaded is not partitioned. // *Action: Remove the partition specification from the SQL*Loader control // file and retry the load. 26001, 00000, "Index %s specified in SORTED INDEXES does not exist on table %s\n" // *Cause: A nonexistent index was specified in the SORTED INDEXES clause. // *Action: Do not specify as a SORTED INDEX. 26002, 00000, "Table %s has index defined upon it.\n" // *Cause: Parallel load was specified into a table which has index // defined upon it. // *Action: Drop index(es) defined upon table, or don't use parallel load, // or use SKIP_INDEX_MAINTENANCE option. 26003, 00000, "parallel load not supported for index-organized table %s.\n" // *Cause: Parallel load is not supported for index-organized tables. // *Action: load the index-organized table without the PARALLEL option. 26004, 00000, "Tables loaded through the direct path may not be clustered\n" // *Cause: User attempted to load a clustered table via the direct path. // *Action: Use the conventional path. 26005, 00000, "Invalid handle for direct path load\n" // *Cause: In direct path load, the handle passed in does not match the type // listed. // *Action: Verify the handle and type are correct. 26006, 00000, "Incorrect bind variable in column %s's sql expression - %s\n" // *Cause: In direct path load, the bind variables listed in the // sql expression do not match the input argument column names. // *Action: Verify all the input arguments are listed in the expression as // bind variables, and all the bind variables are listed as // input arguments to the expression. Or verify that there were // no errors in executing the OCI statements when getting the bind // variable list. 26007, 00000, "For INSERT option, table must be empty. Error on table %s\n" // *Cause: The user tried to use the INSERT option on a non-empty table. // *Action: Empty the table from SQL*Plus, or use the REPLACE option. 26008, 00000, "NOT NULL column %s has a nullif clause\n" // *Cause: A column which is NOT NULL in the database has a SQL*Loader nullif // clause on it. // *Action: Remove the nullif clause in the SQL*Loader control file. 26009, 00000, "NOT NULL column %s has a defaultif clause which may evaluate to null\n" // *Cause: A column which is NOT NULL in the database has a SQL*Loader // defaultif clause which may evaluate to null. // // *Action: Remove the defaultif clause in the SQL*Loader control file. 26010, 00000, "Column %s in table %s is NOT NULL and is not being loaded\n" // *Cause: A column which is NOT NULL in the database is not being loaded // and will cause every row to be rejected. // *Action: Load the column by specifying the NOT NULL column in the // INTO TABLE clause in the SQL*Loader control file. 26011, 00000, "Cannot load type %s into column %s in table %s\n" // *Cause: A column can only store data of type declared for that column. // And a substitutable column can only store data of valid subtypes // of the supertype declared for that column. // *Action: Check that the type or subtype specified is valid for that column. 26012, 00000, "No data found while executing sql statement %s for column %s - check input for: %s\n" // *Cause: Executing sql statement against the data dictionary tables // returned "ORA-01403: no data found". // *Action: No data retrieved when selecting against the data dictionary // tables most likely means that there's an error in user input. // Check that the input listed is correct. 26013, 00000, "List allocated may not be big enough\n" // *Cause: There seems to be a discrepancy between the size for a list or // buffer allocated by direct path api and the size needed. // *Action: Contact Oracle Customer Support. 26014, 00000, "OCI_ATTR_DIRPATH_SUBST_OBJ_TBL is set for non-final object table %s\n" // *Cause: Client seem to have set OCI_ATTR_DIRPATH_SUBST_OBJ_TBL for either // a non-object table or for a final object table. This attribute // can only be and must be set for non-final object tables only. // *Action: Check the type of the loading table. Do not set this attribute // if the table is not a non-final object table. 26015, 00000, "Array column %s in table %s is not supported by direct path\n" // *Cause: User attempted to load an array column via the direct path. // *Action: Use the conventional path. 26016, 00000, "Record %s: Rejected - Error on table %s, partition %s" // *Cause: The record indicated caused an ORACLE error on insert. // *Action: Determine the ORACLE error and correct the record. // The offending column(s) are not known. 26017, 00000, "Global indexes not allowed on direct path partition load, table %s" // *Cause: Global indexes are defined on a table when direct path loading a // single partition of the table. / // *Cause: Too many characters were specified in the ORACLE_SID string // *Action: Rename the ORACLE_SID to a string of up to the maximum number of // *Cause: Logical block size for Oracle files must be a multiple of the // physical block size, and less than the maximum. // *Action: Block size specified is returned as additional information, // check INIT.ORA parameters, additional information also indicates // which function encountered the error. 26018, 00000, "Column %s in table %s does not exist\n" // *Cause: Column specified in the loader control file does not exist. // *Action: Make sure the column exists and that you have privileges on it. // Correct the loader control file if it is wrong. 26019, 00000, "Column %s in table %s of type %s not supported by direct path\n" // *Cause: The Specified column of SQL column type %s is not supported by // the direct path loader. // *Action: If the column is NULLable, remove it from the control file // description. Then it will be loaded as a NULL. 26020, 00000, "index %s.%s loaded successfully with %s keys" // *Cause: Non-partitioned index information put to loader log file. // *Action: None. Information only. 26021, 00000, "index %s.%s partition %s loaded successfully with %s keys" // *Cause: Partitioned index information put to loader log file. // *Action: None. Information only. 26022, 00000, "index %s.%s was made unusable due to:" // *Cause: A Non-partitioned index was made index unusable due to the // error displayed below this error. // *Action: Depending on the error, either rebuild the index, or drop and // re-create it. 26023, 00000, "index %s.%s partition %s was made unusable due to:" // *Cause: A partition of a partitioned index was made index unusable due to // error displayed below this error. // *Action: Depending on the error, either rebuild the index partition, // or drop and re-create the entire index. 26024, 00000, "SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable" //* Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment //* was in unusable state prior to the beginning of the load. //* Action: Informational only. User will need to either rebuild the index //* or index partition, or re-create the index. 26025, 00000, "SKIP_INDEX_MAINTENANCE option requested" //* Cause: User requested that index maintenance be skipped on a direct // path load. //* Action: The listed index was put into Index Unusable state due to the user // requesting that index maintenance be skipped. Either rebuild the // index or index partitions, or drop and re-create the index. 26026, 0000, "unique index %s.%s initially in unusable state" //* Cause: A unique index is in IU state (a unique index cannot have //* index maintenance skipped via SKIP_UNUSABLE_INDEXES). //* Action: Either rebuild the index or index partition, or use //* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. 26027, 0000, "unique index %s.%s partition %s initially in unusable state" //* Cause: A partition of a unique index is in IU state (a unique index //* cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES). //* Action: Either rebuild the index or index partition, or use //* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. 26028, 0000, "index %s.%s initially in unusable state" //* Cause: An index is in IU state prior to the beginning of a direct //* path load, it cannot be maintained by the loader. //* Action: Either rebuild the index, re-create the index, or use either //* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only). 26029, 0000, "index %s.%s partition %s initially in unusable state" //* Cause: A partition of an index is in IU state prior to the beginning //* of a direct path load, it cannot be maintained by the loader. //* Action: Either rebuild index partition, re-create the index, or use either //* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only). 26030, 0000, "index %s.%s had %s partitions made unusable due to:" //* Cause: A logical index error occurred on a partitioned index which //* affected one or more index partitions, which are listed below //* this message. //* Action: The affected index partitions will have to be re-built, or, the //* entire index dropped and re-created. 26031, 0000, "index maintenance error, the load cannot continue" //* Cause: A index errror occurred during the index maintenance phase of //* a direct path load. The load cannot continue. See error message //* below this message. //* Action: See action for the error message which follows this one. 26032, 0000, "index %s.%s loading aborted after %s keys" //* Cause: An index error occurred during direct-load of an index-organized table. //* Loading had to be aborted. No rows were loaded. //* Action: Check the key just following the number of keys mentioned above. //* This key caused the index problem mentioned in an earlier message. //* 26033, 0000, "error while evaluating index %s.%s, row %s due to:" //* Cause: An index error occurred while attempting to evaluate an expression //* on a functional index. //* Action: Verify that the input data is valid for the functional index. 26034, 0000, "end of logical record found when reading length of varying length field\n" //* Cause: While attempting to read the length portion of a varying //* length field, then end of the logical record was reached. //* Action: Verify that the control file describes the data correctly //* and that the data in the data file matches the description //* in the control file 26035, 00000, "Record %s: Rejected - Error on table %s, subpartition %s" // *Cause: The record indicated caused an ORACLE error on insert. // *Action: Determine the ORACLE error and correct the record. // The offending column(s) are not known. 26036, 00000, "subpartition load specified but table %s is not subpartitioned\n" // *Cause: The Loader control file contains a PARTITION clause but the // table being loaded is not subpartitioned. // *Action: Remove the subpartition specification from the SQL*Loader control // file and retry the load. 26037, 00000, "Record %s: Rejected - Error on table %s, subpartition %s" // *Cause: The record indicated caused an ORACLE error on insert. // *Action: Determine the ORACLE error and correct the record. // The offending column(s) are not known. 26038, 00000, "error converting character length field to a number\n" //* Cause: An error occurred while attempting to convert the characters // containing the count portion of a VARCHARC or VARRAWC field. //* Action: Verify that the count portion for the field has the correct value. 26039, 00000, "Table %s has domain index defined upon it\n" // *Cause: Direct path load was specified for a table which has a domain index // defined upon it // *Action: Drop domain index(es) defined on the table or use the conventional // path 26040, 00000, "Data block was loaded using the NOLOGGING option\n" //* Cause: Trying to access data in block that was loaded without //* redo generation using the NOLOGGING/UNRECOVERABLE option //* Action: Drop the object containing the block. / // 26041 - 26044 DATETIME/INTERVAL datatypes 26041, 00000, "DATETIME/INTERVAL datatype conversion error\n" //* Cause: The column could not be converted from DATETIME //* datatype to internal DATETIME/CHARACTER datatype. //*Action: Contact Oracle Customer Support. 26042, 00000, "unable to convert format string into internal form\n" //* Cause: An attempt to convert a DATETIME format string into internal //* format in preparation for DATETIME datatype processing failed. //*Action: Contact Oracle Customer Support. 26043, 00000, "unable to convert time zone for DATETIME/INTERVAL processing\n" //* Cause: An attempt to convert the time zone specified by the ORA_STDZ //* environment variable to internal format failed. //*Action: Verify that the setting for ORA_STDZ is valid. 26044, 00000, "unable to to get DATETIME/INTERVAL reference date\n" //* Cause: An attempt to retrieve the system reference date for //* DATETIME/INTERVAL datatypes failed. //*Action: Contact Oracle Customer Support. / 26045, 00000, "REF column %s expects %s arguments; found %s.\n" // *Cause: The number of arguments for the REF column is incorrect. // *Action: Specify the correct number of input arguments for REFs. // 1. Unscoped system-generated REFs can have exactly 1 or 2 input // arguments. a) It has exactly 1 input argument (one for the OID // value) if a fixed table name was specified through // OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments // (one for the table name and one for the OID value) if a fixed // table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME. // 2. Scoped system-generated REFs can have 1 or 2 input arguments. // Because a table name argument is not needed for a scoped ref, // only 1 argument (OID value) is expected. But if the table name // argument is given, it's still accepted. // 3. Scoped primary-key REFs with N columns in its primary-key OID // can have N or N+1 input arguments. Because a table name argument // is not needed for a scoped ref, only N arguments (making up the // OID value) is expected. But if the table name argument is given, // it's still accepted. 26046, 00000, "REF column %s expects scoped table name %s; user passed in %s.\n" // *Cause: The scoped table name passed in by the user does not match the name // in the schema. // *Action: Specify the correct table name for the scoped REF column. / 26047, 00000, "REF column has invalid value for system generated oid\n" // *Cause: The value passed in by the user for the system generated oid does // not consist of valid hex digits. // *Action: Specify a valid oid value for the REF column. / 26048, 00000, "Scoped REF column has wrong table name.\n" // *Cause: The scoped table name passed in by the user does not match the name // in the schema. // *Action: Specify the correct table name for the scoped REF column. / 26049, 00000, "Unscoped REF column has non-existent table name.\n" // *Cause: The table name passed in by the user does not exist // in the schema. // *Action: Specify a valid table name for the unscoped REF column. / 26050, 00000, "Direct path load of domain index is not supported for this column type.\n" // *Cause: Direct path can not load a domain index of that column type. // *Action: Drop the index and try again or load using conventional path. / 26051, 00000, "internal error parsing packed decimal format string" // *Cause: A packed decimal field with a non-zero scale factor is mapped to // a character column. In order to perform the datatype conversion, // a numeric format string must be created based on the input field's // precision and scale specifications. Direct path loader // encountered an error in creating this format string. // *Action: Examine the packed decimal field's precision and scale // specifications and make sure that they contain valid values. / / // 260xx - 260xx Direct Path API 26076, 0000, "cannot set value after direct path column array is initialized" //* Cause: Client attempted to set or reset the number of rows in a column //* array for a direct path context after the column array is already //* allocated and initialized. //* Action: To set the number of rows in a direct path context's column //* array, call OCIAttrSet with OCI_ATTR_NUM_ROWS only before //* calling OCIHandleAlloc to allocate the column array. 26077, 0000, "direct path column array is not initialized" //* Cause: Client attempted to allocate a column array for a direct path //* function context before allocating a column array for the //* table-level direct path context. //* Action: Allocate the table-level direct path context's column array //* via OCIHandleAlloc before allocating column arrays for //* direct path function contexts. 26078, 0000, "file \"%s\" is not part of database being loaded\n" //* Cause: A parallel load file was specified which is not part //* of the database. //* Action: Check filename and pathname for correctness. 26079, 0000, "file \"%s\" is not part of table %s.%s\n" //* Cause: A parallel load file was specified which is not in the //* tablespace of the table being loaded. //* Action: Check to make sure that the specified parallel load file //* is in the tablespace of the table being loaded. 26080, 0000, "file \"%s\" is not part of table %s.%s partition %s\n" //* Cause: A parallel load file was specified which is not in the //* tablespace of the table (partition, subpartition) being loaded. //* When a partitioned table is being loaded, the file must be //* in the tablespace of every partition or subpartition //* (i.e. each (sub)partition must be in the same tablespace). //* Action: Specify a different parallel load file, or no file at all. 26081, 0000, "load stream synchronization error\n" //* Cause: The row header flag byte contains an unexpected value, this //* indicates that an error has occurred in either the generation //* of, or the pushing of the load stream from the client to the //* server. //* Action: Usually due to an application programming error when dealing //* with error handling, or not resetting the stream state. //* Comments: The trace file contains the previous and the current //* row header flag bytes. Values for the flag bytes are //* defined in kpcdp.h 26082, 0000, "load of overlapping segments on table %s.%s is not allowed" //* Cause: Client application is attempting to do multiple direct path load //* operations on the same table, but the segments overlap. //* Action: Check the partition names (subname attribute of the direct path //* context) being loaded. Make sure you are not loading a table, //* and a partition of the same table. Make sure you are not //* loading a partition, and a sub-partition within the same //* partition. 26083, 0000, "unsupported direct path stream version" //* Cause: The stream version requested is not supported by the server. //* Action: Check to make sure that the VERSION attribute of the direct //* stream is not being set to an invalid value. 26084, 0000, "direct path context already finished" //* Cause: An OCIDirPathLoadStream operation was attempted after //* OCIDirPathFinish was called. Once a direct path operaton //* has been finished, no more data can be loaded. //* Action: Check program logic to make sure OCIDirPathLoadStream is //* not called after OCIDirPathFinish. 26085, 0000, "direct path operation must start its own transaction" //* Cause: A direct path operation is being attempted within a transaction //* that has already been started. //* Action: Commit the transaction and Prepare the direct path operation again. 26086, 0000, "direct path does not support triggers" //* Cause: A direct path operation is being attempted on a table which //* has enabled triggers. //* Action: Disable the triggers on the table and try again. 26087, 0000, "direct path does not support referential constraints" //* Cause: A direct path operation is being attempted on a table which //* has enabled referential integrity constraints. //* Action: Disable the referential integrity constraints on //* the table and try again. 26088, 0000, "scalar column \"%s\" must be specified prior to LOB columns" //* Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be //* specified by the client of the direct path API prior to //* specifying any LOB columns. //* Action: Specify all scalar columns prior to specifying any LOB columns. 26089, 0000, "LONG column \"%s\" must be specified last" //* Cause: A client of the direct path API specified a LONG column to be //* loaded, but the LONG column was not the last column to be //* specified. //* Action: Specify the LONG column last. 26090, 0000, "row is in partial state" //* Cause: A direct path operation is being finished or a data save request //* has been made, but the table for which the request is being made //* on has a row in partial state. The row must be completed before //* the segment high water marks can be moved. //* Action: Either complete the row, or abort the direct path operation. 26091, 0000, "requested direct path operation not supported" //* Cause: A direct path operation was requested that is not supported //* Action: Do not use that operation. Currently, UNLOAD is not supported. 26092, 0000, "only LONG or LOB types can be partial" //* Cause: A column which is not a LONG or LOB had the //* OCI_DIRPATH_COL_PARTIAL flag associated with it. //* Only LONG or LOB type columns can be loaded in pieces. //* Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column. 26093, 0000, "stream offset does not map to a column array" //* Cause: The ROW_COUNT attribute was being read from a direct //* path stream handle and it was found that the stream //* offset for the last processed row did not map to //* a column array offset. //* Action: Make sure the stream was sourced from a column array. 26094, 0000, "stream format error: input column overflow" //* Cause: An input stream contained data for more input columns //* than specified by the client of the direct path API. //* Action: Make sure that the stream being loaded is for the //* correct table. Check initialization sequence. 26095, 0000, "unprocessed stream data exists" //* Cause: Either a OCIDirPathLoadStream call was made which provided //* more stream data prior to the server being able to fully //* process the stream data that it already has, or a //* OCIDirPathFinish call was made when the server had //* unprocessed stream data. //* Action: Most likely an application mis-use of the direct path API. //* Make sure that the stream is not being reset inadvertently //* prior to any previous stream data being processed, or, that //* OCIDirPathFinish is not being called prematurely (i.e. stream //* pushed, error encountered and LoadStream not called to process //* the remainder of the stream before Finish is called.) 26096, 0000, "transfer size too small for row data (%lu bytes required)" //* Cause: Either the transfer buffer size specified, or the default //* transfer buffer size (if you did not specify a size), is //* too small to contain a single row of the converted row data. //* Action: Set the transfer buffer size attribute of the direct path //* context to be larger. 26097, 0000, "unsupported conversion for column %s (from type %d to type %d)" //* Cause: The direct path api does not support the required conversion. //* Action: Make sure the types are correct. //* 26098, 0000, "direct path context is not prepared" //* Cause: A direct path api function was called with a direct path //* context which has not been prepared. //* Action: Make sure all necessary attributes in the direct path //* context have been set, and the context is prepared via //* OCIDirPathPrepare. 26099, 0000, "direct path context is already prepared" //* Cause: OCIDirPathPrepare was called with a context that has already //* been prepared. //* Action: Free the direct path context, set necessary attributes, and //* call OCIDirPathPrepare. / // 26100 - 26110 reserved for tablespace-relative DBA Errors // 26100, 00000, "unused error" // *Cause: // *Action: 26101, 00000, "tablespace # in file header is %s rather than %s for file %s" // *Cause: The tablespace number in the file header is inconsistent // with that in the control file. // *Action: Check if the control file has been migrated correctly. Retry // with the correct control file and data file. 26102, 00000, "relative file # in file header is %s rather than %s for file %s" // *Cause: The relative file number in the file header is inconsistent // with that in the control file. // *Action: Check if the control file has been migrated correctly. Retry // with the correct control file and data file. 26103, 00000, "V6 or V7 data file used to create control file" // *Cause: The file header of the referenced file is in V6 or V7 format. // *Action: Either remove the file from the create control file command, or // somehow migrate the file header to V8 format. / / / 26500 - 26999 Reserved for Replication (KN) / / 26500, 00000, "error on caching \"%s\".\"%s\"" // *Cause: Attempt to cache the replication information which is unavailable // in the catalog for the object. // *Action: Use dbms_reputil.sync_up_rep to validate the replication catalog, // or use dbms_reputil.make_internal_pkg to validate internal // package. 26501, 00000, "RepAPI operation failure" // *Cause: An external RepAPI operation failed. // *Action: consult detail error message. 26502, 00000, "error resignal" // *Cause: An internal service failed and signalled an error" // *Action: consult detail error message. 26503, 00000, "internal RepAPI operation failure on object %s.%s" // *Cause: An unexpected internal RepAPI failure was detected // *Action: Contact Oracle support. 26504, 00000, "operation not implemented" // *Cause: The caller requested a RepAPI operation that was not implemented // *Action: Do not issue this call. 26505, 00000, "unexpected internal null" // *Cause: An internal buffer control structure was NULL // *Action: Verify that sufficient memory resources are available to RepAPI. 26506, 00000, "null global context" // *Cause: An internal buffer control structure was NULL // *Action: Verify that sufficient memory resources are available to RepAPI. 26507, 00000, "null master connection" // *Cause: The master connection handle was or became invalid. // *Action: Verify that the master connection is valid. 26508, 00000, "null materialized view connection" // *Cause: The client connection handle was or became invalid. // *Action: Verify that the client connection is valid. 26509, 00000, "null materialized view control structure" // *Cause: An internal materialized view control structure could not be // obtained. // *Action: Check that the owner and users provided are correct. 26510, 00000, "materialized view name: '%s' is greater than max. allowed length of %s bytes" // *Cause: The specified materialized view name was too long. // *Action: Shorten the materialized view name. 26511, 00000, "master table '%s.%s' not found" // *Cause: A RepAPI operation was attempted against a non-existent or // invalid master table // *Action: Verify that the master table object exists. 26512, 00000, "error pushing transaction to def$error" // *Cause: An unexpected error occurred while sending an def$error rpc to // the master site // *Action: Verify that the DBMS_DEFER package is valid and executable // by the RepAPI client. Contact the local or master site // administrator, if necessary. 26513, 00000, "push error: master proc. %s$RP.%s failed for trans:%s seq:%s" // *Cause: A conflict/error occurred at the master site while executing // a $RP.rep_insert(), rep_update(), or rep_delete() function which // was not handled by conflict resolution logic at the master. // *Action: Notify master site system adminstrator or DBA. 26514, 00000, "object '%s.%s' not found" // *Cause: The specified object was expected but not found. // *Action: Verify that the specified object exists and is valid. 26515, 00000, "no master log available for '%s.%s'" // *Cause: The specified master log was not found or available for the // named table. // *Action: Create the master log at the master site or correct any problems // that may exist with the log. 26516, 00000, "no push transaction acknowledgement" // *Cause: RepAPI was unable to confirm that the last pushed transaction // was successfully commited by the master site. // *Action: Verify that the communications link between the local site and // the master site is still valid. If the transaction has not been // committed at the master, repush the transaction. 26517, 00000, "materialized view control entry for '%s.%s' was not found" // *Cause: The specified materialized view catalog control reocrd was not // found. // *Action: Verify that the local materialized view catalog is valid and that // the local materialized view is properly defined. 26518, 00000, "push queue synchronization error detected" // *Cause: Client tried to repush a transaction has already been committed at // the master site. A common cause of this problem is an error at the // local site in initializing or updating the local site transaction // sequence mechanism. // *Action: Verify that transaction data that RepAPI was attempting to // repushed to the master site exists at the master table and is // valid and consistent with the local site. If this error occurs, // redundantly identified transactions are ignored and then purged // from the local updatable materialized view logs. Check that the // local site is correctly assigning new transactionIDs and is not // accidently generating non-unique values. // 26519, 00000, "no memory available to allocate" // *Cause: There was no memory left for the RepAPI process. This error // may occur when RepAPI is trying to allocate a new table buffer // area. // *Action: Shutdown one or more local applications to attempt to free // heap memory and retry the RepAPI operation. 26520, 00000, "internal memory failure" // *Cause: An internal memory error was detected. // *Action: Check if other errors have occurred or determine if any local // application may have corrupted the memory subsystem. 26521, 00000, "rpc initialization error" // *Cause: An error occurred during the initialization of a PL/SQL rpc. // *Action: Verify that the procudure to be invoked exists and is valid // at the master site and is executable by the RepAPI user. 26522, 00000, "rpc execution error" // *Cause: An error occurred during the execution of a PL/SQL rpc. // *Action: Check the error messages from the remote procedure and fix any // remote site problems that may be preventing the execution of the // invoked rpc. 26523, 00000, "rpc termination error" // *Cause: An error occurred during the termination of a PL/SQL rpc. This // is usually caused by master site being unable to close an // opened cursor or if RepAPI cannot deallocate internal memory. // *Action: Fix any server side problems first, determine if the RepAPI // memory subsystem has been corrupted. 26524, 00000, "nls subsystem initialization failure for product=%s, facility=%s" // *Cause: The NLS product/facility error message file could not be located or // properly initialized. // *Action: Check that the error message directory and file(s) have been // properly installed. 26525, 00000, "session connection attempt failed for %s (@%s)" // *Cause: A connection could not be established to the specified database // using the provided connection string. // *Action: Check that the user, password, connect string, names services, // network, and any remote site listener process are properly // installed and working. 26526, 00000, "materialized view sql ddl parse/expansion failed for %s.%s" // *Cause: The client sql materialized view definition query could not be // properly parsed by the master Oracle site. // *Action: Check that materialized view ddl sql is compatible with the // currently connected version of Oracle and does not violate any of // the RepAPI sql limitations or restrictions. 26527, 00000, "local store callback init phase failed for '%s.%s'" // *Cause: The client callback failed during its INIT phase for the // named object. // *Action: Verify that the objects referenced by the client callback exist // and are valid. Refer to the vendor-specific callback error code // reference to diagnose the local problem. Record all error state // and notify Oracle support. 26528, 00000, "local store callback proc phase failed for '%s.%s'" // *Cause: The client callback failed during its PROC phase for the // named object. // *Action: Refer to the vendor-specific callback error code // reference to diagnose the local problem. Record all error state // and notify Oracle support. 26529, 00000, "local store callback term phase failed for '%s.%s'" // *Cause: The client callback failed during its TERM phase for the // named object. // *Action: Refer to the vendor-specific callback error code // reference to diagnose the local problem. Record all error state // and notify Oracle support. 26530, 00000, "unable to build materialized view refresh control list" // *Cause: The materialized view control list could not be constructed. This // is generally the result of an error while accessing the local // materialized view catalog. // *Action: Verify that the named materialized view(s) are properly defined // and valid. 26531, 00000, "replication parallel push failure recovery test event" // *Cause: N/A. // *Action: event used to simulate site failure for parallel push testing. 26532, 00000, "replication parallel push simulated site failure" // *Cause: A parallel push executed with event 26531 enabled raises this // error to simulation failure of network or destination site. // *Action: Do not enable the event for normal operation. 26534, 00000, "collision: tranID %ld ignored and purged" // *Cause: A transaction that was pushed had a transaction ID that collided // with a transaction that was previously pushed and committed // at the master site. // *Action: See the action section for E_QUEUESYNC (26518). 26535, 00000, "%ud byte row cache insufficient for table with rowsize=%ud" // *Cause: A transaction that was pushed had a transaction ID that collided // with a transaction that was previously pushed and committed // at the master site. // *Action: Increase the RepAPI row buffer size or reduce the width of the // replicated tables. 26536, 00000, "refresh was aborted because of conflicts caused by deferred transactions" // *Cause: There are outstanding conflicts logged in the DEFERROR table at // the materialized view's master site. // *Action: Resolve the conflicts in the master DEFERROR table and refresh // again after the table is empty. Alternatively, refresh with // REFRESH_AFTER_ERRORS, even if there are conflicts in the master's // DEFERROR table. Proceeding despite conflicts can result in an // updatable materialized view's changes appearing to be temporarily // lost, until a refresh succeeds after the conflicts are resolved. 26562, 00000, "last RepAPI error" 26563, 00000, "renaming this table is not allowed" // *Cause: Attempt to rename a replicated table, an updatable materialized view // table or the master table of a materialized view for which a // materialized view log has beencreated. // *Action: If desired, unregister the replicated table with // dbms_repcat.drop_master_repobject, or use the recommended // procedure to rename the master table of a materialized view. 26564, 00000, "%s argument is not of specified type" // *Cause: User passed type of the given argument number doesn't match // with the type of the argument in the stored arguments. // *Action: Invoke correct type procedure (i.e. get_XXX_arg) 26565, 00000, "Call to _arg made before calling dbms_defer.call" // *Cause: User invoked _arg procedure before starting a deferred call // *Action: Invoke various procedures in the correct order. 26566, 00000, "Couldn't open connect to %s" // *Cause: Failed to open connection using given dblink // *Action: Make sure that the dblink is valid and remote m/c is up. 26571, 00000, "%s.%s.%s: number of arguments (%s) does not match replication catalog" // *Cause: number of arguments does not match replication catalog // *Action: examine total number of arguments for the rpc call 26572, 00000, "%s.%s.%s: argument %s does not match replication catalog" // *Cause: the (rpc) call is corrupted // *Action: examine total number of arguments and each argument for // the rpc call 26575, 00000, "remote database does not support replication parallel propagation" // *Cause: The remote database has a version lower than Oracle 8.0 and hence // does not understand replication parallel propagation. // *Action: Use serial propagation or upgrade the remote database to // Oracle 8.0 or above. 26576, 00000, "cannot acquire SR enqueue" // *Cause: An attempt to acquire the SR enqueue in exclusive mode failed. // *Action: / / / 27000-27299 Reserved for Oracle8 Unix OSDs / (skgfr, skgfq, ...) / / 27000 - 27030 keep for SKGFQ (Also 27190-27229) / 27000, 00000, "skgfqsbi: failed to initialize storage subsystem (SBT) layer" // *Cause: sbtinit returned an error, additional information indicates // error // *Action: verify that vendor's storage subsystem product is operating // correctly 27001, 00000, "unsupported device type" // *Cause: the specified device type is supported on this platform // *Action: check V$BACKUP_DEVICE for supported device types 27002, 00000, "function called with invalid device structure" // *Cause: internal error, aditional information indicates which // function encountered error // *Action: check for trace file and contact Oracle Support 27003, 00000, "cannot open file on device allocated with NOIO option" // *Cause: internal error, a file is being created/retrieved on a device // allocated with NOIO option, additional information indicates // which function encountered error // *Action: check for trace file and contact Oracle Support 27004, 00000, "invalid blocksize specified" // *Cause: internal error, blocksize specified is incorrect for the // device on which file is being created, aditional // information indicates blocksize specified, and the // function that encountered the error // *Action: check for trace file and contact Oracle Support 27005, 00000, "cannot open file for async I/O on device not supporting async" // *Cause: internal error, a file is being opened for async I/O on a // device that does not support async I/O, additional // information indicates which function encountered error // *Action: check for trace file and contact Oracle Support 27006, 00000, "sbtremove returned error" // *Cause: additional information indicates error returned by sbtremove, // and the function that encountered the error // *Action: verify that vendor's storage subsystem product is operating // correctly 27007, 00000, "failed to open file" // *Cause: sbtopen returned error, additional information indicates error // returned from sbtopen, and the function that encountered // the error // *Action: verify that vendor's storage subsystem product is operating // correctly 27008, 00000, "function called with invalid file structure" // *Cause: internal error, aditional information indicates which // function encountered error // *Action: check for trace file and contact Oracle Support 27009, 00000, "skgfwrt: cannot write to file opened for read" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27010, 00000, "skgfwrt: write to file failed" // *Cause: sbtwrite returned error, additional information indicates // error returned from sbtwrite // *Action: verify that vendor's storage subsystem product is operating // correctly 27011, 00000, "skgfrd: cannot read from file opened for write" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27012, 00000, "skgfrd: read from file failed" // *Cause: sbtread returned error, additional information indicates // error returned from sbtread // *Action: verify that vendor's storage subsystem product is operating // correctly 27013, 00000, "skgfqdel: cannot delete an open file" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27014, 00000, "skgfqpini: translation error while expanding SS_UDMPDIR" // *Cause: Failure of sltln in skgfqpini // *Action: Check additional return error for more information. 27015, 00000, "skgfcls: failed to close the file" // *Cause: sbtclose returned error, additional information indicates // error returned from sbtclose // *Action: verify that vendor's storage subsystem product is operating // correctly 27016, 00000, "skgfcls: sbtinfo returned error" // *Cause: additional information indicates error returned from sbtinfo // *Action: verify that vendor's storage subsystem product is operating // correctly 27017, 00000, "skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)" // *Cause: media handle string length exceeds SSTMXQMH // *Action: verify that vendor's storage subsystem product is operating // correctly, and that the platform limit (SSTMXQMH) is atleast // 64 (the limit specified for sbtinfo). additional information // indicates the media handle string length returned by sbtinfo, and // the limit (SSTMXQMH) 27018, 00000, "BLKSIZE is not a multiple of the minimum physical block size" // *Cause: User-specified BLKSIZE (blocking factor) is not a multiple of // the minimum block size that is permitted on this platform. // *Action: Two ADDITIONAL INFORMATION messages are displayed which show the // blocking factor provided by the user and the minimum physical // block size. Specify a BLKSIZE that is an integral multiple // of the minimum block size. 27019, 00000, "tape filename length exceeds limit (SBTOPMXF)" // *Cause: length of tape filename provided to sequential I/O OSD functions is // too long // *Action: additional information indicates in which function this error is // encountered, the length of filename provided, and the limit on // filename 27020, 00000, "named devices not supported" // *Cause: the platform or the specified device type does not support // named devices // *Action: do not specify device name or use a device type that supports // named devices. Use V$BACKUP_DEVICE view to see what device // types and names (if any) are available. 27021, 00000, "sequential file handle must be specified" // *Cause: The filename which will be passed to sbtopen was not specified. // *Action: Specify a filename and continue. If this is a backup set // being created via Recovery Manager, use the 'format' option to // specify the backup piece handle name. 27022, 00000, "skgfqsbi: could not allocate memory for media manager" // *Cause: Oracle could not allocate memory required by the media management // software which is linked with Oracle to provide backup/restore // services. // *Action: Increase the amount of memory available to the Oracle process and // retry the backup/restore. 27023, 00000, "skgfqsbi: media manager protocol error" // *Cause: The media management software which is linked with Oracle to // provide backup/restore services did not provide its function // pointer structure to Oracle. // *Action: This is an internal error in the media management // product. Contact the media management vendor. 27024, 00000, "skgfqsbi: sbtinit2 returned error" // *Cause: sbtinit2 returned an error. This happens during a backup or // restore operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27025, 00000, "skgfqsbi: invalid media manager context area size" // *Cause: The media management software requested a context area size // which is greater than the maximum allowable size. // *Action: This is an internal error in the media management // product. Contact the media management vendor. 27026, 00000, "skgfrls: sbtend returned error" // *Cause: sbtend returned an error. This happens during a backup or // restore operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27027, 00000, "sbtremove2 returned error" // *Cause: sbtremove2 returned an error. This happens when deleting a backup // file. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27028, 00000, "skgfqcre: sbtbackup returned error" // *Cause: sbtbackup returned an error. This happens when creating a backup // file during a backup operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27029, 00000, "skgfrtrv: sbtrestore returned error" // *Cause: sbtrestore returned an error. This happens when retrieving a // backup file during a restore operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27030, 00000, "skgfwrt: sbtwrite2 returned error" // *Cause: sbtwrite2 returned an error. This happens while writing a backup // file during a backup operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. / / / 27031 - 27099 keep for SKGFR (if more needed, allocate another range later) / 27031, 00000, "mirror resilvering functions not supported" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27032, 00000, "skgfrpini: failed to obtain file size limit" // *Cause: getrlimit system call returned an error // *Action: check errno 27033, 00000, "skgfrpini: failed to obtain file size limit" // *Cause: ulimit system call returned an error // *Action: check errno 27034, 00000, "skgfrcre: maximum length of ORACLE_SID exceeded" // *Cause: too many characters in the ORACLE_SID string // *Action: rename the ORACLE_SID to a string of up to the maximum number of // characters specified for your system 27035, 00000, "logical block size is invalid" // *Cause: logical block size for oracle files must be a multiple of the // physical block size, and less than the maximum // *Action: block size specified is returned as additional information, // check init.ora parameters, additional information also indicates // which function encountered the error 27036, 00000, "translation error, unable to expand file name" // *Cause: additional information indicates sltln/slnrm error, and also // indicates which function encountered the error // *Action: check additional information 27037, 00000, "unable to obtain file status" // *Cause: stat system call returned an error, additional information // indicates which function encountered the error // *Action: check errno 27038, 00000, "skgfrcre: file exists" // *Cause: trying to create a database file, but file by that name already // exists // *Action: verify that name is correct, specify reuse if necessary 27039, 00000, "create file failed, file size limit reached" // *Cause: an attempt was made to create a file that exceeds the process's // file size limit, additional information indicates which function // encountered the error // *Action: raise the file size limit 27040, 00000, "skgfrcre: create error, unable to create file" // *Cause: create system call returned an error, unable to create file // *Action: verify filename, and permissions 27041, 00000, "unable to open file" // *Cause: open system call returned an error, additional information // indicates which function encountered the error // *Action: check errno 27042, 00000, "not enough space on raw partition to fullfill request" // *Cause: internal error, file too large for raw partition, additional // information indicates which function encountered the error // *Action: check for trace file and contact Oracle Support 27043, 00000, "unable to seek to beginning of file" // *Cause: seek system call failed, additional information indicates which // function encountered the error // *Action: check errno 27044, 00000, "unable to write the header block of file" // *Cause: write system call failed, additional information indicates which // function encountered the error // *Action: check errno 27045, 00000, "unable to close the file" // *Cause: close system call failed, additional information indicates which // function encountered the error // *Action: check errno 27046, 00000, "file size is not a multiple of logical block size" // *Cause: file size as indicated by stat is not correct, additional // information indicates which function encountered the error // *Action: verify that the file has not been overwritten or truncated 27047, 00000, "unable to read the header block of file" // *Cause: read system call failed, additional information indicates which // function encountered the error // *Action: check errno 27048, 00000, "skgfifi: file header information is invalid" // *Cause: possibly trying to use a non-database file as a database file // *Action: verify that file is a database file 27049, 00000, "unable to seek to and read the last block" // *Cause: an attempt was made to seek to and read the last block in file, // additional information indicates which function encountered error // *Action: check errno 27050, 00000, "function called with invalid FIB/IOV structure" // *Cause: internal error, aditional information indicates which // function encountered error // *Action: check for trace file and contact Oracle Support 27051, 00000, "I/O error (simulated, not real)" // *Document: NO // *Cause: this is just a simulated error (not a real one), additional // information indicates which function encountered the error // *Action: none 27052, 00000, "unable to flush file data" // *Cause: fsync system call returned error, additional information // indicates which function encountered the error // *Action: check errno 27053, 00000, "skgfifi: blocksize in file header not a multiple of logical block size" // *Cause: the logical block size is invalid, additional information indicates // the logical block size and the blocksize in the file header // *Action: use a different logical block size, or do not reuse file /27054 /27055 27056, 00000, "skgfrdel: could not delete file" // *Cause: unlink system call returned error // *Action: check errno 27057, 00000, "skgfask: cannot perform async I/O to file" // *Cause: internal error, query is being asked about async vector I/O // when the file does not support async I/O // *Action: check for trace file and contact Oracle Support 27058, 00000, "skgfask: question parameter is invalid" // *Cause: internal error, invalid query is being asked // *Action: check for trace file and contact Oracle Support 27059, 00000, "skgfrsz: could not reduce file size" // *Cause: ftruncate system call returned error // *Action: check errno 27060, 00000, "skgfofi: could not set close-on-exec bit on file" // *Cause: fcntl system call returned error // *Action: check errno 27061, 00000, "skgfospo: waiting for async I/Os failed" // *Cause: aiowait function returned error // *Action: check errno 27062, 00000, "skgfospo: could not find pending async I/Os" // *Cause: There should have been some async I/Os in the system // but a blocking aiowait indicates that there are // no more I/Os. It could be either because of an Oracle // bug or the vendor OS bug or due to a NFS server not // responding // *Action: check Oracle trace file, OS message files and // contact Oracle Support 27063, 00000, "skgfospo: number of bytes read/written is incorrect" // *Cause: the number of bytes read/written as returned by aiowait // does not match the original number, additional information // indicates both these numbers // *Action: check errno 27064, 00000, "skgfdisp: cannot perform async I/O to file" // *Cause: internal error, asked to perform async I/O when IOV // indicates that it cannot be performed on the file // *Action: check for trace file and contact Oracle Support 27065, 00000, "skgfdisp: cannot perform async vector I/O to file" // *Cause: internal error, asked to perform async vector I/O when // it cannot be performed on the file // *Action: check for trace file and contact Oracle Support 27066, 00000, "skgfdisp: number of buffers in vector I/O exceeds maximum" // *Cause: internal error, number of buffers in vector I/O exceeds // maximum allowed by the OSD, additional information indicates // both these numbers // *Action: check for trace file and contact Oracle Support 27067, 00000, "skgfdisp: size of buffer is invalid" // *Cause: internal error, buffer size is either 0, or greater than // SSTIOMAX or not a multiple of logical block size, additional // information indicates where in function the error was // encountered and the buffer size // *Action: check for trace file and contact Oracle Support 27068, 00000, "skgfdisp: buffer is not aligned properly" // *Cause: internal error, buffer is not aligned to SSIOALIGN boundary, // additional information indicates where in function the error // was encountered and the buffer pointer // *Action: check for trace file and contact Oracle Support 27069, 00000, "skgfdisp: attempt to do I/O beyond the range of the file" // *Cause: internal error, the range of blocks being read or written is // outside the range of the file, additional information indicates // the starting block number, number of blocks in I/O, and the // last valid block in the file // *Action: check for trace file and contact Oracle Support 27070, 00000, "skgfdisp: async read/write failed" // *Cause: aioread/aiowrite system call returned error, additional // information indicates starting block number of I/O // *Action: check errno 27071, 00000, "skgfdisp: unable to seek to desired position in file" // *Cause: lseek system call returned error, additional information // indicates block number in file to which seek was attempted // *Action: check errno 27072, 00000, "skgfdisp: I/O error" // *Cause: read/write/readv/writev system call returned error, additional // information indicates starting block number of I/O // *Action: check errno 27073, 00000, "skgfcfi: async I/Os remaining to be dequeued for this file" // *Cause: internal error, the file is being closed but not all async I/Os // to the file have been dequeued, additional information indicates // number of I/Os pending on the file // *Action: check for trace file and contact Oracle Support 27074, 00000, "skgfrofl: unable to determine limit for open files" // *Cause: getrlimit system call returned error // *Action: check errno 27075, 00000, "skgfrofl: SSTMOFRC constant too large" // *Cause: internal error // *Action: check for trace file and contact Oracle Support 27076, 00000, "skgfrofl: unable to set limit for open files" // *Cause: setrlimit system call returned error // *Action: check errno 27077, 00000, "skgfofi: too many files open" // *Cause: internal error, the number of files opened through skgfofi has // reached the limit // *Action: check for trace file and contact Oracle Support 27080, 00000, "skgfrdup: too many files open" // *Cause: the number of files opened has reached system limit. // *Action: check error, and set system configuration values 27084, 00000, "skgfqio: unable to get/set file status flags " // *Cause: system call fcntl with F_GETFL/F_SETFL flag returned error // *Action: check errno. 27086, 00000, "skgfglk: unable to lock file - already in use" // *Cause: the file is locked by another process, indicating that it is // currently in use by a database instance. // *Action: determine which database instance legitimately owns this file. 27087, 00000, "skgfglk: unable to get share lock - file not readable" // *Cause: share lock request was made on a file not open for read access. // *Action: file must be open read-only or read-write to get a share lock. 27088, 00000, "skgfglk: unable to get file status" // *Cause: file not open or file descriptor is invalid. 27089, 00000, "skgfrlk: unable to release advisory lock" // *Cause: release of file lock failed // *Action: see errno 27091, 00000, "skgfqio: unable to queue I/O" // *Cause: read/write/readv/writev system call returned error, additional // information indicates starting block number of I/O // *Action: check errno 27092, 00000, "skgfofi: size of file exceeds file size limit of the process" // *Cause: an attempt was made to open a file that exceeds the process's // file size limit (ulimit), additional information shows the current // limit (logical blocks) and the size of the file (logical blocks) // *Action: increase the processes file size limit (ulimit) and retry / / 27100 - 27139 keep for SKGM / 27100, 00000, "shared memory realm already exists" // *Cause: Tried to start duplicate instances, or tried to restart an // instance that had not been properly shutdown // *Action: Use a different instance name, or cleanup the failed instance's // SGA 27101, 00000, "shared memory realm does not exist" // *Cause: Unable to locate shared memory realm // *Action: Verify that the realm is accessible 27102, 00000, "out of memory" // *Cause: Out of memory // *Action: Consult the trace file for details 27103, 00000, "internal error" // *Cause: internal error // *Action: contact Oracle support 27120, 00000, "unable to removed shared memory segment" // *Cause: shmctl() call failed // *Action: check permissions on segment, contact Oracle support 27121, 00000, "unable to determine size of shared memory segment" // *Cause: shmctl() call failed // *Action: check permissions on segment, contact Oracle support 27122, 00000, "unable to protect memory" // *Cause: mprotect() call failed // *Action: contact Oracle support 27123, 00000, "unable to attach to shared memory segment" // *Cause: shmat() call failed // *Action: check permissions on segment, contact Oracle support 27124, 00000, "unable to detach from shared memory segment" // *Cause: shmdt() call failed // *Action: contact Oracle support 27125, 00000, "unable to create shared memory segment" // *Cause: shmget() call failed // *Action: contact Oracle support 27126, 00000, "unable to lock shared memory segment in core" // *Cause: insufficient privileges to lock shared memory segment in core // *Action: make sure process is running with necessary privileges. 27127, 00000, "unable to unlock shared memory segment" // *Cause: insufficient privileges to unlock shared memory segment // *Action: make sure process is running with necessary privileges. 27128, 00000, "unable to determine pagesize" // *Cause: sysconf() call failed // *Action: contact Oracle support / / 27140-27189 RESERVED FOR SKGP / / 27140 available 27141, 0000, "invalid process ID" // *Cause: process operation attempted using invalid process ID // *Action: contact Oracle Support 27142, 0000, "could not create new process" // *Cause: OS system call // *Action: check errno and if possible increase the number of processes 27143, 0000, "OS system call failure" // *Cause: OS system call failed // *Action: check errno and contact Oracle support 27144, 0000, "attempt to kill process failed" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27145, 0000, "insufficient resources for requested number of processes" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27146, 0000, "post/wait initialization failed" // *Cause: OS system call failed // *Action: check errno and contact Oracle Support 27147, 0000, "post/wait reset failed" // *Cause: OS system call failed // *Action: check errno and contact Oracle Support 27148, 0000, "spawn wait error" // *Cause: OS system call failed // *Action: check errno and contact Oracle Support 27149, 0000, "assignment out of range" // *Cause: internal error, requested conversion too large for type // *Action: contact Oracle Support 27150, 0000, "attempt to notify process of pending oradebug call failed" // *Cause: OS system call // *Action: check errno contact Oracle Support 27151, 0000, "buffer not large enough to hold process ID string" // *Cause: internal error // *Action: contact Oracle Support 27152, 0000, "attempt to post process failed" // *Cause: OS system call failed // *Action: check errno and contact Oracle Support 27153, 0000, "wait operation failed" // *Cause: OS system called failed // *Action: check errno contact Oracle Support 27154, 0000, "post/wait create failed" // *Cause: internal error, multiple post/wait creates attempted simultaneously // *Action: check errno and contact Oracle Support 27155, 0000, "could not execute file" // *Cause: OS system call failed // *Action: check errno and contact Oracle Support 27156, 0000, "request for process information failed" // *Cause: internal error // *Action: contact Oracle Support 27157, 0000, "OS post/wait facility removed" // *Cause: the post/wait facility for which the calling process is awaiting // action is removed from the system // *Action: check errno and contact Oracle Support / / 27190 - 27229 reserved skgfq / 27190, 00000, "skgfrd: sbtread2 returned error" // *Cause: sbtread returned an error. This happens while reading a backup // file during a restore operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27191, 00000, "sbtinfo2 returned error" // *Cause: sbtinfo2 returned an error. This happens while retrieving // backup file information from the media manager's catalog. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27192, 00000, "skgfcls: sbtclose2 returned error - failed to close file" // *Cause: sbtclose2 returned an error. This happens while closing a backup // file during a backup or restore operation. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27193, 00000, "sbtinfo2 did not return volume label" // *Cause: sbtinfo2 did not return the volume label information for the // backup file that was just created. // *Action: This is an internal error in the media management // product. Contact the media management vendor. 27194, 00000, "skgfdvcmd: sbtcommand returned error" // *Cause: sbtcommand returned an error. This happens when an rman SEND // command is issued. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27195, 00000, "proxy copy not supported" // *Cause: An attempt was made to do a proxy backup or restore, but the // media management software installed with Oracle does not support // proxy copy. // *Action: Re-run the backup in non-proxy mode, or contact the // media management vendor if the software is supposed to support // proxy copy. 27196, 00000, "skgfpbk: sbtpcbackup returned error" // *Cause: sbtpcbackup returned an error. This happens when a proxy backup // is begun. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27197, 00000, "skgfprs: sbtpcrestore returned error" // *Cause: sbtpcrestore returned an error. This happens when a proxy restore // is begun. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27198, 00000, "skgfpvl: sbtpcvalidate returned error" // *Cause: sbtpcvalidate returned an error. This happens during a proxy // backup or restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27199, 00000, "skgfpst: sbtpcstatus returned error" // *Cause: sbtpcstatus returned an error. This happens during a proxy // backup or restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27200, 00000, "skgfpgo: sbtpcstart returned error" // *Cause: sbtpcstart returned an error. This happens during a proxy // backup or restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27201, 00000, "skgfpcm: sbtpccommit returned error" // *Cause: sbtpccommit returned an error. This happens during a proxy // backup or restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27202, 00000, "skgfpen: sbtpcend returned error" // *Cause: sbtpcend returned an error. This happens during a proxy // backup or restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27203, 00000, "skgfpqb: sbtpcquerybackup returned error" // *Cause: sbtpcquerybackup returned an error. This happens during a proxy // backup. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27204, 00000, "skgfpqr: sbtpcqueryrestore returned error" // *Cause: sbtpcqueryrestore returned an error. This happens during a proxy // restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27205, 00000, "skgfpcn: sbtpccancel returned error" // *Cause: sbtpccancel returned an error. This happens during a proxy // restore. // *Action: This error is returned from the media management software which is // linked with Oracle. There should be additional messages which // explain the cause of the error. This error usually requires // contacting the media management vendor. 27206, 00000, "requested file not found in media management catalog" // *Cause: A backup file used in a recovery manager catalog maintenance // command was not found in the media management catalog. // *Action: Retry the command with a different file. 27207, 00000, "syntax error in device PARMS - parentheses mismatch or missing" // *Cause: User-supplied PARMS value has incorrect syntax. // *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn 27208, 00000, "syntax error in device PARMS - environment variable value missing" // *Cause: User-supplied PARMS value has incorrect syntax. // *Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..) 27209, 00000, "syntax error in device PARMS - unknown keyword or missing =" // *Cause: User-supplied PARMS value has incorrect syntax. The server // expected to find ENV or BLKSIZE, but found an unknown keyword. // *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn 27210, 00000, "syntax error in device PARMS" // *Cause: User-supplied PARMS value has incorrect syntax. // *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn / 27211, 00000, "Failed to load Media Management Library" // *Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call // to dlopen for media library returned error. See Additional // information for error code. // *Action: Retry the command with proper media library. Or re-install // Media management module for Oracle. 27212, 00000, "some entrypoints in Media Management Library are missing" // *Cause: media library does not have one of the following entrypoints : // sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit // *Action: Retry the command with proper media library. 27213, 00000, "failed to unload Media Management Library" // *Cause: dlclose for media library returned error. See Additional // Additional information for error code. // *Action: contact Oracle Support. / 27300 - 27350 reserved for slos Error Reporting / 27300, 00000, "OS system dependent operation:%s failed with status: %s" // *Cause: OS system call error // *Action: contact Oracle Support / 27301, 00000, "OS failure message: %s" // *Cause: OS system call error // *Action: contact Oracle Support // 27302, 00000, "failure occurred at: %s" // *Cause: OS system call error // *Action: contact Oracle Support // 27303, 00000, "additional information: %s" // *Cause: OS system call error // *Action: contact Oracle Support / / / 27500-27650 RESERVED FOR IPC ERRORS / 27500, 00000, "inter-instance IPC error" // *Cause: most likely OS system call error // *Action: check extra information and contact Oracle Support 27501, 00000, "IPC error creating a port" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27502, 00000, "IPC error setting up signal handler" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27504, 00000, "IPC error querying network address of a port" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27505, 00000, "IPC error destroying a port" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27506, 00000, "IPC error connecting to a port" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27507, 00000, "IPC error disconnecting from a port" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27508, 00000, "IPC error sending a message" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27509, 00000, "IPC error receiving a message" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27510, 00000, "IPC error waiting for a request to complete" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27512, 00000, "IPC error posting a process" // *Cause: OS system call error // *Action: check errno and contact Oracle Support 27528, 00000, "cannot allocate communication buffers of zero size" // *Cause: Client is trying to allocate a zero length message. // *Action: Refer to kgxp.h for usage of kgxpvalo(). 27529, 00000, "cannot allocate zero sized communication buffers" // *Cause: Client is trying to allocate a zero length message. // *Action: Refer to kgxp.h for usage of kgxpvalo(). 27530, 00000, "cannot deallocate pointer to NULL memory" // *Cause: Client is passing in a NULL pointer for deallocation. // *Action: Refer to kgxp.h for usage of kgxpvfre(). 27531, 00000, "cannot destroy invalid port" // *Cause: The port is invalid. // *Action: Recreate the port. 27532, 00000, "IPC global name service is not supported" // *Cause: The global name service used by KGXP is not supported. // *Action: Either use a different name service, of abort the current // process/thread. 27533, 00000, "trying to destroy invalid connection identifier" // *Cause: The connection identifier passed in is invalid. // *Action: Check the connection identifier, or abort the process/thread. 27534, 00000, "cannot send unaligned message" // *Cause: The message being sent is not aligned on the required // boundaries. // *Action: Use the KGXPALSZ() macro to get the alignment size of messages, // and align all messages on this boundary. 27535, 00000, "exceeded the maximum vectored message size" // *Cause: Trying to send a vectored message that exceeds the maximum // vector size. // *Action: Use a smaller vector size. 27536, 00000, "multicast message is not aligned on the correct boundary" // *Cause: The message to multicast is not aligned on the proper boundary. // *Action: Align the message appropriately. 27537, 00000, "cannot receive messages into unaligned buffers" // *Cause: The message being posted for receive is not aligned on the // required boundary. // *Action: Use the KGXPALSZ() macro to get the alignment size of messages, // and align all messages on this boundary. 27538, 00000, "failed to added accept handle to the free pool" // *Cause: Couldn't add an accept handle to the free pool. // *Action: Exit the process. 27539, 00000, "accept handle free pool is empty. Cannot accept new connections" // *Cause: The free pool of accept handles is empty. // *Action: Add accept handles to the free pool. 27540, 00000, "no more communication channels can be created for process/thread. already at maximum. " // *Cause: The maximum communication channels are already in use for this // process/thread. // *Action: Destroy connections which are not needed. 27541, 00000, "fatal error trying to connect to remote port " // *Cause: Either the remote address is not valid, or the process is // in bad shape. // *Action: Destroy all connections, and try to restablish them. 27542, 00000, "failed trying to queue up accept handles" // *Cause: The OSD wouldn't allow KGXP to queue up the storage necessary // to accept new incoming connections. // *Action: Check parameters, if that's okay, abort the process. 27543, 00000, "cannot cancel an outstanding request" // *Cause: The OSD cannot cancel an outstanding request immediately. // *Action: Shutdown all connections and abort the process. 27544, 00000, "memory mapped communication is not supported" // *Cause: The platform doesn't support memory communication. // *Action: Use the default send/receive. 27545, 00000, "IPC tracing event" // *Cause: N/A. // *Action: Event used for tracing inside the KGXP layer. 27546, 00000, "Oracle compilied against IPC interface version %s.%s found version %s.%s" // *Cause: Misconfiguration or installation error // *Action: Install IPC library for this version of Oracle // 27547, 00000, "Unable to query IPC OSD attribute %s" // *Cause: OS dependent IPC error // *Action: Contact Oracle support 27548, 00000, "Unable to unprepare IPC buffer" // *Cause: OS dependent IPC error // *Action: Contact Oracle support // 27549, 00000, "Update of buffer prepared for remote update failed" // *Cause: OS dependent IPC error // *Action: Contact Oracle support // 27550, 00000, "Incompatible remote IPC implementation detected %s %s %s %s" // *Cause: Misconfiguration or installation error // *Action: Verify that IPC library versions are consistent across all instances // / 28000-28499 RESERVED FOR SECURITY RELATED ERRORS / / 28000, 00000, "the account is locked" // *Cause: The user has entered wrong password consequently for maximum // number of times specified by the user's profile parameter // FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account // *Action: Wait for PASSWORD_LOCK_TIME or contact DBA / 28001, 00000, "the password has expired" // *Cause: The user's account has expired and the password needs to be // changed // *Action: change the password or contact the DBA // 28002, 00000, "the password will expire within %s days" // *Cause: The user's account is about to about to expire and the password // needs to be changed // *Action: change the password or contact the DBA // 28003, 00000, "password verification for the specified password failed" // *Cause: The new password did not meet the necessary complexity // specifications and the password_verify_function failed // *Action: Enter a different password. Contact the DBA to know the rules for // choosing the new password // 28004, 00000, "invalid argument for function specified in PASSWORD_VERIFY_FUNCTION %s" // *Cause: The password verification function does not have the required // number and type of input/output arguments and/or the return // argument // *Action: Check the manual to find out the format of the password // verification function // 28005, 00000, "invalid logon flags" // *Cause: The flags are not properly set or // conflicting flags are set in making calls // *Action: Call the function with appropriate flags set. // 28006, 00000, "conflicting values for parameters %s and %s" // *Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot // both be set. One parameter should be unlimited while other is set // *Action: Set one value to UNLIMITED explicitly // 28007, 00000, "the password cannot be reused" // *Cause: The password cannot be reused for the specified number of // days or for the specified nunmber of password changes // *Action: Try the password that you have not used for the specified // number of days or the specified number of password changes // Refer to the password parameters in the CREATE PROFILE statement // 28008, 0000, "invalid old password" // *Cause: old password supplied is wrong; Hence user cannot be // authenticated using old password // *Action: Supply the correct old password for authentication // 28009, 00000, "connection to sys should be as sysdba or sysoper" // *Cause: connect sys/ is no longer a valid syntax // *Action: Try connect sys/ as sysdba or // connect sys/ as sysoper // 28010, 00000, "cannot expire external or global accounts" // *Cause: If a user account is created as IDENTIFIED EXTERNALLY, // or IDENTIFIED GLOBALLY, this account cannot be expired // *Action Try to expire the password of the user that has database // password 28011, 00000, "the account will expire soon; change your password now" // *Cause: The user's account is marked for expir; the expiry period // is unlimited. // *Action: Change the password or contact the DBA. / 28020, 00000, "IDENTIFIED GLOBALLY already specified" // *Cause: The IDENTIFIED GLOBALLY clause was specified twice. // *Action: Use only one IDENTIFIED GLOBALLY clause. 28021, 00000, "cannot grant global roles" // *Cause: A role granted was IDENTIFIED GLOBALLY. Global roles // can only be granted via a central authority for the domain. // *Action: Use ALTER ROLE to change the type of role (from IDENTIFIED // GLOBALLY to other, such as IDENTIFIED BY password), // or allocate it to a global user via the central authority. 28022, 00000, "cannot grant external roles to global user or role" // *Cause: A role granted was IDENTIFIED EXTERNALLY. External // roles cannot be granted to global users or global roles. // *Action: Use ALTER ROLE to change the type of the role being granted // (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY // password), or use ALTER ROLE or ALTER USER to change the // type of the user or role that is the grantee. 28023, 00000, "must revoke grants of this role to other user(s) first" // *Cause: The role altered to IDENTIFIED GLOBALLY was granted to // one or more other users and/or roles. Global roles cannot // be granted to any user or role. // *Action: Use REVOKE to revoke the role from other users or roles first. 28024, 00000, "must revoke grants of external roles to this role/user" // *Cause: The user or role altered to IDENTIFIED GLOBALLY has // external roles directly granted - these must be revoked, since // external roles cannot be granted to global users or roles. // *Action: Use REVOKE to revoke the external roles from the user or role // to be ALTERed. 28025, 0000, "missing or null external name" // *Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS // clause was specified with a valid external name. // *Action: Provide a valid external name. 28026, 0000, "user with same external name already exists" // *Cause: The external name specified for the user being created or // altered already exists for another user. // *Action: External names must be unique among users. Specify another. 28027, 0000, "privileged database links may be used by global users" // *Cause: Only users IDENTIFIED GLOBALLY may use a privileged database // link. // *Action: Either change the user to a global user or try to use a // different database link. 28028, 0000, "could not authenticate remote server" // *Cause: During the course of opening a privileged database link, // the remote server was not securely identified using the // network security service. Additional errors should follow. // *Action: Consult the network security service documentation on how // to properly configure the remote server. 28029, 0000, "could not authorize remote server for user %s" // *Cause: During the course of opening a privileged database link, // the remote server was found to lack the necessary authorizations // to connect as the current global user. // This may be because the server was not authorized by the network // security service. Or it may be because the local server is // restricting access by the remote server using the // DBMS_SECURITY_DOMAINS_ADMIN package. // *Action: Grant the remote server the proper authorization to connect as // the given global user, and check that the local server is not // restricting access. 28030, 0000, "Server encountered problems accessing LDAP directory service" // *Cause: Unable to access LDAP directory service // *Action: Please contact your system administrator 28035, 0000, "Cannot Get Session Key for Authentication" // *Cause: Client and server cannot negotiate shared secret during logon // *Action: User should not see this error. // Please contact your system administrator 28037, 0000, "Cannot Get Session Key for RACF Authentication" // *Cause: Client and server cannot negotiate shared secret during logon // *Action: User should not see this error. // Please contact your system administrator / / 28100-28149 RESERVED FOR FINE-GRAINED SECURITY / 28100, 00000, "policy function schema %s is invalid" // *Cause: The schema was dropped after the policy associated with the // function had been added to the object. // *Action: Drop the policy and re-create it with a policy function owned by // a valid user. Or re-create the user and the policy function under // the new user. 28101, 00000, "policy already exists" // *Cause: A policy with the same name for the same object already exists. // *Action: Check if the policy has already been added or use a different // policy name. 28102, 00000, "policy does not exist" // *Cause: Try to drop/enable/refresh a non-existent policy. // *Action: Correct the policy name argument. 28103, 00000, "adding a policy to an object owned by SYS is not allowed" // *Cause: Try to add a policy to a table or a view owned by SYS. // *Action: You can not perform this operation. 28104, 00000, "policy function or package is invalid" // *Cause: The function or package implementing a policy does not exist or // was created with errors. // *Action: Correct the function or package. 28106, 00000, "input value for argument #%s is not valid" // *Cause: Input values for the argument is missing or invalid. // *Action: Correct the input values. 28107, 00000, "policy was disabled" // *Cause: Try to flush a disabled policy. // *Action: If the policy is supposed to be enforced, it must be enabled. 28108, 00000, "circular security policies detected" // *Cause: Policies for the same object reference each other. // *Action: Drop the policies 28109, 00000, "the number of related policies has exceeded the limit of 16" // *Cause: Too many policies are involved in the same objects. // *Action: Drop one or more policies. Or combine a few of them into one. 28110, 00000, "policy function or package %s.%s has error" // *Cause: The policy function may have been dropped, or is no longer valid. // *Action: Check the status of the function and correct the problem. // Or re-create the policy with a valid function. 28111, 00000, "insufficient privilege to evaluate policy predicate" // *Cause: Predicate has a subquery which contains objects that the owner of // policy function does not have privilege to access. // *Action: Grant appropriate privileges to the policy function owner. 28112, 00000, "failed to execute policy function" // *Cause: The policy function has one or more error during execution. // *Action: Check the trace file and correct the errors. 28113, 00000, "policy predicate has error" // *Cause: Policy function generates invalid predicate. // *Action: Review the trace file for detailed error information. 28115, 00000, "policy with check option violation" // *Cause: Policy predicate was evaluated to FALSE with the updated values. // *Action: 28116, 00000, "insufficient privileges to do direct path access" // *Cause: Users with insufficient privileges attempting to do direct path // access of tables with fine grain access control policies. // *Action: Ask the database administrator to do the operation. // Note that users can work with security administrator // to temporarily drop/disable the policies at time of export, // import, or load, but this has security implication, and // thus access of the database must be controlled carefully. 28117, 00000, "integrity constraint violated - parent record not found" // *Cause: try to update/insert a child record with new foreign key // values, but the corresponding parent row is not visible // because of fine-grained security in the parent. // *Action: make sure that the updated foreign key values must also visible // in the parent 28118, 00000, "policy group already exists" // *Cause: try to create a policy group that already exists // *Action: 28119, 00000, "policy group does not exist" // *Cause: try to drop a policy group that does not exist // *Action: 28120, 00000, "driving context already exists" // *Cause: try to create a driving context that already exists // *Action: 28121, 00000, "driving context does not exist" // *Cause: try to drop a driving context that does not exist // *Action: 28122, 00000, "can not update SYS_DEFAULT policy group" // *Cause: // *Action: 28123, 00000, "Driving context '%s,%s' contains invalid group '%s'" // *Cause: // *Action: 28130, 00000, "Fine Grained Access Control at table level" // *Cause: // *Action: 28131, 00000, "Fine Grained Access Control enforced" // *Cause: // *Action: 28132, 00000, "Merge into syntax does not support security policies." // *Cause: Merge into syntax currently does not support a security policy // on the destination table. // *Action: use the insert / update DML stmts on the table that has a // security policy defined on it. // 28133, 00000, "full table access is restricted by fine-grained security" // *Cause: The user is not SYS and doesn't have full table access due to VPD // policies. This only happens for internal DML/query under a DDL // *Action: Grant appropriate privilege, or report to Oracle if you feel this // is too restrictive / / 28150-28199 RESERVED FOR N-TIER SECURITY 28150, 0000, "proxy not authorized to connect as client" // *Cause: A proxy user attempted to connect as a client, but the proxy // was not authorized to act on behalf of the client. // *Action: Grant the proxy user permission to perform actions on behalf of the // client by using the ALTER USER ... GRANT CONNECT command. 28151, 0000, "more than one user name specified for command" // *Cause: More than one user name was specified for an ALTER USER command. // *Action: Try the command again with only one user name. / 28152, 0000, "proxy user '%s' may not specify initial role '%s' on behalf of client '%s'" // *Cause: A proxy user attempted to specify an initial role for a client, but // the client does not possess the role. // *Action: Change the proxy user so that it does not specify the role or grant // the role to the client. / 28153, 0000, "Invalid client initial role specified: '%s'" // *Cause: A role specified by a proxy user as an initial role to be // activated upon connecting on behalf of a client is invalid. // *Action: Connect again as the client specifying a valid role. / 28154, 00000, "Proxy user may not act as client '%s'" // *Cause: A proxy user may not assume the identity of a privileged user in // order to limit the privileges that a proxy may possess. // *Action: Execute the statement again specify a client other than a // privileged user. / 28155, 0000, "user '%s' specified as a proxy is actually a role" // *Cause: A user specified in an AUDIT BY ON BEHALF OF // is actually a role. // *Action: Execute the statement again with a valid proxy user. / 28156, 0000, "Proxy user '%s' not authorized to set role '%s' for client '%s'" // *Cause: A proxy user has not been granted the right to use a role on // behalf of a client. // *Action: Execute the command ALTER USER GRANT CONNECT THROUGH // PROXY to grant the needed role. / 28157, 0000, "Proxy user '%s' forbidden to set role '%s' for client '%s'" // *Cause: A proxy user was forbidden to use a role on behalf of a client // through the command ALTER USER GRANT CONNECT THROUGH // WITH ALL ROLES EXCEPT // *Action: Execute the command ALTER USER GRANT CONNECT THROUGH // PROXY to grant the needed role. 28158, 00000, "missing ALL keyword" // *Cause: // *Action: / 28159, 00000, "missing BEHALF keyword" // *Cause: // *Action: / 28160, 00000, "missing EXCEPT keyword" // *Cause: // *Action: / 28161, 00000, "missing ROLES keyword" // *Cause: // *Action: / 28162, 00000, "missing THROUGH keyword" // *Cause: // *Action: / 28163, 00000, "GRANT already specified" // *Cause: The GRANT clause was specified twice. // *Action: Use only one GRANT clause. / 28164, 00000, "REVOKE already specified" // *Cause: The REVOKE clause was specified twice. // *Action: Use only one REVOKE clause. / 28165, 0000, "proxy '%s' may not specify password-protected role '%s' for client '%s'" // *Cause: A proxy user attempted to activate a role on behalf of a client // which has a password associated with it. Since the proxy does not // have a password, this activation cannot be allowed. // *Action: Attempt to activate a different role or change the role // administratively so that there is no password. / 28166, 00000, "duplicate rolename in list" // *Cause: The name of a role was specified more than once in a list. // *Action: Repeat the command specifying the role once. 28168, 0000, "attempted to grant password-protected role" // *Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a // role that is protected by a password as a role which the proxy may // execute on behalf of a client. // *Action: Either specify a role that does not have a password or alter the // role so that a password is not required. / 28169, 0000, "unsupported certificate type" // *Cause: The type of certificate from which the server is to extract the // credentials of the client is not supported. // *Action: Specify a supported type. / 28170, 0000, "unsupported certificate version" // *Cause: The version of the certificate from which the server is to extract // the credentials of the client is not supported. // *Action: Specify a supported version. / 28171, 0000, "unsupported Kerberos version" // *Cause: the version the Kerberos ticket which the server is to use to // validate the identity of the client is not supported. // *Action: Specify a supported version. / 28172, 00000, "distinguished name not provided by proxy" // *Cause: A client user is to be identified using a distinguished // name, but none was provided by the proxy user. // *Action: Provide a distinguished name. / 28173, 00000, "certificate not provided by proxy" // *Cause: A client user is to be identified using a certificate but none // was provided by the proxy user. // *Action: Provide a certificate. / 28174, 00000, "Kerberos ticket not provided by proxy" // *Cause: A client user is to be authenticated using a Kerberos ticket but // none was provided by the proxy user. // *Action: Provide a Kerberos ticket. / 28175, 00000, "incorrect certificate type" // *Cause: the type of certificate provided by the proxy user to identify // a client user does not match the type that is required. // *Action: Provide a certificate of the correct type. / 28176, 00000, "incorrect certificate version" // *Cause: the version of certificate provided by the proxy user to // identify a client user does not match the version that is // required. // *Action: Provide a certificate of the correct version. / 28177, 00000, "incorrect Kerberos ticket version" // *Cause: the version of Kerberos ticket provided by the proxy user to // authenticate a client user does not match the version that is // required. // *Action: Provide a Kerberos ticket of the correct version. / 28178, 00000, "password not provided by proxy" // *Cause: A client user is to be authenticated using a database password but // none was provided by the proxy user. // *Action: Provide a password. / 28179, 00000, "client user name not provided by proxy" // *Cause: No user name was provided by the proxy user for the client user. // *Action: Either specify a client database user name, a distinguished name or // an X.509 certificate. / 28180, 00000, "multiple authentication methods provided by proxy" // *Cause: More than one authentication method was specified by the proxy // user for the client user. // *Action: Specify only one of the following: a client database user name, // a distinguished name or an X.509 certificate. / / 28200-28230 RESERVED FOR THE APPLICATION ROLE / // 28200, 00000, "IDENTIFIED USING already specified" // *Cause: The IDENTIFIED USING clause was specified twice. // *Action: Use only one IDENTIFIED USING clause. / 28201, 00000, "Not enough privileges to enable application role \'%s\'" // *Cause: An attempt to enable application role outside the scope of // the designated package // *Action: Enable the role directly or indirectly using the designated package // // / // // / / 28230-28260 RESERVED FOR THE OBFUSCATION TOOLKIT / 28231, 0000, "no data passed to obfuscation toolkit" // *Cause: A NULL value was passed to a function or procedure. // *Action: Make sure that the data passed is not empty. / 28232, 0000, "invalid input length for obfuscation toolkit" // *Cause: Length of data submitted for encryption or decryption is not a // multiple of 8 bytes. // *Action: Make sure that the length of the data to be encrypted or decrypted // is a multiple of 8 bytes. / 28233, 0000, "double encryption not supported" // *Cause: The obfuscation toolkit does not support the encryption of // already-encrypted data. // *Action: Do not attempt to encrypt already-encrypted data. / 28234, 00000, "key length too short" // *Cause: The key specified is too short for the algorithm. DES // requires a key of at least 8 bytes. Triple DES requires a // key of least 16 bytes in two-key mode and 24 bytes in three-key // mode. // *Action: Specify a longer key. / 28235, 00000, "algorithm not available" // *Cause: The encryption algorithm desired is not available. // *Action: Run the installer to install the needed algorithm in // Oracle Advanced Security. / 28236, 00000, "invalid Triple DES mode" // *Cause: An unknown value was specified for the mode in which triple // DES encryption is to run. // *Action: Specify a valid value. See the package declaration for a // list of valid values. / 28237, 00000, "seed length too short" // *Cause: The seed specified for the key generation routine must be at least // 80 characters. // *Action: Specify a longer seed. / 28238, 00000, "no seed provided" // *Cause: A NULL value was passed in as the seed to be used in generating // a key. // *Action: Provide a non-NULL value for the seed. / 28239, 00000, "no key provided" // *Cause: A NULL value was passed in as a encryption or decryption key. // *Action: Provide a non-NULL value for the key. / / 28261-28270 RESERVED FOR APPLICATION CONTEXT / 28261, 0000, "CURRENT_USER can not be used in PLSQL Definer's Right procedure." // *Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL // interface. // *Action: Use a SQL statement to query CURRENT_USER inside a DR procedure. / 28262, 0000, "global_context_pool_size has invalid value." // *Cause: Parameter global_context_pool_size // has a value less than the minimum required value (10K). // *Action: Please specify a value for the init.ora parameter // global_context_pool_size which is atleast 10k. / 28263, 0000, "Insufficient memory in global context pool" // *Cause: Allocations for the global context heap // exceeded the value set in init.ora. // *Action: Increase the value of global_context_pool_size // parameter in init.ora or clear usused global context. // / 28264, 0000, "Client identifier is too long" // *Cause: The length of the client identifier is longer than 64 // *Action: Set a client identifier whose length is less than 64. // / / 28265, 0000, "NameSpace beginning with 'sys_' is not allowed" // *Cause: Namespace beginning with 'sys_' is not allowed. // *Action: Use a namespace that does not begin with 'sys_'. // / 28266, 0000, "Application Context tracing event" // *Cause: N/A // *Action: Debugging event for KZCTX layer. / / 28270-28290 RESERVED FOR PASSWORD AUTHENTICATED GLOBAL USER(KZAL) / 28270, 0000, "Malformed user nickname for password authenticated global user." // *Cause: An attempt to login as password-auuthenticated global user with // a malformed user nickname. // *Action: Make sure the nickname is valid and re-login. / 28271, 0000, "No permission to read user entry in LDAP directory service." // *Cause: ORACLE server does not have read permission on user nickname's // X.500 user entry. // *Action: Make sure ORACLE server is using right SSL credentials to connect // to LDAP directory services. // Make sure permissions for LDAP user entries are right. / 28272, 0000, "Domain policy restricts password based GLOBAL user authentication." // *Cause: Domain policy does not allow password-authenticated GLOBAL users. // *Action: Make sure ORACLE server is using right SSL credentials to connect // to LDAP directory services. // Make sure orclDBAuthTypes attributes within Oracle enterprise // domain object is either set to PWD or ALL. / 28273, 0000, "No mapping for user nickname to LDAP distinguished name exists." // *Cause: ORACLE server cannot map the given user nickname to LDAP // distinguished name. // *Action: Make sure user entries in LDAP are correctly provisioned with // correct user nickname attribute values. / 28274, 0000, "No ORACLE password attribute corresponding to user nickname exists." // *Cause: LDAP user entry corresponding to user nickname does not have a // ORACLE password attribute or the attribute is not initialized. // *Action: Make sure user entries in LDAP are correctly provisioned with // correct ORACLE password attribute values. / 28275, 0000, "Multiple mappings for user nickname to LDAP distinguished name exist." // *Cause: The given user nickname maps to more than one LDAP distinguished // name. // *Action: Make sure user nickname is unique within the enterprise. / 28276, 0000, "Invalid ORACLE password attribute." // *Cause: The ORACLE password attribute of a user entry has an invalid // format. // *Action: Make sure ORACLE password attribute value is RFC-2307 compliant. / 28277, 0000, "LDAP search, while authenticating global user with passwords, failed." // *Cause: The LDAP search for finding the appropriate user entry and ORACLE // password failed. // *Action: Make sure LDAP directory service is up and running. / 28278, 0000, "No domain policy registered for password based GLOBAL users." // *Cause: No policy about password authenticated GLOBAL users has been // registered. // *Action: Add attribute orclDBAuthTypes to the database server's Enterprise // domain. / 28279, 0000, "Error reading rdbms_server_dn parameter in INIT.ORA." // *Cause: rdbms_server_dn parameter in INIT.ORA is not specified corrrectly // cannot be normalized.. // *Action: Make sure rdbms_server_dn parameter is set to correct value. / 28280, 0000, "Multiple entries for ORACLE database password exist." // *Cause: The ORACLE password attribute of a user entry has multiple entries // of ORACLE database password. // *Action: Make sure ORACLE password attribute has one entry for ORACLE Database // password. / / 28500-28749 RESERVED FOR THE HETEROGENEOUS SERVICES / 28500, 00000, "connection from ORACLE to a non-Oracle system returned this message:" // *Cause: The cause is explained in the forwarded message. // *Action: See the non-Oracle system's documentation of the forwarded // message. // 28501, 00000, "communication error on heterogeneous database link" // *Cause: An unexpected communication failure occurred // on a heterogeneous database link to a non-Oracle system. // The message above will be followed by a second message generated // by the connected non-Oracle system. // *Action: See the documentation for the non-Oracle system // for an explanation of the second error message. // 28502, 00000, "internal communication error on heterogeneous database link" // *Cause: A communication error internal to ORACLE's heterogeneous // services has occurred. // *Action: Contact Oracle customer support. // 28503, 00000, "bind value cannot be translated into SQL text for non-Oracle system" // *Cause: A SQL statement used bind variables on a Heterogenous Services // database link to a non-Oracle system, but the non-Oracle system // does not support bind variables. // *Action: Change your SQL statement so that it does not use bind variables. // 28504, 00000, "ROWID not found in ROWID cache for heterogeneous database link" // *Cause: The ROWID cache for Heterogeneous Services held no entry that // corresponds to the specified ROWID. The ROWID entry may have been // overwritten in the ROWID cache. // *Action: Enlarge the Heterogeneous Services ROWID cache size by increasing // the value of the initialization parameter ROWID_CACHE_SIZE // in the server data dictionary by using the DBMS_HS PL/SQL package. // 28505, 00000, "cannot get non-Oracle system capabilities from %s" // *Cause: ORACLE was unable to retrieve capability information // for the non-Oracle system connected through a heterogeneous // database link. This capability information should be // stored in data dictionary tables viewable with the // HS_CLASS_CAPS or HS_INST_CAPS data dictionary views. // *Action: Contact the DBA to check the server data dictionary table // named in the error message. If table contents are // incorrect, the DBA should restore all data dictionary content for // this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is // sufficient to delete all current data dictionary content for this // class and/or instance and initiate a new connection // to let the connected agent upload new data dictionary content // to the server. // 28506, 00000, "parse error in data dictionary translation for %s stored in %s" // *Cause: A reference to an ORACLE data dictionary table or view name // on a heterogeneous database link to a non-Oracle system // could not be translated. The ORACLE data dictionary tables // shown with view HS_CLASS_DD contain invalid SQL for the data // dictionary translation. // *Action: Contact customer support of the agent vendor. // 28507, 00000, "error in data dictionary view %s" // *Cause: The initialization parameter table for the Heterogeneous Services // was not available, or its structure (number of columns or // column types) was incorrect. // *Action: Verify correct installation of the following Heterogeneous Services' // initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. // If these views are not available, make sure you ran the // script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory. // 28508, 00000, "invalid value %s for Heterogeneous Services initialization parameter %s" // *Cause: The specified Heterogeneous Services initialization parameter // had an invalid value when attempting to connect to a non-Oracle // system. // *Action: Check the Heterogeneous Services documentation to determine // acceptable values, and update that parameter in HS_INST_INIT // using a PL/SQL procedure in the DBMS_HS package. // 28509, 00000, "unable to establish a connection to non-Oracle system" // *Cause: Initialization of a database link to a non-Oracle system // failed to connect to the Heterogeneous Services agent // process for this non-Oracle system. // *Action: Check the Net8 service name definition in the following // places: // -- the USING clause of the CREATE DATABASE LINK statement // -- the TNSNAMES.ORA file // -- the Oracle Names Server // // The following are possible reasons for name mismatches: // -- The USING clause in the CREATE DATABASE LINK statement has // to match the service name defined in the TNSNAMES.ORA file // or in the Oracle Names Server. // -- The protocol-specific information in the service name // definition must match the protocol-specific definition // of the responding listener. // -- The SID= in the service name definition // (in the TNSNAMES.ORA file or in Oracle Names Server) must // match the value in the LISTENER.ORA file for the responding // listener. // 28510, 00000, "heterogeneous database link initialization failed" // *Cause: Initialization of a heterogeneous database link to a // non-Oracle system failed due to an error identified // by the agent for this non-Oracle system. // *Action: Make sure the non-Oracle system is up and running and that // all of the environment and initialization values for the agent // are set correctly. // 28511, 00000, "lost RPC connection to heterogeneous remote agent using SID=%s" // *Cause: A fatal error occurred in one of the following places: // -- the connection between the ORACLE server and the agent // -- the heterogeneous services remote agent itself // -- the connection to the non-Oracle system // This error occurred after communication had been established // successfully. // *Action: Check for network problems and remote host crashes. The problem is // probably in the agent software. If so, contact a customer support // representative of the agent vendor. // 28512, 00000, "cannot get data dictionary translations from %s" // *Cause: ORACLE was unable to retrieve data dictionary translation // information for the non-Oracle system connected through a // heterogeneous database link. This data dictionary translation // information should be stored in data dictionary tables viewable // with the HS_CLASS_DD or HS_INST_DD data dictionary views. // *Action: Ask your DBA to check the server data dictionary table // named in the error message. If table contents are // incorrect, the DBA should restore all data dictionary content for // this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is // sufficient to delete all current data dictionary content for this // class and/or instance and initiate a new connection // to let the connected agent upload new data dictionary content // to the server. // 28513, 00000, "internal error in heterogeneous remote agent" // *Cause: An internal error has occurred in the Oracle remote agent // supporting a heterogeneous database link. // *Action: Make a note of how the error was produced and contact the // customer support representative of the agent vendor. // 28514, 00000, "heterogeneous database link initialization could not convert system date" // *Cause: The system date was not retrievable. // *Action: Verify that the ORACLE server's host machine and operating system // are operational. This error should not occur unless low level // system functions are failing. // 28515, 00000, "cannot get external object definitions from %s" // *Cause: ORACLE was unable to retrieve definitions of distributed external // procedures or remote libraries registered for the non-Oracle system // instance, probably because the underlying data dictionary table // does not exist or is malformed. // *Action: Verify that the ORACLE server's Heterogeneous Services // data dictionary was installed correctly. If the Heterogeneous // Services data dictionary is not installed, execute the CATHS.SQL // script in the $ORACLE_HOME/rdbms/admin directory. // 28518, 00000, "data dictionary translation has illegal translation type" // *Cause: A data dictionary translation definition, either in the ORACLE // server data dictionary or in data dictionary content uploaded // from a Heterogeneous Services agent, specified an illegal // translation type code. Legal values are 'T' or 't' for // 'translate', 'M' or 'm' for 'mimic'. Information on the exact // data dictionary translation causing the error is written // to a trace (*.TRC) file for the ORACLE instance and to // the ORACLE instance's alert log. This error occurs // when a Heterogeneous Services agent uploads data dictionary // content to an ORACLE server on the first connection from the server // to the agent. // *Action: Contact the customer support of the agent vendor. // 28519, 00000, "no heterogeneous data dictionary translations available" // *Cause: The ORACLE server's data dictionary did not define data dictionary // translations for the connected non-Oracle system, and automatic // self-registration (data dictionary upload) was disabled. // *Action: Ask a DBA to resolve this problem. The easiest solution is // to enable automatic self-registration by setting the ORACLE // server's HS_AUTO_REGISTER initialization parameter to TRUE. // An alternative is to load the Heterogeneous Services // data dictionary with information specific for the non-Oracle // system by executing a SQL script supplied by the agent vendor. // If the script is run and the error persists, contact the // customer support representative of the agent vendor. // 28520, 00000, "error initializing heterogeneous data dictionary translations" // *Cause: ORACLE was unable to retrieve data dictionary translations for // the non-Oracle system instance, probably because the underlying // data dictionary table does not exist or is formed incorrectly. // *Action: Verify that the ORACLE server's Heterogeneous Services // data dictionary was installed correctly. If the Heterogeneous // Services data dictionary is not installed, execute the CATHS.SQL // script in the $ORACLE_HOME/rdbms/admin directory. If the connected // agent, identified by FDS_CLASS_NAME, requires a custom installation // script for the ORACLE server, verify that the script has been run. // If both scripts were executed and the error persists, contact the // customer support representative of the agent vendor. // 28521, 00000, "no heterogeneous capability information available" // *Cause: The ORACLE server's data dictionary did not contain // capability definitions for the connected non-Oracle system, // and automatic self-registration (data dictionary upload) // was disabled. // *Action: Ask a DBA to resolve this problem. The easiest resolution is // to enable automatic self-registration by setting the ORACLE // server's HS_AUTO_REGISTER initialization parameter to TRUE. // An alternative is to load the Heterogeneous Services // data dictionary with information specific for the non-Oracle // system by executing a SQL script supplied by the agent vendor. // If the script is run and the error persists, contact the // customer support representative of the agent vendor. // 28522, 00000, "error initializing heterogeneous capabilities" // *Cause: ORACLE was unable to retrieve capability definitions for // the non-Oracle system instance, probably because the underlying // data dictionary table does not exist or is formed incorrectly. // *Action: Verify that the ORACLE server's Heterogeneous Services // data dictionary was installed correctly. If the Heterogeneous // Services data dictionary is not installed, execute the CATHS.SQL // script in the $ORACLE_HOME/rdbms/admin directory. If the connected // agent, identified by FDS_CLASS_NAME, requires a custom installation // script for the ORACLE server, verify that the script has been run. // If both scripts were executed and the error persists, contact the // customer support representative of the agent vendor. // 28523, 00000, "ORACLE and heterogeneous agent are incompatible versions" // *Cause: An operation on a database link attempted to connect to // a non-Oracle system, but the ORACLE instance and the // agent process for the non-Oracle system are incompatible. // *Action: Ask your DBA to confirm configuration of both the ORACLE // instance and the agent. Additional information on the // version incompatibility is logged in trace (*.TRC) files, // the ORACLE instance and the agent, and in the ORACLE // instance's alert log. Check the documentation for your agent // to find out which releases of the Oracle Server are supported. // 28525, 00000, "unable to create Heterogeneous Services error message text" // *Cause: Incorrect arguments were passed into the error message // creation routine. // *Action: Contact Oracle customer support. // 28526, 00000, "invalid describe information returned to Heterogeneous Services" // *Cause: The Heterogeneous Services received invalid describe // information for a select list, bind list, or stored procedure // from the Heterogeneous Services agent. This indicates a problem // with the Heterogeneous Services' non-Oracle system agent. // *Action: Contact customer support of the agent vendor. // 28527, 00000, "Heterogeneous Services datatype mapping error" // *Cause: Either an Oracle datatype could not be mapped to a non-Oracle // datatype, or a non-Oracle datatype could not be mapped // to an Oracle datatype. These mappings are defined as // capability definitions in the ORACLE server's data dictionary. // *Action: Verify that the ORACLE server's data dictionary has been // initialized with correct capability definitions for the connected // FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, // a DBA should restore all data dictionary content for this // FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient // to delete all current data dictionary content for this class and/or // instance and initiate a new connection to let the connected agent // upload new data dictionary content to the server. If the error // persists contact the customer support representative of the agent // vendor. // 28528, 00000, "Heterogeneous Services datatype conversion error" // *Cause: Either an Oracle datatype could not be converted to a non-Oracle // datatype, or a non-Oracle datatype could not be converted // to an Oracle datatype. The following are possible reasons for // for the conversion failure: // -- overflow problems (in the case of numbers) // -- length limitations (in the case of character strings) // -- invalid values passed into the conversion routines // *Action: Contact customer support of the agent vendor. If the problem is // due to size discrepancies between Oracle and the non-Oracle system, // it may not be possible to convert the value. // 28529, 00000, "invalid or missing parameter in Net8 service name definition" // *Cause: There was an invalid or missing Heterogeneous Services parameter // in the Net8 service name definition stored in either the // TNSNAMES.ORA file or in the Oracle Names Server. // *Action: Ask your DBA to make sure the information in the Net8 service // definition is correct and complete. The correct information that // should be included in the Net8 service definition can be found in // the agent's documentation. // 28530, 00000, "Heterogeneous Services initialization error in NLS language ID" // *Cause: Heterogeneous Services was unable to initialize an NLS language ID. // Both the ORACLE server and the Heterogeneous Services agent for the // connected non-Oracle system must have language IDs. // *Action: Contact Oracle customer support. // 28533, 00000, "Heterogeneous Services coercion handling error" // *Cause: The Heterogeneous Services encountered an error in coercion // handling. The HS can, if the agent vendor so chooses, perform // extra processing on SQL statements that contain implicit // coercions or that contain coercion functions such as TO_CHAR, // TO_NUMBER or TO_DATE. This functionality is controlled by // coercion-related capabilities. HS logic reports this error // when it encounters an error in one of these capability // definitions. // *Action: The capability table settings are controlled by the agent // vendor and can be modified by the DBA. Contact your DBA and // agent vendor and get the correct set of capabilities installed. // 28534, 00000, "Heterogeneous Services preprocessing error" // *Cause: One of the things that the Heterogeneous Services can do is // to preprocess parts of SQL statements that contain implicit // coercions or calls to explicit coercion functions like TO_CHAR // TO_NUMBER or TO_DATE. For example, it could convert a call to // TO_DATE to a bind variable, pre-evaluate the TO_DATE function // call and pass the resulting value to the non-Oracle system as // the bind value. This behavior is controlled by some coercion // related capabilities. If the capabilities are set incorrectly, // the HS could encounter errors when it attempts to do the // preprocessing. If it does then this error will be signaled. // *Action: The capability table settings are controlled by the agent // vendor and can be modified by the DBA. Contact your DBA and // agent vendor and get the correct set of capabilities installed. // 28535, 00000, "invalid Heterogeneous Services context" // *Cause: A Heterogeneous Services agent's driver module called // an HS service routine with an invalid HS context value. // This probably is a logic error in the driver. // *Action: Contact Oracle customer support or your agent vendor. // 28536, 00000, "error in processing Heterogeneous Services initialization parameters" // *Cause: An error described by a subsequent error message // prevented successful processing of Heterogeneous Services // initialization parameters from the ORACLE server data dictionary. // *Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and // HS_ALL_INITS. Look for conditions which could produce // the error identified in the error message immediately // following this one. // 28537, 00000, "no more result sets" // *Cause: This error code is used internally within Oracle Transparent // Gateway and Heterogeneous Services code and should not be // reported to a client program. // *Action: Contact Oracle customer support. // 28538, 00000, "result set not found" // *Cause: The client program tried fetching from a result set that is not // open anymore. Many gateways will, on execution of a stored procedure, // automatically close all result sets that were returned by any // previously executed stored procedure. // *Action: Check the documentation for the gateway that you are using and see // if it will automatically close currently open result sets each time // a stored procedure is executed. Then check if your client program is // doing anything that violates this rule. If it is, fix your program. If // it is not then contact Oracle customer support. // 28539, 00000, "gateway does not support result sets" // *Cause: The client program tried executing a stored procedure that returns // one or more result sets through a gateway that does not have result // set support. // *Action: Check the documentation for the gateway that you are using and see // if it supports result sets returned from stored procedures. If it // does not, then the only way of accessing such stored procedures is // to upgrade to a version of the gateway that does support result // sets (if such a version exists). If the gateway does have result set // support and you are still seeing this error then contact Oracle // customer support. // 28540, 00000, "internal result set error" // *Cause: A protocol error internal to Heterogeneous Services or Transparent // Gateway code has occurred. // *Action: Contact Oracle customer support. // 28541, 00000, "Error in HS init file on line %d.\n" // *Cause: A syntax error occurred in the gateway initialization file. // *Action: Check gateway init file to correct the syntax error. // For further information, check the error message in the gateway // trace file. // 28542, 00000, "Error in reading HS init file \n" // *Cause: Reading the gateway init file generated an error. // *Action: Check the gateway initialization file name to see that the // gateway initialization file acctually exists. // Check the ifile parameter to see that it points to the correct // location. // 28550, 00000, "pass-through SQL: cursor not found" // *Cause: A value passed to a pass-through SQL function or procedure call // as a cursor does not identify a currently open cursor. // *Action: Use a cursor number returned by the pass-through SQL // OPEN_CURSOR call. // 28551, 00000, "pass-through SQL: SQL parse error" // *Cause: A non-Oracle system rejected text supplied as a // pass-through SQL statement. // *Action: Ensure that the SQL supplied to the pass-through SQL // PARSE call is legal for the non-Oracle system. // 28552, 00000, "pass-through SQL: call flow error" // *Cause: A pass-through SQL function was called in an invalid order. // *Action: Correct program flow by changing the order of API calls // to match the flow described in the manual. // 28553, 00000, "pass-through SQL: invalid bind-variable position" // *Cause: A pass-through SQL function referring to the position // of a bind variable in the currently-parsed SQL statement // supplied an invalid bind-variable position. Valid // values are 1 through n, where n is the number of // bind-variable place-holders in the SQL text. // *Action: Verify that the bind-variable position parameter is in // the correct range to represent a place-holder in the // SQL text. Confirm that the SQL text uses the correct // syntax for a bind-variable place-holder, as required // by the non-Oracle system. // 28554, 00000, "pass-through SQL: out of cursors" // *Cause: The maximum number of open cursors has been exceeded. // *Action: Close open cursors by using the pass-through SQL // CLOSE_CURSOR function. // 28555, 00000, "pass-through SQL: required parameter missing or NULL" // *Cause: An attempt was made to pass a NULL value to a non-NULL parameter. // *Action: Use a non-NULL value for the parameter. // 28556, 00000, "authorization insufficient to access table" // *Cause: A query attempted to access a table in the non-Oracle system // that is either privileged or has privileged columns. // *Action: Contact the DBA for the non-Oracle system. The DBA can // grant permission to access the privileged table or columns. // 28557, 00000, "unknown %s for database link to non-Oracle system" // *Cause: When attempting to connect to a non-Oracle system // through a Heterogeneous Services database link, // the agent supporting this non-Oracle system failed to return // FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these // names to configure the heterogeneous database link. // *Action: Contact the DBA to check setup of the connection and // the Heterogeneous Services agent. // 28558, 00000, "HS_FDS_CONNECT_STRING undefined for non-Oracle system" // *Cause: A database link to a non-Oracle system had no // HS_FDS_CONNECT_STRING initialization parameter in the ORACLE // server's data dictionary for Heterogeneous Services. Without // this parameter, the connection could not be completed. // *Action: Contact your DBA to verify correct setup of an // HS_FDS_CONNECT_STRING entry in the ORACLE Heterogeneous Services // data dictionary (see HS_INST_INITS view in the "Oracle8 Reference" // book). It may be necessary to use PL/SQL procedures in the // SYS.DBMS_HS package to create or replace an entry for the // connection's FDS_CLASS_NAME and FDS_INST_NAME. // 28559, 00000, "FDS_CLASS_NAME is %s, FDS_INST_NAME is %s" // *Cause: An associated error was reported in another message, and this // message supplies supplementary information to assist // diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used // to access information in tables and views of the ORACLE data // dictionary that direct operation of Heterogeneous Services on // a database link to a non-Oracle data store. // *Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values // to check ORACLE data dictionary contents when necessary // to diagnose the cause of the associated error. // 28560, 0000, "error in configuration of agent process" // *Cause: An ORACLE server invoked a function not supported // by the connected agent (Heterogeneous Services // or external procedures). The most probable cause is // incorrect Net8 setup, resulting in use of the wrong // agent executable. // *Action: Check Net8 administration in the following ways: // -- When using TNSNAMES.ORA or an Oracle Names server, make sure // that the connection from the ORACLE server uses the correct // SID. // -- Check LISTENER.ORA on the agent's host machine to assure that // this SID refers to the correct agent executable in its // (PROGRAM=...) clause. 28561, 00000, "unable to set date format on non-Oracle system" // *Cause: Initialization of a Heterogeneous Services connection // to set the date format to be used on the connected // non-Oracle system. // *Action: If the Oracle data dictionary supplies a value for // the HS_NLS_DATE_FORMAT parameter, confirm that this value // is formatted correctly by the rules of the non-Oracle system. // Also check for additional information in log and trace // files generated by the Heterogeneous Services agent. / / 28575 - 28600 reserved for untrusted and distributed external procedures / 28575, 00000, "unable to open RPC connection to external procedure agent" // *Cause: Initialization of a network connection to the extproc agent did // not succeed. This problem can be caused by network problems, // incorrect listener configuration, or incorrect transfer code. // *Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or // check Oracle Names Server. // 28576, 00000, "lost RPC connection to external procedure agent" // *Cause: A fatal error occurred in either an RPC network connection, // the extproc agent, or the invoked 3GL after communication had // been established successfully. // *Action: First check the 3GL code you are invoking; the most likely // cause of this error is abnormal termination of the // invoked "C" routine. If this is not the case, check for // network problems. Correct the problem if you find it. If all // components appear to be normal but the problem persists, the // problem could be an internal logic error in the RPC transfer // code. Contact your customer support representative. // 28577, 00000, "argument %s of external procedure %s has unsupported datatype %s" // *Cause: While transferring external procedure arguments to the agent, // an unsupported datatype was detected. // *Action: Check your documentation for the supported datatypes of external // procedure arguments. // 28578, 00000, "protocol error during callback from an external procedure" // *Cause: An internal protocol error occurred while trying to execute a // callback to the Oracle server from the user's 3GL routine. // *Action: Contact Oracle customer support. // 28579, 00000, "network error during callback from external procedure agent" // *Cause: An internal network error occurred while trying to execute a // callback to the Oracle server from the user's 3GL routine. // *Action: Contact Oracle customer support. // 28580, 00000, "recursive external procedures are not supported" // *Cause: A callback from within a user's 3GL routine resulted in the // invocation of another external procedure. // *Action: Make sure that the SQL code executed in a callback does not directly // call another external procedure, or indirectly results in another // external procedure, such as triggers calling external // procedures, PL/SQL procedures calling external procedures, etc. // 28581, 00000, "protocol error while executing recursive external procedure" // *Cause: An internal protocol error occurred while trying to execute an // external procedure resulting from a callback in another external // procedure. // *Action: Contact Oracle customer support. // 28582, 00000, "a direct connection to this agent is not allowed" // *Cause: A user or a tool tried to establish a direct connection to either // an external procedure agent or a Heterogeneous Services agent, // for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type // of connection is not allowed. // *Action: When executing the CONNECT statement, make sure your database link // or network alias is not pointing to a Heterogeneous Option agent or // an external procedure agent. // // errors 28590 - 28599 are reserved for the HS agent control utility // 28590, 00000, "agent control utility: illegal or badly formed command" // *Cause: The user has issued an unrecognized or syntactically incorrect // command. // *Action: Refer to documentation and correct the syntax of the command. // 28591, 00000, "agent control utility: unable to access parameter file" // *Cause: The agent control utility was unable to access its parameter // file. This could be because it could not find its admin // directory or because permissions on directory were not correctly // set. // *Action: The agent control utility puts its parameter file in either // the directory pointed to by the environment variable AGTCTL_ADMIN // or in the directory pointed to by the environment variable // TNS_ADMIN. Make sure that at least one of these environment // variables is set and that it points to a directory that the // agent has access to. // 28592, 00000, "agent control utility: agent SID not set" // *Cause: The agent needs to know the value of the AGENT_SID parameter // before it can process any commands. If it does not have a // value for AGENT_SID then all commands will fail. // *Action: Issue the command SET AGENT_SID and then retry the // command that failed. // 28593, 00000, "agent control utility: command terminated with error" // *Cause: An error occurred during the processing of the command. There // could be several causes. A SET or an UNSET command could have // been issued after the agent was started. This is illegal. The // user may have attempted to start two agents with the same SID // value or the user could have attempted to shutdown an agent // that is no longer running. // *Action: If the user wishes to issue a SET or an UNSET command, he should // make sure the agent is shutdown first by issuing the SHUTDOWN // command. // 28594, 00000, "agent control utility: invalid parameter name" // *Cause: The user tried to set or unset an invalid agent parameter. // *Action: Refer to documentation and correct the parameter name. // // errors 28600 - 28620 are reserved for bitmap indexes // 28601, 00000, "invalid [no]MINIMIZE option" // *Cause: user didn't type this // alter table MINIMIZE RECORDS_PER_BLOCK // or // alter table NOMINIMIZE RECORDS_PER_BLOCK // *Action: reenter correct sql command // 28602, 00000, "statement not permitted on tables containing bitmap indexes" // *Cause: table has bitmap indexes and user is minimizing or // nominimizing records_per_block // *Action: drop all bitmap indexes before changing records_per_block // // 28603, 00000, "statement not permitted on empty tables" // *Cause: table is empty and statement does not work on empty tables // *Action: try statement after loading your data // 28604, 00000, "table too fragmented to build bitmap index (%s,%s,%s)" // *Cause: The table has one or more blocks that exceed the maximum number // of rows expected when creating a bitmap index. This is probably // due to deleted rows. The values in the message are: // (data block address, slot number found, maximum slot allowed) // *Action: Defragment the table or block(s). Use the values in the message // to determine the FIRST block affected. (There may be others). 28605, 00000, "bitmap indexes cannot be reversed" // *Cause: user tried to create reverse bitmap index // *Action: don't do this; it is not supported // 28611, 00000, "bitmap index is corrupted - see trace file for diagnostics" // *Cause: Validate Index detected bitmap corruption in its argument index // *Action: Drop this bitmap index and create a new one. // // / 28650 - 28699 - Reserved for IOTs // 28650, 00000, "Primary index on an IOT cannot be rebuilt" // *Cause: An attempt is made to issue alter index rebuild on IOT-TOP // *Action: Use Alter table MOVE to reorganize the table(IOT) 28651, 00000, "Primary index on IOTs can not be marked unusable" // *Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX // *Action: Remove the option UNUSABLE // 28652, 00000, "overflow segment attributes cannot be specified" // *Cause: During ALTER MOVE ONLINE of a index-organized table, the user // attempted to enter one or more of the following options: // OVERFLOW, PCTTHRESHOLD,INCLUDING. // *Action: Remove the illegal option(s). 28653, 00000, "tables must both be index-organized" // *Cause: Attempt to exchange a non IOT table/partition with a partition/table // respectively // *Action: Ensure that non-partitioned and partitioned tables are both // index-organized. 28654, 00000, "table and partition not overflow compatible" // *Cause: If one of the tables (partitioned/non-partitioned) has overflow // data segment and the other one doesn't. // *Action: Ensure that non-partitioned and partitioned tables both // have overflow data segment or neither one does. 28655, 00000, "Alter table add overflow syntax error" // *Cause: Syntax error // *Action: Check the syntax. 28656, 00000, "incomplete attribute specification" // *Cause: The attribute specification is not done for all partitions" // *Action: Specify the storage attributes either for ALL partitions or NONE 28657, 00000, "Allow IOT w/o overflow though overflow is required" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE. 28658, 00000, "This operation is supported only for Index-Organized tables" // *Cause: Attempt to perform some IOT specific operation on a non-IOT // *Action: don't do this. This is not supported 28659, 00000, "COMPRESS must be specified at object level first" // *Cause: Attempt to specify COMPRESS at partition level // without first specifying at the table level // *Action: Specify COMPRESS at table level. Use ALTER TABLE xxx // MODIFY DEFAULT ATTRIBUTES COMPRESS ... 28660, 00000, "Partitioned Index-Organized table may not be MOVEd as a whole" // *Cause: Attempt to MOVE partitioned IOT as a whole // *Action: don't do this. This is not supported 28661, 00000, "Object already has COMPRESS clause specified" // *Cause: Attempt to specify compress for iot/index which already // has a compression clause. // *Action: This is a 'create time only' attribute 28662, 00000, "IOT index and overflow segments must share the same LOGGING attribute" // *Cause: Attempt to specify LOGGING for one segment and NOLOGGING for the other segment. // *Action: don't do that 28663, 00000, "Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW" // *Cause: Attempt to specify LOGGING for a Alter Table Add Overflow. // *Action: don't do that 28664, 00000, "a partitioned table may not be coalesced as a whole" // *Cause: User attempted to coalesce a partitioned IOT using // ALTER TABLE COALESCE statement, which is illegal // *Action: Coalesce the table a partition at a time (using // ALTER TABLE MODIFY PARTITION COALESCE) 28665, 00000, "table and partition must have same compression attribute" // *Cause: User attempted to EXCHANGE a compression enabled // partition with a compression disabled table or vice versa // OR the # of columns compressed is different for table and partition // *Action: Make sure the compression attributes match // If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS 28666, 00000, "option not allowed for an index on UROWID column(s)" // *Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL // partitioned index on UROWID column(s) // *Action: Build the index without these options 28667, 00000, "USING INDEX option not allowed for the primary key of an IOT" // *Cause: User attempted to define storage attributes for the primary key // index of an Index-Organized table with USING INDEX clause. All // the storage attribute defined for the (IOT)table applies to the // primary key index and a separate USING INDEX clause is not // required. // *Action: Remove the USING INDEX clause and specify all attributes directly // for the table 28668, 00000, "cannot reference mapping table of an index-organized table" // *Cause: An attempt to directly access the mapping table of an // index-organized table // *Action: Issue the statement against the parent index-organized table // containing the specified mapping table. 28669, 00000, "bitmap index can not be created on an IOT with no mapping table" // *Cause: User attempted to create a bitmap index on an index-organized // table without a mapping table. // *Action: Enable bitmap indexes on the Index-organized table by creating a // mapping table using 'ALTER TABLE .. MOVE MAPPING TABLE'. 28670, 00000, "mapping table cannot be dropped due to an existing bitmap index" // *Cause: User attempted to drop the mapping table with NOMAPPING option // when the IOT has one or more bitmap indexed. // *Action: Drop the bitmap index(es) before dropping the mapping table. 28671, 00000, "UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole" // *Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index // using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is // illegal. // *Action: Issue a partition level operation with // ALTER INDEX .. PARTITION .. UPDATE BLOCK REFERENCES 28672, 00000, "UPDATE BLOCK REFERENCES may not be used on a global index" // *Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned // or non-partitioned index. This feature is not supported for // non-partitioned or global partitioned index on a partitioned IOT // and a global partitioned index on a non-partitioned IOT. // *Action: Use online index [partition] rebuild to fix the block references 28673, 00000, "Merge operation not allowed on an index-organized table" // *Cause: User attempted merge operation on an index-organized table. Merge // is not supported on a IOT . // *Action: Use updates and inserts on index-organized table . / / $Header: nze1us.msg 16-feb-01.14:27:03 vle Exp $ / $Header: nze1us.msg 16-feb-01.14:27:03 vle Exp $ / / Copyright (c) 1997, 1999, 2000, 2001 by Oracle Corporation / NAME / nzeus.msg - Network Zecurity Error messages - american (US) language / DESCRIPTION / Contains error messages for the Oracle Security Server / RETURNS / None. / / NOTES / MODIFIED (MM/DD/YY) / vle 02/16/01 - fix err mesg for 29002,3 / vle 02/09/01 - add nz mesg / ppovinec 02/08/01 - Net8 --> Oracle Net rename. / rturlapa 03/29/00 - Added Entrust error message. / rwessman 07/06/99 - Added SSL error messages / sdange 03/13/97 - ERROR NOT USER-VISIBLE / rwessman 03/06/97 - Corrected error numbers. / 28750, 00000, "Unknown error occurred" // *Cause: Some Oracle Security Server error occurred of unspecified type. // *Action: Contact your customer support representative. This error should // not be visible to applications. / 28751, 00000, "Memory allocation failed" // *Cause: The allocation of memory failed due to exhaustion of system // memory. // *Action: Terminate other processes to free up memory or add memory to the // system. / 28752, 00000, "Failed to initialize data source" // *Cause: The initialization of a data source failed. // *Action: Enable Oracle Net tracing to determine the exact cause of // the error. Frequently, this error is caused by the exhaustion of // system resources. / 28753, 00000, "Failed to terminate use of data source" // *Cause: The termination of the use of a data source failed. // *Action: Enabled Oracle Net tracing to determine the exact cause of // the error. The error may be caused by the corruption of memory or // disk, among other things. / 28754, 00000, "Storage of object failed" // *Cause: Error not user-visible. // *Action: / 28755, 00000, "object retrieval failed" // *Cause: Failure to retrieve subject information from a file or // database. // *Action: Check if the data source exists or check for the correct // subject information. / 28756, 00000, "Callback failed to allocate memory" // *Cause: A function supplied by the caller failed to allocate memory. // *Action: This error could be due to system memory exhaustion. / 28757, 00000, "Attempted to allocate 0 bytes of memory" // *Cause: No more memory. // *Action: This error could be due to system memory exhaustion. / 28758, 00000, "Memory release failed" // *Cause: The release of memory fragment failed. This may be caused by // corruption of memory either within the application or the // Oracle Security Server library. // *Action: Enable Oracle Net tracing to determine the reason why the operation // failed. / 28759, 00000, "Failed to open file" // *Cause: The opening of the specified file failed. // *Action: Enable Oracle Net tracing to determine the name of the file that // could not be opened and the reason. / 28760, 00000, "List creation failed" // *Cause: Error not user-visible. // *Action: / 28761, 00000, "Failed to create element" // *Cause: Error not user-visible. // *Action: / 28762, 00000, "Failed to add element" // *Cause: Error not user-visible. // *Action: / 28763, 00000, "Invalid parameter type" // *Cause: Possible error in parameter in sqlnet.ora. // *Action: Check the sqlnet.ora file for this parameter value. / 28764, 00000, "Configuration parameter retrieval failed" // *Cause: The retrieval of a configuration parameter failed. // *Action: Supply the needed configuration parameter. / 28765, 00000, "Data method list does not exist" // *Cause: Error not user-visible. // *Action: / 28766, 00000, "Failed to terminate use of data source" // *Cause: An error occurred when attempting to end use of a data source. // This could be due to a system error. // *Action: Enable tracing to see what the exact error is. / 28767, 00000, "Invalid version number" // *Cause: Version number of the file is incorrect. // *Action: / 28768, 00000, "Bad magic number" // *Cause: An invalid magic number was specified in a data file. // *Action: This could be due to disk corruption or some other process // overwriting the file. Enable tracing to determine what the exact // error is. / 28769, 00000, "Specified method does not exist" // *Cause: The data access method specified in the configuration file is not // supported. // *Action: Specify a supported method. Consult the Oracle Security Server // documentation to determine the supported types. / 28770, 00000, "Data source already initialized" // *Cause: The caller attempted to initialize a data source which was already // initialized. // *Action: This is a programming error. An application should not attempt to // initialize a data source more than once. / 28771, 00000, "Data source not yet initialized" // *Cause: The caller attempted to use a data source which had not been // initialized yet. // *Action: This is a programming error. The application must always initialize // the data source. / 28772, 00000, "Invalid file ID" // *Cause: Error not user-visible. // *Action: / 28773, 00000, "Write of magic and version numbers failed" // *Cause: The write of both the magic and version numbers failed. // *Action: This error usually occurs because disk space has been exhausted. / 28774, 00000, "Write of file to disk failed" // *Cause: The output of a file failed. // *Action: This error usually occurs because disk space has been exhausted. / 28775, 00000, "Close of file failed" // *Cause: The close of a file used by a data access method failed. // *Action: This error usually indicates an error such as memory corruption // or a system error. Enable tracing and examine the trace file to // see what the exact error. / 28776, 00000, "Output buffer supplied is too small" // *Cause: The data to be returned by a function is too large for the // supplied buffer. // *Action: Call the routine again with a larger buffer. / 28777,00000, "Binding creation failed" // *Cause: The creation of a binding for use in the parsing of a parameter // value failed. This error can be caused by the parameter value // being in an incorrect format, e.g. a right parenthesis was not // supplied where expected, or the exhaustion of system memory. // *Action: Make sure that the parameter is specified in the correct format. // If the format is correct, free up system memory by terminating // processes or add more memory. / 28778, 00000, "Parameter not specified in proper format" // *Cause: The configuration parameter was specified in the proper format. // *Action: Consult the Oracle Security Server documentation for a description // of the proper format for this parameter. / 28779, 00000, "No data access method specified in parameter" // *Cause: No method for data access was specified in the parameter value. // *Action: Specify a parameter method. Consult the Oracle Security Server // documentation for the supported data access methods for this data // data type. / 28780, 00000, "Invalid method specified by parameter" // *Cause: The data access method specified by the parameter value is not // supported. // *Action: Specify a data access method. Consult the Oracle Security Server // documentation for the supported data access methods for this data // data type. / 28781, 00000, "no method data specified in parameter" // *Cause: No data was specified in the parameter for use with the specified // access method. // *Action: Consult the Oracle Security Server documentation for the data // that must be specified for the access method. / 28782, 00000, "Data source not allocated" // *Cause: No memory was allocated for a data source. // *Action: The application should call in the data source initialization // function. / 28783, 00000, "Invalid parameter" // *Cause: No match for parameter name in the configuration file. // *Action: Check your sqlnet.ora file for the parameter. / 28784, 00000, "File name translation failed" // *Cause: The translation of a file name from Oracle format to native format // failed. // *Action: Specify a correct name. Consult your ORACLE documentation for the // correct file name format. / 28785, 00000, "Parameter does not exist" // *Cause: A configuration parameter does not exist in a parameter file. // *Action: Supply the required parameter. / 28786, 00000, "Decryption of encrypted private key failed" // *Cause: Use of incorrect password for decryption. // *Action: Type in the correct password. / 28787, 00000, "Encryption of private key failed" // *Cause: Possible error in parameter for mkwallet in sqlnet.ora. // *Action: Check your sqlnet.ora file. Also turn on tracing and // check the mktoken.trc file for other errors. / 28788, 00000, "Invalid information provided by the user or unknown error" // *Cause: Incorrect input by the user in response to a prompt or an // unknown error. // *Action: Provide the correct input or enable tracing and check the // trace file for errors. / 28789, 00000, "Name type not found" // *Cause: Error not user-visible. // *Action: / 28790, 00000, "NLS string open failed" // *Cause: The opening of a string for use by the NLS subsystem failed. // *Action: Enable Oracle Net tracing to determine the exact error. / 28791, 00000, "Certificate verification failed" // *Cause: Verification of the certificate supplied by the user failed. // *Action: Enable Oracle Net tracing to determine the exact error. / 28792, 00000, "PL/SQL operation failed" // *Cause: A PL/SQL operation attempted by the Oracle Security Server failed. // *Action: This is an internal error. Enable Oracle Net and try the operation // again. Contact Oracle customer support for assistance. / 28793, 00000, "Variable bind failed" // *Cause: Error not user-visible. // *Action: / 28794, 00000, "Attribute initialization data type failed" // *Cause: The initialization of the attribute data type failed. // *Action: Enable tracing to determine the exact error. This error may be // caused by the exhaustion of system resources. / 28795, 00000, "Attribute data type termination failed" // *Cause: The termination of the use of the attribute data type subsystem // failed. // *Action: Enable Oracle Net tracing to determine the exact error. / 28796, 00000, "Unsupported access method" // *Cause: The method specified to access data is not supported. // *Action: Use a supported access method. / 28797, 00000, "Invalid data type" // *Cause: The type specified for a key is not supported. // *Action: Correct the key type. / 28798, 00000, "Number of sub-keys to bind does not match that in key" // *Cause: The number of keys passed by the application to bind does not match // the number used to create the key. // *Action: This is an internal programming exception. Contact your customer // support representative. / 28799, 00000, "Failed to allocate shared memory" // *Cause: The allocation of shared memory for use in operations involving // the shared server failed. // *Action: Enable Oracle Net tracing to determine the exact error. This error // is probably caused by the exhaustion of the memory heap supplied // by the Oracle server. / 28800, 00000, "Open failed" // *Cause: Failed to open the data source (file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28801, 00000, "Invalid object type" // *Cause: Error not user-visible. // *Action: / 28802, 00000, "Invalid mode specified" // *Cause: Mode or data source specified in configuration file is incorrect. // *Action: Check the sqlnet.ora file for method parameter. // Else enable Oracle Net tracing to determine the exact error. / 28803, 00000, "Input/output operation failed" // *Cause: Failed to access a data source(file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28804, 00000, "Close failed" // *Cause: Failed to close the data source(file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28805, 00000, "Retrieve failed" // *Cause: Failed to retrieve information from the data source // (file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28806, 00000, "Store failed" // *Cause: Failed to write to the data source(file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28807, 00000, "Update failed" // *Cause: Failed to update a data source(file or database). // *Action: Enable Oracle Net tracing to determine the exact error. / 28808, 00000, "Retrieval of method information failed" // *Cause: Failed to retrieve method (file/database) // information. // *Action: Check the sqlnet.ora file for method configuration // parameters.Else enable Oracle Net tracing to determine // the exact error. / 28809, 00000, "Deletion failed" // *Cause: Failed to delete information from data source. // *Action: Enable Oracle Net tracing to determine the exact error. / 28810, 00000, "Creation failed" // *Cause: Failed to create a key descripter. // *Action: Enable Oracle Net tracing to determine the exact error. / 28811, 00000, "Invalid access descriptor" // *Cause: Error not user-visible. // *Action: / 28812, 00000, "Record operation failed" // *Cause: Error not user-visible. // *Action: / 28813, 00000, "Invalid record type" // *Cause: Error not user-visible. // *Action: / 28814, 00000, "Conversion of number in Oracle format to native failed" // *Cause: The conversion of a number which was specified in Oracle format // to native format failed. // *Action: This is an internal programming exception. Enable // Oracle Net tracing and attempt to reproduce the problem. Contact // your customer support representative and supply the trace file. / 28815, 00000, "Conversion of native number to Oracle format failed" // *Cause: The conversion of a number which was specified in native format // to Oracle portable format failed. // *Action: This is an internal programming exception. Enable // Oracle Net tracing and attempt to reproduce the problem. Contact // your customer support representative and supply the trace file. / 28816, 00000, "No password provided" // *Cause: A required password was not passed to a PL/SQL function. // *Action: This is an internal error. Contact Oracle customer support. / 28817, 00000, "PL/SQL function returned an error" // *Cause: A PL/SQL function returned an error unexpectedly. // *Action: This is an internal error. Contact Oracle customer support. / 28818, 00000, "no package context provided" // *Cause: The context that holds the state of the security package was not // passed to a function or procedure that was expecting it. // *Action: This is an internal error. Contact Oracle customer support. / 28819, 00000, "no distinguished name provided" // *Cause: The user's distinguished name was not provided to a PL/SQL // function or procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28820, 00000, "state not provided" // *Cause: The state of either a signature or decryption/encryption was not // passed to a PL/SQL function or procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28821, 00000, "no input buffer provided" // *Cause: A PL/SQL function or procedure was not passed an expected buffer. // *Action: This is an internal error. Contact Oracle customer support. / 28822, 00000, "no seed" // *Cause: No seed was specified to the PL/SQL seed initialization function // *Action: This is an internal error. Contact Oracle customer support. / 28823, 00000, "number of bytes not specified" // *Cause: The number of random bytes to generate was not specified to the // PL/SQL random number generator. // *Action: This is an internal error. Contact Oracle customer support. / 28824, 00000, "invalid encryption/decryption/signature state" // *Cause: An invalid state was passed to a PL/SQL encryption, decryption or // signature procedure or function. // *Action: Specify a correct state value. / 28825, 00000, "no cryptographic engine function" // *Cause: No function was specified for the cryptographic engine. // *Action: This is an internal error. Contact Oracle customer support. / 28826, 00000, "invalid cryptographic engine function" // *Cause: An incorrect cryptographic engine function was passed to a PL/SQL // function or procedure. // *Action: Specify a correct engine function. / 28827, 00000, "invalid cipher type" // *Cause: An incorrect cipher type was passed to a PL/SQL function or // procedure. // *Action: Specify a correct cipher type. / 28828, 00000, "invalid identity type" // *Cause: An incorrect identity type was passed to a PL/SQL function or // procedure. // *Action: Specify a correct identity type. / 28829, 00000, "no cipher type specified" // *Cause: No cipher type was passed to a PL/SQL function or procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28830, 00000, "no identity type specified" // *Cause: No identity type was passed to a PL/SQL function or procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28831, 00000, "no data unit format" // *Cause: No data unit format was passed to a PL/SQL function or procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28832, 00000, "invalid data unit format" // *Cause: An incorrect data unit format was passed to a PL/SQL function or // procedure. // *Action: Specify a data unit format. / 28833, 00000, "not enough info provided" // *Cause: Not enough info (usually parameters) provided to a PL/SQL function // *Action: This is an internal error. Contact Oracle customer support. / 28834, 00000, "buffer too small" // *Cause: Buffer provided by PL/SQL to a Oracle Security Server toolkit // function is too small for the data to be returned // *Action: This is an internal error. Contact Oracle customer support. / 28835, 00000, "identity descriptor not present or too small" // *Cause: An identity descriptor passed to a PL/SQL function or descriptor // was not provided or does not have the correct size. // *Action: This is an internal error. Contact Oracle customer support. / 28836, 00000, "wallet not open" // *Cause: The wallet to be used has not been opened yet. // *Action: Call the function that opens the wallet. / 28837, 00000, "no wallet descriptor" // *Cause: No wallet descriptor was specified to a PL/SQL function or // procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28838, 00000, "no identity descriptor" // *Cause: No identity descriptor was specified to a PL/SQL function or // procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28839, 00000, "no persona descriptor" // *Cause: No persona descriptor was specified to a PL/SQL function or // procedure. // *Action: This is an internal error. Contact Oracle customer support. / 28840, 00000, "wallet already open" // *Cause: An attempt was made to open a wallet that had already been opened. // *Action: This is a programming error. A wallet should only be opened once. / 28841, 00000, "operation not supported" // *Cause: An attempt was made to perform an operation that is not supported. // *Action: This is a programming error. / 28854, 00000, "memory allocation failure" // *Cause: The allocation of memory failed due to exhaustion of system // memory. // *Action: Terminate other processes to free up memory or add memory to the // system. / 28855, 00000, "unsupported SSL operation" // *Cause: An unsupported operation was attempted, for example, an unknown // cipher specification or an incorrect version. // *Action: Specify a correct value. // / 28856, 00000, "overflow error" // *Cause: a buffer overflowed during the SSL handshake. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28857, 00000, "unknown SSL error" // *Cause: an unknown SSL error occurred. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28858, 00000, "SSL protocol error" // *Cause: an error occurred during the SSL handshake between two processes. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28859, 00000, "SSL negotiation failure" // *Cause: an error occurred during the negotiation done between two processes // as part of the SSL protocol. // This error will occur if the two sides to the connection do not // support a common cipher suite or if the SSL versions on both sides // are incompatible. // *Action: Configure each process so they support a common cipher suite and // compatible versions and then attempt the connection again. / 28860, 00000, "fatal SSL error" // *Cause: An error occurred during the SSL connection. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error the persists, contact // Oracle Customer Support. / 28861, 00000, "SSL connection would block" // *Cause: This error is informational only. It should never be communicated // to the user. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error the persists, contact // Oracle Customer Support. / 28862, 00000, "SSL connection failed" // *Cause: This error can occur when one side of the connection fails for // one reason or another. For example, the process might have been // terminated. // *Action: Attempt the connection again. / 28863, 00000, "SSL session not found" // *Cause: This error is informational only. It indicates that a specified // session does not exist. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If the error persists, contact // Oracle Customer Support. / 28864, 00000, "SSL connection closed gracefully" // *Cause: This error is informational only. It indicates that the connection // closed without error. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If the error persists, contact // Oracle Customer Support. / 28865, 00000, "SSL connection closed" // *Cause: The SSL connection closed because of an error in the underlying // transport or because the destination process quit unexpectedly. // *Action: Enable tracing and attempt the connection again. The trace output // should indicate how the failure occurred. / 28866, 00000, "invalid certificate encoding" // *Cause: The certificate presented had a field that could not be // recognized. // *Action: Verify that the certificate is correct. If it is, enable tracing // and attempt the connection again. If the error persists, contact // Oracle Customer support. / 28867, 00000, "integer value is too big" // *Cause: The certificate presented had an integer field whose value was // too large. // *Action: Verify that the certificate is correct. If it is, enable tracing // and attempt the connection again. If the error persists, contact // Oracle Customer support. / 28868, 00000, "certificate chain check failed" // *Cause: The check of the certificate list presented by the remote process // failed. This could be caused by a number of problems including: // 1. the expiration of one of the certificates; // 2. a certificate authority in a certificate was not recognized as // a trust point; // 3. the signature in a certificate could not be verified. // *Action: Make sure that: // 1. all of the certificates installed in your wallet are current; // 2. all of the necessary certificates are loaded into your // wallet; // 3. all of the certificates have valid signatures. / 28869, 00000, "certificate expired" // *Cause: The certificate being used to authenticate a client or server // has expired. // *Action: Obtain a certificate which has not expired and attempt the // connection again. / 28870, 00000, "name comparison failed" // *Cause: A comparison between the names contained within two certificates // failed. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If the error persists, contact // Oracle Customer Support. / 28871, 00000, "certificate chain is incomplete" // *Cause: The certificate chain presented was not incomplete. In other words, // the chain did not end with a self-signed root certificate. // *Action: Make sure that the certificate specified as the root is // self-signed. / 28872, 00000, "invalid certificate format" // *Cause: The certficate presented by the other process does not conform // to the X.509v3 standard. // *Action: Obtain a certificate that conforms to the standard and attempt the // connection again. / 28873, 00000, "invalid parameter" // *Cause: A function was presented with a null parameter. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28874, 00000, "SSL: I/O closed - override goodbye kiss" // *Cause: This error is informational only. It indicates that a specified // session does not exist. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28875, 00000, "SSL: use server-gated crypto suites" // *Cause: This error is used as a internal status indicator and not really // an error. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / 28876, 00000, "Internet Explorer SGC Error" // *Cause: An error occurred when processing a certificate sent from // Microsoft Internet Explorer. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / // 28877, 00000, "UNUSED" // *Cause: // // *Action: // / // 28878, 00000, "UNUSED" // *Cause: // // *Action: // / 28879, 00000, "no protocol side set" // *Cause: An application attempted to provide credentials to an SSL // connection but had not previously stated whether that the process // was a client or server. // *Action: This error is not normally visible to the user. Enable tracing and // attempt the connection again. If error persists, contact // Oracle Customer Support. / // 28880, 00000, "UNUSED" // *Cause: // // *Action: // / // 28881, 00000, "UNUSED" // *Cause: // // *Action: // / 28882, 00000, "UNUSED" // *Cause: // // *Action: // / 28883, 00000, "UNUSED" // *Cause: // // *Action: // / 28884, 00000, "invalid cipher suite" // *Cause: An application attempted to convert a cipher suite to a string // representation but the value did not correspond to a known cipher // suite. // *Action: Specify a correct value for the cipher suite. If, however, this // error is returned by the Oracle Net SSL protocol adapter, it should // be reported to Oracle Customer Support as this error should not // be returned by the adapter. / 28890, 00000, "Entrust Login Failed" // *Cause: An application's attempt to login to Entrust Profile failed. // This could be caused by number of problems including: // 1. Entrust Admin/Authority is not online. // 2. Invalid password for Entrust profile specified. // 3. Invalid path to Entrust profile specified // 4. Invalid Entrust initialization file specified. // 5. Entrust Server Login program not executed (server-side only). // *Action: Make sure that: // 1. Entrust Authority is online; // 2. Password for Entrust profile is specified correctly; // 3. Path to Entrust profile is specified correctly; // 4. A valid Entrust initialization file is provided; // 5. Entrust Server Login program is run before the database startup. // For more information, enable tracing and the trace output // should indicate the exact Entrust failure codes. / 29002, 00000, "SSL Transport detected invalid or obsolete server certificate" // *Cause: Client detects mismatched Distinguished Name from server's certificate. // Server's Distinguished Name does not reflect its SID or ServiceName. // *Action: It may not be safe to connect to the server. // Contact your administrator to update the server's certificate // to reflect server's database name or service name. / 29003, 00000, "SSL Transport detected mismatched server certificate" // *Cause: Client detects mismatch from server's DN and the security configuration. // *Action: It may not be safe to connect to the server. // Contact your administrator to configure client TNS connect data // to reflect the server Distinguished Name. / 29228, 00000, "the number of bytes for output could not be calculated" // *Cause: The cryptographic engine is confused about the algorithm. // *Action: Check the parameters being used with the cryptographic functions. / 29229, 00000, "the magic number found in the header does not match expected" // *Cause: The input TDU has either been corrupted or it is not being // used correctly. // *Action: Check that the TDU is being used from the beginning. If // possible, compare the size of the TDU upon generation to // the size trying to be used. / 29230, 00000, "the header length is not sufficient for message header" // *Cause: The input TDU has either been corrupted or it is not being // used correctly. // *Action: Check that the TDU is being used from the beginning. If // possible, compare the size of the TDU upon generation to // the size trying to be used. / 29231, 00000, "the cryptographic engine failed to initialize" // *Cause: During initialization of the cryptographic engine, some // failure occured. This includes running out of memory and // trying to seed the random number generator. // *Action: Make sure the executable has been linked with compatible // library versions, and that you are not running out of swap // space. / 29232, 00000, "the cryptographic engine key initialization failed" // *Cause: During initialization of a key for cryptography, some // failure occured. This includes running out of memory and // passing illegal arguments. // *Action: Make sure the executable has been linked with compatible // library versions, and that the correct parameters are // being used for the cryptographic functions. / 29233, 00000, "the key object could not be encoded" // *Cause: The key object may be corrupted or may be an unsupported type. // *Action: Check the key object being passed to the encoding routine. / 29234, 00000, "a key object was not extracted from encoding" // *Cause: The encoding may be corrupted or may not be a key object // at all. // *Action: Check the encoding and parameters passed to decoding // routine. / 29235, 00000, "the key information could not be retrieved" // *Cause: The key may be corrupted or may be an unsupported type. // *Action: Check the parameters being used with the cryptographic // functions. / 29236, 00000, "the random number generator will not accept seed" // *Cause: The cryptographic engine may have run out of memory. // *Action: Make sure the executable has been linked with compatible // library versions. / 29237, 00000, "the cryptographic engine could not finish the algorithm" // *Cause: The cryptographic engine does not have enough information // to correctly finish applying the algorithm. // *Action: Check the parameters being used with the cryptographic // functions. / 29238, 00000, "the cryptographic engine could not apply the algorithm" // *Cause: The cryptographic engine does not have enough information // to correctly apply the algorithm. // *Action: Check the parameters being used with the cryptographic // functions. / 29239, 00000, "the cryptographic engine could not initialize the algorithm" // *Cause: The cryptographic engine does not have enough information // to correctly initialize the algorithm. // *Action: Check the parameters being used with the cryptographic // functions. / 29240, 00000, "the cryptographic engine does not recognize the algorithm" // *Cause: The application is probably passing the wrong parameters. // *Action: Check the parameters being used with the cryptographic // functions. / 29241, 00000, "a buffer block needs to more space but its length is fixed" // *Cause: The application has preallocated an output buffer that is // too short for the operation and has specified that the // buffer should not grow as needed. // *Action: Either preallocate a larger buffer or allow the toolkit to // grow the output buffer as needed. / 29242, 00000, "the asymmetric key is too short to be used with the data." // *Cause: An asymmetric key must be at least 11 bytes longer than // the data it is being used to encrypt. // *Action: Use an asymmetric key with more bits or break the data // into smaller pieces. / 29243, 00000, "the toolkit does not recognize the type of key being used" // *Cause: The application is probably passing the wrong parameters. // *Action: Check the parameters being used with the toolkit functions. / 29245, 00000, "the toolkit does not recognize the function being used" // *Cause: The application is probably passing the wrong parameters. // *Action: Check the parameters being used with the toolkit functions. / 29246, 00000, "the toolkit could not parse the tdu" // *Cause: The TDU could be corrupted. // *Action: Check the parameters being used with the toolkit functions. / 29247, 00000, "an unopen toolkit object was used before it was opened" // *Cause: Some toolkit objects must be opened before they can be // used. // *Action: Check the parameters being used with the toolkit functions. / 29248, 00000, "an unrecgonized WRL was used to open a wallet" // *Cause: WRL's have a specific set of types and must be formatted // correctly. // *Action: Check the parameters being used with the toolkit // functions. / 29249, 00000, "an unrecognized state was passed to a cryptographic function" // *Cause: The application is probably passing the wrong parameters. // *Action: Check the parameters being used with the toolkit functions. / / / / 29250-29299 RESERVED FOR MORE PL/SQL AND UTILITY PACKAGE ERRORS / 29250, 00000, "Invalid index specifed in call to dbms_sql.bind_array" // *Cause: An invalid index was specified in a call to bind_array of // dbms_sql. The index may have been null or of an improper // value. // *Action: Correct the index value by modifying your PL/SQL program and try // the bind_array call again. 29251, 00000, "Index1 is greater than Index2 in call to dbms_sql.bind_array" // *Cause: The value of index1 was greater than the value for index2 in // the call to bind_array. This is illegal since the elements of // the table that will be bound are those with indexes greater // than or equal to index1 and less than or equal to index2. // *Action: Correct the value of the two indexes and try the call to // again bind_array. 29252, 00000, "collection does not contain elements at index locations in call to dbms_sql.bind_array" // *Cause: The bound table does not contain elements at both index locations // in call to bind_array of dbms_sql. This is illegal. // Both index locations must contain elements. // In other words tab.exists(index1) and tab.exists(index2) must // both return true. // *Action: Either modify the two indexes or the contents of the table // and try the call again. 29253, 00000, "Invalid count argument passed to procedure dbms_sql.define_array" // *Cause: The count argument specified in the call to procedure define_array // of package dbms_sql had an invalid value. Invalid values are // negative numbers and nulls. The argument must be a positive // integer. // *Action: Correct your PL/SQL program so that only valid arguments are passed // to define_array and try again. 29254, 00000, "Invalid lower_bound argument passed to procedure dbms_sql.define_array" // *Cause: The lower_bound argument specified in the call to procedure // define_array had an invalid value. Legal values are all // integers (both positive and negative) including zero. The null // value is illegal. // *Action: Correct your PL/SQL program so that only valid arguments are passed // to define_array and try again. 29255, 00000, "Cursor contains both bind and define arrays which is not permissible" // *Cause: Both define_array and bind_array have been called on this cursor. // This is illegal. It is not possible for a cursor to both contain // array binds and array defines. The semantics of this setting are // nonsensical. Array defines are used to move data from select // queries into PL/SQL tables and array binds to bind PL/SQL tables // to non-select queries. // *Action: Modify your PL/SQL program to only perform calls to one of the two // functions depending on the kind of cursor at hand. 29256, 00000, "Cursor contains both regular and array defines which is illegal" // *Cause: Both define_array and define_column have been called on this // cursor. This is illegal. It is not possible for a cursor // to both contain regular and array defines. The semantics of this // setting are nonsensical. Array defines are used to move data // from select queries into PL/SQL tables and regular defines to // move data from select queries into PL/SQL variables. // *Action: Modify your PL/SQL program to only perform calls to one of the two // functions depending on the situation at hand. 29257, 00000, "host %s unknown" // *Cause: The specified host was unknown. // *Action: Check the spelling of the host name or the IP address. Make sure // that the host name or the IP address is valid. 29258, 00000, "buffer too small" // *Cause: The input or output buffer was too small for the operation. // *Action: Increase the size of the buffer and retry the operation. 29259, 00000, "end-of-input reached" // *Cause: The end of the input was reached. // *Action: If the end of the input is reached prematurely, check if the input // source terminates prematurely. Otherwise, close the connection // to the input. 29260, 00000, "network error: %s" // *Cause: A network error occurred. // *Action: Fix the network error and retry the operation. 29261, 00000, "bad argument" // *Cause: A bad argument was passed to the PL/SQL API. // *Action: Check the arguments passed to the PL/SQL API and retry the call. 29262, 00000, "bad URL" // *Cause: An improperly formed URL was passed to the PL/SQL API. // *Action: Check the URL and retry the call. 29263, 00000, "HTTP protocol error" // *Cause: A HTTP protocol error occured during the HTTP operation. // *Action: Check the HTTP server that the HTTP operation was performed to // make sure that it follows the HTTP protocol standard. 29264, 00000, "unknown or unsupported URL scheme" // *Cause: The URL scheme was unknown or unsupported. // *Action: Check the URL to make sure that the scheme is valid and supported. 29265, 00000, "HTTP header not found" // *Cause: The requested HTTP header was not found. // *Action: Check to make sure that the requested HTTP header is present. 29266, 00000, "end-of-body reached" // *Cause: The end of the HTTP response body was reached. // *Action: If the end of the HTTP response is reached prematurely, check if // the HTTP response terminates prematurely. Otherwise, end the // HTTP response. 29267, 00000, "illegal call" // *Cause: The call to the PL/SQL API was illegal at the current stage of // the operation. // *Action: Retry the call at a different stage of the operation. 29268, 00000, "HTTP client error %s" // *Cause: The HTTP response indicated that the HTTP client error occurred. // *Action: Fix the HTTP client error and retry the HTTP request. 29269, 00000, "HTTP server error %s" // *Cause: The HTTP response indicated that the HTTP server error occurred. // *Action: Fix the HTTP server error and retry the HTTP request. Contact // the admistrator of the HTTP server when necessary. 29270, 00000, "too many open HTTP requests" // *Cause: Too many HTTP requests were opened. // *Action: End some HTTP requests and retry the HTTP request. 29271, 00000, "not connected" // *Cause: The network connection was not made while the network operation was // attempted. // *Action: Retry the network operation after the network connection is made // successfully. 29272, 00000, "initialization failed" // *Cause: The UTL_HTTP package failed to initialize. // *Action: Free up some memory or other system resources and retry the // operation. 29273, 00000, "HTTP request failed" // *Cause: The UTL_HTTP package failed to execute the HTTP request. // *Action: Use get_detailed_sqlerrm to check the detailed error message. // Fix the error and retry the HTTP request. 29274, 00000, "fixed-width multibyte character set not allowed for a URL" // *Cause: The character set used as an encoding of the URL is a fixed-width // multibyte character set and is not allowed for a URL. // *Action: Use the corresponding variable-width multibyte character set for // the URL instead. 29275, 00000, "partial multibyte character" // *Cause: The requested read operation could not complete because a partial // multibyte character was found at the end of the input. // *Action: Ensure that the complete multibyte character is sent from the // remote server and retry the operation. Or read the partial // multibyte character as RAW. 29276, 00000, "transfer timeout" // *Cause: Timeout occurred while reading from or writing to a network // connection. // *Action: Check the remote server or the network to ensure that it responds // within the timeout limit. Or increase the timeout value. 29277, 00000, "invalid SMTP operation" // *Cause: The SMTP operation was invalid at the current stage of the SMTP // transaction. // *Action: Retry the SMTP operation at the appropriate stage of the SMTP // transaction. 29278, 00000, "SMTP transient error: %s" // *Cause: A SMTP transient error occurred. // *Action: Correct the error and retry the SMTP operation. 29279, 00000, "SMTP permanent error: %s" // *Cause: A SMTP permanent error occurred. // *Action: Correct the error and retry the SMTP operation. / / / 29300 - 29399 Reserved for errors from DBMS* pl/sql pakages. / These messages are generated from the dbms_sys_error package. / Messages can be given explicitly in this file or they can be passed as / a (single) string parameter to the / The dbms_sys_error.raise_system_error call. / If an error message is not found in this file, the string passed to the / call is used as the error message. / / 29300 - 29354 RESERVED FOR THE DBMS_SQL PACKAGE / 29300, 00000, "ORACLE error, tablespace point-in-time recovery" // *Cause: Another ORACLE error occured in the DBMS_PITR package. // *Action: See the text of the error message for a description of the error. / 29301, 00000, "wrong DBMS_PITR package function/procedure order" // *Cause: The DBMS_PITR package function/procedure was called in an incorrect // order. // *Action: Restart tablespace point-in-time recovery with a correct procedure. / 29302, 00000, "database is not open clone" // *Cause: The database was not opened as a clone database. // *Action: Mount the database clone and open the database. / 29303, 00000, "user does not login as SYS" // *Cause: The user did not log in as SYS to perform tablespace point-in-time // recovery in a clone database. // *Action: Log in as SYS and restart tablespace point-in-time recovery. / 29304, 00000, "tablespace '%s' does not exist" // *Cause: The selected tablespace does not exist in the database. // *Action: Check the list of tablespaces in V$TABLESPACE and select a valid // tablespace. / 29305, 00000, "cannot point-in-time recover tablespace '%s'" // *Cause: An attempt was made to ALTER the tablespace to be read only. // *Action: Check if the tablespace is SYSTEM or with online rollback segment. / 29306, 00000, "datafile %s is not online" // *Cause: The selected datafile was not online. // *Action: Bring the the datafile online and rename it if necessary. / 29307, 00000, "datafile %s error, %s" // *Cause: The datafile is not ready for tablespace point-in-time recovery. // *Action: Check the correct tablespace point-in-time recovery procedure. / 29308, 00000, "view TS_PITR_CHECK failure" // *Cause: Some objects which crossed the boundary of the recovery set were // not allowed in the tabelspace point-in-time recovery. // *Action: Query TS_PITR_CHECK and resolve the boundary crossing objects. / 29309, 00000, "export dump file was generated by different version of DBMS_PITR package" // *Cause: The version of DBMS_PITR is different from the version of the // cloned database. // *Action: Load the version of DBMS_PITR which matches the version of the // cloned database. / 29310, 00000, "database is not open, or opened as a clone" // *Cause: Either the database was not open, or an attempt was made to open it // as a cloned database. // *Action: Open the production database instead. / 29311, 00000, "export dump file was not generated by this database, %s does not match" // *Cause: The export dump files were imported to an incorrect database. // *Action: Open the correct production database and try the import again. / 29312, 00000, "database not compatible, %s %s" // *Cause: A point-in-time tablespace was chosen to perform the recovery, but // the current database is not compatible with the database that was // used to create the point-in-time tablespace. // *Action: Choose a point-in-time and retry the operation. / 29313, 00000, "tablespace '%s' cannot be imported twice" // *Cause: This is an internal error. // *Action: Contact your database administrator. / 29314, 00000, "tablespace '%s' is not OFFLINE FOR RECOVER nor READ ONLY" // *Cause: Tablespace clean SCN is either 0 or invalid. // *Action: ALTER the tablespace OFFLINE FOR RECOVER. / 29315, 00000, "tablespace '%s' has been recreated" // *Cause: An attempt was made to recover a tablespace to a point-in-time // before it was recreated. // *Action: Choose a different point in time for recovery. / 29316, 00000, "datafile %s been imported twice" // *Cause: This is an internal error. // *Action: Contact your database administrator. / 29317, 00000, "datafile %s does not exist" // *Cause: The specified datafile could not be found in the production // database. // *Action: Copy the datafile from the clone database. / 29318, 00000, "datafile %s is online" // *Cause: The datafile is online. // *Action: Take the datafile offline. / 29319, 00000, "datafile %s is not correct" // *Cause: An incorrect datafile was copied to the production database. The // datafile information in the export dump file differs with the // information in the datafile in the production database. // *Action: Copy the datafile from the clone database to the production // database. / 29320, 00000, "datafile header error" // *Cause: An error occured during reading datafile header. // *Action: Copy the correct datafile from the clone database to the // production database, then retry the operation. / 29321, 00000, "too many datafiles added since the point-in-time" // *Cause: Too many datafiles were added to the recovery set since the // point-in-time recovery. // *Action: Divide the recovery set into smaller subsets and retry. / 29322, 00000, "SCN string size too long -- maximum size 58 bytes/characters" // *Cause: Too many characters in specifying the SCN string // *Action: Remove all unnecessary characters. Only 15 characters are required // for both the hex and decimal representation of the 48 bit SCN. / 29323, 00000, "SET COMPATIBILITY command cannot be used for releases before 8.0.0" // *Cause: The rolling release feature was first implemented in 8.0.3 // *Action: Try 8.0.3 / 29324, 00000, "SET COMPATIBILITY release string format is wrong" // *Cause: It should be of the form 8.x.x // *Action: Try 8.0.3 / 29325, 00000, "SET COMPATIBILITY release number mismatches compatibility release number" // *Cause: In 8.0.3, it should be the same as compatibility release number // *Action: Specify the same as the "compatible" init.ora parameter. Note // that this cannot be a release number less than 8.0.0 / 29326, 00000, "specified SET COMPATIBILITY release number reduced to %s.%s.%s.%s.%s" // *Cause: One or more instances had a lower release number // *Action: To roll the release to the specified number, all instances will // need to migrate to the same release number or higher. / 29327, 00000, "unsupported client compatibility mode used when talking to the server" // *Cause: The client compatibility mode is higher than the // version of the server. // *Action: Using SET COMPATIBILITY command, specify the same // release number as the server. / 29328, 00000, "too many datafiles in this tablespace '%s'" // *Cause: Too many datafiles in this bitmap tablespace. ORACLE does not // support at this moment. // *Action: Call Oracle Support. / / / 29335 - 29349 Reserved for Pluggable Tablespace errors. / 29335, 00000, "tablespace '%s' is not read only" // *Cause: The tablespace is not read only. // *Action: Make the tablespace read only and retry the operation. / 29336, 00000, "Internal error [%s] [%s] from DBMS_PLUGTS" // *Cause: Internal error from package DBMS_PLUGTS. // *Action: Call Oracle Support. / 29337, 00000, "tablespace '%s' has a non-standard block size (%s)" // *Cause: The tablespace has a non-standard block size and making // such a tablespace read-write is not permitted. // *Action: Use some other mechanism to import the data / 29338, 00000, "datafile %s is in an undesired state (%s, %s)" // *Cause: The referred datafile is not in a state ready for tablespace // copy operation. For example, the datafile may be offline. The // datafile needs to be ONLINE, and either READ ONLY or READ WRITE. // *Action: Put the datafile into the desired state. / 29339, 00000, "tablespace block size %s does not match configured block sizes" // *Cause: The block size of the tablespace to be plugged in or // created does not match the block sizes configured in the // database. // *Action:Configure the appropriate cache for the block size of this // tablespace 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. / 29340, 00000, "export file appears to be corrupted: [%s] [%s] [%s]" // *Cause: This is caused either by a corrupted export file or by an // Oracle internal error. // *Action: Make sure the export file used for transportable tablespace // is not corrupted. If the error still occurs, call Oracle support. / 29341, 00000, "The transportable set is not self-contained" // *Cause: The set of objects in the set of tablespaces selected are // not self-contained. // *Action: Consider using different export options, or removing some // of the pointers that caused the violation, or selecting a // different set of tablespaces. / 29342, 00000, "user %s does not exist in the database" // *Cause: The referred user is one of the owners of data in the // pluggable set. This user does not exist in the database. // *Action: Consider either creating the user in the database or map // the user to a different user via FROM_USER and TO_USER // import options. / 29343, 00000, "user %s (mapped from user %s) does not exist in the database" // *Cause: The referred user is one of the owners of data in the // pluggable set. This user does not exist in the database. // *Action: Consider either creating the user or map the original user to // a different user. / 29344, 00000, "Owner validation failed - failed to match owner '%s'" // *Cause: The system failed to match the referred owner. There are two // cases that this may occur. (1) This user owns data in the // transportable set, but this user is not specified in the TTS_OWNERS // list of the import command line option, assuming that TTS_OWNERS // is specified. (2) This user is specified in the TTS_OWNER list, // but this user does not own any data in the transportable set. // *Action: Retry import with a different OWNER list. / 29345, 00000, "can not plug a tablespace into a database using a different character set" // *Cause: Oracle does not support plugging a tablespace into a database // using a different character set. // *Action: Use import/export or unload/load to move data instead. / 29346, 00000, "invalid tablespace list" // *Cause: the tablespace list supplied to dbms_tts.transport_set_check // PL/SQL routine is in an incorrect format. // *Action: Check the manual and use the correct format. / 29347, 00000, "Tablespace name validation failed - failed to match tablespace '%s'" // *Cause: The system failed to match the referred tablespace. There are // 2 cases that this may happen. (1) This tablespace is in the // transportable set, but it is not specified in the TABLESPACES // list of the import command line option, assuming that TABLESPACES // is specified. (2) This tablespace is in the TABLESPACES list, but // it is not in the transportable set. // *Action: Retry the operation with the correct TABLESPACES list. / 29348, 00000, "You must specify the datafiles to be plugged in" // *Cause: The datafiles to be plugged in are not specified. // *Action: Specify the datafiles via the import DATAFILES command // line option. / 29349, 00000, "tablespace '%s' already exists" // *Cause: Tried to plug-in a tablespace which already exists. // *Action: Drop the offending tablespace if possible. Otherwise use a // different method (e.g., import/export) to move data. / 29350, 00000, "server version %s incompatible with package %s version %s" / 29351, 00000, "can not transport system or temporary tablespace '%s'" // *Cause: The referred tablespace is either the system tablespace // or a temporary tablespace. // *Action: Do not include this tablespace in the transportable set. 29352, 00000, "event '%s' is not an internal event" // *Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event // name that is not an internal event. // *Action: Check the list of events from X$KSLED and verify the event name // parameter passed to the WAIT_FOR_EVENT procedure. / / 29355 - 29399 RESERVED FOR DBMS RESOURCE MANAGER PACKAGES / Unused error messages for later use: 29378, 29392 / 29355, 00000, "NULL or invalid %s argument specified" // *Cause: The named argument was either invalid or specified as a NULL // *Action: Specify non-null, valid arguments. / 29356, 00000, "These parameters can be specified only for directives that refer to consumer groups" // *Cause: The below parameters were specified as an argument to procedure // CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package // DBMS_RESOURCE_MANAGER.where the GROUP_OR_SUBPLAN argument is a // resource plan. "ACTIVE_SESS_POOL_P1", "QUEUEING_P1", // "PARALLEL_DEGREE_LIMIT_P1", "SWITCH_P1", "SWITCH_P2", "SWITCH_P3", // "MAX_EST_EXEC_TIME", "UNDO_POOL" // *Action: Specify these parameters only for consumer group directives. / 29357, 00000, "object %s already exists" // *Cause: The name specified as argument to procedure CREATE_PLAN, // CREATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER was // already in use. // *Action: Specify an unused name. / 29358, 00000, "resource plan %s does not exist" // *Cause: An invalid plan name was specified as an argument to procedure // UPDATE_PLAN of package DBMS_RESOURCE_MANAGER. // *Action: Specify an existing plan name. / 29359, 00000, "invalid method name %s specified for resource plan %s" // *Cause: An invalid method was specified as an argument to // procedure CREATE_PLAN or UPDATE_PLAN of package // DBMS_RESOURCE_MANAGER. // *Action: Specify a valid method name. / 29360, 00000, "retry operation. Too much concurrent activity" // *Cause: An attempt was made to revoke the switch consumer group privilege // from a user for his/her initial consumer group but someone is // modifying the user in another session. // *Action: Retry the operation later. / 29361, 00000, "percentage %s is outside valid range of 0 to 100" // *Cause: An invalid percentage value was specified. // *Action: Specify a percentage value between 0 and 100 inclusive. / 29362, 00000, "plan directive %s, %s does not exist" // *Cause: A non-existent plan directive was specified for procedure // UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. // *Action: Specify an existing plan directive for update. / 29363, 00000, "plan directive %s, %s is mandatory and cannot be modified or deleted" // *Cause: An attempt was made to modify a mandatory plan directive. // *Action: Do not attempt to modify mandatory plan directives because they // are required by the Resource Manager and cannot be modified. / 29364, 00000, "plan directive %s, %s already exists" // *Cause: An attempt was made to create a plan directive that already exists. // *Action: Retry the create operation using different values. / 29365, 00000, "NULL or invalid GROUP_OR_SUBPLAN argument specified" // *Cause: A NULL or invalid GROUP_OR_SUBPLAN was specified as an argument to // procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of // package DBMS_RESOURCE_MANAGER. // *Action: Specify a non-NULL, valid argument. / 29366, 00000, "invalid CONSUMER_GROUP argument specified" // *Cause: An invalid consumer group name was specified. // *Action: Specify a non-NULL, valid consumer group name. / 29367, 00000, "object %s does not exist" // *Cause: A non-existent object name was specified as an argument to procedure // CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. // *Action: Specify a valid plan or consumer group name. / 29368, 00000, "consumer group %s does not exist" // *Cause: An non-existent consumer group was specified. // *Action: Specify an existing consumer group. / 29369, 00000, "invalid method name %s specified for consumer group %s" // *Cause: An invalid method name was specified as an argument to // procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package // DBMS_RESOURCE_MANAGER. // *Action: Specify a valid method name. / 29370, 00000, "pending area is already active" // *Cause: An attempt was made to activate a pending area that is // already active. // *Action: Wait until the pending area is no longer active; then, retry // the operation. / 29371, 00000, "pending area is not active" // *Cause: An attempt was made to make changes without creating a pending // area. // *Action: Invoke procedure CREATE_PENDING_AREA before making any changes. / 29372, 00000, "identifier %s is too long; it must be less than %s characters" // *Cause: An attempt was made to specify an identifier that is more than // 30 characters long. // *Action: Use an identifier that is 30 characters or less in length. / 29373, 00000, "resource manager is not on" // *Cause: An attempt was made to execute an operation that cannot be // executed with the resource manager being off // *Action: Turn on the resource manager and try again. / 29374, 00000, "resource plan %s in top-plan %s has no plan directives" // *Cause: A plan was created in the pending area that is an orphan or // stand-alone. // *Action: Create plan directives if needed. Otherwise, delete the plan. / 29375, 00000, "sum of percentages %s for level %s, plan %s exceeds %s" // *Cause: The sum of percentages for the specified plan, level exceeds 100 // *Action: Alter the percentages for the level so that they sum to 100 / 29376, 00000, "number of consumer groups %s in top-plan %s exceeds %s" // *Cause: The number of consumer groups in the specified top-plan is // more than 32. // *Action: Change the top-plan to have no more than 32 consumer groups. / 29377, 00000, "consumer group %s is not part of top-plan %s" // *Cause: OTHER_GROUPS was not included as part of the specified top-plan. // Each top plan must include the built-in consumer group // OTHER_GROUPS. // *Action: Create a plan directive with the argument GROUP_OR_SUBPLAN // being OTHER_GROUPS somewhere in the top-plan. / 29379, 00000, "resource plan %s is involved in a loop in top-plan %s" // *Cause: A loop was discovered while validating a top-plan. // *Action: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN, // and remove the plan directive that causes the loop. / 29380, 00000, "resource plan %s is currently active and cannot be deleted" // *Cause: An attempt was made to delete an active plan in the pending area. // No changes can be made to active plans. // *Action: Delete the plan when it is not in use. / 29381, 00000, "plan/consumer_group %s referred to by another plan and cannot be deleted" // *Cause: An attempt was made to delete a plan or consumer group that is // referred to by another plan. // *Action: Remove all plan directives that have the plan or consumer group as // GROUP_OR_SUBPLAN; then delete the plan or consumer group. / 29382, 00000, "validation of pending area failed" // *Cause: Invalid changes were attempted in the pending area. // *Action: See documentation and the error messages that follow this one. / 29383, 00000, "all leaves of top-plan %s must be consumer groups" // *Cause: An attempt was made to create or modify the specified top-plan // but it has some plans as leaves. // *Action: To identify which plans and/or plan directives need to be modified, // look at all plans that have no plan directives. Then, alter the // top-plan so that all its leaves are consumer groups. / 29384, 00000, "number of children for plan %s exceeds %s" // *Cause: An attempt was made to create or modify the specified plan, but // the plan has more than 32 children. // *Action: Make sure the specified plan points to no more than 32 distinct // nodes. / 29385, 00000, "cannot create plan directive from %s to %s" // *Cause: An attempt was made to create a plan directive from a plan to // itself. // *Action: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure // CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are // different. / 29386, 00000, "plan or consumer group %s is mandatory and cannot be deleted or modified" // *Cause: An attempt was made to delete or modify the specified mandatory // plan or consumer group. // *Action: Do not attempt to delete or modify mandatory plans and // consumer groups. / 29387, 00000, "no top-plans found in the pending area" // *Cause: The VALIDATE_PENDING_AREA procedure found that either the // intended top-plan(s) are involved in a loop or there are no // top-plans. // *Action: Check all edges going from a subplan to the intended top-plan. // Make sure the top plan does not have any plan referring to it. / 29388, 00000, "plan/consumer_group %s is part of more than one top-plan" // *Cause: An attempt was made to delete a subtree that includes a plan or // consumer group that is part of more than one top-plan as part // of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. // Such a plan or consumer group cannot be deleted. // *Action: Check the ancestors of the plan or consumer group and make sure // it is only part of the top-plan that includes the subtree being // deleted. / 29389, 00000, "too many errors during validation" // *Cause: The number of errors detected during validation is too high. // *Action: Perform the necessary actions to remove some errors, and retry // validation. / 29390, 00000, "some resource plans are not part of any top-plan" // *Cause: An attempt was made to create or modify some plans in the // pending area that are not part of any top-plan // *Action: Remove these plans are try validation again. / 29391, 00000, "%s and %s must be mandatory to create a mandatory plan directive" // *Cause: An attempt was made to create a mandatory plan directive where // either PLAN or GROUP_OR_SUBPLAN or both were not mandatory // *Action: Recreate these objects as mandatory and then create the plan // directive. / 29393, 00000, "user %s does not exist or is not logged on" // *Cause: An invalid user name was specified as argument to procedure // SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER // or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or // the specified user was not logged on. // *Action: Specify a valid user name. / 29394, 00000, "session id %s and serial# %s do not exist" // *Cause: Invalid session id and serial# were specified as arguments to // procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package // DBMS_SYSTEM. // *Action: Specify valid values from the view V$SESSION. / 29395, 00000, "cannot set the initial consumer group to %s" // *Cause: An attempt was made to set the initial consumer group of a user to // OTHER_GROUPS. // *Action: OTHER_GROUPS is for the resource manager's internal use. Specify // another consumer group. / 29396, 00000, "cannot switch group to %s" // *Cause: An attempt was made to switch the consumer group of a user or // a session to OTHER_GROUPS. // *Action: OTHER_GROUPS is for the resource manager's internal use. Specify // another consumer group. / 29397, 00000, "cannot grant/revoke switch privilege for %s" // *Cause: An attempt was made to grant or revoke the privilege to switch // to OTHER_GROUPS. // *Action: OTHER_GROUPS is for the resource manager's internal use. Specify // another consumer group. / 29398, 00000, "invalid privilege name specified" // *Cause: An invalid privilege name was specified as an argument to // procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of // package DBMS_RESOURCE_MANAGER_PRIVS. // *Action: Specify a valid privilege name. / 29399, 00000, "user %s does not have privilege to switch to consumer group %s" // *Cause: An attempt was made to set the initial consumer group of the // specified user but the user does not have the privilege to // switch to that group. // *Action: Grant the privilege to switch to the consumer group to the user // and then set the initial group. / / 29400 - 29499 Reserved for Oracle8 Data Cartridges / 29400, 00000, "data cartridge error\n%s" // *Cause: An error has occurred in a data cartridge external procedure. // This message will be followed by a second message giving // more details about the data cartridge error. // *Action: See the data cartridge documentation // for an explanation of the second error message. / / / / / 29500 - 29699 Reserved for DDL and other integration for / embedding Aurora group's Java VM in the server / 29500, 00000, "NAMED keyword is invalid in CREATE JAVA CLASS" // *Cause: A NAMED keyword was specified in the CREATE JAVA CLASS // statement. NAMED keywords are valid only in CREATE JAVA // SOURCE or RESOURCE statements. // *Action: Remove the NAMED keyword from the CREATE JAVA // CLASS statement. / 29501, 00000, "invalid or missing Java source, class, or resource name" // *Cause: The required name for a Java source, class, or resource // was invalid or missing. // *Action: Specify a valid name. / 29502, 00000, "NAMED keyword required in CREATE JAVA RESOURCE" // *Cause: The name for a Java resource was not specified. The name // must be specified with the NAMED keyword. // *Action: Specify a valid name with the NAMED keyword. / 29503, 00000, "SCHEMA keyword not valid with NAMED keyword" // *Cause: SCHEMA and NAMED keywords were used together in the same // CREATE JAVA command, but only one may be used in a // CREATE JAVA command. // *Action: Remove either the NAMED or the SCHEMA keyword. / 29504, 00000, "invalid or missing schema name" // *Cause: The required schema name was invalid or missing. // *Action: Specify a valid schema name. / 29505, 00000, "AS keyword is invalid in CREATE JAVA CLASS or RESOURCE" // *Cause: The AS keyword was used in CREATE JAVA CLASS or RESOURCE. // The AS keyword is valid only in CREATE JAVA SOURCE. // *Action: Use the USING keyword in CREATE JAVA CLASS or RESOURCE. / 29506, 00000, "invalid query derived from USING clause" // *Cause: The USING clause did not form a valid query. // *Action: Correct the USING clause. / 29507, 00000, "query derived from USING clause found zero or many rows" // *Cause: The USING clause defined a query that either did not return any // values, or returned more than one value. // *Action: Correct the USING clause. / 29508, 00000, "query derived from USING clause did not select a value of type %s" // *Cause: The USING clause did not form a query that selects a value of // the type specified by the term following the USING keyword. // *Action: Correct the USING clause. / 29509, 00000, "incorrectly formed Java binary class definition" // *Cause: An attempt was made to create a Java class using data expected // to be in binary (Java .class) format. The data was found not // to be in this format, or to be incorrectly formed. // *Action: Correct the definition data. / 29510, 00000, "name, %s.%s, already used by an existing object" // *Cause: A CREATE JAVA command attempted to create a source, class, // or resource object with a name that is already in use. // *Action: Drop the existing object that is using the desired name, // or use a different name for the new object. / 29511, 00000, "could not resolve Java class" // *Cause: A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified // definition data that could not be resolved, or resolution // failed for some referenced class. // *Action: Remove the NOFORCE option or remove impediments to resolution. / 29512, 00000, "incorrectly formed name resolver specification" // *Cause: A name resolver was not specified in the required // form: (( , ) ...) // *Action: Correct the specification. / 29513, 00000, "referenced class name too long" // *Cause: An attempt was made to import a .class file containing a // class name of length greater than %d. The .class file // could not be imported because the referenced class name // was too long. // *Action: Shorten the referenced class name in the .class file. / 29514, 00000, "class name contains illegal character" // *Cause: An attempt was made to import a .class file containing a // character that cannot be converted to the server character // set. The .class file could not be imported because of the // illegal character. // *Action: Correct the illegal character in the .class file. / 29515, 00000, "exit called from Java code with status %s" // *Cause: Java code included a call to // java.lang.Runtime.exitInternal. // *Action: Do not include this call unless non-local exit is desired. / 29516, 00000, "Aurora assertion failure: %s" // *Cause: An internal error occurred in the Aurora module. // *Action: Contact Oracle Worldwide Support. / 29517, 00000, "recursive resolution failed for a referenced class" // *Cause: An attempt to resolve a referenced class failed. // *Action: Review the errors for referenced classes and complete the // necessary actions to correct them. / 29518, 00000, "name %s resolved to an object in schema %s that is not a Java class" // *Cause: A referenced name was resolved to an object that is not // a Java class. // *Action: Adjust name resolver or add missing Java class. / 29519, 00000, "name %s resolved via a synonym in schema %s to a class with a different name" // *Cause: A referenced name was resolved to a synonym, which translated to // a class whose name does not match the referenced name. // *Action: Adjust name resolver or add missing Java class. / 29520, 00000, "name %s resolved to a class in schema %s that could not be accessed" // *Cause: An attempt to access a referenced class failed. // *Action: Adjust authorizations or name resolution. / 29521, 00000, "referenced name %s could not be found" // *Cause: Name resolution failed to find an object with the indicated name. // *Action: Adjust name resolver or add missing Java class. / 29522, 00000, "authorization error for referenced name %s.%s" // *Cause: An attempt was made to resolve a class that is not authorized // to use the indicated referenced class. // *Action: Adjust authorizations or name resolution. / 29523, 00000, "authorization error for unknown referenced name" // *Cause: An attempt was made to resolve a class that is not authorized // to use a referenced class. The name of the referenced class // could not be determined. // *Action: Adjust authorizations or name resolution. / 29524, 00000, "wrong types of arguments in call to '%s'" // *Cause: A method was called with argument(s) of incompatible type(s). // *Action: Adjust caller. / 29525, 00000, "referenced name is too long: '%s'" // *Cause: An attempt was made to create a class that references a name // longer than 4000 characters. The class could not be created // because the name is too long. // *Action: Adjust the definition. / 29526, 00000, "created Java class %s\"%s\"" // *Cause: An informational message, not an error. // *Action: None. / 29527, 00000, "created Java source %s\"%s\"" // *Cause: An informational message, not an error. // *Action: None. / 29528, 00000, "invalid Java call in trigger %s" // *Cause: The Java method specified in trigger does not exist or cannot be // called as used. // *Action: Adjust trigger definition. / 29529, 00000, "invalid function or method call %s in trigger %s" // *Cause: The function or method specified in Java trigger call expression // could not be resolved. // *Action: Adjust trigger definition. / 29530, 00000, "could not create shortened name for %s" // *Cause: Insert into shortened name translation table failed. // *Action: Retry the insert. / 29531, 00000, "no method %s in class %s" // *Cause: An attempt was made to execute a non-existent method in a // Java class. // *Action: Adjust the call or create the specified method. / 29532, 00000, "Java call terminated by uncaught Java exception: %s" // *Cause: A Java exception or error was signaled and could not be // resolved by the Java code. // *Action: Modify Java code, if this behavior is not intended. / 29533, 00000, "attempt to overwrite class or resource %s while defining or compiling %s.%s" // *Cause: A class or resource defined by a SQLJ source conflicted with an existing object. // *Action: Remove existing object, or modify SQLJ source. / 29534, 00000, "referenced object %s.%s could not be resolved" // *Cause: Name resolution determined that the indicated object is referenced // but could not be resolved. // *Action: Correct name resolver or address resolution problems in the // referenced class, or correct compilation problems in its source. / 29535, 00000, "source requires recompilation" // *Cause: The reason the current class object was invalid is recorded // with the source object from which it was compiled. // *Action: Inspect errors in the source object and take the necessary // corrective actions. / 29536, 00000, "badly formed source: %s" // *Cause: An attempt was made to create a Java source object with text // that could not be parsed adequately to determine the class(es) // defined by it. // *Action: Correct errors in source. / 29537, 00000, "class or resource cannot be created or dropped directly" // *Cause: An attempt was made to create or drop a Java class or resource that // is known to result from compilation of an existing Java source object. // *Action: Act on the class or resource by acting on the source, or change // the source so that it no longer defines the class or resource. / 29538, 00000, "Java not installed" // *Cause: An attempt was made to use a Java command when Java is not installed. // *Action: Install Java, or do not use the command. / 29539, 00000, "Java system classes already installed" // *Cause: An attempt was made to use the CREATE JAVA SYSTEM command in a // database where the Java system classes already are installed. // *Action: Use CREATE OR REPLACE JAVA SYSTEM. / 29540, 00000, "class %s does not exist" // *Cause: Java method execution failed to find a class with the indicated name. // *Action: Correct the name or add the missing Java class. / 29541, 00000, "class %s.%s could not be resolved" // *Cause: An attempt was made to execute a method in a Java class // that had not been previously and cannot now be compiled // or resolved successfully. // *Action: Adjust the call or make the class resolvable. / 29542, 00000, "class %s already defined by source %s" // *Cause: An attempt was made to create a Java source object that // would define a class that is already defined by a different // Java source object. // *Action: Either drop the old source or modify the new source. / 29543, 00000, "Java command %s not yet implemented" // *Cause: An attempt was made to use a Java command that is // not yet implemented. // *Action: Do not use the command. / 29544, 00000, "invalid type" // *Cause: The type argument in a call to a Java export or import command // did not have a recognized value. // *Action: Correct the value. / 29545, 00000, "badly formed class: %s" // *Cause: An attempt was made to create a Java class object with bytecodes // that were rejected by the Java verifier. // *Action: It is possible that an attempt was made to create the Java class // from a damaged class file, in which case the CREATE should be // reattempted with a correct class file. It is also possible that // the message is the result of using "-" in the resolver so that // the verifier could not check the correctness of some code. In // that case, the class needs to be created with a resolver. / 29546, 00000, "badly formed resource: %s" // *Cause: An attempt was made to create a Java resource object with data // that was rejected by the Java verifier. // *Action: Correct the data. / 29547, 00000, "Java system class not available: %s" // *Cause: An attempt was made to use a command that requires a Java system // class that was not yet present or was invalid. // *Action: Load the system classes, or do not use the command. / 29548, 00000, "Java system class reported: %s" // *Cause: A command that uses a Java system class was aborted due to an // error reported by the Java system class. // *Action: Correct the error that was reported. / 29549, 00000, "class %s.%s has changed, Java session state cleared" // *Cause: A class in use by the current session was redefined or dropped, // invalidating the current Java session state and requiring that // it be cleared. // *Action: No action required. / 29550, 00000, "Java session state cleared" // *Cause: The Java state in the current session became inconsistent and // was cleared. // *Action: No action required. / 29551, 00000, "could not convert %s to Unicode" // *Cause: A string in the database character set could not be converted // to Unicode, as required for use by Java. // *Action: Correct the string. / 29552, 00000, "verification warning: %s" // *Cause: An attempt was made to create a Java class object with bytecodes // that caused the Java verifier to issue a warning. // *Action: It is possible that the Java class was created from a damaged // class file, in which case the CREATE should be reattempted // with a correct class file. It is also possible that the message // is the result of using "-" in the resolver so that the verifier // could not check the correctness of some code. In that case, the // class needs to be created with a resolver. / 29553, 00000, "class in use: %s.%s" // *Cause: An attempt was made to modify a Java class that is in use in the // current call. // *Action: Correct the code in use in this call. / 29554, 00000, "unhandled Java out of memory condition" // *Cause: The session encountered an out of memory condition in Java // from which it could not recover. Java session state was cleared. // *Action: No action required. / 29555, 00000, "Java source, class or resource is not allowed here" // *Cause: A Java source, class, or resource was specified in an // inappropriate place in a statement. // *Action: Make sure the name is correct or remove it. / 29556, 00000, "object type has changed" // *Cause: A database object name that named a Java source, class, or resource // now names an object of a different type. // *Action: No action required. / 29557, 00000, "Java system class %s cannot be modified" // *Cause: A command was attempted that would have modified a Java system class. // *Action: No action required. / 29655, 00000, "USING clause is incompatible with its supertype" // *Cause: The USING clause of a type has to be the same as its supertype or // compatible with it. // *Action: Make sure the USING clause is compatible with its supertype. / 29656, 00000, "Invalid option for USING" // *Cause: The class has to implement the required interface for the value // of the option for USING. // // *Action: Make sure the USING clause is supported. / 29657, 00000, "class defined in EXTERNAL NAME clause is used in another subtype" // *Cause: The supertype has an existing type that has the same value // for the EXTERNAL NAME. // *Action: Make sure the EXTERNAL NAME clause is unique among subtypes. / 29658, 00000, "EXTERNAL NAME clause is not compatible with its supertype" // *Cause: The EXTERNAL NAME clause of the type is not a subclass of the // supertype EXTERNAL NAME. // *Action: Make sure the EXTERNAL NAME clause of the type is a subclass of // the EXTERNAL NAME of its supertype. / 29659, 00000, "SQLJ Object Type validation failed to get default connection" // *Cause: Unable to connect using the JDBC default connection. // // *Action: No action required. / 29660, 00000, "Unable to find the class defined in the EXTERNAL NAME clause" // *Cause: The class is not loaded in the database. // // *Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the // the database. / 29661, 00000, "Unable to find the superclass of the defined in the EXTERNAL NAME" // *Cause: The class is not loaded in the database. // // *Action: Make sure the superclass of the EXTERNAL NAME is loaded in the // the database. / 29662, 00000, "Unable to find a field that matches one or more of the attributes" // *Cause: The EXTERNAL NAME option of one or more attributes do not match // any fields in the defined class. // // *Action: Make sure the EXTERNAL NAME option of each attribute matches // a field in the defined in the defined class. / 29663, 00000, "Unable to find a method that matches one or more of the functions" // *Cause: The EXTERNAL NAME option of one or more functions do not match // any method in the defined class. // // *Action: Make sure the EXTERNAL NAME option of each function matches // a method in the defined in the defined class. / 29664, 00000, "Unable to generate the helper class for the defined type" // *Cause: The helper class used for supporting SQLJ Object Type is not // generated. // // *Action: No Action is required. / / 29700-29799 reserved for Global Enqueue Service / 29700, 00000, "enable global enqueue service conversion statistics" // *Document: NO // *Cause: // *Action: Global enqueue service conversion statistics enabled. 29701, 00000, "unable to connect to Cluster Manager" // *Cause: Connect to CM failed or timed out. // *Action: Verify that the CM was started. If the CM was not started, // start it and then retry the database startup. If the CM died // or is not responding, check the Oracle and CM trace files for // errors. 29702, 00000, "error occurred in Cluster Group Service operation" // *Cause: An unexpected error occurred while performing a CGS operation. // *Action: Verify that the LMON process is still active. Also, // check the Oracle LMON trace files for errors. 29703, 00000, "error occurred in global enqueue service operation" // *Cause: An unexpected error occurred while performing a global enqueue // service operation. // *Action: Check oracle trace files for errors. 29704, 00000, "cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release" // *Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the // instances in the cluster was running Oracle 8.1.5 or an earlier // release. // *Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT // parameter. Or, upgrade all instances to Oracle 8.1.6 or later // release and then specify the parameter. 29705, 00000, "ACTIVE_INSTANCE_COUNT is %s which is incompatible with the value in other instances" // *Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same // in all Oracle cluster database instances. // *Action: Check your initialization parameter files in all instances and // ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value. // Then restart the instance. 29706, 00000, "incorrect value %s for parameter ACTIVE_INSTANCE_COUNT" // *Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two // node cluster database configuration or unspecified if a secondary // instance is not needed. // *Action: Check your initialization parameter files and correct the value // of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a // two node primary/secondary cluster database, set this value to 1. // Otherwise, do not specify any value for the parameter. 29712, 00000, "enable global enqueue service cancel event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service cancel. 29713, 00000, "enable global enqueue service close event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service close. 29714, 00000, "enable global enqueue service state object event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service state object. 29715, 00000, "enable global enqueue service reconfiguration event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service reconfiguration. 29716, 00000, "enable global enqueue service post/wait & ASTs event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service post/wait & ASTs event trace. 29717, 00000, "enable global resource directory freeze/unfreeze event trace" // *Document: NO // *Cause: // *Action: Dump trace for global resource directory freeze/unfreeze. 29718, 00000, "enable global enqueue service CGS interface event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service CGS interface. 29720, 00000, "enable global enqueue service SCN service event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service SCN service. 29722, 00000, "enable global enqueue service process death event trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service process death. 29723, 00000, "Failed to attach to the global enqueue service (status=%s)" // *Document: NO // *Cause: // *Action: 29729, 00000, "enable global enqueue service inquire resource modes trace" // *Document: NO // *Cause: // *Action: Dump trace for global enqueue service resource inquiry messages. 29730, 00000, "use global enqueue converts to determine highest held mode" // *Document: NO // *Cause: // *Action: Use global enqueue converts instead of inquiry messages to // obtain highest held mode of a resource. 29740, 00000, "evicted by member %d, group incarnation %d" // *Cause: This member was evicted from the group by another member of the // cluster database for one of several reasons, which may // include a communications error in the cluster, failure to issue // a heartbeat to the control file, etc. // *Action: Check the trace files of other active instances in the cluster // group for indications of errors that caused a reconfiguration. 29741, 00000, "IMR active for some, but not all members of cluster" // *Cause: The IMR feature is not active for this instance, but is active // for another instance in the cluster database. // *Action: Ensure that all instances have the same value for the _imr_active // init.ora parameter 29745, 00000, "Perform IMR test" // *Document: NO // *Cause: // *Action: Simulate various scenarios for IMR testing. 29799, 00000, "crash for soft assert macros in global enqueue service layer" // *Document: NO // *Cause: // *Action: / 29800 - 29999 Reserved for Extensible Indexing project / / sub-ranges 29800 - 29824 Operator DDL / 29825 - 29849 Indextype DDL / 29850 - 29874 Index DDL / 29875 - 29899 Index DML / 29900 - 29924 Query / 29925 - 29999 Optimizer & common errors / 29800,00000, "invalid name for operator" // *Cause: The name specified for the operator is incorrect. // *Action: Specify a correct name for the operator. 29801,00000, "missing RETURN keyword" // *Cause: The RETURN keyword has not been specified. // *Action: Specify the RETURN keyword or check the SQL statement. 29802,00000, "missing CONTEXT keyword" // *Cause: The CONTEXT keyword has not been specified. // *Action: Specify the CONTEXT keyword or check the SQL statement. 29803,00000, "missing ANCILLARY keyword" // *Cause: The ANCILLARY keyword has not been specified. // *Action: Specify the ANCILLARY keyword or check the SQL statement. 29804,00000, "missing DATA keyword" // *Cause: The DATA keyword has not been specified. // *Action: Specify the DATA keyword or check the SQL statement. 29805, 00000, "missing COLUMN keyword" // *Cause: Keyword COLUMN is expected . // *Action: Either specify the COLUMN keyword or specify another option. 29806,00000, "specified binding does not exist" // *Cause: The operator binding which has been specified does not exist. // *Action: Ensure that the operator binding that has been specified does // exist. 29807,00000, "specified operator does not exist" // *Cause: The operator which has been specified does not exist. // *Action: Ensure that the operator that has been specified does exist. 29808,00000, "specified primary operator binding does not exist" // *Cause: The specified binding for the primary operator does not exist. // *Action: Ensure that the specified binding for the primary operator exists. 29809,00000, "cannot drop an operator with dependent objects" // *Cause: The operator which is being dropped has some dependent objects. // *Action: Either drop the dependent objects first and then issue the DROP // OPERATOR command or specify the FORCE option with DROP OPERATOR. 29810,00000, "inadequate operator privileges" // *Cause: The user does not have the appropriate privileges to perform the // specified operation on the operator. // *Action: Grant the appropriate privileges to the user and then reissue the // statement. 29811,00000, "missing STATISTICS keyword" // *Cause: This is not a valid option with the ASSOCIATE command. // *Action: Specify STATISTICS keyword after the ASSOCIATE command. 29812,00000, "incorrect object name specified" // *Cause: The specified name is not a valid name. // *Action: Specify the correct name of the object with for which an // association needs to be defined. 29813,00000, "non-supported object type with associate statement" // *Cause: The type of object specified is not supported with the associate // statistics statement. // *Action: Use a valid object type with the associate command. 29814,00000, "expecting USING or DEFAULT keyword" // *Cause: Expecting the USING or DEFAULT keyword after the names of object(s). // *Action: Provide the USING or DEFAULT keyword. 29815,00000, "object being associated is not present" // *Cause: The object for which the association is being defined is not // present. // *Action: Ensure that all the objects for which the association is being // defined are present. 29816,00000, "object being disassociated is not present" // *Cause: Object which is being disassociated is not present. // *Action: Ensure that the object which needs to be disassociated is // present. 29817,00000, "non-supported option with disassociate statement" // *Cause: The type of object specified is not supported with the disassociate // statistics statement. // *Action: Use a object type which is supported with the disassociate command. 29818,00000, "column name not properly specified" // *Cause: Name of the column should contain the table and the column name. // *Action: Specify a valid column name. 29819,00000, "cannot associate default values with columns" // *Cause: User tried to associate DEFAULT values with columns which is not // a valid option . // *Action: Specify a valid option. 29820,00000, "the statistics type is not present" // *Cause: The statistics type which is being associated with object(s) is // not present. // *Action: Ensure that the type which contains the statistics functions is // present. 29821,00000, "specified primary operator does not exist" // *Cause: The specified primary operator does not exist. // *Action: Check the primary operator and the signature specified. 29822,00000,"selectivity cannot be specified for the type of object" // *Cause: User tried to associate selectivity with index or indextypes which // is not allowed . // *Action: Specify a valid option. 29823,00000,"object being analyzed is not a table " // *Cause: The object being analyzed is not a table and is not supported // *Action: Specify only a supported option. 29824,00000, "operator is invalid" // *Cause: The operator is invalid. // *Action: Drop and recreate the operator. 29825, 00000, "invalid name for indextype" // *Cause: Indextype name or Indextype schema name has invalid characters. // *Action: Verify that the name has valid characters and it is not a reserved // word. 29826, 00000, "keyword FOR is missing" // *Cause: FOR keyword must be provided with Create Indextype statement. // *Action: Use FOR keyword and provide relevant operator information. 29827, 00000, "keyword USING is missing" // *Cause: USING keyword and corresponding implementation details must be provided. // *Action: Provide USING keyword and relevant implementation details with Create // Indextype statement. 29828, 00000, "invalid name for implementation type" // *Cause: Implementation type or Implementation schema name is invalid. // *Action: Verify that the name has valid characters and it is not a reserved // word. 29829, 00000, "implementation type does not exist" // *Cause: The implementation type specified with USING clause could not // be found. // *Action: Check to see if the type exists and the user has EXECUTE // privilege on this type. 29830, 00000, "operator does not exist" // *Cause: The operator could not be found. // *Action: Verify that the operator exists and the user has EXECUTE // privilege for this operator. 29831, 00000, "operator binding not found" // *Cause: The specified binding for the operator is not available // from the operator schema object. // *Action: Verify that the operator with the specified binding exists. 29832, 00000, "cannot drop or replace an indextype with dependent indexes" // *Cause: One or more indexes are dependent upon the indextype. // *Action: Drop all the indexes which are dependent upon the indextype // before dropping the indextype itself. 29833, 00000, "indextype does not exist" // *Cause: There is no indextype by the specified name. // *Action: Use public views for the indextypes to see if an // indextype by the specified name has been created. 29834, 00000, "REF datatype not supported with operators" // *Cause : The user specified a REF datatype which is not supported in CREATE // OPERATOR. // *Action: Reissue the CREATE OPERATOR statement without the REF datatype. 29835, 00000, "ODCIGETINTERFACES routine does not return required interface(s)" // *Cause : The ODCIObjectList returned by the ODCIGetInterfaces routine // does not contain the interface(s) required by the current usage. // *Action : Ensure that the ODCIGetInterfaces routine returns the name(s) // of the required interface(s). 29836, 00000, "failed to validate referenced operators" // *Cause: One of the operators referenced cannot be compiled. // *Action: Try to recompile the operators which are referenced by this // indextype. Use USER_INDEXTYPE_OPERATORS view to find out the // referenced operators. 29837, 00000, "insufficient privileges to execute implementation type" // *Cause: User does not have privileges to execute the implementation type. // *Action: The owner of the implementation type must grant appropriate // privileges to the user. 29838, 00000, "insufficient privileges to execute the operator(s)" // *Cause: User does not have privileges to execute one of the operators. // *Action: The owner of the operators must grant appropriate privileges // to the user . 29839, 00000, "failed to validate implementation type" // *Cause: Implementation type cannot be compiled. // *Action: Try to compile the implementation type. 29840, 00000, "indextype and implementation type are not in same schema" // *Cause: Indextype and implementation type are in different schema. // *Action: Put the indextype and implementation type in the same schema. 29841, 00000, "invalid option for ALTER INDEXTYPE" // *Cause: The user specified an invalid option with the ALTER INDEXTYPE // command // *Action: Choose a valid option with the ALTER INDEXTYPE command 29842, 00000, "option not supported with the version %s of the indextype interface" // *Cause : User specified an option which is not supported with the // version of the indextype interface provided // *Action: User should either not request for this option or should provide // an implementation type that implements the correct version of the // indextype interface. 29843, 00000, "indextype should support atleast one operator" // *Cause : User attempted to drop all the operators from the indextype // *Action : Do not drop all the operators from the indextype 29844, 00000, "duplicate operator name specified" // *Cause : User attempted to add an operator name to an indextype which is already // supported by the indextype // *Action: Remove the duplicate operator and retry the command 29845, 00000, "indextype does not support local domain index on %s partitioned table" // *Cause : User specified a create local domain index statement using an // indextype that does not support local domain indexes on // tables partitioned with the given method // *Action: Use a different indextype or build a global domain index 29846, 00000, "cannot create a local domain index on a %s partitioned table" // *Cause : User specified a create local domain index statement on a // table partitioned using a method not supported by domain indexes // *Action: Build a global domain index on the partitioned table 29847, 00000, "cannot create a local domain index on a partitioned index-organized table" // *Cause : User specified a create local domain index statement on a // partitioned index-organized table // *Action: Build a global domain index on the partitioned index-organized // table 29848, 00000, "error occurred in the execution of ODCIINDEXMERGEPARTITION routine" // *Cause: Failed to successfully execute the ODCIIndexMergePartition routine. // *Action: Check to see if the routine has been coded correctly. 29849, 00000, "error occurred in the execution of ODCIINDEXSPLITPARTITION routine" // *Cause: Failed to successfully execute the ODCIIndexSplitPartition routine. // *Action: Check to see if the routine has been coded correctly. 29850, 00000, "invalid option for creation of domain indexes" // *Cause: The user specified an invalid option like ASC, DESC, SORT or a // parallel clause, partitioning clause or physical attributes clause. // *Action: Choose one of the valid clauses for creation of domain indexes. 29851, 00000, "cannot build a domain index on more than one column" // *Cause: User attempted to build a domain index on more than one column. // *Action: Build the domain index only on a single column. 29852, 00000, "keyword IS is missing" // *Cause: IS keyword must be specified with Create Index statement for domain // indexes. // *Action: Use IS keyword and then specify the indextype name. 29853, 00000, "keyword UNIQUE may not be used in creating domain indexes" // *Cause: An attempt was made to create a domain index with the // UNIQUE attribute. // *Action: Remove UNIQUE from the CREATE INDEX statement. 29854, 00000, "keyword BITMAP may not be used in creating domain indexes" // *Cause: An attempt was made to create a domain index with the // BITMAP attribute. // *Action: Remove BITMAP from the CREATE INDEX statement. 29855, 00000, "error occurred in the execution of ODCIINDEXCREATE routine" // *Cause: Failed to successfully execute the ODCIIndexCreate routine. // *Action: Check to see if the routine has been coded correctly. 29856, 00000, "error occurred in the execution of ODCIINDEXDROP routine" // *Cause: Failed to successfully execute the ODCIIndexDrop routine. // *Action: Check to see if the routine has been coded correctly. 29857, 00000, "domain indexes and/or secondary objects exist in the tablespace" // *Cause: An attempt was made to drop a tablespace which contains secondary // objects and/or domain indexes. // *Action: Drop the domain indexes in his tablespace. Also, find the domain // indexes which created secondary objects in this tablespace and // drop them. Then try dropping the tablespace. 29858, 00000, "error occurred in the execution of ODCIINDEXALTER routine" // *Cause: Failed to successfully execute the ODCIIndexAlter routine. // *Action: Check to see if the routine has been coded correctly. 29859, 00000, "error occurred in the execution of ODCIINDEXTRUNCATE routine" // *Cause: Failed to successfully execute the ODCIIndexTruncate routine. // *Action: Check to see if the routine has been coded correctly. 29860, 00000, "cannot truncate a table with domain indexes marked LOADING" // *Cause: The table has domain indexes defined on it that are marked LOADING. //* Action: Wait to see if the ongoing index DDL ends and the index state // changes from LOADING state. Else ,drop the domain indexes marked as // LOADING with the FORCE option. 29861, 00000, "domain index is marked LOADING/FAILED/UNUSABLE" // *Cause: An attempt has been made to access a domain index that is // being built or is marked failed by an unsuccessful DDL // or is marked unusable by a DDL operation. // *Action: Wait if the specified index is marked LOADING // Drop the specified index if it is marked FAILED // Drop or rebuild the specified index if it is marked UNUSABLE. 29862, 00000, "cannot specify FORCE option for dropping non-domain index" // *Cause: A DROP INDEX FORCE was issued for a non-domain index. // *Action: Reissue the command without the FORCE option. 29863, 00000, "warning in the execution of ODCIINDEXCREATE routine" // *Cause: A warning was returned from the ODCIIndexCreate routine. // *Action: Check to see if the routine has been coded correctly // Check user specified log tables for greater detail. 29864, 00000, "analyzing domain indexes marked LOADING/FAILED not supported" // *Cause: Tried to analyze a domain index which was marked as LOADING or // FAILED. // *Action: If the index was marked LOADING, wait till it is marked valid // before retrying the analyze. If index was marked FAILED, drop it // OR rebuild it and retry the analyze. 29865,00000, "indextype is invalid" // *Cause: The indextype is invalid. // *Action: Drop and recreate the indextype. 29866, 00000, "cannot create domain index on a column of index-organized table" // *Cause: Tried to create a domain index on a column of an index-organized // table. // *Action: Do not attempt to create a domain index on columns of an // index-organized table. 29867, 00000, "cannot create a domain index on a LONG column" // *Cause: The user attempted to create a domain index on a column of LONG // datatype. // *Action: Do not create a domain index on a LONG column. 29868, 00000, "cannot issue DDL on a domain index marked as LOADING" // *Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state. // *Action: Wait till the index operation completes // OR issue a DROP INDEX FORCE to drop the index. 29869, 00000, "cannot issue ALTER without REBUILD on a domain index marked FAILED" // *Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state. // *Action: Truncate the table to mark the index as valid // OR do ALTER INDEX REBUILD to rebuild the index. 29870, 00000, "specified options are only valid for altering a domain index" // *Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index. // *Action: Reissue the statement with the correct syntax for alter. 29871, 00000, "invalid alter option for a domain index" // *Cause: The user specified an invalid option for altering a domain index. // *Action: Reissue the alter statement with a valid option. 29872, 00000, "parameters clause cannot be combined with the specified options" // *Cause: The user combined PARAMETERS clause with other alter index options. // *Action: Reissue the statement with the correct syntax for alter. 29873, 00000, "warning in the execution of ODCIINDEXDROP routine" // *Cause: A waring was returned from the ODCIIndexDrop routine. // *Action: Check to see if the routine has been coded correctly // Check the user defined warning log tables for greater details. 29874, 00000, "warning in the execution of ODCIINDEXALTER routine" // *Cause: A waring was returned from the ODCIIndexAlter routine. // *Action: Check to see if the routine has been coded correctly // Check the user defined warning log tables for greater details. 29875, 00000, "failed in the execution of the ODCIINDEXINSERT routine" // *Cause: Failed to successfully execute the ODCIIndexInsert routine. // *Action: Check to see if the routine has been coded correctly. 29876, 00000, "failed in the execution of the ODCIINDEXDELETE routine" // *Cause: Failed to successfully execute the ODCIIndexDelete routine. // *Action: Check to see if the routine has been coded correctly. 29877, 00000, "failed in the execution of the ODCIINDEXUPDATE routine" // *Cause: Failed to successfully execute the ODCIIndexUpdate routine. // *Action: Check to see if the routine has been coded correctly. 29878, 00000, "warning in the execution of ODCIINDEXTRUNCATE routine" // *Cause: A warning was returned from the ODCIIndexTruncate routine. // *Action: Check to see if the routine has been coded correctly // Check the user defined warning log tables for greater details. 29879, 00000, "cannot create multiple domain indexes on a column list using same indextype" // *Cause: An attempt was made to define multiple domain indexes on the same // column list using identical indextypes. // *Action: Check to see if a different indextype can be used or if the index // can be defined on another column list. 29880, 00000, "such column list already indexed using another domain index and indextype" // *Cause: An attempt was made to create multiple domain indexes on a column // list using indextypes which do not have disjoint operators. // *Action: Check to see if the operator sets for the indextypes can be made // disjoint. 29881, 00000, "failed to validate indextype" // *Cause: Indextype cannot be compiled. // *Action : Try to compile the indextype which is referenced by // the domain index. 29882, 00000, "insufficient privileges to execute indextype" // *Cause: User does not have privileges to execute the indextype. // *Action: The owner of the indextype must grant appropriate // privileges to the user. 29883, 00000, "cannot create a domain index on column expressions" // *Cause : User specified an expression in the column list. // *Action : Specify only simple columns in the column list for domain index. 29884, 00000, "domain index is defined on the column to be dropped" // *Cause : An ALTER TABLE DROP COLUMN was issued on a column on which // a domain index exists. // *Action : Drop the domain index before attempting to drop the column. 29885, 00000, "domain index is defined on the column to be modified" // *Cause : An ALTER TABLE MODIFY COLUMN was issued on a column on which // a domain index exists. // *Action: Drop the domain index before attempting to modify the column. 29886, 00000, "feature not supported for domain indexes" // *Cause : Feature is not supported for domain indexes. // *Action : No action required. 29887, 00000, "cannot support row movement if domain index defined on table" // *Cause : An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which // has a domain index defined on it. // *Action : Drop the domain index if you want to enable row movement and // then reissue the command. 29888, 00000, "cannot create domain index on a table with row movement enabled" // *Cause : A create domain index statement was issued on a table that has // row movement enabled. // *Action : Disable the row movement in the table and then reissue the // create domain index statement. 29889, 00000, "allow a secondary object creation" // *Cause: N/A // *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE // TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE. 29900, 00000, "operator binding does not exist" // *Cause: There is no binding for the current usage of the operator. // *Action: Change the operator arguments to match any of the existing // bindings or add a new binding to the operator. 29901, 00000, "function underlying operator binding does not exist" // *Cause: The function underlying the operator binding does not exist. // *Action: Ensure that the function corresponding to the operator // invocation exists. 29902, 00000, "error in executing ODCIIndexStart() routine" // *Cause: The execution of ODCIIndexStart routine caused an error. // *Action: Examine the error messages produced by the indextype code and // take appropriate action. 29903, 00000, "error in executing ODCIIndexFetch() routine" // *Cause: The execution of ODCIIndexFetch routine caused an error. // *Action: Examine the error messages produced by the indextype code and // take appropriate action. 29904, 00000, "error in executing ODCIIndexClose() routine" // *Cause: The execution of ODCIIndexClose routine caused an error. // *Action: Examine the error messages produced by the indextype code and // take appropriate action. 29905, 00000, "method %s does not exist in type %s.%s" // *Cause: A required method with the required signature does not exist // in the specified type. // *Action: Add the required method to the type. 29906, 00000, "indextype %s.%s does not exist" // *Cause: The indextype does not exist. // *Action: Create the indextype. 29907, 00000, "found duplicate labels in primary invocations" // *Cause: There are multiple primary invocations of operators with // the same number as the label. // *Action: Use distinct labels in primary invocations. 29908, 00000, "missing primary invocation for ancillary operator" // *Cause: The primary invocation corresponding to an ancillary operator // is missing. // *Action: Add the primary invocation with the same label as the // ancillary operator. 29909, 00000, "label for the ancillary operator is not a literal number" // *Cause: The label used for invoking the ancillary operator is not // a literal number. // *Action: Use a literal number as the label. 29910, 00000, "invalid callback operation" // *Cause: Encountered an invalid callback operation. // *Action: Ensure that all the callbacks executed from callouts are // valid in the statement context. 29911, 00000, "null scan context returned by ODCIIndexStart() routine" // *Cause: The ODCIIndexStart() routine returned a null scan context // *Action: Ensure that the ODCIIndexStart() routine returns a non-null // scan context. 29912, 00000, "event for turning off direct invocation of Contains/Score" // *Document: NO - Internal event // *Cause: // *Action: Not a user error 29913, 00000, "error in executing %s callout" // *Cause: The execution of the specified callout caused an error. // *Action: Examine the error messages take appropriate action. 29914,00000,"ODCIGETINTERFACES routine does not return required stream version" // *Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine // does not contain the required stream version for external tables. // *Action: Ensure that the ODCIGetInterfaces routine returns the required // stream version. 29915,00000,"cannot select FOR UPDATE from collection operand" // *Cause: Collection operands cannot be updated // *Action: Remove FOR UPDATE clause 29925, 00000, "cannot execute %s" // *Cause: The specified function does not exist or does not have an // appropriate signature. // *Action: Implement the function with the appropriate signature. 29926, 00000, "association already defined for the object" // *Cause: The object for which the association is being defined, already // has a statistics type associated with it. // *Action: Disassociate the object and then associate the object. 29927, 00000, "error in executing the ODCIStatsCollect / ODCIStatsDelete routine" // *Cause: The ODCIStatsCollect / ODCIStatsDelete function is causing an // error. // *Action: Check the ODCIStatsCollect / ODCIStatsDelete function. 29928, 00000, "duplicate default selectivity specified" // *Cause: The keyword DEFAULT SELECTIVITY can only be specified once. // *Action: Remove the duplicate keyword. 29929, 00000, "missing SCAN Keyword" // *Cause: The scan context is not specified. // *Action: Supply the SCAN keyword. 29930, 00000, "COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause" // *Cause: The COMPUTE ANCILLARY DATA option was specified without the // WITH INDEX CONTEXT clause. // *Action: Specify the WITH INDEX CONTEXT option. 29931, 00000, "specified association does not exist" // *Cause: One or more of the object(s) that have been specified to be // disassociated, do not have an association defined for them. // *Action: Verify the objects which have an association defined and issue // the disassociate command again. 29932, 00000, "the type being dropped is a statistics type" // *Cause: Some objects have defined their statistics methods in the type // being dropped. // *Action: First drop the relevant associations using the DISASSOCIATE // command and then retry the DROP command, or use the FORCE option // with DROP TYPE command. 29933, 00000, "object being disassociated has some user defined statistics stored" // *Cause: There are some user defined statistics collected for the object // being disassociated. // *Action: First delete the user defined statistics and then reissue the // DISASSOCIATE command or specify the FORCE option with DISASSOCIATE. 29934, 00000, "index specified for association is not a domain index" // *Cause: The user issued an ASSOCIATE STATISTICS command with an index // which is not a domain index. // *Action: Issue an ASSOCIATE STATISTICS WITH INDEXES command on a domain // index only 29935,00000, "missing FROM keyword" // *Cause: The keyword FROM is missing. // *Action: Specify the FROM keyword or check the SQL statement. 29936, 00000, "NULL association is allowed only with a column or an index" // *Cause: User tried to use the ASSOCIATE command with a schema object // other than a column or an index // *Action: Specify the NULL clause only with a column or an index 29950, 00000, "warning in the execution of ODCIINDEXMERGEPARTITION routine" // *Cause: A warning was returned from the ODCIIndexMergePartition routine. // *Action: Check to see if the routine has been coded correctly // Check user specified log tables for greater detail. 29951, 00000, "warning in the execution of ODCIINDEXSPLITPARTITION routine" // *Cause: A warning was returned from the ODCIIndexSplitPartition routine. // *Action: Check to see if the routine has been coded correctly // Check user specified log tables for greater detail. 29952, 00000, "cannot issue DDL on a domain index partition marked as LOADING" // *Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition // in a LOADING state. // *Action: Wait till the index partition operation completes // OR issue a DROP INDEX FORCE to drop the index // OR issue a ALTER TABLE DROP PARTITION to drop the partition. 29953, 00000, "cannot issue DDL on a domain index partition marked as FAILED" // *Cause: Tried to issue a DROP/ALTER on a domain index partition in a // FAILED state. // *Action: do ALTER INDEX REBUILD PARTITION to rebuild the index partition // OR ALTER TABLE TRUNCATE PARTITION to mark the index partition // as valid. 29954, 00000, "domain index partition is marked LOADING/FAILED/UNUSABLE" // *Cause: An attempt has been made to access a domain index that is // being built or is marked failed by an unsuccessful DDL // or is marked unusable by a DDL operation. // *Action: Wait if the specified index partition is marked LOADING // Rebuild the specified index partition if it is marked FAILED // or UNUSABLE. 29955, 00000, "error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine" // *Cause: Failed to successfully execute the ODCIIndexExchangePartition routine. // *Action: Check to see if the routine has been coded correctly. 29956, 00000, "warning in the execution of ODCIINDEXEXCHANGEPARTITION routine" // *Cause: A warning was returned from the ODCIIndexExchangePartition routine. // *Action: Check to see if the routine has been coded correctly // Check user specified log tables for greater detail. 29957, 00000, "cannot create a function-based domain index on a %s table" // *Cause: User specified an unsupported create function-based domain index // statement. // *Action: Issue the create function-based domain index statement only on // supported types of tables. 29958, 00000, "fatal error occurred in the execution of ODCIINDEXCREATE routine" // *Cause: Failed to successfully execute the ODCIIndexCreate routine. // *Action: Check to see if the routine has been coded correctly. 29959, 00000, "error in the execution of the %s routine for one or more of the index partitions" // *Cause: An error occurred during execution of the routine for one or more of // the index partitions // *Action: Check the *_IND_PARTITIONS view to see which partitions are marked // FAILED. // Rebuild or Truncate the FAILED index partitions 29960, 00000, "line %s, %s" // *Cause: The ODCIIndex DDL routine has put a warning message into // table SYS.ODCI_WARNINGS$ // *Action: Check the warning message 29961, 00000, "too many warnings occurred in the execution of ODCIIndex DDL routine" // *Cause: The number of warnings during the ODCIIndex DDL routine is // too high. // *Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages / / 30000 - 30010 Reserved 8.1 miscellaneous features / 30000, 00000, "missing either trim specification or char expression in TRIM" // *Cause: Since FROM is specified in TRIM function, either trim specification // (TRAILING, HEADING, BOTH) or trim character or both must be // specified. // *Action: Add either trim specification (TRAILING, HEADING, BOTH) or // trim character or both. / 30001, 00000, "trim set should have only one character" // *Cause: Trim set contains more or less than 1 character. This is not // allowed in TRIM function. // // *Action: Change trim set to have only 1 character. / 30002, 00000, "SYS_CONNECT_BY_PATH function is not allowed here" // *Cause: SYS_CONNECT_BY_PATH function is called at places other than // select list. // // *Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than // select list. / 30003, 00000, "illegal parameter in SYS_CONNECT_BY_PATH function" // *Cause: // *Action: use a non-empty constant string as the second argument, // then retry the operation. / 30004, 00000, "when using SYS_CONNECT_BY_PATH function, cannot have seperator as part of column value" // *Cause: // *Action: Use another seperator which does not occur in any column value, // then retry. / 30005, 00000, "missing or invalid WAIT interval" // *Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword. // *Action: Correct the syntax and retry. / 30006, 00000, "resource busy; acquire with WAIT timeout expired" // *Cause: The requested resource is busy. // *Action: Retry the operation later. / / Error numbers 30011-30069 reserved for Automatic Undo Management Errors / 30011, 00000, "Error simulated: psite=%s, ptype=%s" // *Cause: error generated for testing purposes. // *Action: None. 30012, 00000, "undo tablespace '%s' does not exist or of wrong type" // *Cause: the specified undo tablespace does not exist or of the // wrong type. // *Action: Correct the tablespace name and reissue the statement. 30013, 00000, "undo tablespace '%s' is currently in use" // *Cause: the specified undo tablespace is currently used by another // instance. // *Action: Wait for the undo tablespace to become available or // change to another name and reissue the statement. 30014, 00000, "operation only supported in Automatic Undo Management mode" // *Cause: the operation is only supported in automatic undo mode. // *Action: restart instance in Automatic Undo Management mode before // retrying operation. 30015, 00000, "previously offlined undo tablespace '%s' is still pending" // *Cause: the current operation is not allowed because an undo // tablespace containing active transactions is pending // from a previous SWITCH UNDO operation. The operation // will be allowed again after all transactions in the // previous undo tablespace are committed. // *Action: Wait for all previous transactions to commit before // reissuing the current statement. 30016, 00000, "undo tablespace '%s' is already in use by this instance" // *Cause: the specified undo tablespace is currently used by this // instance. The operation failed. // *Action: If the specified undo tablespace name is wrong, reissue // the statement with the correct name. 30017, 00000, "segment '%s' is not supported in %s Undo Management mode" // *Cause: the type of the specified undo segment is incompatible with // the current undo management mode of the instance. // *Action: Check the undo segment name and the undo management mode // and reissue statement if necessary. 30018, 00000, "Create Rollback Segment failed, USN %s is out of range" // *Cause: the system runs out of undo segment number. Too many undo // segments exist. // *Action: drop some of the unused undo segments and retry operation. 30019, 00000, "Illegal rollback Segment operation in Automatic Undo mode" // *Cause: This operation only allowed in Manual Undo mode. // *Action: restart instance in Manual Undo_Management mode and retry // operation. 30020, 00000, "UNDO_MANAGEMENT=AUTO needs Compatibility %s or greater" // *Cause: Auto undo management mode not allowed in specified compatibility release // *Action: restart instance in correct compatibility release 30021, 00000, "Operation not allowed on undo tablespace" // *Cause: This operation is not allowed on undo tablespaces // *Action: Check the tablespace name and reissue command if necessary 30022, 00000, "Cannot create segments in undo tablespace" // *Cause: Cannot create segments in undo tablespace // *Action: Check the tablespace name and reissue command 30023, 00000, "Duplicate undo tablespace specification" // *Cause: Cannot create more than one undo tablespace during database creation // *Action: Modify the command to contain only one undo tablespace 30024, 00000, "Invalid specification for CREATE UNDO TABLESPACE" // *Cause: You have specified an clause that should not used with CREATE UNDO TABLESPACE // *Action: Drop the clause from the command and reissue it. / 30025, 00000, "DROP segment '%s' (in undo tablespace) not allowed" // *Cause: Explicit DROP operation is not allowed on undo tablespace segments // *Action: Check the undo segment name and reissue statement if // necessary. 30026, 00000, "Undo tablespace '%s' has unexpired undo with %s(sec) left, Undo_Retention=%s(sec)" // *Cause: Tried to drop a tablespace that contains unexpired undo // information // *Action: lower setting of UNDO_RETENTION or wait a while before // reissue command to drop undo tablespace 30027, 00000, "Undo quota violation - failed to get %s (bytes)" // *Cause: the amount of undo assigned to the consumer group of this // session has been exceeded. // *Action: ask DBA to increase undo quota, or wait until other // transactions to commit before proceeding. 30028, 00000, "Automatic Undo Management event for NTP testing" // *Cause: test events for internal use only // *Action: none. 30029, 00000, "no active undo tablespace assigned to instance" // *Cause: the current instance does not have an active undo tablespace // assigned to execute transactions. // *Action: ask DBA to create an undo tablespace, online the undo // tablespace and then retry operation. 30030, 00000, "suppress resumable related error message" // *Cause: none // *Action: This event is to be used if the errors 30031 and 30032 // wish to be suppressed. / level 1 will suppress resumable error messages 30031, 00000, "the suspended (resumable) statement has been aborted" // *Cause: DBA or the user aborted the execution of the suspended statement // in the resumable session // *Action: none 30032, 00000, "the suspended (resumable) statement has timed out" // *Cause: A correctible error was signaled in the resumable session and // the error was not cleared within the timeout interval. // *Action: Fix the correctible error within the timeout. Default is 2 hours. // Or increase the (resumable) timeout. 30033, 00000, "Undo tablespace cannot be specified as default user tablespace" // *Cause: It is incorrect to specify undo tablespace as default user // tablespace // *Action: Check the tablespace name and reissue the command 30034, 00000, "Undo tablespace cannot be specified as temporary tablespace" // *Cause: Undo tablespace cannot be specified as default temporary // tablespace for the user // *Action: Check the tablespace name and reissue the command 30035, 00000, "Undo tablespace cannot be specified as default temporary tablespace" // *Cause: Undo tablespace cannot be specified as default temporary // tablespace for the database // *Action: Check the tablespace name and reissue the command 30036, 00000, "unable to extend segment by %s in undo tablespace '%s'" // *Cause: the specified undo tablespace has no more space available. // *Action: Add more space to the undo tablespace before retrying // the operation. An alternative is to wait until active // transactions to commit. 30037, 00000, "Cannot perform parallel DML after a prior DML on the object" // *Cause: Attempt to perform parallel DML after another DML on the same // object in the same transaction. // *Action: Use bitmap segments to perform multiple (parallel) DML // operations on the same object. Or commit before issueing the DML 30038, 00000, "Cannot perform parallel insert on non-partitioned object" // *Cause: Attempt to perform parallel insert on a non-partitioned object // after a previous DML on the object in the same transaction. // *Action: Commit before issueing the insert. 30039, 00000, "Cannot drop the undo tablespace " // *Cause: Cannot drop an undo tablespace that is in use // *Action: Switch to a different undo tablespace and then try to drop 30040, 00000, "Undo tablespace is offline" // *Cause: Cannot operate on an offlined undo tablespace // *Action: Online the undo tablespace and redo the operation 30041, 00000, "Cannot grant quota on the tablespace" // *Cause: User tried to grant quota on an undo tablespace // *Action: Check the tablespace name and reissue the command 30042, 00000, "Cannot offline the undo tablespace " // *Cause: Cannot offline an undo tablespace that is in use // *Action: Switch to a different undo tablespace and then try to offline 30043, 00000, "Invalid value '%s' specified for parameter 'Undo_Management'" // *Cause: the specified undo management mode is invalid // *Action: Correct the parameter value in the initialization file // and retry the operation. 30044, 00000, "Resumable cannot be enabled with distributed transactions" // *Cause: Either a user tried to enable resumable in a dist tx or // tried to begin a dist txn in a resumable session. // *Action: 30062, 00000, "Test support for ktulat latch recovery" // *Cause: internal use only // *Action: none. 30063, 00000, "Internal Event to Test NTP" // *Cause: none // *Action: none 30064, 00000, "Test support for two phase read only optimization" // *Cause: internal use only // *Action: none. 30065, 00000, "test support for row dependencies" // *Cause: internal use only // *Action: none. 30067, 00000, "Internal Event to turn on nested debugging info" // *Cause: none // *Action: none. 30068, 00000, "Internal Event to turn on nested" // *Cause: none // *Action: none. 30069, 00000, "Auto Undo-Management Error simulation - test site = %s" // *Cause: test events for internal use only. // *Action: none. / / 30070 - 30099 Reserved for datetime/interval feature / 30071, 00000, "conversion between datetime/interval and string fail" // *Cause: An error occurs during a conversion between datetime/interval // and string data type due to one of the following reasons: // - The buffer is too short to hold the result. // - The format string is bad. // *Action: 30072, 00000, "invalid time zone value" // *Cause: The value specified for the time zone string, which appears in // ALTER SESSION statement, environment variable ORA_SDTZ, or // a datetime factor, is not valid. // *Action: 30073, 00000, "invalid adjustment value" // *Cause: The value is none of the followings: 'ADJUST', 'NO_ADJUST', // 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value. // *Action: set it to one of the three values // 30074, 00000, "GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed" // *Cause: try to GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE. // *Action: Do not GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE. 30075, 00000, "TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint" // *Cause: User is trying to create a constraint on a time or timestamp with // or without time zone column without explicitly specifying the time zone. // *Action: Use time or timestamp with time zone literals only. 30076, 00000, "invalid extract field for extract source" // *Cause: The extract source does not contain the specified extract field. // *Action: 30077, 00000, "illegal casting between specified datetime types" // *Cause: Cannot cast between the specified datetime types. // *Action: 30078, 00000, "partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals" // *Cause: An attempt was made to use a time/timestamp expression whose format // does not explicitly have time zone on a TIME/TIMESTAMP or // TIME/TIMESTAMP WITH TIME ZONE column. // *Action: Explicitly use TIME/TIMESTAMP WITH TIME ZONE literal. // 30081, 00000, "invalid data type for datetime/interval arithmetic" // *Cause: The data types of the operands are not valid for datetime/interval // arithmetic. // *Action: 30082, 00000, "datetime/interval column to be modified must be empty to decrease fractional second or leading field precision" // *Cause: datetime/interval column with existing data is being modified to // decrease fractional second or leading field precisions. // *Action: Such columns are only allowed to increase the precisions. // 30083, 00000, "syntax error was found in interval value expression" // *Cause: A syntax error was found during parsing an interval value // value expression. // *Action: Correct the syntax. 30084, 00000, "invalid data type for datetime primary with time zone modifier" // *Cause: When a time zone modifier is specified, the data type of datetime // primary must be one of the following: TIME, TIME WITH TIME ZONE, // TIMESTAMP, TIMESTAMP WITH TIME ZONE. // *Action: 30085, 00000, "syntax error was found in overlaps predicate" // *Cause: A syntax error was found during parsing an overlaps predicate. // *Action: Correct the syntax. 30086, 00000, "interval year-month result not allowed for datetime subtraction" // *Cause: An attempt was made to specify interval year to month as the // result of datetime subtraction. // *Action: This is not allowed currently due to unclear specification // in SQL Standards for this interval type. Change the interval // type to interval day to second and resubmit statement. 30087, 00000, "Adding two datetime values is not allowed" // *Cause: An attempt was made to add two datetime values. // *Action: This addition is not allowed. // 30088, 00000, "datetime/interval precision is out of range" // *Cause: The specified datetime/interval precision was not between 0 and 9. // *Action: Use a value between 0 and 9 for datetime/interval precision. / 30089, 00000, "missing or invalid " // *Cause: A (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is // expected but not found, or a specified the // in an is more significant // than its . // *Action: // / 30100-30134 Reserved for OCIExtract Cartridge Services / 30100, 00000, "internal error [%d]" // *Cause: An internal error has occurred. // *Action: Contact Oracle Worldwide Support and report the error. / 30101, 00000, "unknown parameter name '%.*s'" // *Cause: You have misspelled the parameter name. // *Action: Spell the parameter name correctly. / 30102, 00000, "'%.*s' is not in the legal range for '%.*s'" // *Cause: The value of the parameter is not within the legal range. // *Action: Refer to the manual for the allowable values for this parameter. / 30103, 00000, "'%.*s' contains an illegal integer radix for '%.*s'" // *Cause: An illegal integer radix specification was found. // *Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications. / 30104, 00000, "'%.*s' is not a legal integer for '%.*s'" // *Cause: The value is not a valid integer. // *Action: Specify only valid integers for this parameter. / 30105, 00000, "'%.*s' is not a legal boolean for '%.*s'" // *Cause: The value is not a valid boolean. // *Action: Refer to the manual for allowable boolean values. / 30106, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30107, 00000, "parameter name abbreviation '%.*s' is not unique" // *Cause: The abbreviation given was not unique. // *Action: Use a longer abbreviation to make the parameter name unique. / 30108, 00000, "invalid positional parameter value '%.*s'" // *Cause: An invalid positional parameter value has been entered. // *Action: Remove the invalid positional parameter. / 30109, 00000, "could not open parameter file '%.*s'" // *Cause: The parameter file does not exist. // *Action: Create an appropriate parameter file. / 30110, 00000, "syntax error at '%.*s'" // *Cause: A syntax error was detected. // *Action: Change the input so that the correct syntax is used. / 30111, 00000, "no closing quote for value '%.*s'" // *Cause: A quoted string was begun but not finished. // *Action: Put a closing quote in the proper location. / 30112, 00000, "multiple values not allowed for parameter '%.*s'" // *Cause: You attempted to specify multiple values for a parameter which can // take only one value. // *Action: Do not specify more than one value for this parameter. / 30113, 00000, "error when processing file '%.*s'" // *Cause: A problem occurred when processing this file. // *Action: Examine the additional error messages and correct the problem. / 30114, 00000, "error when processing from command line" // *Cause: A problem occurred when processing the command line. // *Action: Examine the additional error messages and correct the problem. / 30115, 00000, "error when processing an environment variable" // *Cause: A problem occurred when processing an environment variable. // *Action: Examine the additional error messages and correct the problem. / 30116, 00000, "syntax error at '%.*s' following '%.*s'" // *Cause: A syntax error was detected. // *Action: Change the input so that the correct syntax is used. / 30117, 00000, "syntax error at '%.*s' at the start of input" // *Cause: A syntax error was detected. // *Action: Change the input so that the correct syntax is used. / 30118, 00000, "syntax error at '%.*s' at the end of input" // *Cause: A syntax error was detected. // *Action: Change the input so that the correct syntax is used. / 30119, 00000, "unable to obtain a valid value for '%.*s'" // *Cause: No valid value was obtained for this parameter. // *Action: Rerun the application and enter a valid value. / 30120, 00000, "'%.*s' is not a legal oracle number for '%.*s'" // *Cause: The value is not a valid oracle number. // *Action: Refer to the manual for allowable oracle number values. / 30121, 00000, "'%.*s' is not an allowable value for '%.*s'" // *Cause: The value is not a legal value for this parameter. // *Action: Refer to the manual for allowable values. / 30122, 00000, "value '%.*s' for '%.*s' must be between '%d' and '%d'" // *Cause: The value of the parameter is not within the legal range. // *Action: Specify a value that is within the legal range. / / Error numbers from 30123 to 30128 are reserved for possible LRM message / expansion. / 30129, 00000, "invalid function argument received" // *Cause: A function received an invalid argument // *Action: Check function calls, make sure correct arguments are being passed. / 30130, 00000, "invalid parameter key type received" // *Cause: A function received an invalid parameter key type // *Action: Check parameter key types in function calls / 30131, 00000, "number of keys being set exceeds allocation" // *Cause: Number of parameter keys being set exceeds allocation // *Action: Reduce the number of keys being set or increase allocation / 30132, 00000, "invalid key index supplied" // *Cause: The key index specified was not within bounds // *Action: Change key index to ensure it lies within bounds / 30133, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30134, 00000, "reserved for future use" // *Cause: None. // *Action: None. / / Error numbers from 30135 to 30149 are reserved for OCIThread Cartridge / Service. / 30135, 00000, "OCI Thread operation fails" // *Cause: An OCI Thread function call has failed. // // *Action: Check the function call to make sure that the correct parameters // are being passed and take the apropriate action. // / / OCIFile 30150-30174. / Error messages for OCIFile package. / 30150, 00000, "Invalid argument passed to OCIFile function" // *Cause: An invalid argument is passed to the OCIFile function. The most // common cause is that a NULL pointer is passed where a non-NULL // pointer is expected. // *Action: Make sure that the values passed as arguments are valid. Esp // check for NULL pointers. / 30151, 00000, "File already exists" // *Cause: Tried to open a file with OCI_FILE_EXCL flag and the file // already exists. // // *Action: OCIFile is supposed throw this exception in this case. / 30152, 00000, "File does not exist" // *Cause: The OCIFile function requires the file to exist, but it does not. // // *Action: Make sure that the file exists. / / 30153, 00000, "An invalid File Object is passed to the OCIFile function" // *Cause: An invalid File Object is passed to the OCIFile function. // // *Action: Make sure that the file object is a valid one. Create a new // file object by calling OCIFileOpen if needed. / / 30154, 00000, "The memory address given as buffer for OCIFileRead/Write is invalid" // *Cause: An invalid memory address is given as the buffer pointer for // OCIFileRead/Write. // // *Action: Make sure that the required memory is allocated and pass a // valid memory address as buffer pointer. / / 30155, 00000, "An I/O Error occured during an OCIFile function call" // *Cause: An I/O error occurred at the system level. // // *Action: This is a system error and the action will depnd on the error. / / 30156, 00000, "Out of disk space" // *Cause: The disks associated with the underlying file system are full. // // *Action: Create more disk space. / / 30157, 00000, "An invalid argument was given to operating system call" // *Cause: The OS call was called with an invalid argument. // // *Action: Check the values passed. If unsuccessful to solve the problem // contact ORACLE support. / / 30158, 00000, "The OCIFileWrite causes the file to exceed the maximum allowed size" // *Cause: There is no space to write to the file. Its size is at the // maximum limit. // // *Action: Up to the user. / / 30159, 00000, "OCIFileOpen: Cannot create the file or cannot open in the requested mode" // *Cause: The create flag was specified in OCIFileOpen such that the file // was to be created. But unable to do so. Or the file already exists // and the permissions on it doesn't allow the file to be opened in // in the requested open mode // // *Action: Check whether the user has permissions to create the specified // file or if the file exists whether the permissions on it allow // the requested open mode. / / 30160, 00000, "Unable to access the file" // *Cause: The function was unable to access the existing the file. // // *Action: Check if the user has the required permissions on the file. / / / 30161, 00000, "A system error occurred during the OCIFile function call" // *Cause: A system error occured while executing the OCIFile function. // // *Action: Depend on the error. / / 30162, 00000, "The OCIFile context is not initialzed" // *Cause: The function OCIFileInit need to be called before calling any // other OCIFile function to initialize the OCIFile context. // // *Action: Call the function OCIFileInit need to be called before calling any // other OCIFile function. / 30163, 00000, "The thread safety initialization failed" // *Cause: The call to SlgInit failed in OCIFileInit. // // *Action: Contact support / / / Error messages for the OCIFormat package: 30175-30199 / 30175, 00000, "invalid type given for an argument" // *Cause: There is an argument with an invalid type in the argument list. // *Action: Use the correct type wrapper for the argument. / 30176, 00000, "invalid format code used in the format string" // *Cause: There is an invalid format code in the format string. // *Action: Replace the invalid format code with a valid one. / 30177, 00000, "invalid flag used in a format specification" // *Cause: There is an invalid flag in a format specification. // *Action: Replace the invalid flag with a valid one. / 30178, 00000, "duplicate flag used in a format specification" // *Cause: There is a duplicate flag in a format specification. // *Action: Remove the duplicate flag. / 30179, 00000, "invalid argument index used in a format code" // *Cause: Zero or negative argument index or index not following (." // *Action: Replace the invalid argument index with a valid one. / 30180, 00000, "argument index is too large" // *Cause: An argument index exceeds actual number of arguments supplied. // *Action: Fix format string or pass additional arguments. / 30181, 00000, "integer in argument index is not immediately followed by )" // *Cause: Missing closing parenthesis in argument index. // *Action: Fix the format specification. / 30182, 00000, "invalid precision specifier" // *Cause: Period in format specification not followed by valid format. // *Action: Replace the invalid precision specifier with a valid one. / 30183, 00000, "invalid field width specifier" // *Cause: Invalid field width supplied. // *Action: Replace the invalid field width with a valid one. / 30184, 00000, "argument type not compatible with a format code" // *Cause: Bad argument type given for a format code. // *Action: Make format and arguments be compatible. / 30185, 00000, "output too large to fit in the buffer" // *Cause: The buffer is not large enough to hold the entire output string. // *Action: Fix the buffer size and length passed in. / 30186, 00000, "'\' must be followed by four hexdecimal characters or another '\'" // *Cause: In the argument of SQL function UNISTR, a '\' must be followed by // four hexdecimal characters or another '\' // *Action: Fix the string format / 30187, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30188, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30189, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30190, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30191, 00000, "missing argument list" // *Cause: No argument list supplied. // *Action: Modify the argument list to have at least OCIFormatEnd in it. / 30192, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30193, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30194, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30195, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30196, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30197, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30198, 00000, "reserved for future use" // *Cause: None. // *Action: None. / 30199, 00000, "reserved for future use" // *Cause: None. // *Action: None. / / / Error Numbers 30200 - 30299 are reserved for NLS Cartridge Services 30200, 00000, "Wrong NLS item was passed into OCINlsGetInfo()" // *Cause: The item is not supported NLS item // // *Action: Correct the item number passed to OCINlsGetInfo(). / / 30201, 00000, "Unable to load NLS data object" // *Cause: It may be caused by invalid NLS environment setting // // *Action: Check your NLS environment setting such as ORA_NLS33 / / 30202, 00000, "NULL pointer to OCIMsgh was passed to OCIMsg function" // *Cause: The NULL pointer was passed. // // *Action: Check your value of OCIMsgh pointer. / / 30203, 00000, "Cannot open mesage file" // *Cause: The message may not exist in your system. / // *Action: Check your message for the given product and facility. / / / / 30300 - 30330 reserved for transaction recovery / 30300, 00000, "unable to obtain SEG2" // *Document: NO // *Cause: // *Action: Not a user error / 30301, 00000, "cannot recover this transaction in parallel" // *Document: NO // *Cause: // *Action: Not a user error / 30302, 00000, "event to make PMON skip recovery" // *Document: NO // *Cause: // *Action: Not a user error / 30303, 00000, "Internal error" // *Document: Internal event // *Cause: // *Action: Not a user error / 30304, 00000, "Internal error" // *Document: Internal event // *Cause: // *Action: Not a user error / 30305, 00000, "Debug mode" // *Document: Internal event // *Cause: // *Action: Not a user error / 30306, 00000, "Internal error" // *Document: Internal error // *Cause: // *Action: Not a user error / 30307, 00000, "Internal error" // *Document: Internal error // *Cause: // *Action: Not a user error / 30308, 00000, "Internal error" // *Document: Internal error // *Cause: // *Action: Not a user error / 30309, 00000, "Interenal" // *Document: NO // *Cause: // *Action: Not a user error / 30310, 00000, "Interenal" // *Document: NO // *Cause: None // *Action: Not a user error / 30311, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / 30312, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / 30313, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / 30314, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / 30315, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / 30316, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / / 30317, 00000, "Internal" // *Document: NO // *Cause: None // *Action: Not a user error / / 30318, 00000, "Block Level Recovery attempted" // *Document: NO // *Cause: None // *Action: Not a user error / / Error Numbers 30331 - 30429 are reserved for Summary Management Parse / 30331, 00000, "summary does not exist" // *Cause: A non-existant summary name was specified. // // *Action: Check the spelling of the summary name. / / 30332, 00000, "container table already in use by other summary" // *Cause: Another summary is already using this table as a container table. // // *Action: Select another table or materialized view as the container table // for this summary. / / 30333, 00000, "dimension does not exist" // *Cause: The dimension named in a dimension DDL statment does not exist. // // *Action: Check the spelling of the dimension name. / / 30334, 00000, "illegal dimension level name" // *Cause: A level name in a dimension ddl statement did not conform to // SQL identifier rules. // // *Action: Use a level name that begins with a letter, consists of only // letters, digits, and underscores and contains no more than 30 // characters. / / 30335, 00000, "JOIN KEY clause references a level not in this hierarchy" // *Cause: The level name specified with the REFERENCES portion of a JOIN KEY // clause in a dimension DDL statement does not reference a level // in the hierarchy that contains the JOIN KEY clause. // // *Acction: Check the spelling of the level name. / / 30336, 00000, "no child for specified JOIN KEY" // *Cause: The level specified in the REFERENCES portion of a JOIN KEY clause // in a dimension DDL statement does not have a child level. // // *Action: Check the spelling of the level name referenced in the JOIN KEY // clause. If the referenced level is the first level in the // hierarchy, you need not and must not specify a JOIN KEY clause. / / 30337, 00000, "multiple JOIN KEY clauses specified for the same parent level" // *Cause: More than one JOIN KEY clause was specified for a given parent // level in a dimension hierarchy. // // *Action: Match up each JOIN KEY clause with the level it references in the // hierarchy. Eliminate the redundant JOIN KEY clause. / / 30338, 00000, "illegal dimension hierachy name" // *Cause: An illegal dimension hierarchy name was specified in a dimension DDL // statement. // // *Action: Make sure the name begins with a letter, contains only letters, // digits and underscore and contains no more than 30 characters. // If you qualify the name with the owner name, make sure // the owner name conforms with the requirements for an owner name // on your system. / / 30339, 00000, "illegal dimension attribute name" // *Cause: An illegal dimension attribute name was specified in a dimension DDL // statement. // // *Action: Make sure the name begins with a letter, contains only letters, // digits and underscore and contains no more than 30 characters. // If you qualify the name with the owner name, make sure // the owner name conforms with the requirements for an owner name // on your system. / / 30340, 00000, "illegal dimension name" // *Cause: An illegal dimension name was specified in a dimension DDL // statement. // // *Action: Make sure the name begins with a letter, contains only letters, // digits and underscore and contains no more than 30 characters. // If you qualify the name with the owner name, make sure // the owner name conforms with the requirements for an owner name // on your system. / / 30341, 00000, "dropped level has references" // *Cause: An attempt was made to drop a level using the default or RESTRICT // option in a dimension while references to that level remain in the // dimension. References can occur in hierarchies and attributes // within the dimension. // // *Action: First remove any referenes to the level prior to dropping it, or // specify the CASCADE option with the DROP LEVEL clause. / / 30342, 00000, "referenced level is not defined in this dimension" // *Cause: A reference to a level not defined within the dimension was found. // // *Action: Check the spelling of the level name. / / 30343, 00000, "level name is not unique within this dimension" // *Cause: Two or more levels were defined with the same name. // // *Action: Check the spelling of the level names. / / 30344, 00000, "number of child cols different from number of parent level cols" // *Cause: The number of child columns specified in a JOIN KEY clause is not // the same as the number of columns in the specified parent level. // // *Action: Check the child columns and the columns in the definition of the // referenced parent level and correct the discrepency. / / 30345, 00000, "circular dimension hierarchy" // *Cause: A circularity was found the dimension hierarchy. // // *Action: Check the hierarchy for a level name that occurs more than once. / / 30346, 00000, "hierarchy name must be unique within a dimension" // *Cause: The same name was used for more than one hierarchy in a dimension. // // *Action: Check the spelling of the hierarchy name. / / 30347, 00000, "a table name is required to qualify the column specification" // *Cause: A table name was omitted in a column specification where where // the column must be qualified by the table name. // // *Action: Qualify the column with the table name. / / 30348, 00000, "ADD and DROP cannot both be specified" // *Cause: One or more ADD clauses were found in the same ALTER DIMENSION // statement with one or more DROP clauses. // // *Action: Separate your ADD operations into one ALTER DIMENSION statement // and your DROP operations into another. / / 30349, 00000, "specified dimension hierarchy does not exist" // *Cause: A hierarchy name was encountered that is not defined within // the dimension. // // *Action: Check the spelling of the hierarchy name. / / 30350, 00000, "specified dimension attribute does not exist" // *Cause: An attribute name was encountered that is not defined within the // dimension. // // *Action: Check the attribute name spelling. / / 30351, 00000, "query rewrite does not currently support this expression" // *Cause: A complex expression was specified that is is not currently // supported by query rewrite. // // *Action: Reduce the complexity of the expression. / / 30352, 00000, "inconsistent numeric precision or string length" // *Cause: The SELECT expression was of a different numeric precision or string // length than the corresponding container column. Therefore, query // rewrite cannot guarantee results that are identical to the // results obtained with the un-rewritten query. // // *Action: Correct the precision or string length difference, specify the // WITH REDUCED PRECISION option, or disable the REWRITE option // on the materialized view. / / 30353, 00000, "expression not supported for query rewrite" // *Cause: The select clause referenced UID, USER, ROWNUM, SYSDATE, // CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable, // correlation variable, a set result,a trigger return variable, a // parallel table queue column, collection iterator, etc. // // *Action: Remove the offending expression or disable the REWRITE option on // the materialized view. / / 30354, 00000, "Query rewrite not allowed on SYS relations" // *Cause: A SYS relation was referenced in the select clause for a // materialized view with query rewrite enabled. // // *Action: Remove the reference to the SYS relation from the select clause or // disable the REWRITE option on the materialized view. / / 30355, 00000, "materialized view container does not exist" // *Cause: A DROP TABLE command was issued directly against the materialized // view container table. // // *Action: Use the DROP MATERIALIZED VIEW command to clean up the residual // meta data for the materialized view. Then use the CREATE // MATERIALIZED VIEW statement to recreate the materialized view. // Thereafter, use the DROP MATERIALIZED VIEW command rather than the // DROP TABLE command to drop a materialized view. / / 30356, 00000, "the specified refresh method is not supported in this context" // *Cause: The refresh method that was specified is not currently supported. // // *Action: Specify a different refresh method or change the context to // enable support of the chosen refresh method. / / 30357, 00000, "this PL/SQL function cannot be supported for query rewrite" // *Cause: The statement referenced a PL/SQL function that is not marked // DETERMINISTIC. // *Action: Perform one of the following actions: // - Remove the use of the PL/SQL function. // - Mark the PL/SQL function as DETERMINISTIC. // - Disable the REWRITE option on the materialized view. // The function should be marked DETERMINISTIC only if it always // returns the same result value for any given set of input argument // values, regardless of any database state or session state. // Do not mark the function as DETERMINISTIC if it has any // meaningful side-effects. / / 30358, 00000, "summary and materialized view are not in same schema" // *Cause: An internal Oracle error occured. // // *Action: Report the problem through your normal support channels. / / 30359, 00000, "Query rewrite is not supported on SYS materialized views" // *Cause: An attempt was made to enable the REWRITE option on a materialized // view in the SYS schema. // // *Action: Create the materialized view in a different schema or disable the // REWRITE option. / / 30360, 00000, "REF not supported with query rewrite" // *Cause: The statement contained a REF operator. Repeatable behavior cannot // be guaranteed with the REF operator. Therefore, query rewrite // cannot support the REF operator. // // *Action: Remove the reference to the REF operator or disable the REWRITE // option on the materialized view. / / 30361, 00000, "unrecognized string type" // *Cause: An internal Oracle error occured. // // *Action: Report the problem through your normal support channels. / / 30362, 00000, "dimension column cannot be a sequence" // *Cause: The dimension statement referenced a column that is a sequence. // // *Action: Remove the reference to the sequence. / / 30363, 00000, "columns in a dimension column list must be in the same relation" // *Cause: The dimension statement contained a column list where the columns // are not all from the same relation. // // *Action: Specify the list of columns using only columns from a single // relation. / / 30364, 00000, "this level has the same set of columns as another" // *Cause: The level definition contained the same set of columns as another // level. // // *Action: Eliminate the redundant level definition. / / 30365, 00000, "left relation in the JOIN KEY clause cannot be same as right" // *Cause: The relation of the child columns on the left side of the JOIN KEY // clause was the same as that of the parent level on the right side. // // *Action: Remove the JOIN KEY clause. It is not required or allowed when // the child and the parent are in the same relation. / / 30366, 00000, "child JOIN KEY columns not in same relation as child level" // *Cause: The relation of the child columns on the left side of the JOIN KEY // clause differed from that of that child level. // // *Action: Specify the correct child columns in the JOIN KEY clause. / / 30367, 00000, "a JOIN KEY clause is required" // *Cause: A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY // clause is required when the child level and the parent level are // not in the same relation. // // *Action: Specify a JOIN KEY clause to indicate how the relation of the // child level joins to the relation of the parent level. / / 30368, 00000, "ATTRIBUTE cannot determine column in a different relation" // *Cause: An ATTRIBUTE clause in a dimension statement specified a // determined column on the right that is in a different relation // than that of the level on the left. // // *Action: Specify attibutes only for those dimension levels that // functionally determine other columns within the same relation. / / 30369, 00000, "maximum number of columns is 32" // *Cause: A list of columns was specified using more than 32 columns. // // *Action: Specify the list using no more than 32 columns. / / 30370, 00000, "set operators are not supported in this context" // *Cause: A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was // encountered in an unsupported context, such as in a materialized // view definition. // // *Action: Re-specify the expression to avoid the use of set operators. / / 30371, 00000, "column cannot define a level in more than one dimension" // *Cause: A column was used in the definition of a level after it had // already been used to define a level in a different dimension. // // *Action: Reorganize dimension levels and hierarchies into a single // dimension such that no column is used to define levels in // different dimensions. There is no limit on the number of // levels or hierarchies you can place in a dimension. A column can // be used to define any number of levels provided all such levels // are in the same dimension and provided no two levels contain // identical sets of columns. / / 30372, 00000, "fine grain access policy conflicts with materialized view" // *Cause: A fine grain access control procedure has applied a non-null policy // to the query for the materialized view. // // *Action: In order for the materialized view to work correctly, any fine // grain access control procedure in effect for the query must // return a null policy when the materialized view is being // created or refreshed. This may be done by ensuring that the // usernames for the creator, owner, and invoker of refresh // procedures for the materialized view all receive a null policy // by the user-written fine grain access control procedures. / / 30373, 00000, "object data types are not supported in this context" // *Cause: An object data type was encountered in an unsupported // context. // // *Action: Re-specify the expression to avoid the use of objects. / / 30374, 00000, "materialized view is already fresh" // *Cause: If the materialized view is fresh, ORACLE ignores the // ALTER MATERIALIZED VIEW RELY FRESH command, and issues // this error message. // // *Action: None / 30375, 00000, "materialized view cannot be considered fresh" // *Cause: If the materialized view is invalid or unusable, it cannot be considered // fresh with the ALTER MATERIALIZED VIEW CONSIDER FRESH command. // // *Action: None / 30376, 00000, "prevent sharing of a parsed query of an explain rewrite session" // *Cause: Explain rewrite generates a shared cursor after parsing the user // query. Raising this error will prevent the cursor from being // shared. // // *Action: None 30377, 00000, "MV_CAPABILITIES_TABLE not found" // *Cause: You have used the DBMS_MVIEW.EXPLAIN_MV() API before you have // defined the MV_CAPABILITIES_TABLE. // *Action: Invoke the admin/utlxmv.sql script after connecting to the desired // schema. / 30378, 00000, "MV_CAPABILITIES_TABLE is not compatible with Oracle version" // *Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is // either missing or incompatible with the current Oracle version. // *Action: Connect to the appropriate schema, // DROP TABLE MV_CAPABILITIES_TABLE and recreate it by invoking the // admin/utlxmv.sql script prior to invoking the // DBMS_MVIEW.EXPLAIN_MV() API. / / 30379, 00000, "query txt not specified" // *Cause: You have attempted use DBMS_MVIEW.EXPLAIN_REWRITE() API using // an empty query text argument // *Action: Input a valid SQL query // / 30380, 00000, "REWRITE_TABLE does not exist" // *Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have // created the REWRITE_TABLE. // *Action: Create it using the admin/utlxrw.sql script after connecting to the // desired schema // / 30381, 00000, "REWRITE_TABLE is not compatible with Oracle version" // *Cause: One or more column definitions in the REWRITE_TABLE is // either missing or incompatible with the current Oracle version. // *Action: Connect to the appropriate schema, // DROP TABLE REWRITE_TABLE and recreate it by invoking the // admin/utlxrw.sql script prior to invoking the // DBMS_MVIEW.EXPLAIN_REWRITE() API. / / / Error Numbers 30430 - 30479 are reserved for Summary Refresh Packages. These / are raised by calling dbms_sys_error.raise_system_error. / 30430, 00000, "list does not contain any valid summaries" // *Cause: List is empty or does not contain the names of existing summaries // // *Action: Verify that the list of names passed to refresh // contains the name of at least one existing summary object / 30431, 00000, "refresh method must be ANY or INCREMENTAL or FORCE_FULL, not %s" // *Cause: An invalid refresh method was specified // // *Action: Verify that the refresh method is one of 'ANY' or 'INCREMENTAL' or 'FORCE_FULL' / 30432, 00000, "summary '%s.%s' is in INVALID state" // *Cause: The summary is in INVALID state and cannot be refreshed // // *Action: / 30433, 00000, "'%s.%s' is not a summary" // *Cause: There is no such summary, therefore it cannot be refreshed // // *Action: Verify the correct name of the summary / 30434, 00000, "refresh method must be one of FC?AN, not '%s'" // *Cause: An invalid refresh method was specified // // *Action: Verify that the refresh method is one of 'FC?AN' / 30435, 00000, "job_queue_processes must be non-zero in order to refresh summaries" // *Cause: The server must be started with parameter 'job_queue_processes' greater than zero // // *Action: Correct the value of job_queue_processes and restart the server instance / 30436, 00000, "unable to open named pipe '%s'" // *Cause: The refresh process was unable to open a named pipe to the job queue process // usually because of insufficient system resources // // *Action: This is an internal error. Notify ORACLE technical support / 30437, 00000, "all job queue processes have stopped running" // *Cause: All of the job queue processes used by refresh have stopped for some reason. // At least one job queue process must be running in order to refresh summaries. // // *Action: This is an internal error. Notify ORACLE technical support / 30438, 00000, "unable to access named pipe '%s'" // *Cause: The refresh process was unable to access a named pipe to the job queue process // after it successfully opened the pipe. This usually indicates an internal or // operating system error condition. // // *Action: This is an internal error. Notify ORACLE technical support / 30439, 00000, "refresh of '%s.%s' failed because of %s" // *Cause: The refresh job queue process encountered an error and is reporting it. The // accompanying text of the message indicates cause of the error // *Action: Varies, depending upon the reported cause. / 30440, 00000, "can't fast refresh;refresh complete or set event 30441 for partial refresh " // *Cause: Both DML and direct-load are performed against detail tables. Fast // refresh can only process direct-load inserts. // *Action:Refresh complete or set event 30441 to enable partial refresh with // only direct-load inserts / 30441, 00000, "enable partial refresh when both DML and direct load inserts occur" // *Cause: // *Action: level 1 - enable partial refresh with only direct-load inserts / 30442, 00000, "can not find the definition for filter %s " // *Cause: For the specified filterid parameter, there is no corresponding // filter definition found in the advisor repository // *Action: Use a valid filterid geneated by the create_filter function / 30443, 00000, "definition for filter %s's item %s is invalid" // *Cause: The specified filter is invalid. It contains at least one // invalid filter item. If a filter item has a string list, it // becomes illegal when the string list cannot be successfully parsed. // If the filter item contains a range definition, and the lower // bound of the range is greater than the higher bound, the item // also becomes invalid. // *Action: Remove the illegal filter with the purge_filter sub-program and // redefine a correct filter / 30444, 00000, "rewrite terminated by the sql analyzer" // *Cause: The sql analyzer terminates the rewrite process // *Action: This is an internal error. Notify ORACLE technical support / 30445, 00000, "workload queries not found" // *Cause: No workload queries in the advisor repository can satifiy the // specified filter // *Action: Redefine a new filter or load additional workload queries that can // satisfy the specified filter / 30446, 00000, "valid workload queries not found" // *Cause: None of the specified queries can be successfully parsed. The error // may come from many sources: SQL syntax error, the owner // specified by the load_workload subprograms do not match the // real user who generates the SQL statement // *Action: Only load valid SQL statements into the advisor repository. Make // sure the statements can be parsed with privilege of the owner // as specified in the owner parameter of the load_workload() // subprogram. / 30447, 00000, "internal data for run number %s is inconsistent" // *Cause: Users should not explicitly modify summary advisor's internal // tables. Such modifications may cause inconsistency in the // internal tables and result in this error. // // *Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove // the inconsistent data from summary advisor's internal tables / 30448, 00000, "internal data of the advisor repository is inconsistent" // *Cause: Users should not explicitly modify summary advisor's internal // tables. Such modifications may cause inconsistency in the // internal tables and result in this error. // // *Action: This is an internal error. Notify ORACLE technical support / 30449, 00000, "syntax error in parameter %s" // *Cause: The syntax for the specified parameter is incorrect // // *Action: Check ORACLE documentation for the correct syntax / 30450, 00000, "refresh_after_errors was TRUE; The following MVs could not be refreshed: %s" // *Cause: One or more errors occurred during a refresh of multiple summaries. // *Action: The number_of_failures parameter returns the count of how many failures // occurred. The trace logs for each refresh operation describe the // each individual failure in more detail / 30451, 00000, "internal error" // *Cause: An internal error was detected by the summary refresh subsystem, and // aborted the refresh operation // *Action: Notify ORACLE support. / 30452, 00000, "cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)" // *Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally // refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to // in refresh STDDEV(X) or VARIANCE(X) // *Action: Make sure that the required columns are part of the summary definition if incremental // refresh capability is desired. / 30453, 00000, "summary contains AVG without corresponding COUNT" // *Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column // to be included in the summary definition // *Action: Make sure that the required columns are part of the summary definition if incremental // refresh capability is desired. / 30454, 00000, "summary contains STDDEV without corresponding SUM & COUNT" // *Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns // to be included in the summary definition // *Action: Make sure that the required columns are part of the summary definition if incremental // refresh capability is desired. / 30455, 00000, "summary contains VARIANCE without corresponding SUM & COUNT" // *Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns // to be included in the summary definition // *Action: Make sure that the required columns are part of the summary definition if incremental // refresh capability is desired. / 30456, 00000, "'%s.%s' cannot be refreshed because of insufficient privilege" // *Cause: The user lacks one or more permissions that are required in order to refresh summaries. // *Action: Make sure that the user is granted all required privileges. / 30457, 00000, "'%s.%s' cannot be refreshed because of unmnanaged NOT NULL columns in container" // *Cause: The container object for the summary contains one or more unmanaged columns do not // allow nulls, and which do not specify a default valur for those columns. // *Action: Make sure that default values are specified for all NOT NULL columns that are not // part of the summary definition. / 30458, 00000, "'%s.%s' cannot be refreshed because the refresh mask is %s" // *Cause: An attempt was made to incrementally refresh a summary that is not incrementally // refreshable. // *Action: Do not attempt to incrementally refresh the summary; use full refresh instead. / 30459, 00000, "'%s.%s' cannot be refreshed because the refresh method is NONE" // *Cause: An attempt was made to refresh a summary whose refresh method is NONE // *Action: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed. // Alter the summary to change the default refresh method from NONE to some other value. / 30460, 00000, "'%s.%s' cannot be refreshed because it is marked UNUSABLE" // *Cause: An attempt was made to refresh a summary which is UNUSABLE // *Action: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh. / 30461, 00000, "'%s.%s' cannot be refreshed because it is marked DISABLED" // *Cause: An attempt was made to refresh a summary which is DISABLED // *Action: Determine why the summary is DISABLED, re-enable it, and retry the refresh. / 30462, 00000, "unsupported operator: %s" // *Cause: An attempt was made to refresh a summary containing an unsupported operator // *Action: Verify that all columns of the summary contain expressions that are refreshable. / 30463, 00000, "'%s' is not a detail table of any summary" // *Cause: The list of tables passed to refresh_dependent contains at least one // invalid table name. That table is not a detail table of any summary and // is therefore an invalid input to refresh_dependent // // *Action: Verify the correct name of all tables in the list / 30464, 00000, "no summaries exist" // *Cause: A call was made to refresh_all_mviews, but no summaries exist. // At least one summary must exist before calling refresh_all_mviews // // *Action: Create one or more summaries / 30465, 00000, "supplied run_id is not valid: %s" // *Cause: There are three possible causes: The specified run_id does not // exist; the run_id was created by another user other than the // current user; the run_id has already been used. // // *Action: Call DBMS_OLAP.CREATE_ID to create a new id / 30466, 00000, "can not find the specified workload %s" // *Cause: The specified workload_id is not valid // // *Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL / 30475, 00000, "feature not enabled: %s" // *Cause: The specified feature is not enabled. // *Action: Do not attempt to use this feature. / 30476, 00000, "PLAN_TABLE does not exist in the user's schema" // *Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" // command to estimate cardinality of the specified select-clause. // This requires a table called the PLAN_TABLE in the user's // schema. For more information refer to the SQL Reference Manual. // *Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most // systems a script utlxplan.sql will create this table. / 30477, 00000, "The input select_clause is incorrectly specified" // *Cause: The input select-clause parameter to Estimate_Summary_Size // is incorrectly specified and cannot be compiled. // *Action: Check the syntax of the select-clause. / 30478, 00000, "Specified dimension does not exist" // *Cause: the specified dimension to be verified does not exist // *Action: Check the spelling of the dimension name / 30479, 00000, "Summary Advisor error\n%s" // *Cause: An error has occurred in the Summary Advisor package // This message will be followed by a second message giving // more details about the nature of the error. // *Action: See the Summary Advisor documentation // for an explanation of the second error message. // / / / Error Numbers 30480 - 30499 are reserved for OLAP operations / 30480, 00000, "DISTINCT option not allowed with GROUP BY CUBE or ROLLUP" // *Cause: // *Action: 30481, 00000, "GROUPING function only supported with GROUP BY CUBE or ROLLUP" // *Cause: // *Action: 30482, 00000, "DISTINCT option not allowed for this function" // *Cause: // *Action: 30483, 00000, "window functions are not allowed here" // *Cause: Window functions are allowed only in the SELECT list of a query. // And, window function cannot be an argument to another window or group // function. // *Action: 30484, 00000, "missing window specification for this function" // *Cause: All window functions should be followed by window specification, // like () OVER () // *Action: 30485, 00000, "missing ORDER BY expression in the window specification" // *Cause: Either the ORDER BY expression is mandatory for this function, or // there is an aggregation group without any ORDER by expression. // *Action: 30486, 00000, "invalid window aggregation group in the window specification" // *Cause: If the window specification is specified // using RANGE option and there are multiple ORDER BY expressions, then // the aggregation group cannot contain any expression (It can only // have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). // First end point (bound) cannot be UNBOUNDED FOLLOWING and second end // point cannot be UNBOUNDED PRECEDING. If the first end point is // CURRENT ROW, then second end point can only be CURRENT ROW or // /UNBOUNDED FOLLOWING. If the first end point is FOLLOWING, // then second end point can only be /UNBOUNDED FOLLOWING. // *Action: 30487, 00000, "ORDER BY not allowed here" // *Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY // *Action: 30488, 00000, "argument should be a function of expressions in PARTITION BY" // *Cause: The argument of the window function should be a constant for // a partition. // *Action: 30489, 00000, "Cannot have more than one rollup/cube expression list" // *Cause: GROUP BY clause has more than one rollup/cube expression list. // *Action: Modify the query such that only one rollup/cube expressions // appear per sub-query. 30490, 00000, "Ambiguous expression in GROUP BY ROLLUP or CUBE list" // *Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an // expression in the ordinary GROUP BY expression list // *Action: Remove the expression from either ordinary GROUP BY expression list // or ROLLUP or CUBE expression list 30491, 00000, "missing ORDER BY clause" // *Cause: // *Action: 30492, 00000, "One of FIRST or LAST keywords is expected." // *Cause: // *Action: 30493, 00000, "The percentile value should be a number between 0 and 1." // *Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function // is specified out of range. // *Action: Specify a value from [0,1]. 30494, 00000, "The argument [%s] of WIDTH_BUCKET function is NULL or invalid." // *Cause: // *Action: 30495, 00000, "The argument should be of numeric or date/datetime type." // *Cause: // *Action: 30496, 00000, "Argument should be a constant." // *Cause: // *Action: 30497, 00000, "Argument should be a constant or a function of expressions in GROUP BY." // *Cause: // *Action: 30498, 00000, "ALL option not allowed for this function" // *Cause: // *Action: 30499, 00000, "Event to dump stats used during grouping sets transformation" // *Document: NO // *Cause: N/A // *Action: Dumps column stats used during grouping sets transformation / / / / Error Numbers 30500 - 30549 are reserved for system triggers / 30500, 00000, "database open triggers and server error triggers cannot have BEFORE type" // *Cause: An attempt was made to create a trigger that fires before // the database is open or before server errors, but these types of // triggers are not supported. // *Action: Do not attempt to create a trigger that fires before the database // is open or before server errors. / 30501, 00000, "instance shutdown triggers cannot have AFTER type" // *Cause: An attempt was made to create a trigger that fires after // an instance shutdown, but this type of trigger is not // supported. // *Action: Do not attempt to create a trigger that fires after an // instance shutdown. / 30502, 00000, "system triggers cannot have INSERT, UPDATE, or DELETE as triggering events" // *Cause: An attempt was made to create a system trigger with INSERT, // UPDATE, or DELETE triggering events, but this type of trigger // is not supported because a system trigger does not have a base // table. // *Action: Do not attempt to create a system trigger with INSERT, UPDATE, // or DELETE triggering events. / 30503, 00000, "system triggers cannot have a REFERENCING clause" // *Cause: An attempt was made to use a REFERENCING clause with a system // trigger, but this type of trigger is not supported because // a system triggers does not have a base table. // *Action: Do not use a REFERENCING clause with a system trigger. / 30504, 00000, "system triggers cannot have a FOR EACH ROW clause" // *Cause: An attempt was made to use a FOR EACH ROW clause with a system // trigger, but this type of trigger is not supported because // a system triggers does not have a base table. // *Action: Do not use a FOR EACH ROW clause with a system trigger. / 30505, 00000, "system triggers should not reference a column in a WHEN clause" // *Cause: An attempt was made to use a WHEN clause to reference a column // with a system trigger, but this type of trigger is not supported // because a system trigger does not have a base table. // *Action: Change the WHEN clause to an appropriate clause. / 30506, 00000, "system triggers cannot be based on tables or views" // *Cause: An attempt was made to base a system trigger on a table or a // view. // *Action: Make sure the type of the trigger is compatible with the base // object. / 30507, 00000, "normal triggers cannot be based on a schema or a database" // *Cause: An attempt was made to base a normal trigger on a schema or // a database, but normal triggers can be based only on tables or // views. // *Action: Make sure the type of the trigger is compatible with the base // object. / 30508, 00000, "client logon triggers cannot have BEFORE type" // *Cause: An attempt was made to create a trigger that fires before // logon. This type of trigger is not supported. // *Action: Do not attempt to create a trigger that fires before logon. / 30509, 00000, "client logoff triggers cannot have AFTER type" // *Cause: An attempt was made to create a trigger that fires after // logoff. This type of trigger is not supported. // *Action: Do not attempt to create a trigger that fires after logoff. / 30510, 00000, "system triggers cannot be defined on the schema of SYS user" // *Cause: An attempt was made to define a system trigger on the schema of // SYS user. This type of trigger is not supported currently. // *Action: Do not attempt to create a system trigger defined on the // schema of SYS user. / 30511, 00000, "invalid DDL operation in system triggers" // *Cause: An attempt was made to perform an invalid DDL operation // in a system trigger. Most DDL operations currently are not // supported in system triggers. The only currently supported DDL // operations are table operations and ALTER?COMPILE operations. // *Action: Remove invalid DDL operations in system triggers. / 30512, 00000, "cannot modify %s.%s more than once in a transaction" // *Cause: An attempt was made to modify an object more than once in a // transaction. This error is usually caused by a DDL statement that // fires a system trigger that tries to modify the same object. // It can also happen when an attempt is made to perform more than // one DDL operation on a queue table in the same transaction // without issuing a commit between operations. // *Action: Do not create system triggers that might modify an already // modified object. Also, do not specify more than one DDL // operation on a queue table in the same transaction. / 30513, 00000, "cannot create system triggers of INSTEAD OF type" // *Cause: Only BEFORE or AFTER triggers can be created on system events. // *Action: Change the trigger type to BEFORE or AFTER. / 30514, 00000, "system trigger cannot modify tablespace being made read only" // *Cause: A beofre trigger tries to modify a tablespace which is being // made READ ONLY as the part of DDL oepration // *Action: Modify the trigger to avoid modifications to the objects // in the same tablespace as the one which is being made read only, // or use autonomous transactions to commit modifications / 30515, 00000, "suspend triggers cannot have BEFORE type" // *Cause: An attempt was made to create a trigger that fires before // execution suspended. This type of trigger is not supported. // *Action: Do not attempt to create a trigger that fires before execution // suspended. / / Error Numbers 30550 - 30559 are reserved for functional indexes / 30550, 00000, "index depends on a package/function spec/body which is not valid" // *Cause: the functional indexes depends on some invalid/non-existent // package/function spec/body // *Action: verify that all the package/functions which the index depends on // exist and are valid / 30551, 00000, "The index depends on a package/type body which does not exist" // *Cause: the functional indexes depends on a package/type body which // does not exist // *Action: create the package/type body / 30552, 00000, "The package/procedure/function cannot be changed" // *Cause: The package/procedure/function is deterministic and some object // depends on it // *Action: Drop the other object which depends on the // package/function/procedure you are trying to change / 30553, 00000, "The function is not deterministic" // *Cause: The function on which the index is defined is not deterministic // *Action: Mark the function as deterministic / 30554, 00000, "function-based index %s.%s is disabled" // *Cause: An attempt was made to access a function-based index that has // been marked disabled because the function on which the index depends // has been changed. // *Action: Perform one of the following actions: // -- drop the specified index using the DROP INDEX command // -- rebuild the specified index using the ALTER INDEX REBUILD command // -- enable the specified index using the ALTER INDEX ENABLE command // -- make the specified index usable using the ALTER INDEX UNUSABLE // command / 30555, 00000, "global index partitioning key is an expression" // *Cause: An attempt was made to use an expression as a partitioning key in // an index. // *Action: Do not attempt to use an expression as index partitioning key. / 30556, 00000, "functional index is defined on the column to be modified" // *Cause : An ALTER TABLE MODIFY COLUMN was issued on a column on which // a functional index exists. // *Action: Drop the functional index before attempting to modify the column. / 30557, 00000, "function based index could not be properly maintained" // *Cause : The user updated a column on which a function based index is // present which was not successfully updated // *Action : Determine the error in updating the index and fix the problem / 30558, 00000, "internal error [%s] in function based index" // *Cause: This is an internal error. // Action: Contact Worldwide support with the exact error text. / / / Error Numbers 30560 - 30574 are reserved for additional parser errors / 30560, 00000, "SAMPLE option not allowed with index-organized tables" // *Cause: // *Action: 30561, 00000, "SAMPLE option not allowed in statement with multiple table references" // *Cause: // *Action: 30562, 00000, "SAMPLE percentage must be in the range [0.000001,100)" // *Cause: // *Action: 30563, 00000, "outer join operator (+) not allowed in select-list" // *Cause: An attempt was made to reference (+) in select-list. // *Action: Do not use the operator in select-list. 30564, 00000, "Index maintainence clause not allowed for ADD partition to RANGE partitioned tables" // *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for // ADD partition to a HASH partitioned table or ADD subpartition to a // composite partitioned table. // *Action:Remove clause and reissue operation 30565, 00000, "Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified" // *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES was specified more // than once. // *Action:Remove all but one of the INVALIDATE or UPDATE GLOBAL INDEXES // clause and reissue the statement 30566, 00000, "Index maintainence clause not allowed for this command" // *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is not allowed // for this command // *Action:Remove clause and reissue operation 30567, 00000, "name already used by an existing log group" // *Cause: The specified log group name has to be unique. // *Action: Specify a unique name for the log group. The name // cannot be the same as any other log group, constraint, or // cluster hash expression. 30568, 00000, "cannot drop log group - nonexistent log group" // *Cause: The specified in alter table drop log group // is incorrect or nonexistent. // *Action: Reenter the statement using the correct log group name. 30569, 00000, "data type of given column is not supported in a log group" // *Cause: An attempt was made to include a column with one of these // unsupported data types: LONG, VARRAY, nested table, object, // LOB, FILE, or REF in a log group. // *Action: Change the column data type or remove the log group. Then retry // the operation. / 30570, 00000, "SEGMENT SPACE MANAGEMENT option already specified" // *Cause: In CREATE TABLESPACE, the SEGMENT SPACE MANAGEMENT option was // specified more than once. // *Action: Remove all but one of the SEGMENT SPACE MANAGEMENT specifications. / 30571, 00000, "invalid SEGMENT SPACE MANAGEMENT clause" // *Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause. // *Action: Specify one of the valid options: AUTO, MANUAL. / 30572, 00000, "AUTO segment space management not valid with DICTIONARY extent management" // *Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used // with a DICTIONARY extent management clause. // *Action: Either specify LOCAL extent management or remove the AUTO // SEGMENT SPACE MANAGEMENT specification. / 30573, 00000, "AUTO segment space management not valid for this type of tablespace" // *Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used // while creating an UNDO or TEMPORARY tablespace. // *Action: Remove the AUTO SEGMENT SPACE MANAGEMENT clause. / 30574, 00000, "Cannot create rollback segment in tablespace with AUTO segment space management" // *Cause: A rollback segment is being created in a tablespace that was created // with AUTO segment space management. // *Action: Create the rollback segment in a different tablespace. / / / Error Numbers 30575 - 30624 are reserved for ConText Cartridge / 30575, 00000, "ConText Option not installed" // *Cause: Oracle executable doesn't have ConText Option linked in // *Action: get the correct version of Oracle 30576, 00000, "ConText Option dictionary loading error" // *Cause: ConText dictionary tables may be corrupted // *Action: not a user error / / / / / / Error Numbers 30625 - 30644 are reserved for Inter Language Method Services / (ILMS) / 30625, 00000, "method dispatch on NULL SELF argument is disallowed" // *Cause: A member method of a type is being invoked with a NULL SELF // argument. // *Action: Change the method invocation to pass in a valid self argument. 30626, 00000, "function/procedure parameters of remote object types are not supported" // *Cause: // *Action: / / / Error Numbers 30645 - 30664 are reserved for External tables / 30645, 00000, "reject limit out of range" // *Cause: Reject limit specifies the number of records rejected before // terminating a table scan. The range is a either a number between // 1..100000 or UNLIMITED if no limit is intended. // *Action: Change the token representing the reject limit to either a number // in the range of 0 and 100000 or the keyword UNLIMITED. / / 30646, 00000, "schema for external table type must be SYS" // *Cause: A schema other then SYS was specified for the TYPE // *Action: For this version of oracle server always use schema name SYS. / / 30647, 00000, "error retrieving access parameters for external table %s.%s" // *Cause: an error occurred when fetching the access parameters for // the specified external table. // *Action: If the access parameter is a query which returns a CLOB, // check EXTERNAL_TAB$ to make sure the query is correct. / 30648,0000, "missing LOCATION keyword" // *Cause: // *Action: / 30649,0000, "missing DIRECTORY keyword" // *Cause: DEFAULT DIRECTORY clause missing or incorrect. // *Action: Provide the DEFAULT DIRECTORY. / 30650,0000, "missing PARAMETERS keyword" // *Cause: // *Action: / 30651,0000, "missing CLOB keyword" // *Cause: // *Action: / 30652,0000, "missing LIMIT keyword" // *Cause: // *Action: / 30653,0000, "reject limit reached" // *Cause: the reject limit has been reached. // *Action: Either cleanse the data, or increase the reject limit. / 30654,0000, "missing DEFAULT keyword" // *Cause: DEFAULT DIRECTORY clause not specified or incorrect. // *Action: Provide the DEFAULT DIRECTORY. / 30655,0000, "cannot select FOR UPDATE from external organized table" // *Cause: A select for update on an external table was attempted. // *Action: Don't do it! / 30656,0000, "column type not supported on external organized table" // *Cause: Attempt to create an external organized table with a column // of type LONG, LOB, BFILE, ADT, or VARRAY. // *Action: These column types are not supported, change the DDL. / 30657,0000, "operation not supported on external organized table" // *Cause: User attempted on operation on an external table which is // not supported. // *Action: Don't do that! / 30658,0000, "attempt was made to create a temporary table with EXTERNAL organization" // *Cause: An attempt was made to create an External Organized Temporary table. // This is not supported. // *Action: Don't do that! / / / Error Numbers 30676 - 30725 are reserved for Multilanguage Debug / infrastructure (kga/kqa) / 30676, 00000, "socket read or write failed" // *Cause: A problem kept a socket from reading or writing the // expected amount of data. More specific information is not // available. // *Action: Try re-establishing a connection. You may need to restart // whatever program is at the other end of the socket that failed. // Or you may need to have some problem on your network fixed. 30677, 00000, "session is already connected to a debugger" // *Cause: An attempt to connect a session to a debugger could not proceed // because the session is already connected to some debugger. // *Action: Either use the option to force a connection or first disconnect the // session from its existing debugger. 30678, 00000, "too many open connections" // *Cause: An attempt to open a connection failed because too many // are already open by this session. The number of connections // allowed may seem to vary as some may be in use through other // components which share the same pool of allowed connections. // *Action: Retry after closing some other connection. The number of // connections supported is currently not adjustable. 30679, 00000, "JDWP-based debugging not supported in this configuration" // *Cause: An attempt to open a debugging connection failed because this // server configuration cannot support the required asynchronous // socket traffic detection. // *Action: This feature will not work under this server configuration. // Either the feature is not supported on this platform at all, // or is available only through use of a protocol=tcp dispatcher // in shared-server configurations. Please consult the // platform-specific documentation and "readme" material. 30680, 00000, "debugger connection handshake failed" // *Cause: A problem occurred when trying to establish a debugger // connection. This might indicate that the port specified as // the location of the debugger is actually being used by some // other type of application. // *Action: Correct the host or port specifications if they are incorrect, // and verify the debugger is properly waiting for a connection. 30681, 00000, "improper value for argument EXTENSIONS_CMD_SET" // *Cause: An improper parameter value was provided in a call to // dbms_debug_jdwp.connect_tcp. // *Action: Correct the indicated parameter value and try again. 30682, 00000, "improper value for argument OPTION_FLAGS" // *Cause: An improper parameter value was provided in a call to // dbms_debug_jdwp.connect_tcp. // *Action: Correct the indicated parameter value and try again. 30683, 00000, "failure establishing connection to debugger" // *Cause: An error was indicated when trying to establish a connection // to a debugger. Usually a TNS error will display along with // this message to further explain the problem, although this // TNS error will likely be hidden if you choose to trap the error. // *Action: Correct the indicated parameter value and try again. 30684, 00000, "specified role could not be enabled" // *Cause: The role specified for use by the debugger could not be enabled. // The role may not exist or may not be granted to this user, // the password specified may be incorrect, or the authenticating // routine for the role is not currently active. // *Action: Correct or remove the role or password argument in the debugger // connection request. 30685, 00000, "versions of DBMS_DEBUG_JDWP and Oracle are inconsistent" // *Cause: The installed version of the dbms_debug_jdwp package // is not the correct one for the version of the Oracle RDBMS // being used. // *Action: Install the correct version of the dbms_debug_jdwp package. 30686, 00000, "no dispatcher accepted TCP/IP connection request" // *Cause: A connection had to be routed through a local socket // rather than a dispatcher. When this occurs, shared servers // are less beneficial because the session that owns the socket // cannot relinquish the process until the socket is closed. The // most likely cause is that no dispatcher is configured for // protocol=tcp. // *Action: To improve the scalability of your configuration, please // configure a dispatcher for protocol=tcp. To route these // particular connections through a particular set of dispatchers, // you can specify presentation=kgas, but if you haven't done // so any protocol=tcp dispatcher will be used. 30687, 00000, "session terminated by debugger" // *Cause: Your program's execution has been stopped by the debugger. // This can occur because of an explicit request to do so sent // by the debugger, or because the debugger disconnected without // first telling Oracle to let your program continue to run after // the disconnection. To stop your program completely, Oracle // needs to fully terminate the process. // *Action: This is in response to a debugger request; it is not an error. // No action is necessary. 30688, 00000, "maximum program calling depth exceeded" // *Cause: Your program contains a set of calls from one thing to another // too deep to be handled. Only transitions between the different // execution engines (SQL, PL/SQL, and Java) count in reaching this // limit; calls within the same engine don't count. // *Action: Please restructure your program to not need to call so deeply. // Perhaps some recursion can be replaced with iteration. 30689, 00000, "improper value for ORA_DEBUG_JDWP" // *Cause: An improper value was used for ORA_DEBUG_JDWP when trying to // establish a connection to a debugger. The value either did not // conform to the format of ORA_DEBUG_JDWP or was too long. // *Action: Correct the value for ORA_DEBUG_JDWP and try again. 30725, 00000, "JDWP-based debugging is not yet available" // *Cause: This feature is not yet available for use. // *Action: Please wait for a future release. / / / / / Error Numbers 30726 - 30925 are reserved for OBJECT SQL / / 30726, 00000, "cannot specify referenced column list here" // *Cause: An attempt was made to specify a referenced column list // for a referential constraint involving a REF column. // *Action: Remove the referenced column list specification. 30727, 00000, "duplicate referential constraint for a REF column" // *Cause: Multiple referential constraints were specified for a single // REF column. // *Action: Remove the duplicate referential constraint and retry the // operation. 30728, 00000, "maximum number of columns exceeded" // *Cause: Adding referential constraint on a REF column requires the // the creation of an additional column. // *Action: Drop some columns and retry the operation. 30729, 00000, "maximum number of columns exceeded" // *Cause: Adding scope or referential constraint on a REF column // requires the creation of additional columns if the target // table's object identifier is primary key based. // *Action: Drop some columns and retry the operation. 30730, 00000, "referential constraint not allowed on nested table column" // *Cause: An attempt was made to define a referential constraint on a nested // table column. // *Action: Do not specify referential constraints on nested table columns. 30731, 00000, "scope constraint not allowed on nested table column when the nested table is being created" // *Cause: An attempt was made to define a scope constraint on a nested table // column when the nested table is being created. // *Action: Do not specify a scope constraint on a nested table column when // creating it. Instead, specify it using the ALTER TABLE statement. 30732, 00000, "table contains no user-visible columns" // *Cause: An attempt was made to query on a system table which has no // user-visible columns. // *Action: Do not query on a system table that has no user-visible // columns. 30733, 00000, "cannot specify rowid constraint on scoped ref column" // *Cause: An attempt was made to specify rowid constraint // on a scoped REF column. // *Action: Remove the rowid constraint and then retry the operation. 30734, 00000, "cannot specify scope constraint on ref column with rowid" // *Cause: An attempt was made to specify scope constraint // on a REF column with the rowid constraint. // *Action: Remove the scope constraint and then retry the operation. / / Error messages for Inheritance (30735 - 30765) 30735, 00000, "cannot create multiple subtables of the same type under a supertable" // *Cause: An attempt was made to create under a supertable (superview), // a subtable(subview) of the same type as another existing // subtable (subview). // *Action: Drop the existing subtable(subview) and retry the operation. 30736, 00000, "objects in a table or view hierarchy have to be in the same schema" // *Cause: An attempt was made to create a subtable(subview) under a // supertable(superview) located in another schema. // *Action: Connect as schema owner of the superobject and // retry the operation. 30737, 00000, "cannot create subtable of a type which is not a subtype of the type of the supertable" // *Cause: An attempt was made to create a subtable(subview) of a type // which is not a subtype of the type of the super object. // *Action: Change the type of the subtable to be a subtype of the // superobject's type and then retry the operation. 30738, 00000, "object \"%s\" does not exist in schema \"%s\"" // *Cause: The specified object does not exist. // *Action: Ensure that the specified object exists and retry the operation. 30739, 00000, "cannot drop a table that has subtables" // *Cause: The user tried to drop a table that has subtables defined // under it. // *Action: Drop all subtables before trying this operation. 30740, 00000, "cannot grant UNDER privilege on this object" // *Cause: The user tried to grant UNDER privilege on an object that is // not one of the following : non final object type, object table // of non final type, object view of non final type. // *Action: Ensure that the UNDER privilege is granted on a valid object. 30741, 00000, "WITH HIERARCHY OPTION can be specified only for SELECT privilege" // *Cause: The user tried to specify WITH HIERARCHY OPTION for a privilege // other than SELECT privilege. // *Action: Ensure that the HIERARCHY OPTION is specified only with the // SELECT privilege 30742, 00000, "cannot grant SELECT privilege WITH HIERARCHY OPTION on this object" // *Cause: The user tried to grant SELECT privilege WITH HIERARCHY // OPTION on an object that is not one of the following : // object table of non final type, object view of non final type. // *Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is // granted on a valid object. 30743, 00000, "\"%s\" is not an object view" // *Cause: The specified object is not an object view. // *Action: Specify an object view and retry the operation. 30744, 00000, "\"%s\" is not an object table" // *Cause: The specified object is not an object table. // *Action: Specify an object table and retry the operation. 30745, 00000, "error occured while trying to add column \"%s\" in table \"%s\"" // *Cause: The user tried to add a subtype which tried to alter the tables // dependent on the supertype. // *Action: Ensure that the table will not exceed the columnlimit on adding // this subtype. 30746, 00000, "error occured while trying to drop column \"%s\" in table \"%s\"" // *Cause: The user tried to drop a subtype with VALIDATE option which tried to // check for stored instances of the type in the stated table // *Action: Delete all instances of this subtype and then drop the type. 30747, 00000, "cannot create substitutable tables or columns of non final type %s.%s" // *Cause: The user tried to create substitutable table or column of a // non final type. This operation is not currently supported. // *Action: Change the statement to create a non substitutable table/column. 30748, 00000, "column %s already enabled to store objects of type %s.%s" // *Cause: The user is trying to enable a column to store instances of a // type for which it is already enabled. // *Action: None 30749, 00000, "column %s not enabled to store objects of type %s.%s" // *Cause: The user is trying to disable a column from storing instances of a // type for which it is already enabled. // *Action: None 30750, 00000, "cannot enable column %s to store objects of type %s.%s" // *Cause: The user is trying to enable a column to store instances of // a subtype. The error is raised due to one of the following : // *Action: Fix the cause of the error and retry the operation. 30751, 00000, "cannot disable column %s from storing objects of type %s.%s" // *Cause: The user is trying to drop a type from being stored in a // substitutable column or table. This error is raised due to one // of the following reasons : // - the column is enabled to store instances of some subtype of // the type being dropped. // - the column is enabled to store instances of only one type // *Action: Fix the cause of the error and retry the operation. 30752, 00000, "column or table %s is not substitutable" // *Cause: The user is performing an operation that is not allowed on // non substitutable column or table. // *Action: None. 30753, 00000, "column or table %s is substitutable" // *Cause: The user is performing an operation that is not allowed on // substitutable column or table. // *Action: None. 30754, 00000, "column or table %s stores objects of only one type" // *Cause: The user is trying to perform an operation that is not // allowed on object column or table that is enabled to store // instances of a single type. // *Action: None 30755, 00000, "error during expansion of view hierarchy" // *Cause: There was an error while trying to expand a view hierarchy. // This could be due to invalid subviews (or subviews with errors) // *Action: Ensure that all subviews are valid e.g. alter view ... compile // and retry the operation. 30756, 00000, "cannot create column or table of type that contains a supertype attribute" // *Cause: The user tried to create a column or table of an object type that // contains a supertype attribute. This is not supported because // it leads to infinite recursion in our current storage model. // Note that creating a column of a type implies that we // create columns corresponding to all subtype attributes as well. // *Action: Change the type definition to contain a supertype REF attribute // instead of the supertype object attribute. 30757, 00000, "cannot access type information" // *Cause: Either a subtype was created and operations performed with this // new type while the session was in progress, or // the type information was unpinned from the object cache. // *Action: Commit necessary changes, end the user session, reconnect // again and re-try the object operations. // If problem persists, contact your Oracle Support representative. / / Error messages for REF operations 30765, 00000, "cannot modify scope for an unscoped REF column" // *Cause: An attempt was made to modify the scope for an unscoped REF // column. // *Action: Use an ALTER TABLE ADD SCOPE FOR command instead. 30766, 00000, "cannot modify scope for a REF column with a REFERENCES constraint" // *Cause: An attempt was made to modify the scope for a REF column with // a REFERENCES constraint. // *Action: Drop the REFERENCES constraint, and retry the operation. 30767, 00000, "OID type mismatch" // *Cause: An attempt was made to modify the scope for a REF column to a // table whose object identifier's type is different from that // of the original scoped table. // *Action: 30768, 00000, "Cannot evaluate pipelined function" // *Cause: Pipelined functions can only be used in a TABLE expression in // the from clause. // *Action: Use a non-pipelined function instead. 30769, 00000, "event to allow creation of sub-tables" // *Document: NO // *Cause: N/A // *Action: Allows the user to create sub-tables. / 30770, 00000, "Cannot specify storage options for fixed size opaque type" // *Cause: Storage clause was specified during table creation for a fixed // size opaque type. // *Action: Do not provide storage option clause. 30771, 00000, "Cannot add more than one referential constraint on REF column \"%s\"" // *Cause: Multiple referential constraints were specified for a single // REF column. // *Action: Remove the additional referential constraints and retry the // operation. / / / Error Numbers 30926 - 30929 are reserved for SQL execution time errors / 30926, 00000, "unable to get a stable set of rows in the source tables" // *Cause: A stable set of rows could not be got because of large dml // activity or a non-deterministic where clause. // *Action: Remove any non-deterministic where clauses and reissue the dml. / 30927, 00000, "Unable to complete execution due to failure in temporary table transformation" // *Cause: In memory temporary tables we create are aged out of shared pool // before we are able to grab them again. // *Action: Reduce activities that use a lot of shared pool space or wait for a // while, then retry. / 30928, 00000, "Connect by filtering phase runs out of temp tablespace" // *Cause: It is probably caused by the fact that there is a loop in the data. // *Action: Please retry the query with the NO_FILTERING hint. If the same error // still occurs, then increase temp tablespace. / 30929, 00000, "ORDER SIBLINGS BY clause not allowed here" // *Cause: ORDER SIBLINGS BY clause is specifed in a query which doesn't // have CONNECT BY clause. // *Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause. / / / Error Numbers 31000 - 31200 are reserved for XDB (XML Database) / 31000, 00000, "unresolved reference to %s in property declaration %s" // *Cause: The type definition file contained a refers_to tag to a // nonexistent declaration, or requires a reference and has // no refers_to tag // *Action: Check the property given and make sure that the refers_to // tag refers to a valid declaration or lists the contained // properties 31001, 00000, "Invalid resource handle or path name %s" // *Cause: An invalid resource handle or path name was passed to // the XDB hierarchical resolver. // *Action: Pass a valid resouce handle or path name to the hierarchical // resolver. 31002, 00000, "Path name %s is not a container" // *Cause: XDB expected the given path name to represent a container. // *Action: Pass a path name or resource handle that represents a container. 31003, 00000, "Parent %s already contains child entry %s" // *Cause: An attempt was made to insert a duplicate child into // the XDB hierarchical resolver. // *Action: Insert a unique name into the container. 31004, 00000, "Initialization parameter db_block_size must be at least 2K" // *Cause: An attempt was made to use the XDB hierarchical resolver // with a value of db_block_size less than 2K. // *Action: Set the value of of db_block_size to at least 2K. 31005, 00000, "Path name length %s exceeds maximum length %s" // *Cause: The length of a path name passed to the XDB hierarchical // resolver exceeded the maximum length. // *Action: Choose a shorter path name. 31006, 00000, "Path name segment length %s exceeds maximum length %s" // *Cause: The length of a path name segment passed to the XDB // hierarchical resolver exceeded the maximum length of a path // name segment. // *Action: Choose a shorter path name segment. 31007, 00000, "Attempted to delete non-empty container %s/%s" // *Cause: An attempt was made to delete a non-empty container in // the XDB hierarchical resolver. // *Action: Either perform a recursive deletion, or first delete // the contents of the container. 31008, 00000, "stream error in XDB, error code [%s], stream type [%s]" // *Cause: A stream error occurred in XDB. // *Action: 31010, 00000, "Sequence number has maxed out" // *Cause: The maximum no. of elements allowed in the xob has been reached. // *Action: Currently only 1k child elements are allowed for Non // schema based xobs. 31011, 00000, "XML parsing failed" // *Cause: XML parser returned an error while trying to parse the document. // *Action: Check if the document to be parsed is valid. 31012, 00000, "Given XPATH expression not supported" // *Cause: XPATH expression passed to the function is currently unsupported. // *Action: Check the xpath expression and change it to use a // supported expression. 31013, 00000, "Invalid XPATH expression" // *Cause: XPATH expression passed to the function is invalid. // *Action: Check the xpath expression for possible syntax errors. //////////////////////////// DBMS_LDAP & OiD messages / Error Numbers 31201 to 31399 are reserved for OiD (Oracle Internet Dir) / these will be used for the DBMS_LDAP package as well as other services. 31201, 00000, "DBMS_LDAP: generic error: %s" // *Cause: There has been an error in the DBMS_LDAP package. // *Action: Please report the error number and description to Oracle Support. 31202, 00000, "DBMS_LDAP: LDAP client/server error: %s" // *Cause: There is a problem either on the LDAP server or on the client. // *Action: Please report this error to the LDAP server administrator or // your Database administrator. 31203, 00000, "DBMS_LDAP: PL/SQL - Init Failed." // *Cause: There has been an error in the DBMS_LDAP Init operation. // *Action: Please check the host name and port number, or report // the error number and description to Oracle Support. 31204, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Session." // *Cause: There has been an error in the DBMS_LDAP bind operation. // *Action: Please check the session handler that you use for binding, // or report the error number and description to Oracle Support. 31205, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Auth method." // *Cause: There has been an error in the DBMS_LDAP bind operation. // *Action: Please check the authentication credentials that you // use for binding, or report the error number and // description to Oracle Support. 31206, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP search scope." // *Cause: There has been an error in the DBMS_LDAP search operation. // *Action: Please check the search scope that you use for search, // or report the error number and description to Oracle Support. 31207, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP search time value." // *Cause: There has been an error in the DBMS_LDAP search operation. // *Action: Please check the search time value that you use for search, // or report the error number and description to Oracle Support. 31208, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Message." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP message that you use for LDAP operation, // or report the error number and description to Oracle Support. 31209, 00000, "DBMS_LDAP: PL/SQL - LDAP count_entry error." // *Cause: There has been an error in the DBMS_LDAP count_entry operation. // *Action: Please check the LDAP count_operation, or report the error // number and description to Oracle Support. 31210, 00000, "DBMS_LDAP: PL/SQL - LDAP get_dn error." // *Cause: There has been an error in the DBMS_LDAP get_dn operation. // *Action: Please check the LDAP get_dn, or report the error // number and description to Oracle Support. 31211, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP entry dn." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the entry dn that you use for LDAP operation, // or report the error number and description to Oracle Support. 31212, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod_array." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP mod_array that you use for LDAP operation, // or report the error number and description to Oracle Support. 31213, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod option." // *Cause: There has been an error in the DBMS_LDAP populate_mod_array // operation. // *Action: Please check the LDAP mod option that you use for LDAP // populate_mod_array operation, or report the error number // and description to Oracle Support. 31214, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod type." // *Cause: There has been an error in the DBMS_LDAP populate_mod_array // operation. // *Action: Please check the LDAP mod type that you use for LDAP // populate_mod_array operation, or report the error number // and description to Oracle Support. 31215, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod value." // *Cause: There has been an error in the DBMS_LDAP populate_mod_array // operation. // *Action: Please check the LDAP mod value that you use for LDAP // populate_mod_array operation, or report the error number // and description to Oracle Support. 31216, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP rdn." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP rdn value that you use for LDAP // operation, or report the error number and description to // Oracle Support. 31217, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP newparent." // *Cause: There has been an error in the DBMS_LDAP rename_s operation. // *Action: Please check the LDAP newparent value that you use for LDAP // rename_s operation, or report the error number and // description to Oracle Support. 31218, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn." // *Cause: There has been an error in the DBMS_LDAP rename_s operation. // *Action: Please check the LDAP deleteoldrdn value that you use for LDAP // rename_s operation, or report the error number and // description to Oracle Support. 31219, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP notypes." // *Cause: There has been an error in the DBMS_LDAP explode_dn or // explode_rdn operation. // *Action: Please check the LDAP notypes value that you use for LDAP // explode_dn or explode_rdn operation, or report the error // number and description to Oracle Support. 31220, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP sslwrl value that you use for LDAP // operation, or report the error number and description to // Oracle Support. 31221, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP sslpasswd value that you use for LDAP // operation, or report the error number and description to // Oracle Support. 31222, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode." // *Cause: There has been an error in the DBMS_LDAP operation. // *Action: Please check the LDAP sslauth value that you use for LDAP // operation, or report the error number and description to // Oracle Support. 31398, 00000, "DBMS_LDAP: Shared servers are not supported." // *Cause: The session executing functions from the DBMS_LDAP package // is being handled by a shared server in the Database. // *Action: Use dedicated database sessions to execute functions in the // DBMS_LDAP package. 31399, 00000, "Cannot contact LDAP server %s at port %d" // *Cause: The LDAP server specified could not be contacted. This can // happen if the server is down or inaccessible. // *Action: Contact the administrator of the LDAP server //////////////////////////// End of DBMS_LDAP & OiD messages / Error Numbers 31401 - 31599 are reserved for CDC (Change Data Capture) / These are raised by calling dbms_sys_error.raise_system_error. / 31401, 00000, "change source %s is not an existing asynchronous change source" // *Cause: The caller did not use the name of an existing asynchronous / change source. The name given does not match the name of any / existing asynchronous change source. / *Action: Check the spelling of the change source name. Choose an / existing change source. / 31402, 00000, "unrecognized parameter %s" // *Cause: Unrecognized parameter was detected. / *Action: Check for too many parameters in the call. / 31403, 00000, "change table %s already contains a column %s " // *Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column by / this name already exists in the specified table. / / *Action: Check the names and call the procedure again. / / 31404, 00000, "all input parameters are null" // *Cause: All input parameters are null. At least one property must be / altered. / / *Action: Call the procedure again, making sure that all the required / parameters have been specified. Ensure that at least one / parameter is not null. Refer to user documentation for / the correct way of calling this procedure. / 31405, 00000, "cannot make changes while change set %s is advancing" // *Cause: The change set is currently advancing. Change sources related / to an advancing change set cannot be altered. Change tables / related to the advancing change set cannot be created, altered / or dropped. Some or all the parameters of the change set cannot / be altered while the set is advancing. / / *Action: Wait until the change set has finished advancing, then reissue / the command. If altering the change set, only the advance_enable / parameter can be altered during an advance. / 31406, 00000, "change source %s is referenced by a change set" // *Cause: The operation cannot complete because this change source is / referenced by one or more change sets. / / *Action: Drop the change sets first, then re-issue the command. May have / to drop some change tables before the change sets are dropped. / / 31407, 00000, "end_date must be greater than the begin_date" // *Cause: The end data of the change set is earlier than the begin date. / The end date must always be later in time than the begin date, / so that the duration between the begin and end dates is a / positive amount of time. / / *Action: Change the begin date and/or the end date, so that the end date / is later than the begin date. / / 31408, 00000, "illegal value specified for begin_scn or end_scn" // *Cause: The begin_scn is not greater than zero. The end_scn is less than / zero. The end_scn is less than the begin_scn. / / *Action: Check the values of both begin_scn and end_scn. Correct them to / make sure that they form a legal SCN range. An end_scn value of / zero indicates an infinite scn range. / / 31409, 00000, "one or more values for input parameters are incorrect" // *Cause: One or more of the inputs to the procedure had illegal values. / / *Action: Identify the bad parameter(s) and supply correct values to the / procedure. / / 31410, 00000, "change set %s is not an asynchronous change set" // *Cause: Could not find an asynchronous change set by this name. / / *Action: Check the spelling of the change set name. Call the procedure / again, passing the correct change set name. / / 31411, 00000, "change set %s is referenced by a change table" // *Cause: The operation cannot be performed because the change set contains / one or more change tables. / / *Action: You will need to drop the change table(s) first, then repeat the / operation / / 31412, 00000, "change set %s is disabled and cannot be advanced" // *Cause: The specified change set is disabled. The change set needs to be / enabled for the operation to succeed. / / *Action: Determine why the change set is disabled and correct this / condition. Alter the change set specifying 'y' for / advance_enable then retry the operation. / / 31413, 00000, "change set %s is currently being advanced" // *Cause: An advance operation is in progress for this change set and we / only allow one at a time. / / *Action: Since the change set is currently being advanced, the best action / is to wait for it to finish advancing. Only one caller / at a time can advance the change set. Check for the cause of / long running advance operations. / 31414, 00000, "error(s) occurred during change table advance" // *Cause: One or more errors occurred during the advance operation. / / *Action: Check the log file(s) for a more detailed report of the / underlying errors. / / 31415, 00000, "change set %s does not exist" // *Cause: Specified change set does not exist or the user does not have / access to the publications in that change set. The name / specified did not match the name of any existing change set. / Certain privileges are required to access the publications / within that change set. / / / *Action: Check the name and call the procedure again, with the name of / an existing change set. Contact the publisher or database / administrator if user privileges are required to access the / publications in the change set. / / 31416, 00000, "illegal SOURCE_COLMAP value" // *Cause: Cannot specify a source_colmap value of 'y' for asynchronous / / *Action: Specify 'n' for the source_colmap option and call the procedure / again. / / 31417, 00000, "column list contains control column %s" // *Cause: Reserved column name was specified in a column list or column / type parameter. / / *Action: Control columns are selected with separate parameters. If you / did not want a control column, then change the name of the / specified column so that it does not conflict with a reserved / column name. / / 31418, 00000, "source schema %s does not exist" // *Cause: Trying to create a synchronous change table and the source schema / did not match any existing schema names in the database. / / *Action: Specify the name of an existing schema. / / 31419, 00000, "source table %s does not exist" // *Cause: When creating a synchronous change table, the underlying source / table must exist when the procedure is called. In this case, / the source table did not exist. / / *Action: Specify the name of an existing table. / / 31420, 00000, "unable to submit the purge job" // *Cause: When creating the first change table, a purge job is submitted to / the job queue. Submission of this purge job failed. / / *Action: Make sure that job queue processes are enabled and are currently / running. If this does not solve the problem, contact Oracle. / / 31421, 00000, "change table does not exist" // *Cause: Specified change table does not exist. / / *Action: Recheck the name, and call the procedure again using an existing / change table. / / 31422, 00000, "owner schema %s does not exist" // *Cause: Value specifed for the owner parameter does not contain the name / of an existing schema in the database. / / *Action: Recheck the name, and call the procedure again using an existing / schema name. / / 31423, 00000, "change table %s does not contain column %s " // *Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified / column does not exist in the change table. / / *Action: Recheck the names, and call the procedure again. / / 31424, 00000, "change table has active subscriptions" // *Cause: The change table is subscribed to, so it cannot be dropped. / / *Action: Do not drop a change table while there are active subscribers. / If this is an emergency, use the FORCE parameter. This will / forcibly drop the change table out from under all subscribers. / / 31425, 00000, "subscription handle does not exist" // *Cause: The subscription handle does not exist or does not belong to this / user. / / *Action: Call the function again, with a valid subscription handle. / / 31426, 00000, "cannot modify active subscriptions" // *Cause: The subscription handle has been activated, additional calls to / SUBSCRIBE are prohibited. / / *Action: Subscribe to all the desired tables and columns before / activating the subscription. Ensure that the correct subscription / handle was specifed. / / 31427, 00000, "source table %s already subscribed" // *Cause: The subscription represented by the subscription handle already / contains source_schema.source_table. / / *Action: Check the values of the subscription_handle, source_schema, / and source_table. Do not attempt to subscribe to the same table / more than once using the same subscription handle. / / 31428, 00000, "no publication contains all the specified columns" // *Cause: One or more of the specifed columns cannot be found in / a single publication. / / *Action: Change the subscription request to select only columns that are / in the same publication. Consult the USER_PUBLISHED_COLUMNS / view to see current publications. / / 31429, 00000, "subscription handle has not been activated" // *Cause: The called procedure requires an activated subscription. / / *Action: Check the subscription handle and correct if necessary. Call the / ACTIVATE_SUBSCRIPTION procedure for this subscription handle and / then reissue original the command. / / 31430, 00000, "change view exists" // *Cause: The change view was not dropped prior to making this call. / / *Action: Call the DROP_SUBSCRIBER_VIEW procedure and then retry the / original command. / / 31431, 00000, "all source tables must belong to the synchronous change set" // *Cause: Not all of the source tables belong to the synchronous change / set. / / *Action: Check the spelling of the source tables. Make sure that all of / the source tables belong to the synchronous change set. / / 31432, 00000, "invalid source table" // *Cause: The schema_name.source_table does not exist or does not belong to / this subscription. / / *Action: Check the spelling of the schema_name and source_table. Verify / specifed table exists in the specifed schema and is subscribed / to by the subscription handle. / 31433, 00000, "change view does not exist" // *Cause: Specifed an incorrect change view or the view is already dropped. / / *Action: Recheck the name, and specify the name of an existing change / view. / / 31434, 00000, "purge is currently running" // *Cause: Called the PURGE procedure while a purge job was currently / running. / / *Action: Wait for purge to complete before reissueing this command. / / 31435, 00000, "an error occurred during the purge operation" // *Cause: An error occurred during the purge operation / / *Action: Check the logfile for a more detailed report of the underlying / errors. / 31436, 00000, "duplicate change source %s" // *Cause: A change source by the specifed name already exists. / / *Action: Recreate the change source with a unique name. / 31437, 00000, "duplicate change set %s" // *Cause: A change set by the specified name already exists. / / *Action: Recreate the change set with a unique name. / 31438, 00000, "duplicate change table %s" // *Cause: A change table by the specified name already exists. / / *Action: Recreate the change table with a unique name. / 31439, 00000, "subscription is already active" // *Cause: The subscription is already active. / / *Action: Check name and retry. / 31440, 00000, "change set %s is empty and cannot be advanced" // *Cause: User attempted to advance a change set which does not contain / any change tables. Without change tables, a change set cannot / be advanced. / / *Action: Create change tables in the change set, then retry the advance. / / 31441, 00000, "table is not a change table" // *Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a / table that is not a CHANGE table. This can also occur when / a CHANGE table object has been orphaned. CHANGE tables can become / orphaned after a CREATE_CHANGE_TABLE failure or an incomplete / DROP_CHANGE_TABLE. / / *Action: Check spelling. If error was due to an incorrect name, then retry / the procedure using the correct name. To drop a table that is / not a CHANGE table, or an orphaned CHANGE table, use the / DROP TABLE DDL command instead. / / 31442, 00000, "operation timed out while acquiring lock on %s" // *Cause: CDC attempted to acquire a lock on the resource, but the operation / timed out. / / *Action: Retry the operation later. / 31443, 00000, "deadlock detected while acquiring lock on %s" // *Cause: CDC attempted to acquire a lock on the resource, but encountered a / deadlock. / / *Action: Contact Oracle corporation / 31444, 00000, "parameter error while acquiring lock on %s" // *Cause: CDC attempted to acquire a lock on the resource, but encountered a / problem passing parameters to the lock manager. / / *Action: Contact Oracle corporation / 31445, 00000, "invalid lock handle while acquiring lock on %s" // *Cause: CDC attempted to acquire a lock on the resource, but encountered a / invalid lock handle, which did not correspond to any existing handle. / / *Action: Contact Oracle corporation / / 31446, 00000, "this session does not own the lock handle for %s" // *Cause: CDC attempted to acquire a lock on the resource, does not own the / the lock associated with the lock. This is an internal / error. / / *Action: Contact Oracle corporation / / 31447, 0000, "cannot create change tables in the SYS schema" // *Cause: Attempted to create a change table in the SYS schema. / This is not allowed. / / *Action: Use a different existing schema and retry the command. / / 31448, 0000, "illegal value for change_source" // *Cause: The specified value is not a valid name for a Change Source. / / *Action: Specify a valid name and retry the command. / / 31449, 0000, "illegal value for set_name" // *Cause: The specified value is not a valid name for a Change Set. / / *Action: Specify a valid name and retry the command. / / 31450, 0000, "illegal value for change_table_name" // *Cause: The specified value is not a valid name for a Change Table. / / *Action: Specify a valid name and retry the command. / / 31451, 0000, "illegal value %s for capture_values, expecting: OLD, NEW, or BOTH" // *Cause: The specified value is not a valid option for a capture_values. / / *Action: Specify a valid option and retry the command. / / 31452, 0000, "illegal value %s for parameter, expecting: Y or N" // *Cause: The specified value is not Y or N. / / *Action: Specify Y or N for the parameter and retry the command. / / 31453, 0000, "illegal value %s for parameter, expecting: Y, N, or NULL" // *Cause: The specified value is not Y, N or NULL. / / *Action: Specify Y, N or NULL for the parameter and retry the command. / / 31454, 0000, "illegal value %s for operation parameter, expecting: ADD or DROP" // *Cause: The specified value is not ADD or DROP. / / *Action: Specify ADD or DROP and retry the command. / / 31455, 0000, "nothing to ALTER" // *Cause: The specified column list is NULL and all optional control / columns are 'N'. / / *Action: Specify one or more columns to ALTER. / / 31456, 0000, "error executing a procedure in the DBMS_CDC_UTILITY package" // *Cause: An internal attempt to invoke a procedure within the / DBMS_CDC_UTILITY package failed. / / *Action: Check the trace logs for more information. Ensure that the / package has been installed successfully. Try issuing a DESCRIBE / command from SQL on the package. If it fails, then try / reinstalling the package. If it succeeds then try invoking one / of the procedures from SQL. / / 31457, 0000, "maximum length of description field exceeded" // *Cause: The maximum number of characters permitted in the description / field was exceeded. / / *Action: The maximum length of the description field is 30 characters. / Ensure the length does not exceed this value and retry the / command. / / 31458, 0000, "an internal error occurred" // *Cause: This is an internal error. / / *Action: Contact Oracle Worldwide Customer Support and report the error. / / 31459, 0000, "system triggers for DBMS_CDC_PUBLISH package are not installed" // *Cause: One or more required system triggers are not installed. These / triggers are required for the proper operation of Change Data / Capture. Operations on Change tables cannot continue. / / *Action: Install or reenable the triggers, or reinstall the package. / 31460, 0000, "logfile location %s is not an existing directory" // *Cause: The directory specification for logfile location for the change / source, does not correspond with an existing directory, or the / directory was not accessible. / / *Action: 1. Create the directory if it does not exist. If the directory / does exist, change the file system permissions so the directory / can be accessed. OR 2. perform ALTER CHANGE SOURCE and change / the logfile_location to be an existing directory that contains / the logfiles / 31461, 0000, "logfile location %s contains no files that match pattern %s" // *Cause: The directory specification for logfile location for the change source, / does not contain any files whose names pattern-match the logfile_suffix. / / *Action: 1. Make sure that the logfile location contains logfiles whose names match / the logfile_suffix pattern for the change set. / OR 2. perform ALTER CHANGE SOURCE and change the logfile_suffix such that / it matches the names of existing logfiles in the directory / 31462, 0000, "internal error while accessing metadata" // *Cause: An unexpected internal error occurred while CDC was accessing its internal / Metadata. / / *Action: Contact Oracle Corporation / 31463, 0000, "logfile location %s is an empty directory" // *Cause: The directory specification for logfile location for the change source, / is an empty directory / / *Action: 1. Make sure it is the correct location of the logfiles. If it / is, make sure the directory contains logfiles. / OR 2. perform ALTER CHANGE SOURCE and change the logfile_location / to be an existing directory that contains the logfiles / / 31464, 0000, "target table for the change table no longer exists" // *Cause: User tried to drop a change table but its underlying storage table / (that contains the change data) has been dropped. / / / *Action: Contact Oracle Corporation / 31465, 0000, "cannot obtain a lock on the subscription handle" // *Cause: A timeout occurred while trying to place a lock on the / subscription handle. Another session has already aquired the / lock on the subscription handle. / / *Action: Ensure the subscription handle is correct and correct it if / necessary. If it was correct, retry the operation after the / session holding the lock has released it. / / 31466, 0000, "no publications found" // *Cause: Did not find any publications that matched the input parameters / or the user does not have the privileges to access the specified / publication. / / *Action: Check the input parameters on the call to SUBSCRIBE. Validate / that the proposed source table has been published by checking the / USER_PUBLICATIONS view for that source table. Contact the / publisher if user privileges are required to access the / publication. Retry the command with correct security or / publication information. / / 31467, 0000, "no column found in the source table" // *Cause: The OBJECT_ID flag was set to 'Y' on the call to / CREATE_CHANGE_TABLE and change table belongs to the synchronous / change set. The corresponding object column was not detected in / the source table. / / *Action: Create the change table with the OBJECT_ID flag set to 'N' or / investigate why the object column is not in the source table and / add it to the source table. / / 31470, 0000, "asynchronous change tables must contain the RSID$ column" // *Cause: If creating an asynchronous change table, the RSID was set to 'N'. / If altering an asynchronous change table with an operation parameter of / 'DROP' RSID was set to 'Y'. / / *Action: When creating asynchronous change tables, always specify 'Y' for the RSID. / parameter. When altering asynchronous change tables always specify 'N' for RSID. / / 31471, 00000, "illegal OBJECT_ID value" // *Cause: Cannot specify an object_id value of 'y' for asynchronous / change tables. / / *Action: Specify 'n' for the object_id option and call the procedure / again. / / 31472, 00000, "Importing Change Data Capture version %s.%s is too new" // *Cause: An attempt was made to Import a file that was exported by a / newer version of Oracle than the target instance. / / *Action: If possible, re-export the file using a version of export / that matches the import target. Objects can not be imported / into previous versions of Oracle that did not support them. / / 31475, 0000, "redo log catalog contains no metadata for the source table" // *Cause: While advancing a change set, an CDC attempted to query the / LogMiner dictionary system tables to obtain the columns from the source / table. The query returned no rows. / This may be because none of the redo logs contains a catalog, or it / may be an internal error. / / / *Action: First, verify that the source system contains the source table. / execute dbms_logmnr_d.build procedure to populate the redos log with / logminer dictionary information. If this has been done and the / problem persists, then contact Oracle Corporation / 31476, 0000, "a change table data column is missing from the source table" // *Cause: While advancing a change set, an CDC determined that at least / one of the data columns in a change table does not match the name of / any of the columns in the source table. The source table column list / is stored in dictionary table SYSTEM.LOGMNR_OBJ$ / / *Action: Make sure that all of the data columns of the change table / have the same names as the corresponding columns in the source table, / and that all the columns exist in the source table. / 31477, 0000, "could not detach LogMiner session during cleanup" // *Cause: Failure during detach from a LogMiner session during advance of / an asynchronous change set. This is an internal error. This exception / is raised when a previous exception occurred during the internal protocol / with LogMiner, after which Change Data Capture attempted to detach / the LogMiner session as part of recovery. The detach session also failed / *Action: Contact Oracle Corporation / 31478, 0000, "could not detach LogMiner session after change set advance" // *Cause: Failure during detach from a LogMiner session after successful advance of / an asynchronous change set. This is an internal error. This exception / is raised when an asynchronous change set has been successfully advanced / but CDC was unable to detach from the LogMiner session 31479, 0000, "could not create LogMiner session" / Failure during create of a new LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31490, 0000, "could not attach to LogMiner session" / Failure during attach to a LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31491, 0000, "could not add logfile to LogMiner session" / Failure during add logfile to a LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31492, 0000, "could not set session parameters for LogMiner session" / Failure during set parameters for a LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31493, 0000, "could not prepare session for LogMiner session" / Failure during prepare session for a LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31494, 0000, "could not activate a LogMiner session" / Failure during activation of a LogMiner session while advancing / an asynchronous change set. This is an internal error. / *Action: Contact Oracle Corporation / 31495, 0000, "error in synchronous change table on \"%s\".\"%s\"" // *Cause: There was an error originating from this synchronous change / table. One possible cause is that schema redefinition has / occurred on the source table and one or more columns in the / change table are now a different type than corresponding / source columns. Another possible cause is that there is a / problem accessing the synchronous change table. / *Action: Check further error messages in stack for more detail about / the cause. If there has been schema redefinition, drop and / recreate the synchronous change table. / / / ADD NEW CHANGE DATA CAPTURE ERROR MESSAGES ABOVE THIS LINE and add / additional tests to tqccmesg.sql / / / Error Numbers 31600 - 31699 are reserved for DataPump / These are raised by calling dbms_sys_error.raise_system_error. / 31600, 00000, "invalid input value %s for parameter %s in function %s" // *Cause: A NULL or invalid value was supplied for the parameter. // *Action: Correct the input value and try the call again. 31601, 00000, "Function %s cannot be called now that fetch has begun." // *Cause: The function was called after the first call to FETCH_xxx. // *Action: Correct the program. 31602, 00000, "parameter %s value \"%s\" in function %s inconsistent with %s" // *Cause: The parameter value is inconsistent with another value // specified by the program. It may be inconsistent with the // object type associated with the OPEN context, or it may be // of the wrong datatype (a boolean rather than a text string // or vice versa). // *Action: Correct the program 31603, 00000, "object \"%s\" of type %s not found in schema \"%s\"" // *Cause: The specified object was not found in the database. // *Action: Correct the object specification and try the call again. 31604, 00000, "invalid %s parameter \"%s\" for object type %s in function %s" // *Cause: The specified parameter value is not valid for this object type. // *Action: Correct the parameter and try the call again. 31605, 00000, "the following was returned from %s in routine %s:\nLPX-%d: %s" // *Cause: An LPX routine (XML/XSL processing) returned an internal // error number to its PL/SQL wrapper routine in facility KUX which // provides the implementation for package UTL_XML. // *Action: Look up the LPX error number and follow its corrective action. 31606, 00000, "XML context %u does not match any previously allocated context" // *Cause: A method in package UTL_XML was called with an invalid XML // context handle. All handles must have previously been allocated by // UTL_XML.XMLINIT. // *Action: Always call XMLINIT before any other methods in pkg. UTL_XML. 31607, 00000, "Function %s is inconsistent with transform." // *Cause: Either (1) FETCH_XML was called when the "DDL" transform // was specified, or (2) FETCH_DDL was called when the // "DDL" transform was omitted. // *Action: Correct the program. / //////////////////////////// Future Security Features / Error Numbers 31700 to 31900 are reserved for Future Security Features //////////////////////////// End of Future Security Features //////////////////////////// Summary Management / Error Numbers 31901 to 32000 are reserved for Summary Management //////////////////////////// End of Summary Management 31901, 00000, "the current operation was cancelled by the user" // *Cause: The user requested to cancel current operation // *Action: No action is necessary / //////////////////////////// KSP / Error numbers 32001 to 32030 are reserved for parameter operations //////////////////////////// 32001, 00000, "write to SPFILE requested but no SPFILE specified at startup" // *Cause: An alter system command or an internal self tuning mechanism // requested a write to the SPFILE but no SPFILE was used to // startup the instance // *Action: Create an SPFILE and re-start the instance using the SPFILE. / 32002, 00000, "cannot create SPFILE already being used by the instance" // *Cause: A create spfile command is trying to write to an SPFILE // that was used to startup the instance. // *Action: Specify a different SPFILE name / 32003, 00000, "%s" // *Cause: LRM error // *Action: / 32004, 00000, "obsolete and/or deprecated parameter(s) specified" // *Cause: One or more obsolete and/or parameters were specified in // the SPFILE or the PFILE on the server side. // *Action: See alert log for a list of parameters that are obsolete. // or deprecated. Remove them from the SPFILE or the server // side PFILE. / 32005, 00000, "error while parsing size specification [%s]" // *Cause: The value specified for an alter operation on a size parameter // is not valid // *Action: Correct the value and retry the operation / 32006, 00000, "%s initialization parameter has been deprecated" // *Cause: A deprecated parmeter was specified at startup // *Action: Consult Oracle documentation to find new parameters // to use instead. 32007, 00000, "internal" // *Cause: A parameter error occured. // *Action: Call Oracle support. 32008, 00000, "error while processing parameter update at instance %s" // *Cause: An error occured while processing a parameter on a remote // instance. // *Action: See accompanying error messages. 32009, 00000, "cannot reset the memory value for instance %s from instance %s" // *Cause: Memory resets of local parameters are only allowed. // *Action: Retry the query for the local instance if needed. 32010, 00000, "cannot find entry to delete in SPFILE" // *Cause: The SPFILE did not contain the sid.parameter entry. // *Action: Change the sid and/or the parameter. / / / Error Numbers 32031 - 32045 are reserved for WITH clause errors / 32031, 00000, "illegal reference of a query name in WITH clause" // *Cause: forward or recursive reference of a query name in WITH clause is not // allowed. // *Action: Correct query statement, then retry. / 32032, 00000, "free temporary object number not available" // *Cause: Too many queries using temp table transformation are currently // being run to use up all temporay object numbers. // *Action: Turn off temporary table transformation or wait, then retry / 32033, 00000, "unsupported column aliasing" // *Cause: column aliasing in WITH clause is not supported yet // *Action: specify aliasing in defintion subquery and retry / 32034, 00000, "unsupported use of WITH clause" // *Cause: Inproper use of WITH clause because one of the following two reasons: // 1. nesting of WITH clause within WITH clause not supported yet // 2. For a set query, WITH clause can't be specified for a branch. // 3. WITH clause can't sepecified within parentheses. // *Action: correct query and retry / 32035, 00000, "unreferenced query name defined in WITH clause" // *Cause: There is at least one WITH clause query name that is not // referenced in any place. // *Action: remove the unreferenced query name and retry / 32036, 00000, "unsupported case for inlining of query name in WITH clause" // *Cause: There is at least one query name which is inlined more than once // because it's definition query is too simple and references another // query name. This is currently unsupported yet. // *Action: remove such query name and retry / / / Error Numbers 32100 - 32299 are reserved for OCCI errors / 32100, 00000, "operation invalid on transient object" // *Cause: Trying to perform an operation on transient object which is // is valid only on persistent objects // *Action: Make sure object is persistent / 32101, 00000, "cannot create OCI Environment" // *Cause: An OCI Environment could not be created for OCCI // *Action: Insure that the parameters to the creatEnvironment method are valid / 32102, 00000, "invalid OCI handle" // *Cause: An invalid OCI handle is passed to an OCI call. // *Action: This is an internal OCCI Error. Please contact customer support. / 32103, 00000, "error from OCI call" // *Cause: An error code other than OCI_ERROR is returned from an OCI call. // *Action: This is an internal OCCI Error. Please contact customer support. / 32104, 00000, "cannot retrieve OCI error message" // *Cause: Error message after an OCI call could not be retrieved. // *Action: This is an internal OCCI Error. Please contact customer support. / 32105, 00000, "invalid connection passed to the migrate method" // *Cause: An invalid Connection is passed to the Session::migrate method. // *Action: Passed a valid Connection to the migrate method. / 32106, 00000, "array fetch not allowed without setBuffer on all columns" // *Cause: The setBuffer method was not called for all column postions and // the next method was called to fetch more than one row. // *Action: Call the setBuffer method for all column positions if next is to // to be called to fetch more than one row. / 32107, 00000, "internal OCI memory allocation failure" // *Cause: Memory could not be allocated from an OCI heap. // *Action: Increase the process memory size. / 32108, 00000, "max column or parameter size not specified" // *Cause: The max column or parameter size is not specified. // *Action: Specify the max size by setMaxColumnSize or setMaxParamSize. / 32109, 00000, "invalid column or parameter position" // *Cause: An invalid column or parameter position is specified. // *Action: Specify a valid column or position number. / 32110, 00000, "Connection not specified" // *Cause: A null connection was passed. // *Action: Pass a valid, non-null connection. / 32111, 00000, "The size of the vector does not match the size of the VARRAY" // *Cause: The number of elements in the vector passed to the setVector // method was not equal to the size of the VARRAY. // *Action: Pass a vector of size equal to the size of the VARRAY. / 32112,00000,"Call not applicable until an attribute has been fetched" // *Cause: wasLastAttrNull() was called before an attribute was fetched. // *Action: Fetch an attribute value before making this call. / 32113,00000, "Null object passed" // *Cause: Null object was passed. // *Action: Pass a non-null object. / 32114, 00000, "Cannot perform operation on a null LOB" // *Cause: The LOB instance on which the operation was attempted was null. // *Action: Use a valid, non-null LOB instance to perform this operation. / 32115, 00000, "LOBs do not belong to any connection" // *Cause: Neither of the LOBs being compared had associated connection // information. // *Action: Atleast one of the LOBs being compared must be associated with // a valid connection. / 32116, 00000, "Buffer size is less than amount specified" // *Cause: The buffer size specified for the LOB read or write operation // was less than the amount to be read or written. // *Action: The buffer size must be equal to or greater than than the amount // to be read from or written to the LOB. / 32117, 00000, "Source LOB is null" // *Cause: The source LOB instance on which the operation was attempted // was null. // *Action: Use a valid, non-null source LOB instance for this operation. / 32118, 00000, "Cannot perform operation on a null FILE" // *Cause: The FILE instance on which the operation was attempted was null. // *Action: Use a valid, non-null FILE instance to perform this operation. / 32119, 00000, "FILEs do not belong to any connection" // *Cause: Neither of the FILEs being compared had associated connection // information. // *Action: Atleast one of the FILEs being compared must be associated with // a valid connection. / 32120, 00000, "Buffer size is less than amount specified" // *Cause: The buffer size specified for the FILE read or write operation // was less than the amount to be read or written. // *Action: The buffer size must be equal to or greater than than the amount // to be read from or written to the FILE. / 32121, 00000, "Source FILE is null" // *Cause: The source FILE instance on which the operation was attempted // was null. // *Action: Use a valid, non-null source FILE instance for this operation. / 32122, 00000, "Statement invalidated, cannot get metadata" // *Cause: An attempt was made to get metadata for a terminated statement // *Action: None / 32123, 00000, "Attribute number is out of range" // *Cause: The attribute number passed is greater than the total number of // attributes of the described object. // *Action: Pass the attribute number within the allowable range. / 32124, 00000, "Illegal attribute passed" // *Cause: The attribute passed is not applicable for the described object. // *Action: Pass a valid attribute. / 32125, 00000, "Attribute type is not appropriate" // *Cause: The return type of the get method does not match the type of the // attribute being passed. // *Action: Call the appropriate get method. / 32126, 00000, "Cannot perform operations on a null REF" // *Cause: The REF instance on which the operation was attempted was null. // *Action: Use a valid, non-null REF instance to perform this operation. / 32127, 00000, "REFs do not belong to any connection" // *Cause: Neither of the REFs being compared had associated connection // information. // *Action: Atleast one of the REFs being compared must be associated with // a valid connection. / 32128, 00000, "setDataBuffer called after fetch has started" // *Cause: Fetch from result set has already started and the setDataBuffer // call was made. // *Action: Call the setDataBuffer method before calling the next() method. / 32129, 00000, "cannot get information about this column" // *Cause: The setDataBuffer method was called to get information about this // column. Therfore, the current method cannot be called. // *Action: Use the information from the buffers specifed in the setDataBuffer // call. / 32130, 00000, "invalid offset/index refrenced in Bytes" // *Cause: The offset/index is out of range of valid data locations in Bytes // offsets. // *Action: Insure that offsets or index is within the range of Bytes object. / 32131, 00000, "bind data type cannot be changed" // *Cause: The setXXX method is called again with a different data type than // originally specified, or the setXXX method is called for a subsequent // iteration without being called before the first iteration. // *Action: Call the setXXX method with the same data type as done before the first // iteration. If no setXXX method was called for this parameter postion // the first iteration, then make sure that a setXXX method is called before // the first addIteration method is called. / 32132, 00000, "maximum iterations cannot be changed" // *Cause: The setMaxIterations is called after a setXXX method has been called. // *Action: Call the setMaxIterations method before calling any setXXX methods. / 32133, 00000, "Cannot get stream from LOB/FILE" // *Cause: An open stream exists on the the LOB/FILE on which // the operation was attempted. // *Action: Close the stream before getting another. / 32134, 00000, "Cannot assign LOBs" // *Cause: An open stream exists on the target LOB. // *Action: Close the stream on the target LOB before assigning the LOBs. / 32135, 00000, "Cannot assign FILEs" // *Cause: An open stream exists on the target FILE. // *Action: Close the stream on the target FILE before assigning the FILEs. / 32136, 00000, "Cannot perform operation on an invalid stream" // *Cause: The LOB/FILE from which the stream was obtained had been // nullified or destroyed. // *Action: Use a valid stream. / 32137, 00000, "Cannot perform read/write operation on stream" // *Cause: The readBuffer() or the writeBuffer() method was called // on a UTF16 character set stream. // *Action: Use the readUBuffer() or the writeUBuffer() method. / 32138, 00000, "Cannot perform read/write operation on stream" // *Cause: The readUBuffer() or the writeUBuffer() method was called // on a non-UTF16 character set stream. // *Action: Use the readBuffer() or the writeBuffer() method. / 32139, 00000, "Cannot write to the stream" // *Cause: A write was performed after the last buffer was written. // *Action: Close this stream and get a new stream to perform the write. / 32140, 00000, "cannot peform this operation on stream" // *Cause: Either a read is attempted from a stream oi write mode, or // a write is attempted on a stream in read mode. // *Action: Check the status of the stream to find out the valid // operations that can be performed. / 32141, 00000, "get method does not match the type of the parameter" // *Cause: The getXXX method called on the Statement object does // not match the type of the bind parameter. // *Action: Call the getXXX method that is the same as the type of the // parameter. / 32142, 00000, "maximum number of iterations exceeded" // *Cause: The addIteration exceeds the maximum number of iterations // set by the the setMaxIterations method. // *Action: Increase the maximum number of allowed iterations. / 32143, 00000, "Environment not specified" // *Cause: A null environment was passed. // *Action: Pass a valid, non-null environment. / 32144, 00000, "Cannot perform operation on a null interval" // *Cause: The interval involved in this operation is null. // *Action: Use valid, non-null interval instance to perform this operation. / 32145, 00000, "Environment not specified" // *Cause: The interval on which the operation was attempted was null // and no environment was specified. // *Action: Specify non-null environment or perform the operation // on a non null instance. / 32146, 00000, "Cannot perform operation on a null date" // *Cause: The date involved in this operation is null. // *Action: Use valid, non-null date instance to perform this operation. / 32147, 00000, "Environment not specified" // *Cause: The date on which the operation was attempted was null // and no environment was specified. // *Action: Specify non-null environment or perform the operation // on a non null instance. / 32148, 00000, "Cannot perform operation on a null time" // *Cause: The time involved in this operation is null. // *Action: Use valid, non-null time instance to perform this operation. / 32149, 00000, "Environment not specified" // *Cause: The time on which the operation was attempted was null // and no environment was specified. // *Action: Specify non-null environment or perform the operation // on a non null instance. / 32150, 00000, "Cannot perform operation on a null timestamp" // *Cause: The timestamp involved in this operation is null. // *Action: Use valid, non-null timestamp instance to perform this operation. / 32151, 00000, "Environment not specified" // *Cause: The timestamp on which the operation was attempted was null // and no environment was specified. // *Action: Specify non-null environment or perform the operation // on a non null instance. / 32152, 00000, "Cannot perform operation on a null number" // *Cause: The number involved in this operation is null. // *Action: Use valid, non-null number instance to perform this operation. / 32153, 00000, "Environment not specified" // *Cause: The number on which the operation was attempted was null // and no environment was specified. // *Action: Specify non-null environment or perform the operation // on a non null instance. / 32154, 00000, "Anydata context not specified" // *Cause: A null anydata context was passed. // *Action: Pass a valid, non-null anydata context. / 32155, 00000, "Anydata not specified" // *Cause: A null anydata was passed. // *Action: Pass a valid, non-null anydata. / 32156, 00000, "Cannot perform operation on stream" // *Cause: This operation is not applicable to streams obtained from LOBs. // *Action: / 32157, 00000, "Infinity not supported" // *Cause: // *Action: / 32158, 00000, "Invalid type passed" // *Cause: An inapplicable type was passed to this call. // *Action: Pass an applicable type. / 32159, 00000, "Cannot set prefetch options for a null Type" // *Cause: A null Type name was passed. // *Action: Pass an non-null Type name. / 32160, 00000, "Argument out of range" // *Cause: Zero or negative value was passed. // *Action: Pass a positive value. / 32161, 00000, "Cannot perform piecewise fetch" // *Cause: Zero amount was passed and buffer size was less than LOB size // *Action: Specify a larger buffer or use Stream / 32162, 00000, "Read/Write SQL method not registered" // *Cause: readSQL/writeSQL method was NULL or was not registered // *Action: Register readSQL/writeSQL by calling put method in Map / / / Error Numbers 32300 - 32399 are reserved for Materialized view errors / 32300, 00000, "cannot drop a secondary materialized view \"%s\".\"%s\"" // *Cause: An attempt was made to drop a materialized view of a // nested table column's storage table. // *Action: Drop the materialized view that contains the nested // table column. This will implicitly drop all secondary // materialized views. / 32301, 00000, "object-relational materialized views must be primary key based" // *Cause: An attempt was made to create an object-relational // materialized view that is not primary key based. // *Action: Create the materialized view with the PRIMARY KEY keyword. / 32302, 00000, "object materialized views must be object ID based" // *Cause: An attempt was made to create an object materialized view // that is not object ID based. // *Action: Create the materialized view using the OF clause but omit // any ROWID or PRIMARY KEY clauses. / 32303, 00000, "mviews with user-defined types cannot reference multiple master sites" // *Cause: For materialized views with user-defined types, // the definition query cannot reference tables from different // master sites. // *Action: Do not create materialized views with user-defined types // referencing multiple master sites. / 32304, 00000, "materialized views with user-defined types cannot use prebuilt table" // *Cause: An attempt was made to create a materialized view with the // ON PREBUILT TABLE option. // *Action: Do not create the materialized view with the // ON PREBUILT TABLE option. / 32305, 00000, "RepAPI materialized views with user-defined types are not supported" // *Cause: An attempt was made to create a RepAPI materialized view // with user-defined types. // *Action: Do not create a RepAPI materialized view with user-defined types. / 32306, 00000, "updatable materialized views with user-defined types must use SELECT *" // *Cause: An attempt was made to create an updatable materialized // view with user-defined types where the definition query // did not use SELECT * at the topmost level. // *Action: Rewrite the definition query so that SELECT * is used // at the topmost level. / 32307, 00000, "must use FROM ONLY clause when referencing an object table" // *Cause: An attempt was made to create a materialized view whose // definition query references object tables without the // FROM ONLY clause. // *Action: Rewrite the definition query to use the FROM ONLY clause // for all the object tables in the query. / 32308, 00000, "object materialized views must use SELECT *" // *Cause: An attempt was made to create an object materialized view // where the definition query did not use SELECT * // at the topmost level. // *Action: Rewrite the definition query so that SELECT * is used // at the topmost level. / 32309, 00000, "object mview type \"%s\".\"%s\" does not match the master table type" // *Cause: An attempt was made to create an object materialized view // whose type does not match the type of the master object table. // *Action: Redefine the type so that it matches the type of the // master object table. / 32310, 00000, "object materialized views must select from an object table" // *Cause: An attempt was made to create an object materialized view whose // definition query did not select from an object table. // *Action: Rewrite the definition query to select from an object table. / 32311, 00000, "materialized view definition query selects an unsupported user-defined type" // *Cause: An attempt was made in the definition query to select an // embedded user-defined type, function returning a // user-defined type, or a function whose arguments are // user-defined types. // *Action: Rewrite the definition query to exclude these unsupported // user-defined types. / 32312, 00000, "cannot refresh a secondary materialized view \"%s\".\"%s\"" // *Cause: An attempt was made to refresh a materialized view of a // nested table column's storage table. // *Action: Refresh the materialized view that contains the nested // table column. This will implicitly refresh all secondary // materialized views. / 32313, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after PMOPs" // *Cause: A Partition Maintenance Operation (PMOP) has been performed on a // detail table, and the specified materialized view does not support // fast refersh after PMOPs. // *Action: Use REFRESH COMPLETE. Note: you can determine why your // materialized view does not support fast refresh after PMOPs using // the DBMS_MVIEW.EXPLAIN_MV() API. / 32314, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after deletes/updates" // *Cause: One or more deletes or updates has been performed on one or more // of the detail tables referenced by the specified materialized // view. This materialized view does not support fast refresh after // deletes or updates. // *Action: Use REFRESH COMPLETE. Note: you can determine why your // materialized view does not support fast refresh after deletes or // updates using the DBMS_MVIEW.EXPLAIN_MV() API. / 32315, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after mixed DML and Direct Load" // *Cause: One or more of the materialized view logs on the detail tables // referenced by the specified materialized view omits the sequence // number option. Such a log cannot be used to refresh a // materialized view after deletes or updates and direct path insert. // *Action: Use REFRESH COMPLETE. Note: you can use the // DBMS_MVIEW.EXPLAIN_MV() API to determine which materialized view // logs omit the sequence number option. / 32316, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after mixed DML" // *Cause: One or more of the materialized view logs on the detail tables // referenced by the specified materialized view omits the sequence // number option. Such a log cannot be used to refresh a // materialized view after deletes or updates have been performed on // multiple detail tables. // *Action: Use REFRESH COMPLETE. Note: you can use the // DBMS_MVIEW.EXPLAIN_MV() API to determine which materialized view // logs omit the sequence number option. / 32317, 00000, "cannot run a job from a job" // *Cause: An attempt was made to execute a job from within another job. // *Action: Do not submit jobs that run other jobs. / 32318, 00000, "cannot rename a materialized view" // *Cause: Renaming a materialized view or its base table is not supported. // *Action: Do not rename the base table of a materialized view. / 32319, 00000, "Cannot use direct loader log to FAST REFRESH materialized view \"%s\".\"%s\"" // *Cause: The direct loader log might have been dropped // *Action: Need to do complete refresh / 32320, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after cointainer table PMOPs" // *Cause: A Partition Maintenance Operation (PMOP) has been performed on the // materialized view, and no materialized view supports // fast refersh after container table PMOPs. // *Action: Use REFRESH COMPLETE. Note: you can determine why your // materialized view does not support fast refresh after PMOPs using // the DBMS_MVIEW.EXPLAIN_MV() API. / 32321, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after detail table TRUNCATE" // *Cause: A detail table has been truncated and no materialized view // supports fast refersh after a detail table has been truncated // *Action: Use REFRESH COMPLETE. Note: you can determine why your // materialized view does not support fast refresh after TRUNCATE using // the DBMS_MVIEW.EXPLAIN_MV() API. / 32330, 00000, "invalid operation on online redefinition interim table \"%s\".\"%s\"" // *Cause: An invalid operation was performed on an interim table which // was being used for online redefinition of a table. // *Action: Do not perform any unsupported operation on the interim table. 32331, 00000, "type \"%s\".\"%s\" is incompatible with the master site" // *Cause: A type used by the materialized view was found to be // incompatible with its coressponding type on the master site. // This could be because the type does not exist on the master site // or has been evolved to a different version from that on the // materialzied view site. // *Action: Make sure that the types used by the materialized view are the // same on both the materialized view and master sites. 32332, 00000, "cannot refresh materialized view \"%s\".\"%s\" as type evolution has occured" // *Cause: The types used by the materialized view or its master tables have // been evolved.e29250.msg@@/main/308e29250.msg@@/main/308 // *Action: Ensure that the types used by the materialized view have been // evolved to the same version at both the master and materialized // sites. Then, before refreshing the materialized view, evolve the // materialized view using ALTER MATERIALIZED VIEW. / 32333, 00000, "disable table scn update for Materialized view" // *Cause: an event is set for disabling table scn update to prevent // deadlock situation. (bug 1376209) // *Action: disable null refresh and/or base table scn update for Materialized view / 32334, 00000, "cannot create prebuilt materialized view on a table already referenced by a MV" // *Cause: the table on which the materialized view is created as prebuilt is already // referenced by a materialized view // *Action: create the materialized view on a different table / 32335, 00000, "dimension must have at least one level" // *Cause: An level-less dimension is not allowed. // *Action: Do not drop the only level of a dimension. / 32336, 00000, "cannot use USING NO INDEX to create materialized view \"%s\".\"%s\"" // *Cause: The USING NO INDEX option was specified to create an updatable // primary key based materialized view, an index-organized // materialized view or an object-id materialized view. // *Action: Do not use the USING NO INDEX option to create an updatable // primary key based materialized view, an index-organized // materialized view or an object-id materialized view. / 32337, 00000, "cannot alter materialized view with pending changes refresh on commit" // *Cause: There are some pending changes in the detail tables // *Action: Execute an on-demand refresh on the materialized view to // synchronize the data between the materialized view and the detail // tables and then issue an ALTER MATERIALIZED VIEW statement. / // Error Numbers 32400 - 32499 are reserved for Materialized view log errors / 32400, 0000, "cannot use object id columns from materialized view log on \"%s\".\"%s\"" // *Cause: The materialized view log either does not have object id columns // logged, or the timestamp associated with the object id columns is // more recent than the last refresh time. // *Action: A complete refresh is required before the next fast refresh. // Add object id columns to the materialized view log, if required. / 32401, 00000, "materialized view log on \"%s\".\"%s\" does not have new values" // *Cause: Materialized view log on the indicated table does not have new // values information. // *Action: Add new values to materialized view log using the ALTER // MATERIALIZED VIEW LOG command. / 32403, 00000, "cannot use new values from mv log on \"%s\".\"%s\"" // *Cause: The materialized view log either does not have new values // logged, or the timestamp associated with the new values columns is // more recent than the last refresh time. // *Action: Perform a complete refresh is required before the next fast // refresh. / 32404, 00000, "snapshot log uses Change Data Capture which is not enabled for this database" // *Cause: A snapshot log that utilizes Change Data Capture is being imported // to a database where Change Data Capture has not been enabled. // *Action: First enable Change Data Capture on the database then retry the // import. / //////////////////////////// DIAGNOSIBILITY / Error numbers 32500 to 32549 are reserved for diagnosibility //////////////////////////// 32500, 00000, "Dirname '%s' cannot exceed '%d' characters" // *Cause: Path name too long // *Action: Use shorter pathname than maximum specified for dirname. / 32501, 00000, "Writing SGA to file failed" // *Cause: Underlying OSDs encountered an error // *Action: Check additional information. slercerrno contains errno. / 32502, 00000, "Cannot execute command. Flash Freeze is not in effect" // *Cause: This command can only be issued after a flash freeze // *Action: Refer to instructions for flash freeze and Oracle diagnostics. / 32503, 00000, "Mapping SGA from file failed" // *Cause: Underlying OSDs encountered an error // *Action: Check additional information. slercerrno contains errno. / //////////////////////////// LITERAL REPLACEMENT / Error numbers 32550 to 32574 are reserved for literal replacement //////////////////////////// 32550, 00000, "Replacement occured despite hint to the contrary" // *Cause: This should never be signalled; it's internal. // *Action: Report to Oracle support. / //////////////////////////// PARSER / Error numbers 32575 to 32599 are reserved for additional parsing errors //////////////////////////// 32575, 00000, "Explicit column default is not supported for modifying views" // *Cause: Default keyword was used to modify views. // *Action: Use implicit default - omitting column-value pair. / 32576, 00000, "missing TYPE keyword" // *Cause: keyword TYPE is missing. // *Action: Use TYPE keyword. / / Put errors here. / 32767 - (MAX ERROR NUMBER; NONE CAN BE LARGER) /